Run Virtual Domain Controller in Hyper-V in a workgroup environment


i'm sorry if dumb question, before go trying implement this, can tell me problems might encounter or if idea.  i'm trying setup test lab learn hyper-v.  here how i'm thinking of implementing current environment.

install hyper-v on dedicated system intel i5 processor.  run hyper-v in workgroup no domain yet exists.  install windows server 2012 on virtual machine in hyper-v , promote domain controller.  since hyper-v system runs before dc available, can never part of domain correct?  mean if dc isn't booted , need log in hyper-v, won't authenticate because credentials can't verified, thinking correct?  possible?  know ideally should have hardware dc available that's not virtualized , have hyper-v join it, in environment, not possible.

any input appreciated.

you mean, things single-sign on; central gpo control; easy configuration centralized remote access, management, , control; ability configure security pass government-, finance-, , healthcare-grade audits without disabling remote access , control; access clustering, shared nothing live migration, , vm storage on smb 3.0 shares; , general avoidance of micromanagement hell multiple workgroup computers? in non-test/dev environment none of things useful hyper-v is?

eric siron
http://www.altaro.com/hyper-v/



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group