SCCM MONTHLY PATCHES DEPLOYMENT STATUS - IN PROGRESS & ERROR

Question

SCCM MONTHLY PATCHES DEPLOYMENT STATUS - IN PROGRESS & ERROR

InfraSolutions 771

Dear Team,

I deployed last month's patches and Dell drivers to our production machines. The drivers were installed on most machines, and the machines were rebooted a few times. However, the SCCM deployment status shows that not all machines are compliant. Some machines have the following statuses: "In progress tab—"Pending system restart," "Downloaded update(s)," "Non-compliant," and "Error tab - Pl refer to the pictures."

I randomly connected to a few machines manually and verified the Software Centre, but I did not see any pending activities on the Updates tab. Could you please help me troubleshoot this issue further?

Deployed Dell latest drivers using third-party software update catalogs:
User's image

In-Progress**:** User's image

Error: User's image

2 answers

Your answer

Answer 1

AllenLiu-MSFT 49,436 Microsoft External Staff

Hi, @MJ

Thank you for posting in Microsoft Q&A forum.

To find the Configuration Manager clients that require a reboot, you can use the SCCM console. Here are the steps to follow:

Launch the SCCM console and navigate to Assets and Compliance \ Overview \ Devices.

Right-click on the Menu bar and add a new column for Pending Restart.

The Pending Restart column will show why the device need a reboot, if the Pending Restart column show "No", it does not need a reboot.

Once you have identified the devices that require a restart, you can use a client notification action to restart those client devices.

For the status "Error," you can refer to the error message and take appropriate action.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

InfraSolutions 771 Reputation points

2023-10-04T09:15:05.37+00:00

it is showing a 'Pending Restart = NO' status, Also I double-checked by launching Software Center on the client machine and didn't see any restart notification. In fact, I didn't see anything listed in the 'Updates' tab
AllenLiu-MSFT 49,436 Reputation points Microsoft External Staff

2023-10-05T01:46:03.4166667+00:00

You may check the log RebootCoordinator.log.

It records details about the coordination of system restarts on client computers after software update installations.
InfraSolutions 771 Reputation points

2023-10-05T09:28:06.61+00:00

I checked the RebootCoordinator.log and it shows that a reboot is pending. I have restarted twice and recorded that in the log file, but the reboot remains pending after every restart.
InfraSolutions 771 Reputation points

2023-10-05T09:30:14.03+00:00

RebootCoordinator.logI checked the RebootCoordinator.log and it shows that a reboot is pending. I have restarted twice and recorded that in the log file, but the reboot remains pending after every restart.

Answer 2

Garth Jones 1,366

You will need to start by reviewing the log file that get created as part of the deployment. If one is not created then you need to fix that first.

InfraSolutions 771 Reputation points

2023-10-04T12:07:38.7333333+00:00

Thanks for your response Garth,

Do we have any specific logs where I can check for the pending system restart issue? I checked Appenforce.log and a few other logs, but I couldn't find which update needs a reboot. I also checked the Software Center > Updates tab, but I didn't see any updates listed there. There is also no notification to restart the client machine.
Garth Jones 1,366 Reputation points

2023-10-05T12:09:53.5566667+00:00

What make you think it is ConfigMgr is the cause of the pending restart? Have you reviewed the Event viewer on those machines?
InfraSolutions 771 Reputation points

2023-10-05T14:04:59.97+00:00

I'm not sure if I checked Event Viewer properly for the pending reboot reason, but when I ran the PowerShell command to identify the pending reboot value, it returned 'false,' indicating no pending restart

InfraSolutions 771

I have also checked the pending reboot flags in the registry, and everything looks fine,

Key	Value	Condition
HKLM:\SOFTWARE\Microsoft\Updates	UpdateExeVolatile	Value is anything other than 0
HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager	PendingFileRenameOperations	value exists
HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager	PendingFileRenameOperations2	value exists
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired	NA	key exists
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending	NA	Any GUID subkeys exist
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\PostRebootReporting	NA	key exists
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce	DVDRebootSignal	value exists
HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending	NA	key exists
HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootInProgress	NA	key exists
HKLM:\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackagesPending	NA	key exists
HKLM:\SOFTWARE\Microsoft\ServerManager\CurrentRebootAttempts	NA	key exists
HKLM:\SYSTEM\CurrentControlSet\Services\Netlogon	JoinDomain	value exists
HKLM:\SYSTEM\CurrentControlSet\Services\Netlogon	AvoidSpnSet	value exists
HKLM:\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName	ComputerName	Value ComputerName in HKLM:\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName is different

Share via

SCCM MONTHLY PATCHES DEPLOYMENT STATUS - IN PROGRESS & ERROR

2 answers

Your answer