WSUS not able to detect few PC's and all servers 1

[windowsfan]

I configured WSUS on a big network and for some reason it's not detecting few PC's and all Servers.

I checked on all PC's and servers to make sure group policy is applied and nothing seems to be wrong with group policy. I had user restarted their PC's two to three time and WSUS still cannot detect those PC's and servers. I also ran wuauclt.exe / detectnow.

What could be wrong?

 

[windowsfan]

Below are the test result from the server which is not detected by WSUS
C:\Documents and Settings\bpatel>\\192.168.100.19\bpatel$\Networking\WSUS\Client
Diag.exe

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 2 : Notify Prior to Download . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer =

http://192.168.100.8/wsusadmin

WUStatusServer =

http://192.168.100.8/wsusadmin

UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS

Press Enter to Complete

C:\Documents and Settings\bpatel>wuauclt.exe /detectnow

 

[porkchopexpress]

Does the client logfile give any clues?

C:\WINDOWS\WindowsUpdate.log

Are you seeing the clients appear on the server but not reporting? If not you can try wuauclt /resetauthorization /detectnow

 

[windowsfan]

Below are the errors from log files and I also ran wuauclt /resetauthorization /detectnow
I do not see few clients and all servers on WSUS console.

WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
WinHttp: ShouldFileBeDownloaded failed with 0x80190191
WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
WinHttp: ShouldFileBeDownloaded failed with 0x80190191
WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
WinHttp: ShouldFileBeDownloaded failed with 0x80190191
WinHttp: SendRequestToServerForFileInformation failed with 0x80190191
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190191
DownloadFileInternal failed for

http://192.168.100.8/wsusadmin/selfupdate/wuident.cab:

error 0x80190191

 

[porkchopexpress]

If you paste

http://192.168.100.8/wsusadmin/selfupdate/wuident.cab

into internet explorer are you prompted to down load the file?

Are all clients on the same subnet as the WSUS or are there any differences compared to the working clients, SP level or OS version?

 

[windowsfan]

when I try

http://192.168.100.8/wsusadmin/selfupdate/wuident.cab

I get pagenotfound error on both clients and server. I also tried this on the clients which are detected by WSUS and even for the working client same error. It also prompted me for authentication.

Default website has anonymous access.

All the clients are on same subnet.
When I try

http://192.168.100.8/selfupdate/wuident.cab

it prompts me to download file where do i need to save this file?

 

[monsterjta]

BITS 2.0 and WinHTTP 5.1 are required for clients to connect to WSUS.

http://support.microsoft.com/kb/842773

I hope you find this post helpful,

Jonathan Almquist
Minneapolis, MN

 

[windowsfan]

I compared those files (

http://support.microsoft.com/kb/842773)

with one of the computers not detected by WSUS and all the files are same. I checked the reportingevents.log file on that computer and logs looks fine. In the log it says following updates have beign downloaded, installed and PC has rebooted, but in WSUS that PC is not detected.

 

[porkchopexpress]

Sorry i gave you the wrong URL for the cab file try this

http://servername/selfupdate/wuident.cab

Were the clients imaged? If so it might be worth checking if the missing ones have the same SUSID.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
"PingID"
"AccountDomainSid"
"SusClientId"


Also i've been having a few issues with certain clients showing up in the WSUS console but not downloading updates, apparently this is due to a reporting error in IIS6 there is now a hotfix for this from MS it might be woth reading the KB to see if it applies to you.

http://support.microsoft.com/?id=898708

 

[silvercas]

goto SYSTEM and then Computer Name does it say anything about your network being non functional? I ran into a problem today that only affects 1 pc

CAS

http://www.helpmecas.com

 

[windowsfan]

In my case
Some of the clients not detected by WSUS are still getting updates from WSUS. I found this from logs of each missing PC and on all missing PC logs it says
Synchronize Successfull Agent has finished detecting items.
Success Content Download, Download Succeeded.

how can I fix this?

Few of the PC's the appear for a while on WSUS and than disappear next day?

I will look into SID for missing PC's.

 

[porkchopexpress]

It sounds like the SUSID to me i've had this before WSUS hold the Computer Client ID in the tbComputerTarget Table in the SQL Database. This is the Unique identifier that the WSUS software uses to Update the Computer list in WSUS if more than one computer has the same unique ID then each time a computer connects to the WSUS Server that Computers information overwrites what the previous computers name and info is. The end result is that the clients 'do' download updates but then seem to disappear leaving no record of their status.

 

[windowsfan]

You mean to say the computers have same Computer SID?
if this is the case can I run newSID program to change the SID?
is this computer SID different from SUSID or what is SUSID?

 

[porkchopexpress]

They are different the SUSID is located at the key i posted above.

 

[windowsfan]

how do I fix it? SUSID is something from WSUS or windows, I dont use SQL as database for WSUS. I am using WMSDE.

 

[porkchopexpress]

MSDE is the SQL Data base for WSUS if you delete the registry key on a client PC and then force detect with the reothorize switch it should generate a new ID and you will see it appear in the console.

 

[windowsfan]

how is the SUSID Created? IS SID part of SUSID?

I just need to delete regKey once on the PC not reporting or do I have to run everytime?

thanks for your help.

 

[porkchopexpress]

The Windows SID and the SUSClientID are completly seperate and unrelated. You just need to delete the key once on each affected client and a new one will be genenerated.

Test it on one client first to see if it works it might not be the solution to your problem but it's likely.

 

[windowsfan]

The reason I am asking how is SUSClientID is because I have read on many forum about same issue where first question they ask is did used the clone image?

Thats why I was trying to figure out how is SUSclientID created.

thanks for your help

 

[porkchopexpress]

The SUSclientID is created by the Auto Update service when it connects to WSUS, this along with the Windows SID become part of the cloned image.

If the SUSClientID is the same as another client then the WSUS server cannot distinguish between clients. The same happens with the SID Windows cannot tell cients appart and this undermines Windows security.

This is why you should run Sysprep or NewSID before cloning a Windows PC, unfortunatly these utils do not change the SUSClientID.

Hope that helps.