|
WSUS SUS Wiki Community |
SYMPTOMS Operating system: Unknown Cause This is casued by the AU client having trouble accessing the computer information using WMI, thus preventing the client from updating its OS information on the server. In the RC release, this has the side effect of the client not getting updates, leaving the client potentially insecure. Workaround As a workaround, please run the following command on the server to unblock the client from receiving updates.
osql -E -S <SqlServerName> -Q "UPDATE SUSDB.dbo.tbComputerTarget SET IsRegistered=1 where IsRegistered = 0" where <SqlServerName> is the SQL server you are using or%computername%\wsus if you are using WMSDE. Note that this would still leave the client information as unknown, but the client will start receiving updates. Status This behavior will be corrected in the final release. Comments:From rajivpn - 4/15/05 1:26 PM Last Modified 4/7/05 1:14 PM | Hide Tools |
Jason from the WSUS OEP newsgroup has some information of repairing WMI issues on the client.
<snip>
Stop the "Windows Management Instrumentation" Service
Go to "system32\wbem" folder
Delete the "repository" folder
Start the "Windows Management Instrumentation" Service
run "wuauclt /detectnow" to force check.
</snip>