Hi,
Im Setting up V Center 5 with Domain Senario as it says VMWare recommands.
In our environment we dont have a domain but i build the windows 2008 r2 with domain role.
My question was ..what will happen if domain is not available or crash.
Can i able to connect v center and work normally with the v center server local account.
Because in this senario i have to maintain high availability for both machines.
Infact both are physical machine due to the reason i read about issues of Virtual v center with VDS environment.
Thanks in advance
My question was ..what will happen if domain is not available or crash.
In general we have multiple role in AD, there will be a minimum of 2 DC (Primary and child) to avoid single point of failure.
few common issue:
1. If Domain is not available, user authentication based on domain will fail, users wont be able to login to server.
2. If DNS is intergarated with domian, internal dns resolution wont work. ESXi resolving with this DNS will get disconnected temporary if dns with domain is configured and you dont have host entry in the resolve.conf.
3. Time synchronisation issue if the time is configured from DC.
Any resource using ad authentication will not abe accessible.
Can i able to connect v center and work normally with the v center server local account.
Yes you should able able to connect Vcenter via IP and local accont and also Database for your server should be authenticated via sql authentication.so that database authentication will not have issues.
Infact both are physical machine due to the reason i read about issues of Virtual v center with VDS environment.
Just a Note:
This should be not longer a issue, all the running VM will up running, only thing is vds wont be able to manage and you can do a migration of vds to vss with no downtime for the vms. and relating this to AD down, you VM will up, but dns, ad authentication issue will be there.
refer this below link between vds - vcenter outage testing - I have done all this testing and vcenter outage, this shouldnt be a barrier for vms to work.
http://www.yellow-bricks.com/2012/02/08/distributed-vswitches-and-vcenter-outage-whats-the-deal/
My question was ..what will happen if domain is not available or crash.
In general we have multiple role in AD, there will be a minimum of 2 DC (Primary and child) to avoid single point of failure.
few common issue:
1. If Domain is not available, user authentication based on domain will fail, users wont be able to login to server.
2. If DNS is intergarated with domian, internal dns resolution wont work. ESXi resolving with this DNS will get disconnected temporary if dns with domain is configured and you dont have host entry in the resolve.conf.
3. Time synchronisation issue if the time is configured from DC.
Any resource using ad authentication will not abe accessible.
Can i able to connect v center and work normally with the v center server local account.
Yes you should able able to connect Vcenter via IP and local accont and also Database for your server should be authenticated via sql authentication.so that database authentication will not have issues.
Infact both are physical machine due to the reason i read about issues of Virtual v center with VDS environment.
Just a Note:
This should be not longer a issue, all the running VM will up running, only thing is vds wont be able to manage and you can do a migration of vds to vss with no downtime for the vms. and relating this to AD down, you VM will up, but dns, ad authentication issue will be there.
refer this below link between vds - vcenter outage testing - I have done all this testing and vcenter outage, this shouldnt be a barrier for vms to work.
http://www.yellow-bricks.com/2012/02/08/distributed-vswitches-and-vcenter-outage-whats-the-deal/
In general we have multiple role in AD, there will be a minimum of 2 DC (Primary and child) to avoid single point of failure.
Just a little detail, you should definitely have at least two domain controllers to get redundancy and they should be in the same domain - but is not really called primary and child. If selecting "child" in dcpromo then it will be another subdomain which is not the wished configuration here. The two DCs should be hosting the same domain database between them and there is not really a primary one (with some exceptions..)
Anyway, I totally agree that a minimum Active Directory setup should have at least two DCs.
Agreed .