Solved

Server 2016 domain two way trust with 2003 domain function level

Posted on 2016-08-16
5
1,205 Views
Last Modified: 2016-12-09
I saw an article where it says that you can establish two way trust between 2003 domain functionality and 2008, 2012, 2012R2 but i cant find anywhere is it possible to do this with Server 2016. The release date is end of September and our domain is due to an upgrade so need to know if it's possible to make a new forest based on 2016 and establish two way trust with 2003 domain functionality?
0
Comment
Question by:MRS
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 31

Accepted Solution

by:
Scott C earned 500 total points
ID: 41757999
Doesn't look like it will.  2003 DFL and FFL have been deprecated in Windows Server 2016.

https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-ds/windows-server-2016-functional-levels

Looks like you will have to install one Windows Server 2008 R2 DC server, remove the 2003 DCs and raise the functional level.

You may want to try this in a lab environment.
1
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 41758042
"The release date is end of September"

Precisely. And in Microsoft's recent move towards more rapid development, some decisions are going to be made literally days before shipping. You really won't get a definitive answer for a product not yet out. Only prerelease info (subject to change) and conjecture. Not good for basing upgrade plans on.
1
 
LVL 31

Expert Comment

by:Scott C
ID: 41758057
You would be better upgrading your domain to 2012 R2 or at least 2008 R2 and then to Windows Server 2016.

Your domain isn't due to be upgraded...it is WAY PAST due.  Windows Server 2003 hasn't been supported for over 2 years.

There is no reason to expect Server 2016 will be compatible.

Exchange Server 2003/2007 users are in the same boat.  There is no direct migration path from these legacy systems to Exchange 2016.  It is a two-step migration.  You will most likely have to do the same thing.
0
 

Author Closing Comment

by:MRS
ID: 41758092
I guess we will wait and see. For now i will assume it will not be supported. But i can also test in the lab and make sure it is not indeed. :)
0
 
LVL 31

Expert Comment

by:Scott C
ID: 41758224
Glad I could help.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here's a look at newsworthy articles and community happenings during the last month.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

615 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question