SOLVED Client reflecting Unknown mostly in Software Update Deployment

[Amol Bhatt]

Hi Prajwal, My Clients are reflecting their software deployment status very late. I had deployed Server patches on March 11 however, still 40 + Servers are still in unknown state. Below troubleshooting I have done respectively.

-Restarted Services: BITS, SMSAgentHost, Windows Module Installer,WindowsInstaller,WindowsUpdate
-Initiated Policies: Machine Policy, Scan POlicy, Software Update Evaluation, Machine POlicy, DDR Cycle, ScanPolicy, Software Update Evaluation
-WUAHandler - Reboot Required-Yes
-Statesys - State Messages are getting processed

-Tried SCCM Client Clean Re-installation on Machines. Even though these 40 + Machines are still in Unknown state, they should show status as Pending Restart as I have checked in Wuahandler Reboot Required is Yes, but no they are still reflecting in unknown state of the Compliance.
I do have few clients they are showing as complaint, but those too reflected after so many days.

Please help in this matter urgently..
Imp: Note: This is happening after the Machine Keys got corrupted in Jan Month, post which these status are getting deployed. However Application deployment status are sending their results quickly. It is happening only in case of SoftwareUpdateDeployment.

 

[Amol Bhatt]

Hi Prajwal
Please respond.

 

[Amol Bhatt]

Hi Prajwal, Kindly respond.

 

[Amol Bhatt]

Hi Garth Please respond to my above query

 

[Amol Bhatt]

DEAR ALL,
JUST WANTED TO HIGHLIGHT THAT THIS ISSUE IS RESOLVED NOW. PLEASE MARK THIS THREAD AS RESOLVED.

 

[Gokul]

Hi Amol, Did you changed any roles (Uninstall/install) in you primary server ? Like remote differential compression ,BITS, IIS, MP?

Curious to hear -Can you update your resolution ?

 

[Amol Bhatt]

Yes Gokul. It was BITS.

Here are the highlights of the issue and resolution:
Issue:

• I was not aware that In Jan 2020, somehow my SCCM Primary site machine keys got corrupted.
• The software deployment status and all other deployment status was suddenly showing me unknown state.
• Found IIS service in stopped mode and not starting and giving error. (Do not have error snap.)
• Logged a case in MS for the same and they suggested to uninstall and re-install IIS & WSUS. It’s done.
• Then my MP started misbehaving MPCONTROL.log and logged a second case in MS for MP and they fixed it by re-generating required certificates for MP and Clients

Post above chronology, my deployment started showing the status, however, the frequency of the status change was very ab normal. Sometimes it was showing in a day for 1 or 2 machines and other machines went in to unknown, I struggled this scenario from Jan till 20th April. I checked all the relevant logs however all logs were in green. No errors in the client logs. It was sending status properly.

Resolution

• I checked MP_Status.log on my Primary Server.
• This log was showing me BITS Error from the Client Side.
• The I went to Basics and found in Roles and Features BITS was not installed Even though BITS Service was showing me Services.msc

Then I re-installed BITS service & my issue got resolved immediately.