Quick Tip: Restarting all Microsoft Exchange services
There are times when you need to restart all Exchange related services so here are 2 small scripts that will help you achieve this without going over each service in the Services mmc.
Of course restarting the "Microsoft Exchange Active Directory Topology" will restart a most of them but these 2 will restart them all.
Restarting All Running Services
This will get all services starting with MSexchange that are running and restart them.
$services = Get-Service | ? { $_.name -like "MSExchange*" -and $_.Status -eq "Running"} foreach ($service in $services) {Restart-Service $service.name -Force}
Restarting All Running Services with startup type Automatic
Although the above script should be enough in most cases, it will not restart any Microsoft Exchange related service that is supposed be running but is not for any reason. Here is another version of the script that would take care of this issue, note that we are looking for all services starting with MSExchange with startup type Automatic and restarting them
$services = get-wmiobject win32_service | ? {$_.name -like "MSExchange*" -and $_.StartMode -eq "Auto"} foreach ($service in $services) {Restart-Service $service.name -Force}
That's it for now
Quick Tip: Forcing OAB Generation
When migrating between Exchange version or when introducing a new CAS server sometimes we need to force the generation of the Offline Address Book so clients can pick it up and avoid unneeded outlook errors.
Here is how to do it in 3 quick steps
1. Update the Offline Address Book
From Exchange Management Shell (EMS) run:
Get-OfflineAddressBook | Update-OfflineAddressBook
2. Restart Microsoft Exchange System Attendant service on the Mailbox Server responsible for OAB Generation
Do NOT install Exchange 2010 SP1 on your Edge/TMG server
If you are running Exchange 2010 Edge on Forefront TMG do NOT install Exchange 2010 SP1 on it yet. Doing so will lead to crash your TMG Managed Control service with the error
The Forefront TMG Managed Control service failed to initialize. Error information: Command failed with error: The term 'Get-AntiSpamUpdates' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again
Can’t install Exchange 2010 RTM when Exchange 2007 SP3 exists
I am faced with a very funny issue at a client where I'm migrating from Lotus Domino to Exchange.
As you might know Microsoft didn't release migration tools from Lotus to Exchange 2010 directly so the path was Domino -> Exchange 2007 and then Exchange 2007 -> Exchange 2010.
Since Exchange 2007 SP3 has been released a couple of days ago I've installed it on, what I was planning to be, a temporary server.
I was surprised today that I was not able to install Exchange 2010 and setup.com /PrepareSchema failed with the following error.
Single Mailbox Recovery in Exchange 2010 – Magic
Introduction
We have seen in part 1 of this tutorial the classical approach to single mailbox recovery from backups using Exchange 2010 and how this method can only restore the mailbox content to a new structure and this could be annoying for some.
Analyzing the findings of our first approach we can deduce that the problem lies behind the fact that the new mailbox of user2 has a different GUID than the one in the backup. So, logically, changing the GUID of the new mailbox and setting it to the same as the one in backup should solve the issue right ?
Let's see how we can accomplish this to make the magic happens.
Disclaimer:This article contains steps that tell you how to use ADSIEdit.msc. However, serious problems might occur if you use it incorrectly. Therefore, make sure that you follow these steps carefully and I cannot be held responsible for any damage you might bring do to your system.
Single Mailbox Recovery in Exchange 2010 – Classic
Introduction
I have written a 2 part tutorial at simple-talk.com about Microsoft Exchange 2010 Backup and Restore in which I have covered all steps needed to successfully backup your database as well as different recovery scenarios. This article can be looked at as an extension of the recovery process, part 2, and will cover the case when a single mailbox needs to be recovered from the backup.
I would like to stress first that it is not usually needed to recover a single mailbox from a backup when running Microsoft Exchange 2010 because deleted mailbox can be found in the "Disconnected Mailboxes" under "Recipient Configuration" and can simply be reconnected. However if you are just curious to learn or you are in need to recover a single mailbox for whatever reason keep on reading.
I will assume in this article that you are already familiar with the backup and restore process and that a successful full backup of the database already exists.
