Exchange 2007 with Server 2016 Domain controllers

Hi All,

We have server 2008 dc with exchange 2007. We are planning to migrate users to exchange 2013 before migrating them to O365. We are planning to introduce Server 2016 in order to better manage our Windows 10 machines.

I have a few questions:

1 - Would exchange 2007 work fine with Server 2016 domain controllers?
2 - Has anyone faced any major issues with Server 2016 domain controllers?
3 - Should we proceed with Server 2012 R2 as domain controllers or Server 2016 as domain controllers makes sense since we need to better manage our Windows 10 workstations with GPOs?

Thank you
LVL 1
skyjumperdudeAsked:
Who is Participating?
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.

Scott CSenior EngineerCommented:
1.  Yes it will work just fine.
2.  No, none at all.
3.  I'd go with Server 2016  see answers to #1 and #2.

Question...Why not just migrate to O365 from Exchange 2007.   That is a valid migration path.  Heck...I've even seen it done from Exchange 2003.

Also, Exchange installed on a DC is not a supported configuration unless that machine is an SBS.  Just a heads up in case you need to call MS for assistance.  They won't be able to help you.
0
Jose Gabriel Ortega CEE Solution Guide - CEO Faru Bonon ITCommented:
1 - Would exchange 2007 work fine with Server 2016 domain controllers?
I'm not sure about this, I'd go with Windows server 2012 R2, either way the final way is O365.

2 - Has anyone faced any major issues with Server 2016 domain controllers?
I don't think you would have major issues with it, as far as you don't increase the functional level of the domains or forest to 2016. (since 2012 or 2016 wasn't even in the picture when exchange 2007 was in the game). I mean Exchange itself won't have major issues at least you move something that breaks the server, like the forest and domain level,
The important thing is to have  the domain levels in at least 2003 because if you don't you will get something like this:
https://social.technet.microsoft.com/Forums/getfile/9761643 - Should we proceed with Server 2012 R2 as domain controllers or Server 2016 as domain controllers makes sense since we need to better manage our Windows 10 workstations with GPOs?
I'd go with server 2012 r2 since there's no really a need for 2016, you can work with domain controllers in 2012 R2, and work on your migration for O365 and then decommision both (new 2013 exchange and the 2012 r2 AD server).
0
RoninCommented:
I would recommend the following:
1. Migrate Exchange 2007 to at least Exchange 2013.
2. Install and update your desired AD servers using any of the versions indicated here.
3. Migrate Exchange 2013 to Office 365 and leave Exchange 2013 on-prem as Hybrid server with no users on it.

That's probably the safest way not to cause any incompatibility.
0

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
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Ajit SinghCommented:
Consider Exchange Server Deployment Assistance a web based application just you have to select what kind of deployment you were interested and then its provide you step-wise instructions to get this job done: https://technet.microsoft.com/en-us/office/dn756393.aspx

How to: Step-by-step guide for migrating from Exchange Server 2007 to Exchange Server 2013:
https://community.spiceworks.com/how_to/122658-step-by-step-guide-for-migrating-from-exchange-server-2007-to-exchange-server-2013

Hope this helps!
0
skyjumperdudeAuthor Commented:
Thank you everyone for your contribution. You guys have been very amazing. We will be keeping our Domain and forest funtional levels at 2008 R2 but need the server 2016 to better manage our Windows 10 workstations as server 2012 R2 is also quiet older than windows 10. We faced lots of issues when trying to manage our win 10 workstations using gpo.
0
Scott CSenior EngineerCommented:
Agreed on going to 2016 over 2012 R2....support will be for quite a few years more.  To install "new" 2012 servers is just doing yourself and your customers a disservice.

And you won't have any issues with 2016 DCs in an Exchange 2007 environment.  This will work just fine.
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
Windows Server 2016

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.