With the release of SCCM 1710, a lot of new features were added. Software center customization was something that i loved the most. Here is the post on customizing software center in SCCM 1710. One of the exciting feature that i wanted to try was SCCM 1710 restart client feature. So far I have used right click tools and it worked well while you wanted to restart remote computers. But now Microsoft has come up with option to identify and restart clients.
So what is this SCCM 1710 Restart Client Feature ?. Using Configuration Manager console, you can now identify client devices that require a restart. Post then you use a client notification action to restart those client devices. The client computer receives restart notification and a notification window opens to inform the user about the restart. By default, the restart occurs after 90 minutes. This can be changed under client settings > computer restart setting.
SCCM 1710 Restart Client Devices Values
When we say SCCM identifies client devices that needs a restart, it shows the following values under Pending Restart column. Let’s see what those values are and what they mean.
|No||If you see this value, it means no restart is pending.|
|Configuration Manager||This value comes from rebootcoordinator.log file.|
|Add or Remove Feature||You see this value when you install/uninstall any role/feature that needs a device reboot.|
|Windows Update||The value is displayed when the client computer is patched and requires a reboot. The value comes from Windows Update Agent that reports a reboot required.|
|File rename||This value comes from Windows reporting a pending file rename operation.|
SCCM 1710 Restart Client Feature
We will now test SCCM 1710 restart client feature. As mentioned earlier, you can use the Configuration Manager console to identify clients that require a restart. Then use a client notification action to restart them. I have a Windows 10 machine where I have enabled Hyper-v under features. Since we know that enabling hyper-V requires reboot, I have cancelled the restart. So there is a pending restart on Windows 10 VM.
Launch configuration manager console and navigate to Assets and Compliance > Overview > Devices. Right click on column and select Pending Restart.
Review rebootcoordinator log file. This log file provides information about the process for coordinating system restarts on client computers after software update installations. Notice the last line of log file. Notified UI grace period start with 2700 grace seconds and 600 final seconds. These values are the ones that we have defined under client settings > computer restart settings.