"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.

By the "main server" I assume you mean the host? Don't install AD and Hyper-v together on the host. That is bad. Put your roles in VMs when running hyper-v. Leave the host 'pure' and only used for virtualization management.

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

By the "main server" I assume you mean the host? Don't install AD and Hyper-v together on the host. That is bad. Put your roles in VMs when running hyper-v. Leave the host 'pure' and only used for virtualization management.

Agree, I've done this on other servers have another server configuration coming up soon wanted to clear the air in my mind around this question. Another question, when you say, "Leave the host 'pure' and only used for virtualization management" do you mean not even host data on it? I usually share data on the host.

No shares on the host either. Even if you're far away from setting up a high-availability hyper-V cluster, the host should be setup and run so that, if you had such a cluster, you could reboot it and the users would never have a clue.