How to migrate AD controllers from VMware to OpenStack

How to migrate AD controllers from VMware to OpenStack

Task


Migrate AD controllers from VMware to OpenStack.

Solution


Key points to consider during the migration of AD controllers from VMware to OpenStack with Hystax Acura.

Before the migration
  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.
During the migration
  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.
After the migration
  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.
FSMO-related notes
  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.

    • Related Articles

    • How to change network settings of an Acura instance in VMware (version 4.2 or newer)

      Challenge Hystax Acura for VMware is deployed as a virtual machine to a source ESXi host. It uses DHCP for its NIC by default. However, these default settings might not work in case the source VMware infrastructure doesn't have DHCP enabled or ...

    • How to turn on debug logging for Hystax VMware Replication Agent

      Task Turn on debug logging to perform advanced troubleshooting of Hystax VMware Replication Agent (HVRAgent) SolutionGo to the TUI and select the “Agent options” menu Choose the “Enable debug logging” option You can see the logs in agent TUI or in ...

    • How to change the hostname of a VMware replication agent

      Task Change the hostname of a VMware replication agent. Solution The VMware replication agent hostname ("hwragent", by default) can be changed from the agents's console. Go to the agent command line by pressing the "To console" button in TUI. Edit ...

    • How to edit the "hosts" file of a VMware agent

      Task Edit the "hosts" file of a VMware agent. Solution The VMware agent's "hosts" file is mounted in the agent system and can be edited from its TUI. Perform the following steps: 1. Go to the TUI and select the “Agent options” menu. 2. Select “Edit ...

    • How to change network settings of an Agent in VMware

      Challenge Hystax VMware Agent (HVRAgent) is deployed as a virtual machine to a source ESXi host. It uses DHCP for its single NIC by default. However, these default settings might not work in case the source VMware infrastructure doesn't have DHCP or ...