Upgrade AD server 2012 to 2022

Question

Upgrade AD server 2012 to 2022

Sandeep Prajapat 0

Hi,

Currently we are using microsoft server 2012 R2 Standard as active directory domain server, due to no security patches and updates by microsoft, planned to upgrade AD server to 2025, But As I did research we can not migrate AD Server 2012 to 2025 directly, we can migrate in 2022. So I install a server with 2022 R2 Standard and activated with the offical license.

Once installation completed, Steps followed:

assign a new server name

domain joinned with the existing AD Server

now install AD DS role, try to promting new 2022 as domain server, unfornutally can't

later I upgrade 2022 schema for FSMO roles in following manner

So I followed some powershell method to upgrade schema such as :
cd D:\support\adprep ,

   .\adprep.exe /forestprep ,  

    Get-ADForest | Select-Object SchemaVersion
```Now it's reflecting new schema 88. synced FSMO roles to new AD server

Schema master               newserver.domain.com

Domain naming master        newserver.domain.com

PDC                         newserver.domain.com

RID pool manager            newserver.domain.com

Infrastructure master       newserver.domain.com

The command completed successfully.

Replication health is also good and result showing positive

Issue:   
point 1. while I'm replacing the server from old to new showing status like this![User's image](/api/attachments/9769ba77-7170-406d-b6d1-e5fa1f3751e2?platform=QnA)

point 2. 

When the old server (2012) goes down, the Active Directory (AD) functionality on the new server (2022) also stops working. However, while the old server is operational, any user activities on new server (2022) — such as creating new users, granting access, or revoking access—are synchronised with the original AD server (2012) and work correctly. means it's depend on old server (2012)

**We can't demote Server 2012 until Server 2022 is not working because LDAP is configured in the Active Directory server, so it will impact everything.**

Our goal is to have an independent AD server (2022 or 2025). 

If any experts can provide advice on the best method to achieve this, I would greatly appreciate your assistance. 

Thank you!

0 comments

1 answer

Your answer

Answer 1

To achieve an independent Active Directory (AD) server running on Windows Server 2022, you need to ensure that the new server is fully promoted as a domain controller and that it can operate without relying on the old server (Windows Server 2012). Here are some steps you can follow:

Ensure Proper Promotion: Make sure that the new server is properly promoted to a domain controller. You can do this by using the Active Directory Domain Services Configuration Wizard or PowerShell commands. If you encounter issues during promotion, check the event logs for any errors that may provide insight into what went wrong.
Transfer FSMO Roles: Since you have already upgraded the schema and verified that the FSMO roles are on the new server, ensure that all roles are correctly assigned. You can use the Get-ADForest and Get-ADDomain PowerShell cmdlets to verify the roles.
Check Replication: Verify that replication between the old and new servers is functioning correctly. You can use the repadmin /replsummary command to check the replication status and ensure that there are no issues.
Demote the Old Server: Once you confirm that the new server is functioning independently and that all necessary data has been replicated, you can demote the old server. This can be done using the Active Directory Domain Services Configuration Wizard or the Uninstall-ADDSDomainController PowerShell cmdlet.
Verify Independence: After demoting the old server, test the new server's functionality by creating users, groups, and other objects to ensure that it operates independently without relying on the old server.
Backup and Documentation: Ensure you have proper backups of your AD environment and document the changes made during the migration process for future reference.

If you continue to face issues, consider consulting Microsoft documentation or reaching out to a Microsoft support professional for further assistance.

References: