This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 24%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
Team,
Our current AD Forest looks like this:
root.contoso.com - Schema Master for the Forest Resides on a DC here.
main.root.contoso.com. - Exchange Servers resides here.
main2.root.contoso.com
All DCs are Win Server 2016
When attempting to update the schema by running the command: setup /prepareschema /IacceptExchangeServerLicenseTerms , I get the following error even though I am a member of Enterprise Admin and Schema Admin groups:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or
'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
Setup encountered a problem while validating the state of Active Directory: The user-specified domain controller
Dc1.root.cotoso.com is not a domain controller in the local domain. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To
install Exchange Server 2016, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Any thoughts or suggestions? Thanks in advance!
Disregard. I needed to install .net 4.8 for it to move forward. I needed to just pay attention to the error message.
Where are you running this from? What server?
Hopefully from the root domain on a machine joined there.
I tried it from the domain controller in root that has the FSMO role but it gives me 2 errors: 1 about needed to reboot due to a pending reboot. 2. Need to install .NET 4.8 which I believe shouldn't be needed on a domain controller.
We also tried running it on the Exchange Server in the Main.contoso domain which is where we get the initial error messages I posted.
Thoughts?
Updated the original post to show that main and main2 domains are child domains.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
We also tried running it on the Exchange Server in the Main.contoso domain which is where we get the initial error messages I posted.
As regards to the initial error messages, it could be due to that "the computer needs to be a member of the same Active Directory domain and site as the schema master." See the official link below for more information about the requirements when extending schema:
Extend the Active Directory schema
Regarding the error about installing .NET 4.8 when you tried it from the DC on root, as indicated in the document mentioned above, "the computer that you use for these procedures needs to meet the system requirements for Exchange", so I am assuming that this could explain why .NET 4.8 is needed to be installed for DC in your scenario.