AD+File Server Migration Best Practice From: OS 2012 To: OS 2022

Sathishkumar Singh 486 Reputation points
2023-08-08T09:55:35.0333333+00:00

Hello Team
Windows 2012 R2 is End of life on October 2023
I would like to plan migrations of Servers with exchange

My Current Infra
Servers are running VMWare

1-Primary Domain Controller**(Win2012)**
TLS.LOCAL

1-Secondary Domain Controller + File Server __(Win2012)
Running in VWare Virtualization
C: 100GB HDD
E:1TB HDD
__
Now Migrating From: OS 2012 To: OS 2022 What is the best practice to Migrate?
We have a Veeam Backup does it help?
1TB Data with permissions -> Subfolders are different permissions and Enable Access-based Enumeration are running. how to do that? Datas are link with production servers as well and GPO for Map Drives

Please advise? 1 TB HDD is VDMK file, if i disconnect and re-connect to New Server without impacting permissions how can we do that. Please advice

Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
408 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Darshana Jayathilake 156 Reputation points
    2023-08-08T21:53:16.4866667+00:00

    I would suggest the below steps for this

    1-Install new VM with server 2020

    2-Migrate FSMO roles

    If you have enough capacity

    3-Create one more new VM with server 2022

    4-Make it an additional domain controller

    5-Decomssion secondary domain controller(remote ADDS) from old 2012

    6-Do an in-place upgrade of the old Secondary domain controller, then you don't need to do any file migration

    If you don't have enough capacity

    ignore step 3 above

    Follow step 5,6

    then

    7-Promote the upgraded server as a secondary domain controller

    0 comments
  2. Dave Patrick 426.1K Reputation points MVP
    2023-08-08T22:07:12.4466667+00:00

    The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

    The storage migration service may be helpful but better option is to stand up a separate instance for this role.

    https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview

    --please don't forget to upvote and Accept as answer if the reply is helpful--