Yes Jason. But I was putting it out there just in case someone on this list mentioned that it may be a possible cause.. it was brought up at one point from my team. Cynthia Erno
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Wednesday, June 08, 2016 3:38 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM force reboot after patching ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. When patching with ConfigMgr, most of the group policy settings don’t apply or have any relevance including the one you’ve cited below. Sherry’s answer had nothing to do with group policy either. She’s specifically talking about deployment settings within ConfigMgr. J From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Erno, Cynthia M (ITS) Sent: Wednesday, June 8, 2016 1:34 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM force reboot after patching Thank you Sherri. I was hoping that was not the answer since too many of our servers are not rebooting after having been patched with SCCM. No reboot = machine not in compliance. And yes, we’ve checked the group policies of all the domains and there isn’t any consistency in them as well – meaning some have the group policy setting enabled for “ no auto-restart with logged on users…” and some do not. So, we really need a force reboot we can count on to happen for all. If anyone thinks of anyway to pull it off, let me know please. Cynthia Erno From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Sherry Kissinger Sent: Wednesday, June 08, 2016 1:56 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] SCCM force reboot after patching ATTENTION: This email came from an external source. Do not open attachments or click on links from unknown senders or unexpected emails. This is what I believe is meant by that. Let's say you have a Software Update Group with all of this months' patches inside it, which every workstation in your environment deserves; but Accounting LOB wants to reboot when they feel like it; and everyone else gets patched, and they are required to reboot in the XX minutes you've defined for normal notifications. So you have two collections: Accounting LOB, and "All workstations, excluding Accounting LOB" You have two Deployments of that same Software Update Group; and to the Accounting, you check the boxes under "User Experience" to Suppress the system restart on workstations. and to the deployment targeting "all workstations excluding accounting", you don't check that suppress system restart workstation; in which case those targets get the normal countdown timer (whatever it is you have defined) for post-patching restarts, if a restart is required. On Wed, Jun 8, 2016 at 11:09 AM, Erno, Cynthia M (ITS) <cynthia.e...@its.ny.gov<mailto:cynthia.e...@its.ny.gov>> wrote: I found a doc that claims that sccm 2012 has the ability to force a reboot after patching: “Through SCCM, we can easily define or Customize Restart behaviour for different LOBs (Line Of Business). Often, seen that some LOBs required their systems to be forcefully restarted after patching but some are interested to supress reboot until the end user reboot the system.” Does anyone know how to implement this ability in SCCM? Cynthia Erno -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
