I normally check for exit code 3010 in Configmgr logs and\or eventvwr. The usual logs are execmgr, appexec, smsts, wuahandler, rebootcoordinator depending on the nature of assignments.
how to know which application or update reason for system restart device managed by SCCM
Hello Expert,
I have deployed Windows 365 PC that is co-managed in sccm. I have deployed a task sequence on this pc collection but found that this task sequence is not get started showing status in Progress in sccm deployment status of Task sequence.
I login this pc ,found that restart is needed as other apps and updated were push on this device collection.
How I know that what particular application required this restart for that another TS is not get started and struck in progress.
I know after restart the device ,TS will started but it is not automatic way .
what to know which installed apps required restart.
Thanks
Rich
3 answers
Sort by: Most helpful
-
-
Pavel yannara Mirochnitchenko 12,391 Reputation points MVP
2024-05-29T09:19:59.08+00:00 If event viewer will not help you, you could try to identify via appenforce.log from CM client, which was the last app install. I remember also there was some ccm log file showing what updates has been installed, if that is the update which created a restart.
-
Simon Ren-MSFT 31,756 Reputation points Microsoft Vendor
2024-06-04T09:37:09.1966667+00:00 Hi,
Thank you for posting in Microsoft Q&A forum.
1,You can check the event log and logs as above suggestions to determine which application/update triggers a device restart.
2,A little piece of info that might help is there's a column in the console when you're looking at all devices for Pending Restart and it gives you reasons as to why the server/workstation may need a restart. As shown below:
Thanks for your time. Have a nice day!
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.