PENDING Devices getting reboot from SCCM

[erikdeklerck]

Several devices are getting reboots (notification sftware center), no deployments currently.
What are log files on client and or monitoring to search for reboot cause ?
On client : Rebootcoordinator.log / Updatesdeployment.log ?

Rebootcoordinator.log :
Entered ScheduleRebootImpl - requested from 'DCMAgent' with reason 'ScopeId_C95D14E6-072F-49E0-885F-D2A8F8CB35C8/RequiredApplication_30412961-3307-482f-b379-17cbb1732524'. set Rebootby = 1680594743. set NotifyUI = True. set PreferredRebootWindowType = 3

 

[chrisj76]

Check there are no old software deployments to collections where those devices are memebers of that have the deployment set to reboot device outside of maintaince window

 

[erikdeklerck]

ok did some research...compliance settings on rename folder is putting the device into a collection for reboot.
Reason is :
\??\\AppData\Local\Temp\cc5b9279-5031-4c8b-9c84-d9d34b2c4e4d.tmp

\Program Files (x86)\Microsoft\Edge\Temp\scoped_dir5160_1195349794\old_msedge.exe

\Program Files (x86)\Microsoft\Edge\Temp\scoped_dir5160_1195349794

Program Files (x86)\Microsoft\Edge\Temp
So something is going wrong with edge updates and renaming is to old_msedge.exe

 

[Prajwal Desai]

Can you remove or disable that compliance rule and see if that resolves this issue.