The Non-domain Member Check policy shuts down my server
hi, read on windows essentials blog that use 1 license install hyper-v role on physical machine , essentials role on virtual machine on top of that.
so purchased r2 essentials license, installed on new server, did not run wizard, enabled hyper-v, , installed essentials again in vm launched wizard. removed essentials role physical install, file server role , hyper-v roles enabled here. runs fine.
i wanted explore hyper-v replica functionality used old esx server , installed hyper-v server core (r2) on it. based on various tips on interent joined both hyper-v machines (the 'essentials' 1 , core) (essentials) domain , replication work fine out of box. fantastic!
however after while 'essentials' machine started shutdown due non-domain member check notion: this server can in workgroup or domain controller.
is designed behaviour? if use essentials license install physical os can't joined domain? without joining domain, authentication between servers (not mention replication - certificate stuff) gets complicated typical 'essentials' admin me.
i know can install hyper-v core on new server instead of 'essentials' one, have no ui restrictive me. there other way?
kind regards,
rogier
hi,
afaik, designed behaviour. when first setting ws essentials 2012 r2, choice of setting virtual machine in wizard. when choosing that, hyper-v host remain in workgroup.
a domain controller in single dc enviroment not recommend, since host not able authenticate these dcs if not yet started. (even though works , supported..)
an article on how set hyper-v replica between 2 workgroup machines certificate, find here:
http://blog.powerbiz.net.au/hyperv/how-to-set-up-hyper-v-replica-for-small-businesses/
hope helps you, though might not answer wanted...
mct | mcse: private cloud/server, desktop infrastructure
Windows Server > Windows Server 2012 Essentials
Comments
Post a Comment