Share via

Having issues and queries after deploying the new AD server from 2016 to 2022

Anonymous
2024-03-27T11:49:55+00:00

Having issues and queries after deploying the new AD server from 2016 to 2022

  1. DHCP Failover is not working after upgrading from 2016 to 2022 server.
  2. How to validate the each FSMO role, whether it is working fine or not.
Windows Server | Identity and access

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments
Accepted answer
  1. Anonymous
    2024-03-28T06:27:28+00:00

    Hi krishnasai DANDANAYAK,

    Thank you for posting in the Microsoft Community Forum.

    It may be due to configuration changes after operating system upgrade, incompatible service configurations, network setting changes, etc. You can troubleshoot the problem by following the steps below:

    Confirm the DHCP server configuration: Make sure the DHCP server configuration is the same as before the upgrade. Check that the network configuration such as IP address, subnet mask, gateway, and DHCP scopes and options are correct.

    Verify Network Connectivity: Ensure that the network connection between the DHCP servers is working. If you are using the failover feature, the DHCP server running on Windows Server 2022 must be able to communicate with the DHCP server previously running on Windows Server 2016.

    Check the DHCP server logs: Review the event logs of the DHCP server for any error messages or warnings related to failover.

    This article is about how to view and transfer FSMO roles, I hope it can help you:View and transfer FSMO roles - Windows Server | Microsoft Learn

    Best regards

    Neuvi Jiang

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest