you found a doc that says you can make multiple collections and create separate deployments to each collection. On one collection you can set it so that SCCM will suppress the reboot, and on the other it will reboot if needed.
To force a reboot I just create an old school package that runs the command ipconfig and I set the after run behavior to configmgr reboots the computer. I make the maintenance window from 9 PM to 4 AM and set the updates to begin installing at 9:15 PM. Then I have the package run once at 3:30 AM 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* > > > >
