locked
WSUS Upgrade RRS feed

  • Question

  • Hi,

      My WSUS server is running server 2008 R2 with WSUS 3.0 sp2 installed. The server is running fine without any issues. However  I would like to be able to manage WSUS a bit better by upgrading the server from server 2008 R2 to Server 2012 R2. The upgrade would allow me to take advantage of the built in WSUS PowerShell tools. Has anyone upgraded their WSUS servers without any major issues? What do you recommend...upgrade or Clean install? any assistance would be greatly appreciated.

       


    Flite23
    • Edited by Flite23 Monday, January 5, 2015 4:14 PM
    Monday, January 5, 2015 4:13 PM

Answers

  • No sir, i do not know! Thanks for the reasoning behind it. The supported way is for sure the way you would want to go.

    • Edited by Adam Schildmeyer Tuesday, January 6, 2015 4:36 PM
    • Marked as answer by Flite23 Thursday, January 8, 2015 7:44 PM
    Tuesday, January 6, 2015 4:36 PM

All replies

  • I would recommend doing a fresh install. If you want to migrate settings and updates look at these two articles found here and here.

    I recommend that because when your server does an in place upgrade it might try and stuff all the updates into the windows.old directory as a backup. Usually if they are found on the C drive that is.

    Monday, January 5, 2015 5:24 PM
  • by upgrading the server from server 2008 R2 to Server 2012 R2.

    This requires the following steps:

    1. Uninstall the WSUS and Web Server roles, and the WID Feature.
    2. Upgrade the OS.
    3. Install the Web Server role, WSUS role, and WID feature.

    And that's even assuming that your machine running Windows Server 2008 R2 is capable of running Windows Server 2012 R2.

    Has anyone upgraded their WSUS servers without any major issues?

    No, and it's quite explicitly documented in the WSUS v6 Release Notes that attempting to do this will permanently BREAK your WSUS installation and require you to reformat and reinstall the operating system. I would highly encourage reading the documentation prior to making any changes.


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

    Monday, January 5, 2015 7:02 PM
  • I would recommend doing a fresh install. If you want to migrate settings and updates look at these two articles found here and here.

    Neither of those two articles apply to this scenario. :-)

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

    Monday, January 5, 2015 7:03 PM
  • I figured it applied to the scenario of a clean install but maintaining his approved updates and all files so he wouldn't have to download again. But I guess they could be wrong since its same generation or 2000 to 2003. It appears someone also did 2008 R2 to 2012 WSUS using this method.

    Monday, January 5, 2015 7:52 PM
  • It appears someone also did 2008 R2 to 2012 WSUS using this method.

    Perhaps.

    But it's not a supported migration methodology.

    Most notably it installs a WSUS v3 database to a WSUS v6 server.

    The procedure is critically defective in that it fails to note the *required* condition that KB2734608 MUST be applied to the WSUS v3 server prior to making the database backup.

    Even then, this is all predicated on the presumption that the database *schema* for WSUS v6 is identical to the database schema for WSUS v3. I don't know that to be a fact. Do you? :-)


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

    Tuesday, January 6, 2015 4:09 PM
  • No sir, i do not know! Thanks for the reasoning behind it. The supported way is for sure the way you would want to go.

    • Edited by Adam Schildmeyer Tuesday, January 6, 2015 4:36 PM
    • Marked as answer by Flite23 Thursday, January 8, 2015 7:44 PM
    Tuesday, January 6, 2015 4:36 PM
  • Thank you everyone for your responses. I have decided to setup a new server with Server 2012R2 and I am going through the process now. I have a few more questions that maybe someone could help with.

    1. What are the main differences between WSUS v3 and v6.

    2. Will the computers subscribed to the new server require a new WSUS client to be installed? 

    3. The new WSUS server uses port 8530. Do I need to change anything on the client side?


    Flite23

    • Edited by Flite23 Friday, January 16, 2015 3:45 PM
    Friday, January 16, 2015 3:39 PM
  • Flite23,

    1. Lawrence in this thread answered that question in another forum post.

    2. Possibly, but its not a WSUS agent. Its just updating the windows update service on the local computer. This will happen when the client machine does a check with the update server by itself and should require you to do anything.

    3. The WSUS install will default to port 8530 because it doesn't want to conflict with port 80 or 443 if by chance something else is using it. If you are aware of nothing using you can change it or just let it be port 8530. On your old WSUS install if it was using port 80 or a different port you will have to modify your GPO used for updates to reflect using port 8530. Your GPO should show a http:// address to your old WSUS server. if it was port 80 it should just look like http://mywsusserver Just make sure it has :8530 at the end of the address. So it would appear like http://mynewwsusserver:8530 for example.

    Friday, January 16, 2015 3:55 PM