zag Posted March 16, 2012 Posted March 16, 2012 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?
british_government Posted March 16, 2012 Posted March 16, 2012 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
sted Posted March 16, 2012 Posted March 16, 2012 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
jamesfed Posted March 16, 2012 Posted March 16, 2012 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.
british_government Posted March 16, 2012 Posted March 16, 2012 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!
sonofsanta Posted March 16, 2012 Posted March 16, 2012 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.
FN-GM Posted March 16, 2012 Posted March 16, 2012 If you put them on the domain make sure you have a physical DC
british_government Posted March 16, 2012 Posted March 16, 2012 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 anyway
PotNoodleTech Posted March 16, 2012 Posted March 16, 2012 (edited) 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. Edited March 16, 2012 by PotNoodleTech
glennda Posted March 16, 2012 Posted March 16, 2012 Why? All of our servers are virtual and never had a problem, apart frm the DNS one mentioned above which is solved now anyway 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!
FN-GM Posted March 16, 2012 Posted March 16, 2012 Why? All of our servers are virtual and never had a problem, apart frm the DNS one mentioned above which is solved now anyway 1. Its what Microsoft recomend. You can also get yourself into a situation where you cant boot any servers. See here: http://www.edugeek.net/forums/windows-server-2008-r2/92003-hyper-v-all-our-virtual-servers-wont-start-please-help.html
british_government Posted March 16, 2012 Posted March 16, 2012 (edited) 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.... Edited March 16, 2012 by british_government
glennda Posted March 16, 2012 Posted March 16, 2012 Interesting theory, but I have never heard of a server not starting up because it cant contact a DC Its if they are in a cluster I believe - stand alone I think it would be fine although not 100% sure.
zag Posted March 19, 2012 Author Posted March 19, 2012 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.
zag Posted March 19, 2012 Author Posted March 19, 2012 Also some great Hyper-V gotcha's here: Hyper-V: Gotchas - TechNet Articles - Home - TechNet Wiki
pritchardavid Posted March 19, 2012 Posted March 19, 2012 1. Its what Microsoft recomend. You can also get yourself into a situation where you cant boot any servers. See here: http://www.edugeek.net/forums/windows-server-2008-r2/92003-hyper-v-all-our-virtual-servers-wont-start-please-help.html I just has this problem, our San (CSV Volume) wouldn't boot without a DC running, both of our domain controllers were off, luckly I had a backup I could run until I could start our normal dcs. We now have two virtual DCs on our Hyper V Hosts and another virtual DC on our backup server with no san, so there is no problem off that goes off, we will be able to reboot it.
mthomas08 Posted March 19, 2012 Posted March 19, 2012 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. Same. Dont see the real effects of not having it on a domain but for us it gives quick easy access to anything across the system.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now