Stopping all of Exchange Server 2010 services during Service Pack / Cumulative Update installation ?


To prevent email lost or data inconsistency during the Windows Update or SP / CU installation, do I have to stop all of the Exchange Server services before I run the updates or upgrade ?

I also wondering if I should change the MS Exchange Information Store service startup mode to Delayed Start from the default Automatic on all mailbox server to allow the server to be brought online safely after the patching reboot ?

Therefore if it is yes, then I can safely take VM snapshot on the mailbox server role to easy roll back if the updates causing some issue.

Source of my inspiration:

Please correct me if I'm wrong.
Senior IT System EngineerIT ProfessionalAsked:
Who is Participating?
VB ITSConnect With a Mentor Specialist ConsultantCommented:
Hello again ITSystemEngineer.

Pretty much agree with Cliff on his points above. Only thing I want to add is that if you have Mailbox servers in a DAG setup then you'll want to use the StartDagServerMaintenance and StopDagServerMaintenance scripts that come with Exchange 2010 (SP1) to put your servers into maintenance mode to install the updates. It also reduces/prevents the loss of mail service while you make your upgrades.
See this article for more information:

With snapshots, that's definitely a big no-no. Have a read of this excerpt from the Exchange 2010 Virtualisation page:
Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it's running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots aren't application aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange. As a result, making virtual machine snapshots of an Exchange guest virtual machine isn't supported.
More reading can be done here:

As for setting the Information Store service to Delayed Start, that's only really necessary if the Exchange services don't start properly in the first place. No need to do this if you aren't seeing issues now with services not starting when your servers reboot.
Cliff GaliherConnect With a Mentor Commented:
You do not need to stop services before patching.
You should definitely not use snapshots with exchange, under any circumstances.
There is no benefit, and a few drawbacks, to changing the defaults for the information store. If delayed start was better, it'd ship that way as default.
Senior IT System EngineerIT ProfessionalAuthor Commented:
So how do I prevent email lost when rolling back the change using the snapshot ?

If the snapshot method is not allowed, then what's the other alternative for quick rollback or restore ?

Other than long painful whole VM restore from last night backup (~4 hours).
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Senior IT System EngineerIT ProfessionalAuthor Commented:
No, I do see any issue but just in case.
Because I'm about to apply 118 patches and SP3 with CU 8 to this mailbox server so I don't want to risk it to failed to boot up of taking so long to boot up.
So what's the other option ?
Cliff GaliherConnect With a Mentor Commented:
Don't install all patches at once. Do small groups. Start with a full real backup, and backup again after each batch. These are usual precautions when patching.
VB ITSConnect With a Mentor Specialist ConsultantCommented:
That's a lot of patches.. I would suggest you don't install them all at once. Backup, install a batch of updates, reboot, repeat.

EDIT: Cliff beat me to it!
Senior IT System EngineerIT ProfessionalAuthor Commented:
Yeah I know this server hasn't been rebooted with total of 775 days up time in so far.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.