A particular machine had been giving me fits on security updates since it had been built in a remote site. It had never successfully installed any security update deployment pacakge. The machine was being used by a software developer, so finding time to work on it was difficult.
The WUAHandler.log was filled with the following:
Its a WSUS Update Source type ({FA4813DE-1024-4E08-BECA-75C44C30C834}), adding it.
Existing WUA Managed server was already set (http://siteservername:8530), skipping Group Policy registration.
Added Update Source ({FA4813DE-1024-4E08-BECA-75C44C30C834}) of content type: 2
Failed to run BeginSearch() on WUAgent. Error = 0x80004002.
When I finally gained access to the machine, I remoted in and decided to try to hit the Windows Update site, despite my knowledge that it was being blocked. The fact that the machine wanted to install the latest update agent clued me in on a possible problem.
The download page for the lastest verion of the Windows Update Agent is:
http://support.microsoft.com/kb/949104
Once I downloaded and installed this agent, the machine functions as expected.
After receiving approvals for setting up Branch Distribution Points in two of our remote sites, I began building and configuring the workstations in our lab. I had decided to ensure all of our necessary packages were replicated to the sites prior to shipping the boxes to their new homes.
I was a little perplexed when it was taking hours to replicate very small packages. After some searching I found the culprit - the default value for BITS in the Computer Client Agent Properties is set to 20 kbps. Just thought I would compose a small informative note so that others who may encounter this characteristic can quickly resolve the replication slowness.
You can find a discription of the setting options here: http://technet.microsoft.com/en-us/library/bb633140.aspx
Here is a picture of the dialog box tab:
