Best way to install Exchange Server 2013 in this 'situation'?

Hello:)

I have 'one' physical machine that works as a Domain Controller (Active Directory, File Server, Back-up)(Server 2012 R2). Last week i got an Exchange 2013 Product Key. Now my question is... What is the best way to install this? This were the only ways i could think of:

- Run another Windows Server 2012 R2 on a virtual machine(Hyper-V) on my physical machine(Server 2012 R2)?

- Remove everything from my Physical machine, install Hyper-V Server 2012 and run 2 Virtual Machine's? 1 for the Domain Controller and 1 for Exchange?

- No other options i know:(

Someone knows a better solution for this situation?

Greetings,

Marc.

September 11th, 2015 4:34am

Hi

Well, its not recommended to install exchange on a DC. Your VM option should be fine but you running everything on 1 box which will be your single point of failure.

Free Windows Admin Tool Kit Click here and download it now
September 11th, 2015 4:37am

Hi

Well, its not recommended to install exchange on a DC. Your VM option should be fine but you running everything on 1 box which will be your single point of fa

September 11th, 2015 4:40am

Does your Physical box have enough to run hyper-v?

Dont you have another server to install exchange on?

Free Windows Admin Tool Kit Click here and download it now
September 11th, 2015 4:56am

Does your Physical box have enough to run hyper-v?

Dont you have another server to install exchan

September 11th, 2015 5:26am

I suspect it's a big ask for 4 cores to run all of that but 16GB RAM should be ok. Make sure that your server meets the requirements for Hyper-V virtualization. See here: https://technet.microsoft.com/en-us/library/cc731898.aspx.

Also, ensure that you size up Exchange correctly. See the calculator here: http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx.

Also, make sure you have storage space for growth etc. 

Agreed - it's supported but not recommended to run Exchange 2013 on a domain controller.

It's also best practice to ensure you're not running on a single point of failure - i.e. either use a second host and a SAN or a second host that you'll replicate VMs onto in case of host failure.

The other option of installing Hyper-V on a domain controller is not recommended and I doubt supported by MS.

Thanks.

Free Windows Admin Tool Kit Click here and download it now
September 11th, 2015 6:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics