To update the DAG members with new patches the process should be managed to prevent all of the DAG members from being offline at the same time.
You can move the active mailbox databases off a particular server so that it can be patched, and if necessary rebooted, without causing any downtime for mailbox users on that database.
Exchange Server 2010 Service Pack 1 introduced a new method for exporting mailboxes called Mailbox Export Requests. This new method replaces the previous Export-Mailbox command.
Before we look at how to create a new mailbox export request in Exchange 2010 SP1 there are a few things that you should understand.
Some administrators prefer to do everything manually, other automated. I have always preferred to have as much as possible automated or at least set up with a script so the action can easily be repeated without varying end results.
I have written a script which verifies that all users that should have a home folder has one, and that it has the appropriate permissions.
Security is very important, especially when it comes to IT.
We’ve created a password generating script to assist in making sure we all use high security passwords.
Lately I’ve been setting up a back-end script for one of our customers. The full script creates Domain users, generates passwords and emails the manager/CEO the user information.
This post will only contain the Email function, more functions will be posted later.
After setting up a new domain and deploying SCCM 2012 I came to realize how much work it actually is to set up new applications.
I have made a script which creates AD groups and Collections.
I’ve always liked VB scripting, but I have officially converted to Powershellism (?!).
If you’d like to convert your old VBS scripts to Powershell check this out…
The last few days I’ve been working with Powershell. The idea behind this function is to customize folders. In my case I needed to make sure that the file path does not contain spaces, yet show user friendly folder names to the end user.