Skip to content
English
More support Sign in
Contact us
  • There are no suggestions because the search field is empty.

Windows Server In-Place Upgrade

Search

Windows Server In-Place Upgrade

Upgrade Prep Day 1:  

  1. Download the necessary files (Windows Server 2012 Standard Edition, Windows Server 2019 Standard Edition,  SQL Server 2017) 

    1. Windows Server 2012 Std. Edition: https://drive.google.com/drive/folders/1KFO_uwDF8E-rukewTkqCx0Ur-QpQEn_j

    2. Windows Server 2019 Std. Edition: https://drive.google.com/drive/folders/1MsyqD2hLWiL9bfw_E9sa83B5weH9FRth

    3. SQL Server 2017 https://drive.google.com/drive/folders/10IlnI_CHsp_3CX9KCtNLu4bzdT9Vpfmh

  2. Check Duplicati to see when the last successful waivers & files backup was. If it was unsuccessful for a day or more and the location has a backup server available, zip the folders up and back them up to C:\Clubspeed\CSBack on the backup server. 

  3. If the location has a backup server: 

    1. Create a folder on the C: drive on the backup server named “YYYYMMDDHHMMPM/AM_WindowsServerBackup” and map it as a network drive. Add the Windows Server Backup feature through Server Manager, once it’s added, open the Windows Server Backup utility and run a full server backup to the shared network folder you made earlier.

Upgrade Prep Day 2/Upgrade Process:

  1. Truncate ClubspeedLog DB, then zip up C:\Clubspeed\SQL and move the .zip file to C:\Clubspeed\CSBack, upload it to Google Drive, and check splashtop for the location’s backup server. If one is available, back the files up to C:\Clubspeed\CSBack. 

  2. Backup ClubspeedV8 DB to C:\Clubspeed\CSBack, zip up and upload to Google Drive, and check splashtop for the location’s backup server. If available, back the .bak file up to C:\Clubspeed\CSBack as well. 

  3. Open server manager, expand the roles on the left side, and click "remote desktop services"'

    1. Scroll down to the "role services" section, click "remove role services" 

    2. Deselect "Remote desktop session host", "remote desktop connection broker", "remote desktop virtualization host", and "remote desktop web access."  (Not all of these might be installed on the server)

    3. Click "next", then click "remove"

    4. It should prompt you for a restart, go ahead and restart the server.

    5. Once restarted, the "resume configuration wizard" should pop up with a progress bar. Once it is done, make sure it says "removal succeeded", and click "Close."

      1. If a restart is prompted, click “Yes” to restart the server.

Upgrading to Windows Server 2012R2

  1. Navigate to the Server 2012 .iso file you downloaded, right click it, highlight 7-zip, click "extract files", click "OK."

    1. Navigate to the folder that's created, navigate to the "support" folder, then navigate to the "adprep" folder.

    2. Open a command prompt in the adprep folder by clicking the folder path bar, typing in "cmd", then clicking enter. 

    3. Run the following commands:

      1. adprep /forestprep

        1. After you run this command, type in 'C' in response to the prompt and click enter. 

        2. Verify there are no errors and that you get the "Adprep successfully updated the forest-wide information" message. Move on to the next command.

      2. adprep /domainprep

        1. Verify there are no errors and that you get the "Adprep successfully updated the domain-wide information" message. 

  1. Navigate to the Server 2012 install folder that you extracted from the ISO earlier, and run "setup.exe" 

    1. Click "Install now" 

    2. Click "Go online to install updates now (recommended)

    3. Enter the product key given to you, then click "Next"

    4. Select "Windows Server 2012 R2 Standard (Server with a GUI)"

      1. IMPORTANT: DO NOT MOVE ON WITHOUT VERIFYING THE CORRECT OS IS SELECTED

    5. Click Next, accept to the terms, click next again.

    6. Select "Upgrade: Install Windows and keep files, settings, and applications.

  2. You should see a compatibility report. Scroll down to the "Installing Windows will affect these devices" section, and make sure nothing related to RAID drivers/utilities or hard drives is listed here. If there is something related listed, please consult with a shift lead or management.

    1. Note: You may be prompted for a restart at this point. You can hit “close”, exit out of the setup, restart the server, then start the setup again from step 3.1.

  3. Click "Next", the upgrade should now start. The server will restart multiple times in order to complete the upgrade. (This process should take between 1 ½ - 2 ½ hours+ to complete.

Once the upgrade to 2012r2 is done, follow these steps:


  1. Navigate to the Server 2019 .iso file you downloaded, right click it, highlight 7-zip, click "extract files", click "OK.

  2. Navigate to the folder that's created, navigate to the "support" folder, then navigate to the "adprep" folder.

  3. Open a command prompt in the adprep folder by clicking the folder path bar, typing in "cmd", then clicking enter. 

    1. Run the following commands:

      1. adprep /forestprep

        1. After you run this command, type in 'C' in response to the prompt and click enter. 

        2. Verify there are no errors and that you get the "Adprep successfully updated the forest-wide information" message. Move on to the next command.

      2. adprep /domainprep

        1. Verify there are no errors and that you get the "Adprep successfully updated the domain-wide information" message. 

  1. Navigate to the Server 2019 install folder that you extracted from the ISO earlier, and run "setup.exe" 

    1. Select "Download updates, drivers and optional features (recommended), and click "Next"

    2. Select "Windows Server 2019 STANDARD (DESKTOP EXPERIENCE)" from the operating system list.

      • IMPORTANT: DO NOT MOVE ON WITHOUT VERIFYING THE CORRECT OS IS SELECTED

    3. Accept to the terms and conditions

    4. Select "Keep personal files and apps" and click next. 

    5. On the "what needs your attention page", you may see the message "Plug and Play and RemoteFX USB device redirection is disabled by default in this version of Windows. You can re-enable this setting in Group Policy". Click the "Confirm" button on the right side of the screen, then click "Refresh"

      • You may also see a message that states that the Intel HD Graphics P530 is not compatible with Windows Server 2019. This is normal, click "Confirm", then hit "Refresh."

    6. You should now be at the "Ready to install" page. Confirm that the two check boxes are as stated below. If they are not, click "back" and refer to the above steps to pick the correct settings. If everything is correct, click "Install." 

      • Install Windows Server 2019 Standard (Desktop Experience) 

      • Keep personal files and apps

    7. The upgrade along with the installation of all updates may take up to 4-5 hours+ to finish. 


Once the upgrade to 2019 is done, follow the below steps:


  1. Set the startup type of Main Engine to Automatic (Delayed) in FireDaemon.

  2. The IIS URL rewrite module has to be installed. (you have to manually download the x64 installer) (you may need to remove it and then reinstall it.) The issue is that a few app pools such as sp_admin, ClubSpeedServices, and DefaultAppPool crash if the rewrite module isn’t reinstalled.

    1. https://download.microsoft.com/download/1/2/8/128E2E22-C1B9-44A4-BE2A-5859ED1D4592/rewrite_amd64_en-US.msi  

  3. In Step 28 of the 2019 Manual Build article: (https://clubspeed.freshdesk.com/a/solutions/articles/47001112009) , the following steps need to be done: 

    1. "Install Remote Desktop", “ Adding a RD Licensing Server", "Setting Collection & Session", and "Edit group policy settings" sections needed to be completed. 

      1. When performing the “Edit group policy settings step, typing in gpedit.msc in the start menu will not work. You need to navigate to C:\Windows\SysWOW64 and launch gpedit.msc.

    2. Open Remote Desktop Licensing Server, right click the server, point to “Advanced”, then click “Reactivate Server.” For the “Name” field you can put in the track name, and you can use support@clubspeed.com  for the “Email” field..

      1. NOTE: For AIS in-place upgrades, use “justin.tomkins@autobahnspeed.com ” for the email. 

  4. Open this article (https://clubspeed.freshdesk.com/a/solutions/articles/47001112009 ) and follow the steps under “Re-enabling Environment Setting” in order to add the needed registry key.

  5. Uninstalling SQL Server 2012 or 2008 will not work through Apps and Features because the path to the uninstall application changes after the Windows Server Upgrade. To get around this, you need to navigate to the uninstall application manually. 

  6. Navigate to C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64 and run “SetupARP.exe”.

    1. For SQL Server 2008, the path is C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x64.

  7. Click “Remove” and click “OK” on the “Setup Support Rules” window. Once the “Select Instance” window appears, click “Next”, click “Select All”, click “Next”, click “Next”, then click “Remove.”

  8. The removal should now be completed, hit “Close” and refresh Apps & features, you should not see SQL Server 2012/2008 anymore.

  9. A server restart is needed before installing SQL Server 2017. 

  1. To install SQL Server 2017, follow the instructions in this article: https://clubspeed.freshdesk.com/a/solutions/articles/47001111933

      7. Reinstall Node: 

  1. Open Powershell and run this command:

    1. get-wmiobject Win32_Product -Filter "name='Node.js'" | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize

    2. Open command prompt and run the following command:

      1. cd C:\Windows\System32

    3. Copy the IdentifyingNumber for Node.js in the Powershell window

    4. Paste the IdentifyingNumber into this command:

      1. Msiexec.exe /uninstall {IdentifyingNumber}

Note: Do not include the brackets in the command.

    1. Proceed with uninstalling Node. You can verify it was uninstalled with the command “node -v”

  1. Reinstall node by downloading v12.13.0 and launching the .msi file

    1. https://nodejs.org/dist/v12.13.0/node-v12.13.0-x64.msi

    2. Use default options to install.

  1. Upgrade Clubspeed to the same version that the server is currently on. (This is to make sure permissions and files are all in order). Builds are found in Google Drive in the “Enterprise Builds” shared drive > Release

Related Articles