LinkBack URL
About LinkBacksThis is something I have wondered for a long time.
Should I put our Hyper-V servers on the domain? Or should they be left off it?
This is something I have wondered for a long time.
Should I put our Hyper-V servers on the domain? Or should they be left off it?
I would say yes.
Ours are, and even at a bsic level of manging updates/av and logon it is an advantage. Not sure on exact technical details or reasons why though, we have 4 clustered servers so I assume that has something to do with it too although I have little to no knowledge on clustering
i dont domain them. I prefer having local access but i doubt either way is 100 ideal. I generally do updates manually on them anyway and av can manage itself just need to manually install it 1st. Having said that a lot of my vms are the school only dc running on a vm so i can run other odds n sods servers on the same host
On the domain for us - makes system management easy (after all Windows Servers were designed to be domain joined).
You can always have a local admin account ready to go in the event of some kind of DC failure as well.
Oh and slighty related and something I learned the hard way!
Make a note of the static IP addresses of the hyper-v hosts, just for that day when your DNS server goes down and you can get on to reboot!
Clustering (and managing clusters with SCVMM) requires domaining them I believe, particularly if you want to share ISO images rather than copy them when mounting virtual DVD drives etc.
If you put them on the domain make sure you have a physical DC
Why? All of our servers are virtual and never had a problem, apart frm the DNS one mentioned above which is solved now anywayOriginally Posted by FN-GM
No problem with having virtual DCs as long as you AVOID SNAPSHOTS and are careful not to allow them to get out of time sync in any way shape or form (e.g having the VM sync its time with the host , moving to a new host and the new host has the wrong time set in bios.) My DCs are virtual. Pysical are no different in that if you somehow make a mistake and allow a physical DC to get out of time sync then your in the same position as with a VM.
Last edited by AButters; 16th March 2012 at 12:19 PM.
Becuase when the entire cluster is off it won't start until a DC is running - no DC running as you can't start etc = headaches
Although I've only picked that up from others - I don't use it!
1. Its what Microsoft recomend.
You can also get yourself into a situation where you cant boot any servers. See here: Hyper-V - All our virtual servers won't start........ please help
Interesting theory, but I have never heard of a server not starting up because it cant contact a DC
EDIT: just need FN-GM's post, very interesting. We arent in a posistion to change our setup anyway, and do cold boots quite regularly so you know what they say, if it aint broke....
Last edited by british_government; 16th March 2012 at 12:29 PM.
Its if they are in a cluster I believe - stand alone I think it would be fine although not 100% sure.
Just to add to this I was originally having a problem with Hyper-V loosing the network connection.
It turns out this is a known problem and there is a hotfix available here
Seems to work so far.
Also some great Hyper-V gotcha's here:
Hyper-V: Gotchas - TechNet Articles - Home - TechNet Wiki
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
