By default when a SD Job is running on an Agent, reboot of windows are blocked waiting the end of SD Job execution.
In TRC_CF_CAF_SERVICE_*.log there are these lines :
201124-11:15:15.5932918L|003036|00000f44|CAF_SERVIC|caf|caf|000000|NOTIFY | CFShutdowner::waitForPluginTermination: [0] waiting for sdagent to terminate before allowing system shutdown
201124-11:15:16.5949227L|003036|00000f44|CAF_SERVIC|caf|caf|000000|NOTIFY | CFShutdowner::waitForPluginTermination: [1] waiting for sdagent to terminate before allowing system shutdown
201124-11:15:17.6117475L|003036|00000f44|CAF_SERVIC|caf|caf|000000|NOTIFY | CFShutdowner::waitForPluginTermination: [2] waiting for sdagent to terminate before allowing system shutdown
...
201124-11:16:28.1860781L|003036|00000f44|CAF_SERVIC|caf|caf|000000|NOTIFY | CFShutdowner::waitForPluginTermination: [72] waiting for sdagent to terminate before allowing system shutdown
201124-11:16:29.1931141L|003036|00000f44|CAF_SERVIC|caf|caf|000000|NOTIFY | CFShutdowner::waitForPluginTermination: [73] waiting for sdagent to terminate before allowing system shutdown
Sometimes this behavior could cause some problem (in case of blocked SD Job execution) and a windows reboot should be made even if a SD Job is running.
Following parameter could be set on configuration policy to change this behavior :
DSM/Software Delivery/Agent/Reboot: Allow application logoff and reboot = True
See this article for more details : caf blocks the shutdown of Windows
This parameter is working fine in version 14.5 CU1, 14.5 and before 14.5
But starting 14.5 CU2, this parameter does not work anymore and the reboot is blocked (in case of SD Job execution) even if it is set to True.
Client Automation 14.5 CU4 - Windows Agents
Open a case at Broadcom Technical Support and ask for the fix T437431
This fix delivers this file :
Name : sd_jexec.exe
Size : 805 624 bytes
Date : 8 January 2025
Version : 14.5.0.432
This fix is only for version 14.5 CU4
If a fix for different version is needed ask for the porting of the fix to another version
This problem is introduced in patch CU2
14.5 -> OK
14.5 CU1 -> OK
14.5 CU2 -> NOT OK
14.5 CU3...CU7 -> NOT OK