none
WSUS Server Upgrade Plan Advice

    Question

  • Hi guys,

    Currently I'm patching my infrastructure using WSUS 3.0 SP2 running on 2003 32-bit WSUS servers with a main server at my main site and then downstream servers at my remote sites. I need to get all the servers running 2008 R2. Some of the hardware doesn't support it. The main concern though is getting the main server up to 2008 R2 as it's one of the last physical servers present and we are nearly 90% virtualized at this stage. So, I could virtualize it but that still doesn't get me to 2008 R2. So, I was thinking (happens now and again!). Could I do the following:

    1. Build a 2008 R2 WSUS server and bring it in as a downstream server
    2. Let it sync content and meta data
    3. Somehow promote it to the master server and keep all approvals etc.

    or is there a better way? Any advice would be much appreciated.

    Saturday, October 19, 2013 10:58 AM

Answers

  • Seems like this is the way to do it:

    1. Copy udate/config settings manually
    2. Copy over content
    3. Expoer/import metadata using wsutil.exe
    4. Copy approvals using the migration tool bundled with the API samples.
    • Marked as answer by shocko Monday, October 21, 2013 11:49 AM
    Monday, October 21, 2013 11:49 AM
  • Hi Lawrence,

    How do I sync the approvals though and promote the downstream server?

    Install the new server as a *replica* server. Updates, Target Groups, and Update Approvals are automatically synchronized to a replica server. Such is the exact nature of a replica server, and why it's perfectly suited for this purpose.

    Once the new server has completely finished replicating from the old server, go to Options | Update Source and Proxy Server on the new server, and configure it to synchronize from Microsoft.

    Synchronize with Microsoft to ensure functionality and get any newly released updates.

    Point the other downstream servers to the new one (as well as any clients) and life goes on.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by shocko Wednesday, October 23, 2013 9:44 AM
    Tuesday, October 22, 2013 9:41 PM
    Moderator

All replies

  • I think, the best way to do that, is to use the WsusUtil Export and  WsusUtil Import. This will Export/import MetaData. You will have to copy update files too.

    David COURTEL
    IT Technician
    Wsus Third-Party Softwares Publishing : http://wsuspackagepublisher.codeplex.com

    • Edited by DCourtel Saturday, October 19, 2013 12:51 PM
    Saturday, October 19, 2013 12:51 PM
  • Thanks David,
    Would make sense. So essentially you could just copy all the content files and then import the WSUS config settings and update metadata using the utility?
    Monday, October 21, 2013 8:59 AM
  • Reading this Technet Article I realize that you will lost all Approvals. Not a big problem but can be annoying to re-set all these approvals.

    If you use this method, after WsusUtil Import, you should also launch a WsusUtil Reset (Be aware of that the CPU will be at 100% for a while).


    David COURTEL
    IT Technician
    Wsus Third-Party Softwares Publishing : http://wsuspackagepublisher.codeplex.com

    • Edited by DCourtel Monday, October 21, 2013 10:24 AM
    Monday, October 21, 2013 10:24 AM
  • Seems like this is the way to do it:

    1. Copy udate/config settings manually
    2. Copy over content
    3. Expoer/import metadata using wsutil.exe
    4. Copy approvals using the migration tool bundled with the API samples.
    • Marked as answer by shocko Monday, October 21, 2013 11:49 AM
    Monday, October 21, 2013 11:49 AM
  • Could I do the following:

    1. Build a 2008 R2 WSUS server and bring it in as a downstream server
    2. Let it sync content and meta data
    3. Somehow promote it to the master server and keep all approvals etc.
    YES! And that is the recommended, and time-proven methodology for doing exactly what you need to do.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, October 21, 2013 10:43 PM
    Moderator
  • Hi Lawrence,

    How do I sync the approvals though and promot the downstream server?

    Tuesday, October 22, 2013 7:50 AM
  • Hi Lawrence,

    How do I sync the approvals though and promote the downstream server?

    Install the new server as a *replica* server. Updates, Target Groups, and Update Approvals are automatically synchronized to a replica server. Such is the exact nature of a replica server, and why it's perfectly suited for this purpose.

    Once the new server has completely finished replicating from the old server, go to Options | Update Source and Proxy Server on the new server, and configure it to synchronize from Microsoft.

    Synchronize with Microsoft to ensure functionality and get any newly released updates.

    Point the other downstream servers to the new one (as well as any clients) and life goes on.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by shocko Wednesday, October 23, 2013 9:44 AM
    Tuesday, October 22, 2013 9:41 PM
    Moderator
  • Thanks Lawrence
    Wednesday, October 23, 2013 9:45 AM