Forum Discussion
Deleted
Apr 08, 2023Exchange 2016 Security updates
Hello. If I am just applying Exchange monthly security updates which we do using our software distribution product, not Windows update, do I still need to put the server in maintenance mode like I wo...
Deleted
Apr 08, 2023Deleted https://www.microsoft.com/en-us/download/details.aspx?id=105091
MS recommends to restart your server before and after update. Restarting a server without putting in into maintenance mode is not the best idea.
So first start the maintenance mode which will switch over the database copies, the restart your server, turn off antivirus software, patch it, restart again, turn on antivirus, switch off maintenance mode and finally, when you‘re in a hurry, start redistribution of the DBs.
- DeletedApr 08, 2023So what happens if a server restarts on it's own. Servers do that. A bugcheck or an exception and there's an unplanned restart. My assumption is all the DB's fail over to the mailbox server and when the rebooted server comes back up, all is good. Just seems like they make you go through a lot of trouble just to patch a server. Flushing queues, stopping the cluster service etc. Guess the question is what is so different about 2013/16 than 2010 that you have to do all this. Example, MBX1 is running a bit slow and a reboot is needed. I can't just activate DB's on MBX2 and reboot the thing? I have to put it in maintenance mode first? Seem ridiculous.
- DeletedApr 09, 2023
Deleted If it seems ridiculous to you, don’t do it. Your server, your decision.
- DeletedApr 10, 2023Still doesn't answer the question as to what happens in an unplanned reboot. They happen for a variety of reasons like power fails, a VM being accidently rebooted etc. There is no one there to put the server in maintenance mode. If you don't know, its OK because I haven't been able to find the answer either. Are we just to assume that everything will be OK. As I mentioned in my previous reply, my assumption is Active Manager will fail over the DB's, the Shadow Queue or Safety Net will take care of any messages, the Cluster Manager will maintain quorum as long as the witness server is available, and after the server comes back up, your only job is to re-distribute databases, or is it? Does anything else need to be done?