How to Kill WSUS and Internal Database

If you have a messed up install of WSUS You will need the following.

http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/221bd010-ae12-429b-8c10-3f9d0c1ceb6c

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

http://technet.microsoft.com/en-us/library/cc708610(WS.10).aspx

For me i had to Uninstall WSUS but tell it to leave the DB. Reboot. Then find the Reg Keys as explained in one of the links. I had to delete these rather than change. After this uninstalled Windows Internal DB from Add/ Remove. The reboot. The manually delete the stuff in c:\windows\sysmsi\SQL Server 2005. Then check the :\WSUS or wherver it was installed was empty.

Then i was able to re-install from Package.

WSUS Server Setup Notes

Just remember if using GP to place computers in group you have to tell WSUS server that this is the case;

Options –> Computers –> “Use Group Policy or Registry settings on computers”

 

On replica servers ensure that the status is rolled up to the upstream server;

Options –> Reporting Rollup

 

Ensure that the Upstream server can see the status of all PC’s

Options –> Personalization –> “Include computers and status from replica downstream servers”

How can I force Group Policy to refresh on a Windows Server 2003 or Windows XP machine?

To manually force Group Policy to refresh under Windows 2000, you use the command

secedit /refreshpolicy

Microsoft has replaced this command in Windows 2003 and XP with this command:

gpupdate

You can run this command without any switches to update both machine and user policies. When you run Gpupdate on Windows 2003, the machine will display the following:

Refreshing Policy… User Policy Refresh has completed.
Computer Policy Refresh has completed. To check for errors in policy processing, review the event log.

The last line doesn’t appear on XP machines. To update only the user command components, type

gpupdate /target:user

To load only the computer command components, type

gpupdate /target:computer

The optional switches that you can use with the Gpupdate command are

/Force. This switch loads all policy settings rather than just those that have changed.

/Wait:. This switch specifies the amount of time to wait for the policy processing to finish before returning to the command prompt.

/Logoff. This switch causes the user to log off after Group Policy refreshes.

/Boot. This switch causes a reboot after Group Policy refreshes.

/Sync. This switch synchronously (i.e., in the background) applies the next boot or user logon policy (the system will prompt you to log off or reboot, depending on the /target setting).

via How can I force Group Policy to refresh on a Windows Server 2003 or Windows XP machine?.

WSUS Computer not reporting status

PC not reporting status in WSUS server.

Be patient allow 2 hours.

wuauclt

wuauclt.exe /DetectNow
wuauclt.exe /resetauthorization /detectnow

1. Stop the Automatic Updates service
2. Removing the AccountDomainSid and SusClientId values from the HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate key
3. Start the Automatic Updates service
4. Issue a wuauclt /resetauthorization /detectnow command

Log can be found at c:\windows\WindowsUpdate.log