Renaming WSUS server before or after Migration and Process?


  • Hello. I'm wanting to migrate our current WSUS server to a new box which also has a different name. Ive found several articles on the migration part but not much on the rename part when doing both. Here is what I have.

    Currently Windows 2003 Standard SP2
    Want to go to Windows 2008 Enterprise R2 X64.
    Using current WSUS version 3.2.7600

    Since the new server has a different name than the old will that affect anything. I looked here and currently the WSUS db points here:
    SQLSVRNAME= %computername%\MICROSOFT##SSEE

    I just want to make sure that my approvals, declined updates, groups and rules all pull over. Just not sure about the naming part. I was going to post the links I'm using for migration, but as I started, IE crashed and I lost the tabs. Go figure.


    Friday, April 06, 2012 1:48 PM


All replies

  • If you move your WSUS server you will need to update the GPO with the new WSUS name (edit the Specify intranet Microsoft update service location policy), so clients will know where to go for updates; if not they will try the old server name.

    Follow this guide to move your WSUS server to a new box

    Adrian Costea - MCP, MCTS, MCSA 2003, MCITP: Windows 7

    My Blog:

    • Marked as answer by Carito Monday, April 09, 2012 1:19 PM
    Saturday, April 07, 2012 8:04 AM
  • Thanks Adrian.

    I know I need to update all my GPOS that point back to the various groups in WSUS. Thats not a problem. I was more talking about the embeded database. I wasnt sure if the server name was in the db somewhere or not and needed to be updated. If all I have to worry about as far as the server name goes are the GPOs I'm set.

    Saturday, April 07, 2012 1:36 PM
  • Hi Carito,

    I think the following link may give you some insights:

    Best regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Carito Monday, April 09, 2012 1:19 PM
    Monday, April 09, 2012 3:32 AM
  • Clarence thanks. I beleive over the weekend I got everything up and running, al GPOs reconfigured etc. I was able to add the server as a replica and sync. I only had one issue if it even is an issue.

    When I opened the applicationhost.config file for IIS 7 and modified the

     <system.webServer><modules> tag, remove <add name="CustomErrorModule">, if it is present.

    3. In the <system.webServer><modules> tag, add <remove name="CustomErrorModule">.

    That pretty much crashed IIS. Application pools would not run, services would not run etc etc. Nothing worked until I put the line back the way it was. One post says this is not a needed step another says it is. No idea.

    Monday, April 09, 2012 1:24 PM
  • One post says this is not a needed step another says it is. No idea.

    If the change caused problems, then leave it unchanged. The change is functionally insignificant.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile:

    Wednesday, April 11, 2012 2:30 AM