After vMotion of domain controller (win2008R2) problems with sysvol share

Hi all,

we always run into trouble when migrating a domain controller (win2008R2) with vMotion. Eventually after the vMotion is finished successfully the sysvol share of the migrated dc becomes not accessible for all other dcs (3 virtual, 2 physical). Because of that the sysvol replication (via DFSR) breaks down and has to be manually restarted.

We use ESXi 5.1 build 1157734 for a long time now and had never such problem when a DC is migrated (e.g. by DRS). We do not take snapshots of the virtual DCs.

Has anyone experienced similar issues and probably got it solved?

ESXi 5.1 build 1157734

ESX cluster of 16 hosts

shared storage (SAN) via EMC VPLEX (distributed volumes)

ESX hardware: fujitsu BX9xx in BX900

Tags (3)
0 Kudos
0 Replies