0

I would like to ask you guys, who already done some Hyper-V implementation if it's good idea to use this solution for set-up a small company infrastructure.

The idea is to have 1 physical server (2 processors, 32gb ram) and license for Server 2012 Standard + Exchange 2013 Standard. I'm aware of recommendations not to install Exchange on a DC and that's why I prefer to install 2 hosts (DC and Exchange) on Hyper-V server.

What is not clear is Hyper-V set-up on the server: Should this be Server 2012 Core or Hyper-V can be installed on Full featured (with GUI) sever? What should I be aware of in terms of hardware set-up? Is there any guidelines/best practice for this scenario?

Bororo
  • 13

3 Answers3

3

Whether it's a "good choice" is, I think, mostly subjective. I think my answer/opinion would be something like, "well, if that's all you have, you can technically make it work. I would not consider it an ideal situation, but I would consider it better than installing the DC and Exchange on the same OS instance."

Should this be Server 2012 Core on can be installed on Full featured (with GUI) server?

Depends on what you think your administrators can handle. There is nothing in this scope that Server Core cannot handle. But you need to know plenty of Powershell and have RSAT installed on a remote machine to effectively manage Server Core.

Ryan Ries
  • 56,311
-1

In my opinion its a sort of good choice. However, I'm not convinced that you need Hyper-V Server 2012 for this (Bare metal). Due to licensing, in your case its better to run hyper-v on Windows 2012 Std. Since you are allowed to run 2 windows 2012 std guest hosts on your physical machine, you can actually use it as a file server or maybe even a domain controller. Then you still have the option to install 2 VM's with windows 2012 std with the same license to install a DC and exchange 2013.

In any case, I would certainly look into buying another similar machine so you can cluster the physical host. If you buy a 3rth, you don't even need a file share withness. But that will triple your licensing costs and since your clustering the VM's (floating on the cluster nodes) you still can have only 2 vm machines running on that cluster. But its a good failover alternative. Actually Exchange is designed to work in a clustered vm enviroment.

Hope this helps.

Johannes
  • 1
-1

It is not a good idea because it is nesting two critical pieces of your network infrastructure inside each other, in a place that may make it harder to get out of some failure modes.

I would prefer even to run a domain controller on a small inexpensive desktop PC before I would run my primary domain controller inside Hyper-V. Why? Because your actual probability of some failure interrupting access to your Primary Domain Controller is higher.

Things to watch out for:

  1. Using Hyper-V virtualized networking has not been completely reliable when I have tested it with a domain controller, especially when the outer physical PC has only a single ethernet port and you use the Hyper V Virtual Ethernet Adaptor and the virtual networks segments. If you really must use a single box, you really MUST invest $20 in a second pci-E ethernet card.

  2. Expect and watch for disk bandwidth issues if you try this.

I wouldn't even try it.

Warren P
  • 1,215
  • 8
  • 22
  • 35