Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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!


share|improve this question
How long has it been "stuck"? – MDMarra Aug 9 '12 at 17:35
We ran it overnight, so at this point 14-16 hours. – George Aug 9 '12 at 18:48
up vote 1 down vote accepted

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.

  1. Install WSUS on new server. Use a local database.
  2. During configuration wizard choose "Synchronize from another WSUS server…", and provide your original host.
  3. Wait for initial synchronization to complete. In my case this took several hours.
  4. Change the new server from a replica to standalone.
  5. Install the WSUS API Tools on both systems.
  6. Export settings with "wsusmigrationexport.exe settings.xml"
  7. Copy settings.xml to new server
  8. Import settings with "wsusmigrationimport.exe settings.xml All None"
  9. Cut over your hosts to the new system via group policy. I started with a few targeted OUs to test and expanded from there.
share|improve this answer
Whether the database is local or not really doesn't impact it much, other than it could possibly be one less thing to worry about. SQL permissions are fairly straightforward for WSUS. – nojak Aug 10 '12 at 3:30
@nojak - I think the issue I ran into was the NTFS permissions from attempting to copy the database from server to server, not within SQL itself. :) – Tim Brigham Aug 10 '12 at 13:27
I was just putting that comment on there for people that read it in the future, so that they don't think they have to use a local db. I figured you had your reasons for doing so. – nojak Aug 10 '12 at 13:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.