Where should the first 2016 DC be introduced the Forest domain or the child domain?

I am preparing for an AD upgrade from 2008 R2 to 2016.  I have an "empty" Forest root domain with only 2 DCs and nothing else.  The child Domain has 10 DCs.
Where should the first 2016 DC be introduced the Forest domain or the child domain?  Or, does it not matter.
Thanks.
Jose ThorneAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MASEE Solution Guide - Technical Dept HeadCommented:
It is always recommended to have it installed in your ADSite where you FSMO holder is existing.
0
MaheshArchitectCommented:
You can add additional DC to either child domain or root domain itself, that's not make any difference

Your forest root domain is empty root domain, so better add new 2016 DC's in child domain 1st and later on you can add them to parent domain later point of time
0
Todd NelsonSystems EngineerCommented:
Where should the first 2016 DC be introduced the Forest domain or the child domain?  Or, does it not matter.

You shouldn't if you happen to have Exchange 2010 or older in your forest.  If you don't have Exchange, disregard.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Jose ThorneAuthor Commented:
Todd,
We do have Exchange 2010, but have moved on to gmail, so no one is using Exchange.  We plan to have it decommissioned before the AD upgrade starts.   But that brings up a new question - What does happen to Exchange 2010 if you upgrade to AD 2016? Does it simply break Exchange (like no one can login to mailboxes, etc), or does it have other more serious consequences.  
In other words, in my case, since no one is using Exchange, (but we still have it up because management is scared to turn it off) will it effect the upgrade to 2016?
0
MASEE Solution Guide - Technical Dept HeadCommented:
Agree with Todd, There is no 2016 DC support for Exchange 2010.Please check this for more details.
https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396


@Todd,
Thanks for pointing the missed point.
0
MaheshArchitectCommented:
According to exchange supportability matrix, 2016 dc servers are supported with exchange 2010 sp3 ru5 and above
https://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
0
Todd NelsonSystems EngineerCommented:
What does happen to Exchange 2010 if you upgrade to AD 2016?

You would not be able to uninstall Exchange 2010 in the normal way.  The uninstall will fail because of the presence of a Windows 2016 DC.  If you introduce a Windows 2016 DC prior to removing Exchange 2010 and plan to remove it through the uninstall process, you would need to demote all Windows 2016 DCs before proceeding.

I strongly encourage you to remove Exchange 2010 prior to promoting that first Windows 2016 server to a DC or install an Exchange 2016 server and decom 2010.
0
Todd NelsonSystems EngineerCommented:
According to exchange supportability matrix, 2016 dc servers are supported with exchange 2010 sp3 ru5 and above
https://technet.microsoft.com/library/ff728623(v=exchg.150).aspx

Mahesh, that is incorrect.

Supported-AD.png
0
MASEE Solution Guide - Technical Dept HeadCommented:
As commented by Todd it is not supported. Either uninstall Exchange 2010 or upgrade Exchange2010 to Exchange2013SP1 or Exchange2016 before promoting 2016 server to a DC. Here is a similar thread.
https://social.technet.microsoft.com/Forums/en-US/c6b79674-d319-468e-9f5a-ede4c733633a/compatiblity-with-server-2016-dcs-ad?forum=exchange2010
0
MaheshArchitectCommented:
You are right,
I over looked article
Its my bad
0
Jose ThorneAuthor Commented:
Ok thanks for all the Exchange 2010 comments.  We will surely uninstall Exchange 2010 before proceeding with the AD 2016 upgrade.
Thanks again.
0
MASEE Solution Guide - Technical Dept HeadCommented:
Glad to know our comments helped.
Wish you good luck. :))

MAS
0
Todd NelsonSystems EngineerCommented:
Sufficient guidance provided for solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.