WSUS clients not reporting

[ArmedAndClueless]

So here's the situation. I'm running Windows 2000 SBS, nothing too shocking really. I dropped on a copy of WSUS, running on MSDE SP3a. For some reason, none of the clients are reporting in! I ran the client diagnostic on several of the machines. One has the UseWuServer set to zero, so it wasn't reporting in. However, the machines that came out clean in the clientdiag.exe didn't report in either.

I've had some issues with BITS as well. When I run wsusdebugtool.exe with the /tool:GetBitsStatus, it errors out, saying that there is not bitsadmin.exe file. I searched the hard drives, and came out with nada. I Downloaded BITS2.0 and WinHTTP 5.1, and installed it again. However, same error:

C:\>wsusdebugtool.exe /tool:getbitsstatus
Running... GetBitsStatus
bitsadmin.exe /list /allusers /verbose

'bitsadmin.exe' is not recognized as an internal or external command,
operable program or batch file.

Error processing node: GetBitsStatus

Here's the result of GetConfiguration, I think I'm missing something obvious in here:

C:\>wsusdebugtool.exe /tool:getconfiguration
Running... GetConfiguration
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
WmsdeInstalled:0
PsfsipInstalled:1
TargetDir:C:\Program Files\Update Services
ContentDir:C:\Program Files\Update Services
CreatedContentDir:0
SqlServerName:VALLEYRIDE-DC\WSUS
SqlAuthenticationMode:WindowsAuthentication
SqlDatabaseName:SUSDB
SqlUserName:
SqlEncryptedPassword:
InstallType:128
:
WsusAdministratorsSid:S-1-5-21-583907252-1303643608-1801674531-1332
IISTargetWebSiteIndex:601052883
IISTargetWebSiteCreated:True
IISUninstallConfigFilePath:C:\Program Files\Update Services\setup\Uninst
allSettings.xml
IISPreviousInstallRevision:
IISInstallRevision:5.5.2472
EncryptionKey:System.Byte[]
<NewDataSet>
<Table>
<ConfigurationID>1</ConfigurationID>
<LastConfigChange>2005-12-23T06:30:14.8570000-07:00</LastConfigChange>
<DssAnonymousTargeting>false</DssAnonymousTargeting>
<IsRegistrationRequired>true</IsRegistrationRequired>
<MaxDeltaSyncPeriod>30</MaxDeltaSyncPeriod>
<ReportingServiceUrl>

http://stats.update.microsoft.com</ReportingServiceUrl>

<ServerID>96c3ebaf-0d7d-45e2-8c47-5f20447a1b30</ServerID>
<AnonymousCookieExpirationTime>10080</AnonymousCookieExpirationTime>
<SimpleTargetingCookieExpirationTime>60</SimpleTargetingCookieExpirationTime
>
<MaximumServerCookieExpirationTime>10080</MaximumServerCookieExpirationTime>

<DssTargetingCookieExpirationTime>240</DssTargetingCookieExpirationTime>
<EncryptionKey>vfmq3JCHUBIw+kV+2u82Epu79mGgu48I</EncryptionKey>
<ServerTargeting>true</ServerTargeting>
<SyncToMU>true</SyncToMU>
<UpstreamServerName />
<ServerPortNumber>80</ServerPortNumber>
<UpstreamServerUseSSL>false</UpstreamServerUseSSL>
<UseProxy>false</UseProxy>
<ProxyName />
<ProxyServerPort>80</ProxyServerPort>
<AnonymousProxyAccess>true</AnonymousProxyAccess>
<ProxyUserName />
<ProxyPassword>xMAuBXrCQF6RnrtKmmfwNePgyst59oktAb+iPcsBBmM=</ProxyPassword>
<HostOnMu>true</HostOnMu>
<LocalContentCacheLocation>C:\Program Files\Update Services\WsusContent\</Lo
calContentCacheLocation>
<ServerSupportsAllLanguages>true</ServerSupportsAllLanguages>
<LogLevel>3</LogLevel>
<LogPath>%programfiles%\\Update Services\\LogFiles\\SoftwareDistribution.log
</LogPath>
<SubscriptionFailureNumberOfRetries>3</SubscriptionFailureNumberOfRetries>
<SubscriptionFailureWaitBetweenRetriesTime>15</SubscriptionFailureWaitBetwee
nRetriesTime>
<DispatchManagerPollingInterval>5</DispatchManagerPollingInterval>
<StateMachineTransitionLoggingEnabled>false</StateMachineTransitionLoggingEn
abled>
<StateMachineTransitionErrorCaptureLength>600</StateMachineTransitionErrorCa
ptureLength>
<MaxSimultaneousFileDownloads>10</MaxSimultaneousFileDownloads>
<MUUrl>

https://update.microsoft.com/v6</MUUrl>

<EventLogFloodProtectTime>10</EventLogFloodProtectTime>
<HandshakeAnchor>648422,2006-01-02 08:37:17.363</HandshakeAnchor>
<StatsDotNetWebServiceUri>

http://localhost</StatsDotNetWebServiceUri>

<QueueFlushTimeInMS>3000</QueueFlushTimeInMS>
<QueueFlushCount>100</QueueFlushCount>
<QueueRejectCount>300</QueueRejectCount>
<SleepTimeAfterErrorInMS>30000</SleepTimeAfterErrorInMS>
<LogDestinations>3</LogDestinations>
<AutoRefreshDeployments>true</AutoRefreshDeployments>
<RedirectorChangeNumber>0</RedirectorChangeNumber>
<ImportLocalPath />
<UseCookieValidation>true</UseCookieValidation>
<AutoPurgeClientEventAgeThreshold>15</AutoPurgeClientEventAgeThreshold>
<AutoPurgeServerEventAgeThreshold>90</AutoPurgeServerEventAgeThreshold>
<AutoPurgeDetectionPeriod>12</AutoPurgeDetectionPeriod>
<DoReportingDataValidation>true</DoReportingDataValidation>
<DoReportingSummarization>true</DoReportingSummarization>
<MaxNumberOfIdsToRequestDataFromUss>100</MaxNumberOfIdsToRequestDataFromUss>

<MaxCoreUpdatesPerRequest>30</MaxCoreUpdatesPerRequest>
<MaxExtendedUpdatesPerRequest>50</MaxExtendedUpdatesPerRequest>
<DownloadRegulationUrl />
<AllowProxyCredentialsOverNonSsl>false</AllowProxyCredentialsOverNonSsl>
<LazySync>true</LazySync>
<DownloadExpressPackages>false</DownloadExpressPackages>
<DoServerSyncCompression>true</DoServerSyncCompression>
<ProxyUserDomain />
<BitsHealthScanningInterval>3600000</BitsHealthScanningInterval>
<BitsDownloadPriorityForeground>false</BitsDownloadPriorityForeground>
<MaxXmlPerRequest>200000</MaxXmlPerRequest>
<MaxXmlPerRequestInServerSync>2000000</MaxXmlPerRequestInServerSync>
<MaxTargetComputers>30000</MaxTargetComputers>
<MaxEventInstances>1000000</MaxEventInstances>
<LogRolloverFileSizeInBytes>20000000</LogRolloverFileSizeInBytes>
<WUSInstallType>0</WUSInstallType>
<ReplicaMode>false</ReplicaMode>
<AutoDeployMandatory>true</AutoDeployMandatory>
<DeploymentChangeDeferral>30</DeploymentChangeDeferral>
<RevisionDeletionTimeThreshold>30</RevisionDeletionTimeThreshold>
<RevisionDeletionSizeThreshold>1024</RevisionDeletionSizeThreshold>
</Table>
</NewDataSet>

 

[markdmac]

How are you forcing the clients into WSUS? Via GPO?

I've run into problems with this where I needed to copy WUAUENG.DLL from the server down to the clients.

You need to unregister the file regsvr32 /u wuaueng.dll in order to be able to copy it. Replace the copy in DLLCACHE as well otherwise it get replaced back to the original.

Download and install BITS using the Admin account. I've also seen problems with WSUS not working if your PCs have not run through the Windows Genuine Validation Tool (manually).

If you PCs were all imaged that could cause a problem as well.

I hope you find this post helpful.

Regards,

Mark

 

[ArmedAndClueless]

All of the computers come from a wide variety of manufacturers, so identical SIDs are not an issue. The thing is that I've touched several machines to get them fully up to speed. Even the servers that get updated every Tuesday have not reported in.

With the Wuaueng.dll, do I need to unregister it on the client, the server, or both? And what's the underlying issue with that? As an added thought, when I fireup Wuauclt.exe /detectnow, or any switch for that matter, there is no output. I enter the command, and it pops back with the C:\ prompt again. I can't use /? to get the switch info.

Do I need BITS 2.0 on all the client machine for WSUS to work? I know this isn't an issue ATM, because the machines that are fully udpated aren't reporting in either.


And with the GPO, I loaded the wuau.adm template in, and configured it. The clientdiag.exe shows that the clients are able to connect to the server, namely

http://server:8530

for the updates. They just won't report in!

 

[markdmac]

With the Wuaueng.dll, do I need to unregister it on the client, the server, or both? And what's the underlying issue with that? As an added thought, when I fireup Wuauclt.exe /detectnow, or any switch for that matter, there is no output. I enter the command, and it pops back with the C:\ prompt again. I can't use /? to get the switch info.

Just the client side. Issue is that for whatever reason the client is not getting the version of the DLL it needs to have from WSUS. It is still using the version for Windows Update. Running Wuauclt.exe /detectnow will not produce any visible results. I typically just execute it from a Run command. What you are seeing is normal on that part.

Do I need BITS 2.0 on all the client machine for WSUS to work?

Yes, absolutley.

I hope you find this post helpful.

Regards,

Mark

 

[ArmedAndClueless]

I planned on posting the resolution sooner, but I got swamped by work again. Here it is:
When I was poking around in IIS, I noticed that the selfupdate folder in the WSUS administration directory didn't have anonymous users enabled. The documentation that I was following said that you only had to have selfupdate in the default site enabled for anon access, but when I turned anon access for the admin folder, the PCs started reporting in. Chalk one up to misleading documentation, and my own ineptitude.