Is there any impact for migrating windows server 2016 to 2022 for Active Directory.

Md. Mahfuzur Rahman 346 Reputation points
2023-07-18T16:12:48.65+00:00

We want to migrate Active Directory 2016 to 2022.

We have Windows 10 clients and some Windows 7 clients. Is there any impact on Windows 7 clients?

And some applications use LDAP authentication. Is there any impact on LDAP authentication after migrating windows server 2016 to windows server 2022 for Active Directory?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,882 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Sina Salam 17,491 Reputation points
    2023-07-18T17:21:47.05+00:00

    @Md. Mahfuzur Rahman

    Welcome to Microsoft Q&A and thank you for posting your questions here.

    You were asking the impact of migrating windows server 2016 to 2022 on your Active Directory. Also, you asked to know if there Is there any impact on Windows 7 clients and some applications use LDAP authentication.

    The are many supported scenarios when upgrading domain controllers from Windows Server 2016 to Windows Server 2022. Also, the impact of migrating Windows Server 2016 to 2022 on Active Directory depends on the current version of Active Directory Domain Services (AD DS) functional level.

    To more details about the impact of migrating, read more here:

    1. Active Directory Domain Services Functional Levels in Windows Server
    2. Active Directory Domain Services migration

    If you can go through the above links, you will gain more insight on how to perform clean and successful migration.

    Hope this is helpful, do not forget to accept it as an answer to help the community. Also, do not hesitate to ask more questions if there is a need.

    Regards,

    Sina Salam

    0 comments No comments

  2. Anonymous
    2023-07-18T17:33:18.29+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.

    As to the LDAP something here could help with the migration.

    https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/enable-ldap-signing-in-windows-server#how-to-discover-clients-that-do-not-use-the-require-signing-option

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


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.