miércoles, 13 de junio de 2012 15:28
I've a huge domain with a lot of site, in each site I've an Hyer-V cluster with several virtual machines, all satellite site have domain controller implemented as virtual machine. So in each satellite site the only physical machines are the Hyper-V cluster nodes.
When my cluster reboot after a controlled shutdown, commanded by the UPS, it boots without a domain controller in its site and several resources often fail:
all the virtual machine
Is there any workaround?
Todas las respuestas
miércoles, 13 de junio de 2012 16:26Moderador
Just make sure that the DC is auto starting up. and you can create a task scheduler that runs only if the server bootsup that task makes sure all the items that you need are running.
best practice is at least on DC is physical. So the placement of the DC is critical, I would place the DC not on a CSV ( chicken and egg )
Greetings, Robert Smit [MVP] http://robertsmit.wordpress.com/ “Please click "Vote As Helpful" if it is helpful for you and Proposed As Answer”
viernes, 15 de junio de 2012 14:02
Store the VM on local storage and have it auto-start, as Robert says. I do this for my labs all the time and it works without a hitch. It is not a best practice, but it works fine.
Here is a good article that explains the things you need to consider for your environment - http://support.microsoft.com/kb/888794
martes, 19 de junio de 2012 3:21Looking back all the post.. is interesting to see this forum have grow
Cisco Certified Network Associate
Cisco Certified Internetwork professional - MPLS
Certified Information Systems Security Professional
Microsoft Partner Network 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Certified Ethical Hacker
Computer Hacking Forensics Investigator
Certified Sonicwall Security Administrator
martes, 19 de junio de 2012 8:28
I'm thinking a development based on the information you all have given to me, the idea is:
Hyper-V cluster with x nodes, each node has a domain controller stored in its local storage (so theese domain controllers are not high available). Each node of the cluster has the cluster service in "Manual Start", this domain controller is set to auto start when Hyper-V starts.
I develop a simple service that I install into each domain controller, this service is in automatic delayed start. This service has the task to start the cluster service on the node where the domain controller resides, the service runs with the privileges needed to start clussvc on the cluster node. In this way I'm shure that when a single cluster node boot, no errors are risen in the cluster environment, when the custom service in the domain controller starts the clusvc, the cluster environment has AD fully available.
What do you think?
viernes, 22 de junio de 2012 13:09Sounds like a bit of overkill. <grin> Even with a two-node cluster, with a DC VM on local storage on each node, I generally have no issues with things starting correctly after a power outage. And, that assumes that you don't have a network to the rest of your environment available. You say you have a lot of sites. I would assume that you have network connections back to a parent site of some sort. So, if the cluster is looking for a domain controller and does not find it locally, it will try across the network. The situation you are trying to protect against might happen in very, very rare situations, e.g. your network is down, you have a power failure, and neither of your domain controller VMs starts automatically. Sure, you can write a custom service, but it's a lot of work for something that might never happen.