Forum Discussion

Zach_B635's avatar
Zach_B635
Copper Contributor
Apr 04, 2022
Solved

Microsoft Recommendation on Upgrade Path from 2012R2 to 2022?

Hello,   Doing some searches on the web, it's not clear if there is an upgrade path from 2012R2 to 2022 Windows Server. From the link, I was wondering if there is an upgraded diagram, or if Microso...
management
  • Harm_Veenstra's avatar
    Harm_Veenstra
    Apr 11, 2022
    Did a in-place upgrade from 2012 R2 to 2019 just last week for two servers, no issues.. It just depends on the installed software/drivers/anti-virus etc if it will work. But nobody thinks twice about upgrading Windows 7 tot 8 to 8.1 to 10 to 11 😉 Upgrading does work and having issues in the future because of it is something of the past in my experience. If you can migrate to a new server without a lot of work.. Please do so, but it is still an option (But keep your backup and snapshots close)
Alban1999's avatar
Alban1999
Iron Contributor
Apr 07, 2022
Avoid in-place upgrade whenever you can, as it is very unreliable, and prone to keep non-desired settings. Even if it works, you may encounter later multiple bugs and issues, potentially difficult to troubleshoot and fix.
This is even more true when you try to fill a 10+ years gap.
Do yourself a favor and plan a side-by-side migration with a fresh install of Windows Server 2022.
  • Otis_Capps's avatar
    Otis_Capps
    Copper Contributor
    Mar 05, 2024

    Alban1999 I have a Server 2012 R2 Datacenter file server that I need to get to 2022.  While in place upgrade may not be optimal, it would be easier in this case just because of the amount of data that is involved as well as the messy folder permissions that predate me (we have a single file server that hosts all personal drives as well as corporate shares).  Is it possible to migrate this (the plan is to go to 2019 first then to 2022) going from 2012 R2 datacenter to a 2022 standard?

    • Karl-WE's avatar
      Karl-WE
      MVP
      Mar 06, 2024

      there are different ways:

      Method 1:
      "as-is cutover"
      install a new VM WS 2022 core edition (no gui)

      domain join with a new name

      use Storage Migration service to migrate via WAC
      Storage Migration Service uses MS native tools (robocopy)

      Method 2:
      "as-is" with very short downtime

      install a new VM WS 2022 core edition (no gui)

      domain join with a new name

      export LANMANSERV (shares and perm. from registry) on the original server

      shutdown old FS
      attach VHDX to the new VM, assign same drive letter and make the drives online
      import registry from lanmanserver 
      set AD DNS entry to short update time like 30 min
      rename old FS and assign different ip
      rename new FS and assign same ip (or DHCP)

      reboot


      Method 3

      migrate with new paths / permissions etc or as-is
      install a new VM WS 2022 core edition (no gui)

      domain join with a new name

      DL, license and install GSCopy Enterprise on the old FS (this is way faster than robocopy / Storage migration service and has a plethora of benefits for a very small price.

      • LFN support > 256 chars
      • open file support through VSS
      • doesn't care for permission issues as running as service
      • time based and recurring jobs
      • perfect logging
      • massive speed
        • one or more vNIC for SMB 3 multichannel, do not use LBFO nic teaming
        • enable-netadapterrss for SMB 3
        • vCPU and RAM recommended it is very scalable

      • using core server for FS has great improvements
        • fewer updates
        • blasting fast reboots
        • no one can ruin permissions with File Explorer via RDP "no access > take ownership" as UAC and explorer does not work by design, only via remote.
        • Share and permission management either via Server Manager / WAC
        • at scale via free SetACL Studio
          • much faster than Explorer ACL
          • can even do undo changes
          • fix broken perm. easily
          • can do more than one change at once like ownership and permissions
  • Chrisntps's avatar
    Chrisntps
    Copper Contributor
    Oct 19, 2023

    Alban1999 

     

    "Avoid in-place upgrade whenever you can"

     

    This is very difficult to do when the DC has hundreds of users and computers and other roles running, especially when you are a new sys admin with no connection to the prior sys admin of anything else the DC vm may be doing that is critical that you can't migrate by doing a fresh install.

    • ColachoMendoza's avatar
      ColachoMendoza
      Brass Contributor
      Nov 05, 2023

      Chrisntpsfor new domain controllers it's better just to spin up a new server 2022 and join it to the domain then make it a domain controller (DNS Server) I've removed all other roles from my domain controllers such as (DHCP, CERT, KMS, other roles) this way it's easier to upgrade domain controllers by adding a new DC already running the latest OS. if you haven't move the roles out of your DC I recommend you to first work on moving DHCP, KMS, Certificate of Authority or any roles you may be running on that DC aside from (DNS only) this role must stay in the DC imho.

    • mercurio2054's avatar
      mercurio2054
      Copper Contributor
      Nov 03, 2023

      Chrisntps If is a Domain Controller the recomendation is to create a new Windows server 2022, add the roll of Domain Controller and move all the DC rolls to this new one, then "demote" the old one. 

       

Resources