Troubleshooting unexpected reboots caused by software center computer maintenance setting – All about Microsoft Endpoint Manager

Troubleshooting unexpected reboots caused by software center computer maintenance setting

In a latest transition from Citrix VDI to AVD (single and multi-session), the AVD units are being effectively managed by SCCM and Intune (co-management).

As a part of routine upkeep, we’ve applied a weekly reboot schedule for our AVD units to make sure optimum efficiency and safety.

To realize this, I created a easy bundle with a command line (shutdown –r –f –t 300 “Rebooting the system as a part of weekly upkeep”) for rebooting the units weekly.

From the time, the weekly reboot job applied, there have been no points till somebody reported to workforce that AVD system was rebooting day by day at 2 AM native time, opposite to our meant schedule.

I picked it as much as examine additional to establish the basis trigger.

Very first thing is to take a look at the SCCM consumer logs specifically execmgr.log for the commercial standing and it reveals that, the particular bundle is being run day by day at 2AM.

Subsequent is to look deployment properties, if there have been any modifications to the schedule ? …. discovered it intact, set to run weekly as meant.

Additional investigation, I’ve additionally verified that, the weekly schedule data will be seen from the consumer WMI class.

For that the next Powershell script will assist you to get the schedule of particular commercial utilized to the system.

gwmi -Namespace rootccmpolicymachine -class CCM_Scheduler_ScheduledMessage | the place {$_.ScheduledMessageID-like “*ABC21452*”} | Choose ScheduledMessageID,ActiveMessage,Triggers | fl *

ABC21452 = Commercial ID

To transform the Schedule string, we are able to use Convert-CMSchedule cmdlet obtainable in SCCM powershell module.

Login to SCCM server or a tool that has put in with SCCM powershell module.

Import the SCCM powershell module and run the next with schedulestring.

Convert-CMSchedule 00A2AD40001B2000

image

As you may see from the above, the recurring schedule is identical what we’ve configured it within the deployment.

Regardless of confirming that the deployment schedule remained unchanged (from SCCM deployment schedule properties), the system continued to reboot day by day.

To additional examine deep dive, I’ve enabled the verbose logging (easy methods to allow verbose logging) and submit the reboot, reviewing the consumer logs reveals there may be particular setting in software program middle that’s inflicting the day by day reboot habits difficulty.

Software program middle –> Choices –> Pc upkeep—>Robotically set up or uninstall required software program and restart the pc solely outdoors of specified enterprise hours

This setting is disabled by default.

image

After disabling the setting in software program middle, the day by day reboot stopped and observe the weekly schedule (authentic schedule).

Disabling this setting rectified the problem, permitting the system to observe the unique weekly schedule as meant. Nonetheless, the logic behind this setting and its interplay with scheduled deployments stays unclear.

Is that this a bug, or is there a deeper understanding required of the particular setting within the Software program Middle for this use case?

In continuation to our investigation, we might want to establish the listing of units which are having this particular setting enabled in software program middle that may influence day by day reboot,

Software program middle setting particulars are saved in WMI class (CCM_SoftwareCenterSettings) therefore we are able to use Powershell scripts function in SCCM and run it on all goal endpoints to see what number of units would count on day by day reboot habits.

$information=(gwmi -Namespace rootccmpolicymachine -class CCM_SoftwareCenterSettings | Choose AutoInstallRequiredSoftware).AutoInstallRequiredSoftware
if ($information)
{
write-host “Not Anticipated, require repair”
}
else
{
write-host “All Good”
}

Because the units are managed by intune, it’s time to transfer the legacy duties Microsoft Intune for higher administration and adaptability.


We use cookies to enable site functionality and collect data about user interactions. By clicking Accept, you agree to our use for advertising, analytics, and support.