Group policy pointing to a .bat that stops the services when a reboot (windows shutdown) is in process for that server.
Cynthia Erno From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Beardsley, James Sent: Wednesday, July 12, 2017 10:43 AM To: mssms@lists.myitforum.com Subject: [mssms] Handling Service Stops Prior to Updates ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. I'm looking for some ideas on how to handle Windows updates on a specific server. Our VMWare database is housed on a SQL box and until now, we've been managing Windows updates manually on that server but I'm trying to find a way to automate it. I've been told that before that SQL box can be rebooted, I need to stop two VMWare related services on it first and then I can install Windows updates and reboot it. What would be the best way to handle stopping services prior to applying updates? Should I set up a task sequence to stop the services and then use the apply updates step afterwards? Would it be better to script the whole thing in a package? Or do I just create a package to stop the services at the beginning of the maintenance window and then let Software Updates do its thing? Any suggestions? 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.
