Domain controller roles in a virtual hosting environment

from Microsoft

Tips for DC's migration to a virtual hosting environment and p2v migrations:

1. Disable the write cache on all volumes of the guest operating system that host the Active Directory database, the logs, and the checkpoint file ( It include Active Directory, the File Replication service, WINS, and DHCP).

2. Back up the system state of at least one domain controller in every domain several times a day (Microsoft's recommendation).

3. Do not pause the domain controller for long periods of time before you resume the operating system image. If you do pause the domain controller for a long time, replication may stop and cause lingering objects.
Event ID: 2042

4. Active Directory does not support other methods to roll back the contents of Active Directory except of a system state restore.

5. Microsoft strongly recommends that:

you locate critical server roles on domain controllers that are installed directly on physical hardware. Critical server roles include the following:

Global catalog servers
Domain Name System (DNS) servers
Operations master roles, also known as flexible single master operations (FSMO)

Recommended links:

875495 hotfix for Windows 2003 SP1

885875 hotfix for Windows 2000

Considerations when hosting Active Directory domain controller in virtual hosting environments

Support policy for Microsoft software running in non-Microsoft hardware virtualization software

1 comment:

Vladan said...

It means that you should not use your VMs with FSMO roles. But if you have hardware failure on a physical server, you are ....

Vladan - ESX Virtualisation

Recent Posts