• Creator
  • #4080104

    Move windows 2003 AD Domain Controller to Windows server 2016

    by richard463 ·

    I am stuck with adding a Windows 2016 DC to my 2003 domain, Windows 2003 R2 32bit is the current Domain Controller, and I am trying to add redundant DC on my Windows 2016 Server. I am getting stuck at the part where I am supposed to update the Forrest and Domain on the 2003 server. Currently, the Domain Functional Level is set to Windows 2003 (and says that this is the highest possible) but the Forrest Functional Level is blank. When I go to the Domains & Trusts and right click on the Active Directory (top level) and select raise Forest Level, I get a message: “mmc has detected an error in a snap-in” error during “Raising Forest Functional Level”
    I have found that this is a problem with a potential solution:

    “There was a similar thread on this cant find now, there is known issue with Win2003 Server with regards to schema snapin.

    This problem occurs because the Adsiedit.dll module uses an uninitialized pointer. When the system frees this pointer, some random data is freed. Therefore, an access violation may occur.

    Try this Hotfix and”

    However, this kb article is no longer available on Microsoft, so I found it somewhere else but the kb946459 download is nowhere to be found.

    Any help would be appreciated.

You are posting a reply to: Move windows 2003 AD Domain Controller to Windows server 2016

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Answers

  • Author
    • #4086526
      Avatar photo

      Hope it works

      by Rohit Sri ·

      In reply to Move windows 2003 AD Domain Controller to Windows server 2016

      Hi Richard, It seems like you’re facing a common issue when trying to raise the forest functional level in a Windows 2003 domain. This issue can occur due to a problem with the Adsiedit.dll module, which uses an uninitialized pointer, causing an access violation error.

      As you mentioned, there is a hotfix available for this issue, but unfortunately, the KB article is no longer available on Microsoft’s website, and the hotfix download is not available either. However, there are a few workarounds you can try to resolve this issue:

      Try using a different management console to raise the forest functional level, such as the command-line tool “Ntdsutil.exe.”

      You can also try disabling the “Active Directory Sites and Services” snap-in and then try raising the forest functional level again.

      If none of the above solutions works, you can consider upgrading your domain to a newer version, such as Windows Server 2012 or later, which does not have this issue.

      Before attempting any of these solutions, make sure to take a backup of your domain controller and test the solution in a non-production environment.

      I hope these suggestions help you resolve the issue and successfully add your Windows 2016 DC to your 2003 domain.

Viewing 0 reply threads