SCCM Last enforcement state still reboot Pending after rebooted devices

Question

Env SCCM 1906

SCCM patches deployed to Citrix VDI,s with automatic restart and collection without maintenance window.

but still shows reboot pending and we have rebooted forceful but still last enforcement state not yet updated.

same deployment working on laptops and servers these are rebooted successfully and updated compliance also only issue with citrix VDIs.

WUAHandler log

11. Update (Missing): Update for Microsoft Outlook 2016 (KB4484511) 64-Bit Edition (f175657b-36c1-4330-9ebb-c8d78c098e26, 200)
    WUAHandler 9/24/2020 11:52:41 PM
    6308 (0x18A4)
    Async installation of updates started. WUAHandler
    9/24/2020 11:54:05 PM 6308 (0x18A4)
    Update 1 (1b550ea1-509e-4549-a6cb-e97831629cc9) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/24/2020 11:55:49 PM
    8144 (0x1FD0)
    Update 2 (1d6be167-631f-4f12-991b-32294ff0b08f) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/24/2020 11:56:36 PM
    6532 (0x1984)
    Update 3 (417a61d9-3b6a-4215-a83f-e5e6e0a0dd7d) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/24/2020 11:57:27 PM
    712 (0x02C8)
    Update 4 (48d52288-aaa9-4a75-8d8e-ede212badc85) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/24/2020 11:58:06 PM
    4128 (0x1020)
    Update 5 (58cba128-7e94-4015-864f-9c8d85f7dc60) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/24/2020 11:59:32 PM
    9064 (0x2368)
    Update 6 (59a5d6b8-762e-4e00-83fe-1fa99585f8b1) finished installing (0x00000000), Reboot Required? Yes
    WUAHandler 9/25/2020 12:00:45 AM
    7284 (0x1C74)
    Update 7 (6a3c57fe-6501-4f98-a125-c6acc8ea9d2b) finished installing (0x00000000), Reboot Required? Yes
    WUAHandler 9/25/2020 12:18:25 AM
    5844 (0x16D4)
    Update 8 (7429444c-bac6-4627-85d5-e47aa0b928bc) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/25/2020 12:19:37 AM
    6716 (0x1A3C)
    Update 9 (78b8ebae-ba63-4a9c-9927-734bef64dfd7) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/25/2020 12:20:19 AM
    6716 (0x1A3C)
    Update 10 (b0a743d6-025a-4ca4-a998-b019a5b176f3) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/25/2020 12:23:32 AM
    3916 (0x0F4C)
    Update 11 (f175657b-36c1-4330-9ebb-c8d78c098e26) finished installing (0x00000000), Reboot Required? No
    WUAHandler 9/25/2020 12:24:27 AM
    2292 (0x08F4)
    Async install completed. WUAHandler
    9/25/2020 12:24:27 AM 2292 (0x08F4)
    Installation of updates completed. WUAHandler
    9/25/2020 12:24:27 AM 10216 (0x27E8)
    Scan results will include all superseded updates. WUAHandler 9/25/2020 12:24:27 AM
    10216 (0x27E8)
    Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '25AED893-7C2D-4A31-AE22-28FF8AC150ED') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'A3C2375D-0C8A-42F9-BCE0-28333E198407'))
    WUAHandler 9/25/2020 12:24:27 AM
    10216 (0x27E8)
    Async searching of updates using WUAgent started. WUAHandler 9/25/2020 12:24:27 AM
    10216 (0x27E8)
    Async searching completed. WUAHandler
    9/25/2020 12:24:56 AM 7164 (0x1BFC)
    Successfully completed scan. WUAHandler
    9/25/2020 12:24:56 AM 10216 (0x27E8)
    updatedeployment.log

CUpdateAssignmentsManager received a SERVICEWINDOWEVENT END Event
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
8788 (0x2254)
CUpdateAssignmentsManager received a SERVICEWINDOWEVENT START Event
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
Suspend activity in presentation mode is selected UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
At least one user has elected to suspend non-business hours activity when in presentation mode. Checking for presentation mode.
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
Proceeding to non-business hours activites as presentation mode is off.
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
Automatic required software installation during non-business hours is selected
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
Auto install during non-business hours is enabled, selecting all required updates.
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
Unable to find CCM_PrePostActions.SiteSettingsKey=1.
UpdatesDeploymentAgent 9/25/2020 12:00:00 AM
5708 (0x164C)
GetActions() did not succeed. 80070490. UpdatesDeploymentAgent
9/25/2020 12:00:00 AM 5708 (0x164C)
Reboot Coordinator.log

Reboot Coordinator received a SERVICEWINDOWEVENT START Event
RebootCoordinator 9/24/2020 8:00:00 PM
916 (0x0394)
System restart turnaround time is 600 seconds. RebootCoordinator 9/24/2020 11:51:26 PM
6308 (0x18A4)
Reboot Coordinator received a SERVICEWINDOWEVENT END Event
RebootCoordinator 9/25/2020 12:00:00 AM
6308 (0x18A4)
Reboot Coordinator received a SERVICEWINDOWEVENT START Event
RebootCoordinator 9/25/2020 12:00:00 AM
6308 (0x18A4)
System restart turnaround time is 600 seconds. RebootCoordinator 9/25/2020 12:24:27 AM

Answer 1

Hi,

Thank you for coming Microsoft MECM Q&A forum.

1.Please help check which Detail level you have specified in the update deployment settings, All messages, only error messages or Only success and error messages? This will specify the level of detail for the state messages that clients report to the site.

2.State messages are sent every 15 minutes assuming the client has connectivity to the MP. If you aren't getting state messages from specific clients, they most likely aren't connected. Please help check if the client could communicate with the MP.

3.Also we could examine the Updatesdeployment.log and Statemessage.log files on the client. By interpreting the state messages in these logs, we can get a clear picture of what is occurring at the various steps in the process. Refer to:
State messages in Configuration Manager

Thanks for your time.

Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.