My immediate team doesn’t patch and reboot every server we have as CM clients. For the ones we are responsible for, we do rely on Maint. Windows, and allow reboot after patching (if within MW). We rely on SCOM to alert us if a server doesn’t come back correctly post-reboot.
For other teams that have CM server clients they patch, they also all rely on MW. One team does the same as we do: allow reboot during MW post-patching, and they monitor. There’s another team I know where the majority of their servers they do the same, but for 1 collection of servers they patch, but manually (well, via a remote script) trigger a reboot manually and monitor “live” that the servers come back in a timely fashion. Sherry Kissinger From: Beardsley, James Sent: Monday, November 3, 2014 2:59 PM To: [email protected] I’m looking for some guidance on how to handle server reboots after they’ve been patched. I have all of my maintenance windows configured so servers only get patched between 1am and 4am and I separate the servers in different collections so they don’t all patch on the same night but I’m extremely hesitant to allow the servers to reboot automatically when finished. Certainly others have had the same reservations at some point in time. How does everyone handle their server reboots? I’ve been patching PC’s for several years now but the server responsibility is now being transitioned over to me. The person who patched servers before me just used WSUS (no SCCM) and he set up scheduled tasks via GPO that would patch and then reboot at 5am on a Sunday morning. Then he used a script to monitor and alert him if the servers didn’t come back up or a particular service doesn’t start. I thought about going that route and do a similar script but I’m trying to avoid having to get up early on a Sunday morning J I worry that if I allow the servers to reboot on their own, if for some reason they don’t come back up (which admittedly is rare), its going to be a terrible day. Do you have some sort of monitoring mechanism in place to alert you if they don’t come back up? We’re implementing SCOM at some point over the next year but we aren’t there yet. Do you allow all of your servers to reboot automatically? Or for the more important servers, do you handle the reboots manually (ie: DC’s, SQL servers, etc)? Thanks, James Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
