Below are the steps for SBS 2011*: * For the SBS 2008 the steps are the same, but WSUS 3.0 SP2 will need to be downloaded from the Microsoft site. It will be more difficult to move the WSUS DB later.
To move the location, change the C:\WSUS to another drive.
Here’s a great tip from Rob Coffey, a real life WSUS support engineer from North Carolina.
We’ve seen reports of this occurring if you upgrade to WSUS Service Pack 1 and then remove the SP although I haven’t been able to confirm this myself.
Updating of computer equipment is an aspect often overlooked by companies because there are too many constraints.
It is necessary to manage downtime, while patches provide sometime malfunctions.
However WSUS can’t be used alone in a big IT infrastructure requiring automation.
This product doesn’t have a granular scheduler to deploy update. SCCM has a system role called Software Update Point (SUP). When it is set, SCCM can manage updates catalog and binaries to make updates packages.
More specifically I want to talk about the most common issue I see with my customers.On the next part, I will present the configuration of an SUP point. But it is the same process when WSUS is installed on another server.After integration of WSUS in SCCM hierarchy, I will deploy updates by two different methods: Once SUP is configured correctly, the catalog of updates appears in SCCM console.If you have a bunch of clients trying to get updates and failing with a 0x80190194 error then this may be something to check: ======== The client starts its detection cycle by checking if it’s running a compatible version of the client prior to talking to the WSUS server. This is done by downloading therefore if the selfupdate virtual directory has been removed or is missing then the clients will fail with the 0x80190194 error when attempting to check for the file.