Solved

Windows Server version for new PDC

Posted on 2014-01-21
6
493 Views
Last Modified: 2014-01-21
I have the usual setup with two DCs, each running on W2003 32-bit at a client. It's a small shop with < 10 workstations and two file servers.

I wish to add a new DC as the PDC leaving the old PDC as a normal DC.

But which server OS should the new PDC run in? Should I jump to W2012 R2 or will a previous version be fine? I have a W2008 license which could be allocated for the purpose.
Or I could ask: Will a W2012 R2 based PDC add any relevant benefit for this scenario compared to a PDC running W2008 or even W2003?

The plan is soon to install an Exchange 2013 server. Will that change requirements to the level of AD?

/gustav
0
Comment
Question by:Gustav Brock
6 Comments
 
LVL 17

Assisted Solution

by:Chris Millard
Chris Millard earned 100 total points
Comment Utility
The minimum OS requirement of Exchange 2013 is Windows Server 2008 R2 (SP1), so if your license covers R2 then you may as well stick with that.

Whichever option you go for, you'll need to update the schema.
0
 
LVL 53

Accepted Solution

by:
Will Szymkowski earned 200 total points
Comment Utility
You can have FSMO roles on any DC in your environment that is a R/W DC. This has no barring on the type of OS you have. Personally i like to put the FSMO roles on the server that has the most resources. I say this because when you add FSMO roles to a DC it creates overhead which requires more resources to be used.

Exchange 2013 requires a domain/forest  functional level of 2003 or higher. As long as you have that you will be fine. As for the server side you can use 2008 R2 or 2012. Personally if you have a license ues the latest (mitigates from doing OS upgrades in the future) OS version. If not 2008 R2 will work fine for the install.

Exchange 2013 minimum system requirements

Will.
0
 
LVL 57

Assisted Solution

by:Mike Kline
Mike Kline earned 200 total points
Comment Utility
A lot of the functionality comes when you updated your domain and forest functional levels (AD recycle bin for example.).

Having said that I'd at least try to get to 2012 because of the new ADAC and things that will make it easier for administration.  

Nice job getting to 2 DCs.  I've seen plenty of folks try to get away with one on a small network and that thing crashes hard and then they have a lot of work to do.  That second one gives you some insurance.

Thanks

Mike
0
Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

 
LVL 49

Author Comment

by:Gustav Brock
Comment Utility
Thanks all of you, that was fast!

I should point out that both Exchange 2013 and the new DC will be separate installs on two dedicated servers.

So is it correctly understood that for operations I could go with W2003+ for the DC and W2008 R2 for the Exchange 2013 server, but should choose W2012+ for the DC to be prepared for future updates and to have the ADAC functionality?

/gustav
0
 
LVL 57

Expert Comment

by:Mike Kline
Comment Utility
that is what I'd do, ADAC is there in 2008 R2 but it is greatly improved in 2012.

Thanks

Mike
0
 
LVL 49

Author Closing Comment

by:Gustav Brock
Comment Utility
Thanks! Much appreciated.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

763 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now