How to override the default RemoteHostName parameter value used in Native Move migrations (4338328)

The value chosen for the RemoteHostName parameter in native move jobs can sometimes be incorrect or undesirable which can lead to errors similar to the following:

"Could not establish trust relationship for the SSL/TLS secure channel with authority 'CASName.domain.com'." 

Knowledge Article 152063 explains how the default value for RemoteHostName is constructed and offers a potential method to change this value by modifying the RpcClientAccessServer for each individual mailbox database.  However this method may not be suitable or allowable in some environments. 

In such scenarios it is possible to override the RemoteHostName value used for native moves, on an individual collection basis.

The ability to override the default value is included in the Migration Manager for Exchange hotfix 20160120EX.

Once the hotfix has been installed, perform the following to override the RemoteHostName value for each native move collection:

1. Open PowerShell on the MMEX console server

2. Import the MMEX PowerShell module:

Import-Module 'C:\Program Files (x86)\Quest Software\Migration Manager\Exchange Data\Tools\DMMExPowerShell\DMMExPowerShell'

3. Set-DMMExCollection –Name COLLECTIONNAME–Type NativeMove –SourceRemoteHostName CASNAME 

note: 

COLLECTIONNAME is he name of the collection as it appears in the MMEX console

CASNAME is the FQDN of the CAS or CAS array in source that should be used as the RemoteHostName value.

The -TargetRemoteHostName parameter can be used to set the target CAS.