Client not reporting to WSUS Console.

The first thing to check is whether the client computer is using the latest Automatic Update client version.

The current version of the Windows Update Agent (the WSUS client component in AU) is determined by the version of the WUAUENG.DLL, located in %systemroot% \system32 folder. If the version of WUAUENG.DLL is 5.4.3790.1000 or greater, the WSUS client (or WUA) is installed. A version less than 5.4.3790.1000 indicates that SUS or earlier AU version 1.0 is installed.

If you have an earlier version of the AU client, it must be updated in order to work with WSUS. Computers running Windows XP with Service Pack 2 (SP2) already have the WSUS client installed.

The AU client, when contacting the WSUS server, will automatically update itself to the latest WSUS version if the self-update files are properly setup on the server. When connected to Windows Update or Microsoft Update, the AU client will also be able to self-update if it is not running the latest version. In addition, the AU client can also be updated by using a signed stand-alone, installation package that is available from Microsoft.

For further instructions on how to detect the need for, and or download the standalone latest release version of WUA, see the Updating the Windows Update Agent section of the Windows Update Agent API portion of the WSUS SDK at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wus/wus/portal.asp

On the left navigation, from Windows Server Update Services -> Windows Update Agent API -> Using the Windows Update Agent API -> Updating the Windows Update Agent.

 Imaged clients with a duplicate client ID will only appear once in the WSUS Admin Console. Each AU client must have a unique id which is created for each individual install. When imaging systems it is recommended always to use SysPrep. The WSUS admin console will only display one client for each unique ID. If you have multiple clients created from one image which are sharing the same ID, only one will appear in the WSUS admin console. All clients will check in and download updates, but only one will appear and display status in the WSUS admin console. In cases where clients are not checking in, and they were created from images without running SysPrep, the following steps will reset the existing duplicative client IDs.

a. Run regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

b. Delete the PingID, SUSClientID and the AccountDomainSID values

c. Stop and start the Wuauserv Service

d. From the command prompt run: wuauclt /resetauthorization /detectnow

or-

From the command line, once you are sure the AU client is properly configured and not disabled, you could run a batch file (which might look something like this sample) and get the same results:

rem Fixes problem with client machines not showing up on the server due to imaging method

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f

cls

@echo Triggering detection after resetting WSUS client identity

net stop wuauserv

net start wuauserv

wuauclt /resetauthorization /detectnow

Unable to Open/View Roles in Server Manager (Windows Server 2008)

If you’re unable to open/view roles in Server Manager (Windows Server 2008) , the problem might be with a patch which was not installed properly Or the server is not rebooted for long time after patches installation. Here are the steps to be followed to resolve the error.

Problem Description

a. In server manager you can not see any roles or features that are installed and in the bottom of the screen there is an error that says:

Last refresh: Failed Enable Error Details


b. When you click on Error Details you’ll see the following error :
Unexpected error refreshing Server Manager: No signature was present in the subject. (Exception from HRESULT: 0x800B0100)
Problem Resolution
Step 1. Determine Update state of system

a. This step can be done by using a new tool developed by Microsoft to resolve these kind of issues :
WS08 ·
b. When you install this “Update” a logfile will be generated at c:\windows\logs\CBS with the name CheckSUR.log
The content of this log :
=================================
Checking System Update Readiness.Version 6.0.6001.222752008-10-18 09:38
Checking Deployment Packages
Checking Package Manifests and catalogs.
Checking package watchlist.
Checking component watchlist.
Checking packages.(f) CBS MUM Missing 0x00000002 servicing\packages\Package_for_KB951978_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum (f) CBS MUM Missing 0x00000002 servicing\packages\Package_for_KB951978_server~31bf3856ad364e35~amd64~~6.0.1.0.mum (f) CBS MUM Missing 0x00000002 servicing\packages\Package_for_KB951978~31bf3856ad364e35~amd64~~6.0.1.0.mum
Checking component store Checking SMI StoreSummary:Milliseconds: 197278Found 3 errors CBS MUM Missing Total Count: 3
Checking component store

c. This means that from the KB951978 *.MUM files are missing in the packages store (located at c:\windows\servicing\packages)
Step 2. Retrieve the missing files

a. Download the KB Update as we need to extract files from it. In your Update History you can find this update fast as it is listed as the first failed update that happened :

 

b. Now double click this update.


c. Click on the link to the KB Article, this link will open internet explorer and just scroll down to the download links on the page :
d. Download the related package, rename the extension of the file from MSU to CAB
e. Open the file

f. Extract the CAB file to another location for example c:\temp
g. Open the cab file and search for the files that are listed in the checksur.log, extract those files to another lcoation (C:\temp)
h. Most of the time 1 of the files can not be found : Here it is
Package_for_KB951978~31bf3856ad364e35~amd64~~6.0.1.0.mum
i. Extract the update.mum instead and rename it to the missing name.
j.Now we have a collection of files that need to be copied to a protected location (C:\Windows\servicing\packages)
Step 3. Install the missing files

a. First we need to unprotect the packages directory so we can copy files to it
right click “Packages” Folder and choose properties, select tab security, click advanced and click on the tab “Owner”

 


b. As you can see the correct owner (trusted installer) is listed, for now you need to change the ownership to your own account. When done, you will be returned to the security overview, add yourself with full control permission to the folder

c. Now we can copy the missing files to the packages directory.
d. Most of the times you need to rerun the update to determine which files are missing and it will list *.CAT files as missing so you need to repeat the steps for extracting and copying the missing files.
e. If Still the check says that one package is missing, rename update.cat & update.mum to that missing package name and copy those files to c:\windows\servicing\packages.
f.Rerun the update detection until the log file does not report any missing files.
g.When all is well, the error’s in server manager are gone :



And the Roles can be viewed again :

Don’t forget to set the rights of the Packages folder back to how they were.