Task

Solution

1. Run dcdiag and repadmin /showrepl to ensure there are no replication or AD-related errors.
2. Address any DNS misconfigurations or lingering objects.
3. Consider use the same IP address and hostname in OpenStack if possible.
4. Ensure subnet, gateway, and DNS settings are pre-configured in the target environment.
5. If the IP changes, update AD Sites and Services and relevant DNS entries.
6. Ensure that time sync is in good health: use w32tm /query /status to verify time service health.

1. Ensure that Hystax replication agent for VMware uses "force" quiesce strategy to take VMware snapshots - this guarantees that VMware calls VMware Tools and VSS inside the VM to take application consistent snapshots.
2. Before running Cloud Site for final cutover, use "Power off before final replication mode" to gracefully shut down the source DC to avoid USN rollback.
3. Never power on both the source and target DC at the same time to avoid conflicts.

1. Verify that AD DS, DNS, and SYSVOL services start properly.
2. Run dcdiag, repadmin, and check for Event IDs related to SYSVOL and replication.
3. Validate authentication, LDAP queries, and group policies are functioning as expected.

1. For a single DC migration: no FSMO transfer needed; roles move with the DC.
2. For a multi-DC environment: transfer FSMO roles off the migrating DC to another healthy DC before migration.
3. After migration, verify roles with netdom query fsmo and optionally reassign as needed.