Hyper-V permissions while domain is down
hello,
i ran interesting situation couple of weekends ago. did full shutdown of our building, required servers shut down. have 2 hyper-v hosts, configured identically. both member servers , both each host 1 dc domain joined to. have 1 physical dc same domain.
with virtual server 2005 r2, long host machine logged locally non-domain account, start vms using tools vmrc+. in other words, virtual dcs started without domain being up.
with hyper-v, assumed same true. happened was able log in local administrator , see vms listed under hyper-v manager, when tried start of them, got error vm not started because configuration file inaccessible. browse configuration file, open it, read it, etc, after rebooting , restarting hyper-v services, got same error.
luckily had physical dc started, , moment became available, hyper-v manager allowed me start virtual dcs and/or other vms. still logged in local administrator account.
i have read article http://blogs.dirteam.com/blogs/jorge/archive/2009/06/16/fixing-hyper-v-acls.aspx and 1 http://www.virtualizationteam.com/microsoft/hyper-v/hyper-v-a-new-breed-of-sid.html but neither explains why happening, permissions appear correct.
i planning on moving dcs hyper-v need make sure not lock myself out of house. there can provide insight situation?
thanks,
brit davis
i ran interesting situation couple of weekends ago. did full shutdown of our building, required servers shut down. have 2 hyper-v hosts, configured identically. both member servers , both each host 1 dc domain joined to. have 1 physical dc same domain.
with virtual server 2005 r2, long host machine logged locally non-domain account, start vms using tools vmrc+. in other words, virtual dcs started without domain being up.
with hyper-v, assumed same true. happened was able log in local administrator , see vms listed under hyper-v manager, when tried start of them, got error vm not started because configuration file inaccessible. browse configuration file, open it, read it, etc, after rebooting , restarting hyper-v services, got same error.
luckily had physical dc started, , moment became available, hyper-v manager allowed me start virtual dcs and/or other vms. still logged in local administrator account.
i have read article http://blogs.dirteam.com/blogs/jorge/archive/2009/06/16/fixing-hyper-v-acls.aspx and 1 http://www.virtualizationteam.com/microsoft/hyper-v/hyper-v-a-new-breed-of-sid.html but neither explains why happening, permissions appear correct.
i planning on moving dcs hyper-v need make sure not lock myself out of house. there can provide insight situation?
thanks,
brit davis
well got hyper-v team, way helpful in process.
****************
brit – close loop, dev team have identified cause , bug in our vmms (virtual machine management service) when performing sid translation incorrectly process unexpected error code. exists in both v1 , r2. have filed bug resolve in future release. cannot answer though whether backported service pack in server 2008 or server 2008 r2.
****************
-
brit
****************
brit – close loop, dev team have identified cause , bug in our vmms (virtual machine management service) when performing sid translation incorrectly process unexpected error code. exists in both v1 , r2. have filed bug resolve in future release. cannot answer though whether backported service pack in server 2008 or server 2008 r2.
****************
-
brit
Windows Server > Hyper-V
Comments
Post a Comment