Is it okay to have identically named DAG or CAS arrays in source and in target org?
Will this cause any issues during the migration, when using Migration Manager for Exchange?
Identically named DAG servers will cause issues with the Legacy Agents will not be able to work. The DAG will have to be renamed, and then the org re-added or enumerated again.
The same has been observed with identically named CAR arrays. When MSA and MTA were able to work the CSA was failing with
CExchAdmin::GetMailboxInfoE2K Error -2147467259 GetMailboxInfo failed - MAPI_E_CALL_FAILED File: 'aeExchAdmin2K.cpp' Line: '68'
Possible resolution could be to deploy new target Exchange servers (in a different Active Directory site) and create a different Client Access Server Array with a different CAS Array name, and then point the agent hosts (via host file entries) accordingly.
This is due to the NetBIOS name dependency of the CSA. If the source and target CAS Array name is the same, the name has to change to accommodate the NetBIOS name dependency.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center