During sealing (preparation phase) BIS-F checks if a pending reboot flag exists on the system. In this BIS-F 7 1912 release this check run’s earlier then in previous releases.
GPO Setting:
- If you enable this policy setting, a pending reboot will be suppressed. BIS-F will send out a warning if a pending reboot flag exist. Image sealing walks traight forward.
Note: a suppressed Pending reboot can send out warnings to administrators at further logon’s.
- If you disable or do not configure this policy setting, a pending reboot will not be suppressed and Image sealing is exiting with Error Code 1.
With BIS-F 7.1912.6 and later the responsible Component for the pending reboot will be grabbed and put into the Logfile as shown int he following table:
If a Pending Reboot exists, the Componentname will be logged
| Component | Logic |
| Component Based Servicing | HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending |
| Windows Update | HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired |
| Session Manager – PendingFileRenameOperations | HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager” -Name PendingFileRenameOperations |
| RebootPending | Invoke-CimMethod -Namespace root\ccm\ClientSDK -ClassName CCM_ClientUtilities -Name DetermineIfRebootPending | Select-Object “RebootPending” |
| IsHardRebootPending | Invoke-CimMethod -Namespace root\ccm\ClientSDK -ClassName CCM_ClientUtilities -Name DetermineIfRebootPending | Select-Object “IsHardRebootPending” |