Sun, Jul 1 2012 9:12
Windows Update error 800B0001
If you installed the Windows update engine update to your workstations, you'll find that they can no longer communicate with WSUS.
On Jun 29, 2012, at 4:39 PM, "Lawrence Garvin" wrote: > Yes. That is the expected behavior. Browsing to Windows Update caused the > Windows Update Agent to be updated to the v7.6 build which cannot > communicate with a v3.2.7600.226 WSUS server. One of the components baked > into the WSUS update is an update to the Windows Update Agent. > > You'll either need to patch the WSUS server immediately, or rollback the > Windows Update Agent installation(s) to the v7.4 or v7.5 WUAgent. > > Note: From what I've seen, most of the issues with the WSUS update have > occurred when attempting to install the update *from* the WSUS server (e.g. > by having the WUAgent install the update as a WSUS approved update). We saw > a lot of this when WSUS3SP1 and WSUS3SP2 were released as well. > > My recommendation is to download the package from the Microsoft Download > Center and install the update from the command line of the WSUS server. I > have done this on a few servers already and I have not had any issues at all > applying the update. >
If you update the WU agent on the workstations, they now have the hardening stuff and can no longer "talk" to WSUS. You now have to install the update for WSUS 2720211.
This sucker is an all or nothing. You can't just update the clients without needing the server up'd as well.
Set up WSUS. To do this, at a command prompt, type one of the following commands, as applicable to your system:
Filed under: News
- WSUS-KB2720211-x64.exe /q C:\MySetup.log