One of the new features with Migration Manager for Exchange starting with the installation of hotfix 20170303EX is the ability to configure the tool work with load balancers when using a Native Move. Because of how the New-MoveRequest cmdlet works with Exchange many customers were running into certificate issues when the tool would build the request to submit to Exchange.
So with this hotfix installed we can now use load balancer name spaces such as "outlook.sourcedomain.com".
Here are the steps to configure MMEX to use a load balancer.
Step 1 install public update 8.13 20170303EX or latest if possible
After doing this step, please make sure a project option called UseAdvancedExchangeServerLookup is enabled.
*** Please notice: this option is added since 20170303Ex and is enabled by default.
Step 2 Manually set remote host name via MMEx PowerShell cmdlet
Depending on actual situation, source or/and target remote host name must be set manually via MMEx PowerShell cmdlet:
- In most situations, it must be set to the Exchange server that isn't found as shown in MAgE log, and typically it is the CAS array or load balancing server.
- It can be set to another value if this value can resolve the issue. For guidance please contact Technical Support.
For source remote host name:
For target remote host name:
Step 3 Inject required server data into MMEx DB via SQL script (optional)
This step is required only if after Step 1 & Step 2, the not found Exchange server Exception stack trace still shows in log.
For source remote host name, you can use the SourceRemoteHostName.sql.
For target remote host name, you can use the TargetRemoteHostName.sql.
*** These scripts are found in the attached LoadBalancerSQLScripts.zip