• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1019
  • Last Modified:

Windows 2012 Domain Controller Exchange 2010/2013

Hello,

We are currently running Windows Small Business Server 2008.  This server is currently experiencing various issues and needs to be replaced.

As an equivalent option, because Microsoft no longer offers SBS, we are planning on deploying a Windows 2012 R2 server which will act as a file & print server, DNS, DHCP, and Domain Controller.  We will also need an internal mail which in our case would be Microsoft Exchange 2013.

I understand Microsoft frowns upon installing Exchange on the same server that is acting as a domain controller.  We have been successful in using a single server to host all services listed above in addition to Exchange 2010 (although Microsoft also says not to have Exchange 2010 on the same machine as a domain controller).

I’m looking for input in this regard.  What are the primary concerns of having both services run on a single machine?  Can it be done anyway?  What potential issues could we face?  If in fact there is no option to setup two separate machines, could we minimize potential issues by sticking with Exchange 2010 rather than Exchange 2013?

Thanks in advance.

Regards,
Real-Timer.
0
realtimer
Asked:
realtimer
5 Solutions
 
Ned RamsayCommented:
Its not recommended but it is supported.

You would need to setup and maintain the Domain Controller side of it first as promoting or demoting a domain controller containing exchange is not supported.

The main concern is that exchange required internet access, open ports, means of direct attack to the server it resides on. Which in this case is your primary server. I personally would find a cheap second box to run DHCP/DNS/Domain Controller/File Server as exchange can be an absolute monster.

Hope that helps.
0
 
realtimerAuthor Commented:
Thanks Nedramsay - I imagine that the same issues pertain to both Exchange 2010 and Exchange 2013?
0
 
EEhotlineCommented:
You can do that but it is not recommended.

01. Redundancy and Stability: If both of these are running on the same system, it may reduce the performance and stability of server. If in any case Exchange Server services fails, the whole DC will fail, which may create critical problems.
02. Port Conflict: Domain Controller & Exchange Server both uses port 389 for LDAP queries, which creates conflict.
03. Disaster & Recovery: Disaster & Recovery can not be performed.
04. DSAccess: DSAccess, DSProxy and many other services will perform well.

http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller%28v=exchg.150%29.aspx
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Ned RamsayCommented:
No Problem realtimer.
Ive been in the same situation and its not fun. If you can separate the two its better, the same issue will arise with 2010 or 2013.

If you can find an old server for Domain Control, DNS, DHCP, another old one for File Stores and a new one for exchange that would be best. Depending on the number of users of course.

If you need further advice let me know... just MAKE SURE you install and configure the DC before you touch exchange :) don't want you annoying microsofts support!!
0
 
EEhotlineCommented:
0
 
Cliff GaliherCommented:
I won't bother going into details what others have said: technically supported but heavily discouraged, etc.  But I will say this:

With 2012 (and 2012 R2) standard, you get 1+2 virtualization rights.  When you separate the two, in a small environment (which can be assumed if you really were going to run all of this on a single server anyways), the DC requirements are fairly light. *ALMOST* any server capable of running Exchange would be capable of running two VMs with very little impact to performance. The simple truth is, while it is supported, there is rarely (if ever) a good reason to run them all on the same OS anymore. The cost difference is simply negligable and the tools are there to make separation dead simple.

-Cliff
0
 
Gareth GudgerCommented:
What about if you pushed the Exchange piece into the cloud with Office 365? Mailboxes are only $4 a user/mo.

That will also include all your email anti-virus / anti-spam protection as well.
0
 
Simon Butler (Sembee)ConsultantCommented:
While SBS 2011 isn't sold by Microsoft, sales only stopped at the end of last year. There are plenty of supplies still floating around, so if you are quick you could deploy SBS 2011 instead. Rock solid product, if setup correctly it gives no hassles at all. I have done three installations this year already.

Simon.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now