PENDING SCCM WINDOWS UPDATE NEEDED BUT REQUIRED UPDATE STAYING ZERO

[PASCAL JOURDAN]

HI
I recently installed a new sccm with all the necessary prerequisites wsus is ok the settings for downloads are ok the client settings are ok however no workstation has required updates for three months. Do you have any suggestions ?
Regards
pascal

 

[Youssef Saad]

Hello Pascal,
You have to check the logs from client side to see if they are getting your SUP server and checking the software updates compliance correctly, below the logs to check from "%WINDIR%\CCM\Logs":

• LocationServices.log
• WUAHandler.log
• UpdatesHandler.log
• UpdatesStore.log

 

[PASCAL JOURDAN]

Hi Youssef ,
hop your well !!
From log under a pc machine j can see these error :
From :
UpdatesStore.log


UpdatesHandler.log

WUAHandler.log

LocationServices.log



Boundarys group seem to be the pb ...

Regards

Hello Pascal,
You have to check the logs from client side to see if they are getting your SUP server and checking the software updates compliance correctly, below the logs to check from "%WINDIR%\CCM\Logs":

• LocationServices.log
• WUAHandler.log
• UpdatesHandler.log
• UpdatesStore.log

 

[Youssef Saad]

Exactly, you need to create a boundary (ip range is preferred) and add it in a boundary group by assigning your SUP/DP/MP as a site system server (under boundary group Properties).
You will find more details in my following guide:

• How To Configure Boundaries and Boundary Groups for SCCM / ConfigMgr

Once done, run SCCM client cycles from Control Panel / Configuration Manager, then double check LocationServices.log. The client machine should now get the WSUS location.

 

[PASCAL JOURDAN]

Hi youssef,
Boundaries already set and the pb be the same .
the discovery was force but no resolve the pb at this time .
no information about inventory devices that needed update
For office 365 be the same pb ...
perhaps have to wait more time for result

Regards
Pascal

 

[PASCAL JOURDAN]

inventory look in progress now

Waiting and revert back
Tks

 

[Youssef Saad]

Good news! Let's force the software updates scan cycle from control panel and check at the same time WUAHandler.log.
If the issue persists, you may try resetting Windows Update stuff with the following script:

net stop wuauserv
net stop CryptSvc
net stop BITS
ren %windir%system32catroot2 catroot2.old
ren %windir%SoftwareDistribution sold.old
ren "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader" downloader.old
net Start BITS
net start CryptSvc
net start wuauserv

 

[PASCAL JOURDAN]

Hy Youssef,
Tks for your information ,
I thank you for your help and give you a feedback of situation .it is to be noted that the inventory of positions to start however it seems very slow I have a return for only two positions in two days for software updates while for M 365 it is more consequent.
How resolved it ?
Regards

 

[Youssef Saad]

Does your M365 Apps updates deployed on the machine? If so, try to run a Machine Policy Evaluation & Retrieval cycle then monitor PolicyAgent.log file.