How to move WSUS from one server to another

How to move WSUS from one server to another

  • Comments 19
  • Likes

TipSometimes you may find that it’s necessary to move your WSUS server from one machine to another.  If this is you then here are the steps to get this done:

1. Install WSUS on the new Server just as you had installed before.

For more information on installing WSUS please check the following link for more information: http://technet.microsoft.com/en-in/library/cc708445(en-us).aspx

2. Match the Advanced Options on the old WSUS Server & the new WSUS Server

Ensure that the advanced synchronization options for express installation files and languages on the old server match the settings on the new server by following the steps below:

  1. In the WSUS console of the old WSUS server, click the Options tab, and then click Advanced in the Update Files and Languages section.
  2. In the Advanced Synchronization Settings dialog box, check the status of the settings for Download express installation files and Languages options.
  3. In the WSUS console of the new server, click the Options tab, and then click Advanced in the Update Files and Languages section.
  4. In the Advanced Synchronization Settings dialog box, make sure the settings for Download express installation files and Languages options match the selections on the old server.

3. Copy Updates from File System of the old WSUS Server to the new WSUS server*

To back up updates from file system of old WSUS server to a file, follow these steps:

  1. On your old WSUS server, click Start, and then click Run.
  2. In the Run dialog box, type ntbackup. The Backup or Restore Wizard starts by default, unless it is disabled. You can use this wizard or click the link to work in Advanced Mode and use the following steps.
  3. Click the Backup tab, and then specify the folder where updates are stored on the old WSUS server. By default, WSUS stores updates at WSUSInstallationDrive:\WSUS\WSUSContent\.
  4. In Backup media or file name, type a path and file name for the backup (.bkf) file.
  5. Click Start Backup. The Backup Job Information dialog box appears.
  6. Click Advanced. Under Backup Type, click Incremental.
  7. From the Backup Job Information dialog box, click Start Backup to start the backup operation.
  8. Once completed, move the backup file you just created to the new WSUS server.

To restore updates from a file to the file system of the new server, follow these steps:

  1. On your new WSUS server, click Start, and then click Run.
  2. In the Run dialog box, type ntbackup. The Backup or Restore Wizard starts by default, unless it is disabled. You can use this wizard or click the link to work in Advanced Mode and use the following steps.
  3. Click the Restore and Manage Media tab, and select the backup file you created on the old WSUS server. If the file does not appear, right-click File, and then click Catalog File to add the location of the file.
  4. In Restore files to, click Alternate location. This option preserves the folder structure of the updates; all folders and subfolders will appear in the folder you designate. You must maintain the directory structure for all folders under \WSUSContent.
  5. Under Alternate location, specify the folder where updates are stored on the new WSUS server. By default, WSUS stores updates at WSUSInstallationDrive:\WSUS\WSUSContent\. Updates must appear in the folder on the new WSUS server designated to hold updates; this is typically done during installation.
  6. Click Start Restore. When the Confirm Restore dialog box appears, click OK to start the restore operation.

4. Copy Metadata from the Database on the old WSUS Server to the new WSUS Server **

Note: The WSUS Setup program copies WSUSutil.exe to the file system of the WSUS server during installation. You must be a member of the local Administrators group on the WSUS server to export or import metadata; both operations can only be run from the WSUS server itself and during the import or export process, the Update Service is shut down.

To export metadata from the database of the old Microsoft Windows Server Update Services Server, follow these steps:

  1. At a command prompt on the old Microsoft Windows Server Update Services Server, navigate to the folder that contains WSUSutil.exe. (usually located at c:\Program Files\ Update Services\tools\).
  2. Type the following: wsusutil.exe export packagename logfile ...(For example: wsusutil.exe export export.cab export.log) The package (.cab file) and log file name must be unique. WSUSutil.exe creates these two files as it exports metadata from the WSUS database.
  3. Move the export package you just created to the new Microsoft Windows Server Update Services Server.

To import metadata into the database of the new Microsoft Windows Server Update Services Server, follow these steps:.

Note: It can take from 3 to 4 hours for the database to validate content that has just been imported. Please be patient.

  1. At a command prompt on the new WSUS server, navigate to the directory that contains WSUSutil.exe. Type the following: wsusutil.exe import packagename logfile (For example: wsusutil.exe import export.cab import.log).
  2. WSUSutil.exe imports the metadata from the old WSUS server and creates a log file of the operation.

5. Point your Clients to the new WSUS Server.

Next we’ll need to change the Group policy and make it point top the new server.  To redirect Automatic Updates to a WSUS server, follow these steps:

  1. In Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then click Windows Update.
  2. In the details pane, click Specify Intranet Microsoft update service location.
  3. Set the intranet update service for detecting updates box and in the Set the intranet statistics server box. With the new server details and port For example, type http(s)://newservername :Port in both boxes.

Note: For more information check http://technet.microsoft.com/en-us/library/cc720539.aspx

That’s it!

*Important:

The initial settings for access control lists differ between Windows 2000 Server and Windows Server 2003. If you are copying content from Windows 2000 Server to Windows Server 2003, you have to manually add the Network Service group to the access control list for the folder where updates are stored. Give the Network Service group Full Control.

**Important:

Never import exported data from a source that you do not trust. Importing content from a source you do not trust might compromise the security of your WSUS server.

Sudheesh Narayanaswamy | Support Engineer

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Sorry, but this procedure does not seem to work.

    I have just attempted this as a migration path from Windows 2003 and WSUS 3.0 SP1 to Windows 2008 and the WSUS role.

    Despite the source server being up to date, and the destination server having fewer selected products than the source, the destination server attempted to download 45GB of updates rather than use the existing copies on disk. It's worth noting that in this "backwater" (?) country (Australia!!) 45GB is a reasonable monthly quota for a household with very heavy usage, and a significant chunk of change for many corporates (who are still slugged up to 19c/MB for Internet data traffic) - $5000 for this little effort.

    Furthermore, this procedure did not migrate computer groups, approvals, auto-approval rules, email notification settings, or product and update type selections.

    A far, far better approach would be to reconfigure the database so it supports detach/attach semantics (even with Windows Internal Database, not just SQL Server) rather than throwing signature errors after attach; or that runs a series of BCP scripts to move the table data, or even simply automatically backs up the database, restores it to the new server, copies the content and executes "wsusutil movecontent -skipcopy" to relocate the content data.

    eg:

    wsusmigrate oldserver newserver temppath newcontentpath

    wsusmigrate oldwsus3 newwsus3 %TEMP% E:\WSUS

  • I tested this in my VMWARE workstation client POC lab and it just works fine... thanks !!!

  • I agree with David.Rawling. This procedure does not work.

    Unlike David, I attempted the move between two different instances of Windows 2003, WSUS 3 SP1. Which should be more likely to work.

    It only successfully moved the list of patches over, the patches themselves were disconnected. i.e every patch says 'the files for this need to be downloaded'.

    From googling around it seems the only way to get a decent backup is just to have more that one WSUS and have them mirror each other.

    Restoring a backup of either the content dir or the whole WSUS dir does not work.

    The wsusutil.exe import command does make the patch list appear after the restore from backup.

  • Hi,

    For me above proceedure had worked perfectly. Just thinks to remember: You should have backup of:

    1) Documentation how wsus has configured

    2) SQL backup. This will work incase your server been completely crashed. Because in that case you can simple install wsus & restore SQL database. Then you can go for export/import of metadata.

    3) or periodically export your metadata backup

    4) Schedule monthly incremental backup of wsus content.

    Please suggent if any. you can also reach me at sunadupadhye@yahoo.co.in

    Again i would like to thanks Sudheesh Narayanaswamy that i pull me out from trouble.

  • Q.

    What would happen if you just. Install a new wsus 3.0 sp2 on win 2008. And at the intinial install. You just point to the old wsus 3.0 instead off the default windows update service on the internet. and select it as it's replica partner. And start the first time connect. After sync has finished.  Changing the default options to your liking. And pointing to the internet for it's updates. and sync again.

  • Q.

    What would happen if you just. 1. Install a new wsus 3.0 sp2 on win 2008. 2. And at the initial install. You just point to the old wsus 3.0 instead off the default windows update service on the internet. 3. And select the old wsus 3.0 as it's replica partner. Then start the first time connect. After sync has finished. Pointing to the internet for it's updates by changing the options. And change the default options further to your liking. and sync again.

    wait wait refresh computers groups view :)

    I'am new sorry

  • I have completed the move, before pointing PC's to new server with GPO editor I opened WSUS on new server.

    Like David Rawling experience all updates are 'not approved'.

    I wondered same thing as leafer and may uninstall and try it. Will it work to mirror a WSUS server sync with old server, break mirror and point to internet.

  • I have had mixed responses from many with the Sucess and failure . Just to summaries i would feel along with the WSUSutil import - export if we use the wsusmigration tool also we can make aure that theour migration is correct.

    Note: Dont remove your old server unless and util you are 100 sure that the migration is completed 100%

    To the question leafer what i would say is this is actually to compltely remove the old server from the network. Else the approach you had said would work well . Suggestion though :)

  • I am sorry wheteher this is the right place to ask.

    FYI, the existing condition I have one upstream server and 3 downstream servers.  Since teh boxes are old and my boss ask me whetehr I can install WSUS3 sp2 on the VMware or HyperV?  I will keep the same as the current condition i.e., 1 upstream and 3 downstream.

    thanks

  • can you send me Backup and restore for WSUS with snap sort stap by stap

  • can you send me Backup and restore for WSUS with snap sort stap by stap

  • Where can i find info about how to move wsus server databases from one remote sql server 2005 to another remote sql server 2005.

    I found info about how to move from internal database to remote sql.

  • Small remark, export Updates View from old Wsus snap-in and import to new server. WsusContent folder just copy between servers.

    Old cfg: Wsus 3.0 Sp2, DB on local host SQL Server Std, Content stored localy.

    New cfg: Wsus 3.0 Sp2, remote DB on old SQL Server Std, Content moved (copy/paste) from old to new server drive\folder.

    regards

  • @David.Rawling Count yourself lucky you don't live in New Zealand then. Would cost about $95 for 45GB of downloads for month plus there is still a large portion of the country not upgraded to ADSL2+ yet. Business is slightly more expensive than that.

  • Hi, i want to move wsus 2003 to 2008 r2 permanently (both the system has installed wsus 3.0 s2.... can i do same step