How do you do....it? Thread, Virtual DC on a single Hyper V Host in Technical; Hi
Im taking over some primaries, doing new domains etc with new server hardware as they are massively behind (one ...
12th February 2014, 12:14 PM #1
Virtual DC on a single Hyper V Host
Im taking over some primaries, doing new domains etc with new server hardware as they are massively behind (one doesn't even have a domain)
I am going down the route of having the physical server just being a PDC and HyperV Host. I do windows server backups of the bare metal states, and so back up the AD that way.
However, I am wondering if it is worth virtualising a DC - in the hope that if the physical server was to fail, my VEEAM backups of all VMs, including the BDC VM could be restored to an alternative server with ease and, because the BDC would exist, the entire network could then be brought back up quickly and easily on a plain server OS with no links to the domain?
12th February 2014, 12:30 PM #2
Yep. I would not join the HyperV host to the domain either - keep it as a standalone (I am not a fan of tying in HyperV or Vmware hosts by joining the domain when virtual machines that are actually running on them are the domain controllers). It's added complexity for no good reason as far as I can see.
12th February 2014, 12:36 PM #3
@AButters beat me to it. This is exactly what I would do.
12th February 2014, 03:14 PM #4
I can understand that logic, but was always told that its best to keep a physical DC, has this changed with 2012? As my main school is a 2008r2 failover cluster, with both the physical hosts being DCs
12th March 2014, 12:05 PM #5
- Rep Power
I heard the same thing too! But recently I had some hardware failed on secondary DC, so decided to virtualise it. All went smoothly and it's been running for a bit now without any problems whatsoever, I can even say it's a bit quicker (definitely the management part)! However not sure I'm ready to risk it and go fully virtual yet.
Originally Posted by mattianuk
12th March 2014, 01:04 PM #6
Haven't had a physical DC here for years. The old wives tales of not virtualising DCs was created by unfortunate people years ago who 1) didn’t realise that you shouldn’t take or restore snapshots on DCs as it can change the time on the virtual machine, thus disconnecting the DC from Active Dir and 2) Didn't realise that if they joined their physical Hosts into the AD they could get into a situation where they may not be able to log in to their hosts if a virtual DC running on that host goes down 3) didn’t realise that if they enabled VMs to automatically sync with the physical host, and the physical host gets out of time for whatever reason they could lose their domain controllers due to time errors as per 1).
Keep your physical hosts as standalone machines, don't auto sync the time on the host and VM, and don't use snapshots with wild abandon and you will be able to keep your virtual DCs running like me, for years.
13th March 2014, 09:14 AM #7
Sorry to butt in. I look after a small primary and we have one physical 2008r2 DC and another 2008r2 server running the hyper-v role with a second DC as a VM. The physical server that has the hyper-v role is also a member of the domain. I have noticed on this post that that is not a good idea but not a 100% sure why. I can see an issue with the main DC going down and not being able to log in to the second physical DC using a domain account but can you not use a local account? Keep your physical hosts as standalone machines
Last Post: 27th October 2008, 08:58 PM
By cooper in forum Windows
Last Post: 28th August 2008, 11:56 AM
By speckytecky in forum How do you do....it?
Last Post: 8th April 2008, 02:57 PM
By Norphy in forum Thin Client and Virtual Machines
Last Post: 6th February 2007, 01:35 PM
By ajbritton in forum Windows
Last Post: 1st April 2006, 05:13 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)