windows 2008 r2 domain controller on VMWARE
dear gurus
we heard from experts of vmware vendor local in emea
that keeping the master or primary ad dns windows 2008 r2 server on virtual enviornment not advisable as it should be always on physical seperate server to manage it
rest secondary servers can be build on it
your input highly appreciate then you may close this call
we heard from experts of vmware vendor local in emea
that keeping the master or primary ad dns windows 2008 r2 server on virtual enviornment not advisable as it should be always on physical seperate server to manage it
rest secondary servers can be build on it
your input highly appreciate then you may close this call
Agreed - Unless your VM Hosts are authenticating against AD, you don't need a physical DC so long as you have no more than one DC per VM Host.
If you can provide sufficient hardware for virtualized DC, I don't see any good reason for not installing most of DCs on VMware
I always noticed that organizations do not provide sufficient resources to virtualized DC servers
OR
If you take one physical DC and virtual DC with same configuration I always seen a better performance with physical DC server (Because physical DC hardware has to tackle only its own load)
Also if your VMware infrastructure is hosted on Blade server, personally I never install virtual DC in blade center because of possible network issues
Only thing you should not take snap shots of virtual DC on VMware as it will create USN roll back issue and resulting replication will stop with that virtual DC and then you need to demote \ promote the same
Also you should avoid time sync between virtual DC and VMware ESX host
As long as you are taking full system state backup of virtual DC, you are safe hopefully
For bigger size organizations having 10,000+ users, computers I'd always prefer to build at least two physical servers with 4 to 8 core cpu and 8 GB of memory from performance point of view as I have noticed some sluggish performance with virtual DC
Also if your VMware is fully loaded with another app servers as well, then I'd prefer physical DCs to separate AD traffic, because virtualization is concept where all virtual servers practically communicate through physical host network cards only
Mahesh
I always noticed that organizations do not provide sufficient resources to virtualized DC servers
OR
If you take one physical DC and virtual DC with same configuration I always seen a better performance with physical DC server (Because physical DC hardware has to tackle only its own load)
Also if your VMware infrastructure is hosted on Blade server, personally I never install virtual DC in blade center because of possible network issues
Only thing you should not take snap shots of virtual DC on VMware as it will create USN roll back issue and resulting replication will stop with that virtual DC and then you need to demote \ promote the same
Also you should avoid time sync between virtual DC and VMware ESX host
As long as you are taking full system state backup of virtual DC, you are safe hopefully
For bigger size organizations having 10,000+ users, computers I'd always prefer to build at least two physical servers with 4 to 8 core cpu and 8 GB of memory from performance point of view as I have noticed some sluggish performance with virtual DC
Also if your VMware is fully loaded with another app servers as well, then I'd prefer physical DCs to separate AD traffic, because virtualization is concept where all virtual servers practically communicate through physical host network cards only
Mahesh
Below Microsoft KB article will clarify your doubts and these are best practices while configuring DC on virtual environment.,
Things to consider when you host Active Directory domain controllers in virtual hosting environments
http://support.microsoft.com/kb/888794/en-us
- Manjunath Sullad
Things to consider when you host Active Directory domain controllers in virtual hosting environments
http://support.microsoft.com/kb/888794/en-us
- Manjunath Sullad
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i am highly appreciate your response put on this
Most of my customers are running all of their infrastructure on vmware and nothing physical.