Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 135
  • Last Modified:

Is it ok to use the host OS (2008R2) as the DC, DHCP, AD, and file server?

I have built a host 2008r2 server with the hyper-v role  that has 2 servers running on it. 1 for Exchange and 1 for quickbooks. Is it ok or best practice to use the host OS as the Domain Controller, Active Directory, DHCP, and file server or should I build another VM to serve as the server?
0
JRome225
Asked:
JRome225
1 Solution
 
Mark GalvinManaging Director / Principal ConsultantCommented:
Depends on the hardware configure and the number of users that will be accessing the system as well as the network configure (100MB or 1000GB etc.

Are you able to share the generic details?
0
 
Gabriel CliftonCommented:
Always separate as much as possible. Ideally you want the ability for if the file server goes down, it is not taking anything else with it like DC.
0
 
Gabriel CliftonCommented:
For small orgs, I usually separate it by critical role server(s) and non critical server(s)
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
MacleanSystem EngineerCommented:
I'd personally have the DC separate on Hyper-V, partially as you can take snapshots before patching for quick reverts, and partially because you don't want to overload your Hyper-V host with multiple other roles and functions. I rather have a clean Hyper-V, and allocate resource required to guests, in order to manage the resource consumption a bit better.

But have a look at this blog, it will give you some options to consider.

http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/11/24/the-domain-controller-dilemma.aspx
0
 
rindiCommented:
No. The Server running the Hyper-V role must only do that and nothing else. Hyper-V should never run on a DC.
0
 
Lionel MMSmall Business IT ConsultantCommented:
Think of it like this--if Hyper-V is also the DC and the File server and the .... and any of those roles cause the server to crash you not only have brought your Hyper-V down but the VM's too. So as mentioned above depending on the hardware and your budget for server licenses you should keep "mission" critical roles separate. I work mostly for small businesses with limited clients and I am forced to put multiple roles on VM servers and in most cases it works out fine but you must think about which one or which ones (roles) you want to isolate as much as possible from other roles.
0

Featured Post

Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

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