NLM Errors in the Windows SCCM Client

-

1.    Stop the windows update service, rename or delete the Software Distribution folder (%windir%\softwareDistribution) and start windows update service. This approach provides a fresh start with a new Windows Update data store if the Datastore.edb file is corrupted.
2.    Open Windows update log file under path C:\Windows\WindowsUpdate.log and check latest logs especially NLM error.
3.    Download below KB article from Microsoft catalog site. KB2919355 or you can download the the patches from the below link.
    https://www.microsoft.com/en-us/download/details.aspx?id=42334
4.    Uninstall all patches(KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, KB2934018, KB2919442) if it is installed and restart server
5.    Install KB2919355 now on server and restart server again.
6.    Restart the windows update service, Go to control panel, open configuration manager, Go to Actions tab and trigger software update scan cycle and software update deployment evaluation cycle & check the logs.
7.    Wait for 15-30 Minutes, fresh bunch of patches will be available in software center.

 Logs that can be used in for Troubleshooting :

  • locationservices.log =>This log is used to check the correct software update point has been detected by the client , to check the management point and distribution point entries.
  • wuahander.log => when the software update scan cycle initiated, Windows update agent will contact WSUS for scanning and if is successful,a state message will be sent to site server confirming that,software update scan is completed successfully which can be seen from this log.
  • windowsupdate.log => If Software update scan is not successful then,you should look at this log for more information. This log Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.
  • Updatesdeployment.log => This log shows the number of updates and deployments being targeted to a machine.
  • Updatesstore.log =>Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle .
  • Rebootcoordinator.log =>Provides information about the process for coordinating system restarts on client computers after software update installations.

Popular posts from this blog

Running CLI Commands in ESXi using plink software

-
Image
Get-esxcli will help us to run the CLI commands over the host directly but to extend it we cannot run certain commands directly over the host, In such case, we can use the below script to run directly on the host and achieve our goals. One shot with the script to achieve multiple targets My target was given to check the status of smartd services in each host and disable it, So I have put the commands on the variable $cmd and $cmd2 and executing it in all the machines,  which has been feed in the variable $machines , command get executed in all the hosts fed in the variable $machines . Script :  $user = '' $pswd = '' $cmd = 'etc/init.d/smartd status' $cmd2 = 'chkconfig smartd off' $machines = Get-Content "" foreach ( $MACHINE in $machines ) { Get-VMHost -Name $MACHINE | % {     $ssh = Get-VMHostService -VMHost $_ | where { $_ . Key -eq 'TSM-SSH' }     if ( ! $ssh . Running)
Read more

Default powershell commands not getting executed , getting command not recognized.

-
I was working on some weird cases that some of the basic powershell commands are not getting  executed in the machine and i came to know that the powershell modules are not getting loaded due to which default modules are not getting loaded in the psmodule path. Resolution would be to run the below commands: $PSModulePath = Get-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\Session Manager\Environment" -Name "PSModulePath" $newPSModulePath = $PSModulePath.PSModulePath + ";C:\Windows\System32\WindowsPowerShell\v1.0\Modules" Set-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\Session Manager\Environment" -Name "PSModulePath" -value $newPSModulePath Else you need to create a PSModulePath value under the below path : HKLM:SYSTEM\CurrentControlSet\Control\Session Manager\Environment and need to enter the value of path mentioned below in the PSModulePath key : %SystemRoot%\system32\WindowsPowerShell\v1.0\M
Read more