WSUS synchronization stuck and 0%

windows-server-2003windows-server-2008wsus

I, now, have two WSUS servers (one is running on Windows Server 2003 and the other on Windows Server 2008), I am trying to decommission one of them. I followed the instructions on how to move WSUS server. I am trying to sync the two servers via Update Service console, before I decommission it, but it's getting stuck at 0%.

What am I doing wrong? Am I missing something? Please, help!

Thanks!

Best Answer

I've had strange things happen when trying to use the file system copy route for this kind of migration. In retrospect I think it was mostly due to file system permissions issues either on the updates or the database. I found it easier to axe the new WSUS instance and start over.

This is the method I use.

Install WSUS on new server. Use a local database.
During configuration wizard choose "Synchronize from another WSUS server…", and provide your original host.
Wait for initial synchronization to complete. In my case this took several hours.
Change the new server from a replica to standalone.
Install the WSUS API Tools on both systems.
Export settings with "wsusmigrationexport.exe settings.xml"
Copy settings.xml to new server
Import settings with "wsusmigrationimport.exe settings.xml All None"
Cut over your hosts to the new system via group policy. I started with a few targeted OUs to test and expanded from there.

Related Solutions

Windows XP laptop doesn’t appear in WSUS All computers list

Clearly you can ping a server, but you can't communicate with WSUS on the WSUS port.

Been a while since I used WSUS 2.0, and I can't remember if I was using port 80 or some other port, but I always specified the port that I was using:

"WUStatusServer"=http://wsusserver:8530

-- and you need to check the spelling of your server name in the GPO: that's an easy mistake to make.

You need to check what port the server is using, and that nothing else has grabbed that port, and that the firewall at both server and client allows connection on that port.

WSUS not detecting computers

There is a whole bunch of possible issues here:

Is the WSUS actually operating on the defaults ports as you say ? It could be using the alternate config.
The pfSense suggest the WSUS server is in another subnet as the clients. Are you sure the URL used in the policy is actually valid from the clients perspective ?
Is the policy really deployed to the clients ? Check if the registry keys are created on a client computer. GPUPDATE /FORCE is your friend.
On a client run "wuauclt /DetectNow" from a command prompt. Check WindowsUpdate.log (in C:\Windows or c:\Winnt) to see what is happening.

Best Answer

Related Solutions

Windows XP laptop doesn’t appear in WSUS All computers list

WSUS not detecting computers

Related Topic