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) < [email protected]> 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
