I believe there is a "uservoice" item for something like that--pre- and post- tasks.
Look for it and vote it up. Otherwise, if you are looking for something available NOW to do that... I believe that would be a custom solution. probably "something" like... (I don't do this, just thinking thru the logic) 1) target the SUG to the collection of those apps servers. But the deadline is way way in the future. 2) using a Task Sequence (as an example, could probably use posh as well, or PADT)... something like... a) posh task to stop services. b) Install Updates task c) Reboot server That's simplified of course--it's just my vague thoughts on how to get it done. On Mon, May 23, 2016 at 10:39 AM, Brian McDonald <[email protected]> wrote: > In this case there is an application server that uses SQL. There are > services that need shut-down prior to the server rebooting or it causes > issues in our environment. > ------------------------------ > *From:* [email protected] <[email protected]> > on behalf of Lindenfeld, Ivan <[email protected]> > *Sent:* Monday, May 23, 2016 10:05:17 AM > *To:* [email protected] > *Subject:* [mssms] RE: Stopping Windows Services before Patching solution > > > I’m not sure I understand what you are asking. Why do you need to > shutdown Windows services prior to patching? > > > > Ivan L > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Brian McDonald > *Sent:* Monday, May 23, 2016 10:40 AM > *To:* [email protected] > *Subject:* [mssms] Stopping Windows Services before Patching solution > > > > Hello, > > > Does anyone have an automated method for handling the shutdown of windows > services prior to applying patches? > > > > I'm looking for a way to shut down the services, then apply the patches. I > could write a script to shutdown the services, but not sure how to setup > the patch deployment to know when the services are shut down. Has anyone > dealt with anything like this before? > > > > Brian M. > > > ------------------------------ > NOTICE: The information contained in this message is proprietary and/or > confidential and may be privileged. If you are not the intended recipient > of this communication, you are hereby notified to: (i) delete the message > and all copies; (ii) do not disclose, distribute or use the message in any > manner; and (iii) notify the sender immediately. > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
