Dual domain controllers using Hyper-V
I'm starting to work with a new customer whom I'm bringing onboard. They currently have 2 physical servers. One is dedicated to their ERP application and the other one is a Hyper-V host with 4 VM's on it. Two of the VM's are domain controllers and I'm trying to understand the purpose of this.
I'm used to seeing two physical servers when configuring two domain controllers in case one fails. What good are two domain controllers if they are on the same Hyper-V physical server? If the host fails everything is down.
The company has 40-50 computer users. Exchange is done by an outside provider.
I would like to have some input in to this
I'm used to seeing two physical servers when configuring two domain controllers in case one fails. What good are two domain controllers if they are on the same Hyper-V physical server? If the host fails everything is down.
The company has 40-50 computer users. Exchange is done by an outside provider.
I would like to have some input in to this
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Two domain controllers on the same Hyper-V box is not good. The only thought is that they have the two physical servers clustered for failover?
Other then that, If i was to set it up... I would have the primary DC on a VM and have the secondary DC on the other physical box.
But from what i understand their other hostbox is a dedicated application server, so it doesnt sound like they would have clustered anything.
Other then that, If i was to set it up... I would have the primary DC on a VM and have the secondary DC on the other physical box.
But from what i understand their other hostbox is a dedicated application server, so it doesnt sound like they would have clustered anything.
ASKER
That is what I figured too.
The ERP physical server is dedicated and there is no clustering or fail over in place.
The customer is ready to invest in IT so I will make some recommendations.
I'm thinking about recommending having a fail over DC on Azure. This is the first time I'm entertaining this idea.
Any recommendations?
The ERP physical server is dedicated and there is no clustering or fail over in place.
The customer is ready to invest in IT so I will make some recommendations.
I'm thinking about recommending having a fail over DC on Azure. This is the first time I'm entertaining this idea.
Any recommendations?
I think thats a great idea, I have never done this but I think Azure is the way to go. Let me know how you get on with this. I am interested to know the infrastructure behind getting this set up.
Microsoft Azure is an Extension of Active Directory when you are using it in an on-prem scenario. Relying on Azure will not work as it cannot authenticate on-prem clients (workstations/servers etc).
So having at least one physical server as a DC (does not need to have loads of resources) and then creating a clustered environment for Hyper-v with addtional DC's would likely be your best option, given the environment you are working with.
Will.
So having at least one physical server as a DC (does not need to have loads of resources) and then creating a clustered environment for Hyper-v with addtional DC's would likely be your best option, given the environment you are working with.
Will.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm setting up a physical server now as the secondary DC.
@Greg - you were right. The original plan was to have two HypoerV host with one DC on each but apparently that never happen because the budget was not there.
@Greg - you were right. The original plan was to have two HypoerV host with one DC on each but apparently that never happen because the budget was not there.
https://technet.microsoft.com/en-us/library/virtual_active_directory_domain_controller_virtualization_hyperv%28v=ws.10%29.aspx