-
Title
Running Native Move with MMEX when Load Balancers are used in source or target Exchange organizations -
Description
Instead of the FQDN of the Client Access Server or CAS Array we specify the Load Balancer FQDN as a SourceRemoteHostName for MMEX Native Move collection. This is done with the cmdlet described in https://support.quest.com/technical-documents/migration-manager-for-exchange/8.13/user-guide/configuring-migration-using-powershell
As a result we get the following error in the MAGE.log file:
Error Quest.MigrationManager.Exchange.Agent.Jobs.Movers.NotFoundExchangeServerException: Server Name = '[load_balancer_FQDN] not found in the DB.at Quest.MigrationManager.Exchange.Agent.Jobs.Movers.QCrossOrgMover.GetExchServerLdapInfo(String serverName, MigrationSide side, ILdapHelper helper)at Quest.MigrationManager.Exchange.Agent.Jobs.Movers.QCrossOrgMover.Init(Int32 collectionId, IQMailboxDatabase targetMbxDb, IComplexConnectionInfo connections, QMailbox mbx, QMailboxLDAPInfo targetMbx, ActionType actionType, String targetDeliveryDomain)at Quest.MigrationManager.Exchange.Agent.Jobs.QNativeMoveJob.RunJob()Info Native Move Job has been finished(State - 'Failed'). -
Cause
When generating a new Move Request Migration Manager retrieves information from Active Directory by searching for the real Exchange servers in it. It cannot use Load Balancers to generate Native Move Requests.
MMEX 8.13 update 20170303EX has been released to resolve this issue.
-
Resolution
Just installing the latest update for MMEX 8.12 or 8.13 is not sufficient to resolve the issue. Please perform the steps listed below to resolve it:
1) Install the latest update for MMEX 8.12, 8.13 or 8.14 available at https://support.quest.com/kb/77417
2) Re-add both source and target Exchange Organizations to MMEX SQL database by right-clicking on the Source [Target] Exchange Organizations node in MMEX Management Tree and selecting Add Organization command from the shortcut menu.
IMPORTANT: Refreshing the source and target Exchange organizations is not enough. You need to re-add them.
3) Add Load Balancer to MMEX SQL database by running the SQL query below. Before running the query, replace the 'load_balancer_FQDN' and 'Version 14.3 (Build 30123.4)' with a real FQDN of your Load Balancer and real version of your Exchange server. 'anyEx' and 'anyLEDN' values may stay intact.
DECLARE @AGID int
DECLARE @RGID int
DECLARE @ESID int
SET @AGID = (SELECT TOP 1 ID From EXCH_ADMINGROUP)
SET @RGID = (SELECT TOP 1 ID From EXCH_ROUTINGGROUP)
INSERT INTO EXCH_SERVER (AG_ID, ROUTINGGROUP_ID, NAME, OBJECTGUID, LEDN, SERVER_ROLES, VERSION, DELETED)
VALUES (@AGID, @RGID, 'anyEX', 0x1234567890, 'anyLEDN', 1, 'Version 14.3 (Build 30123.4)', 0)
SET @ESID = @@IDENTITY
INSERT INTO EXCH_SERVER_PROPERTY (EXCH_SERVER_ID, NAME, VALUE)
VALUES (@ESID, 'FQDN', 'load_balancer_FQDN')
4) While in the SQL Database in the EXCH_SERVER table it is important to copy the DN of a CAS server from the right exchange environment to the "anyEX" entry.
After that MAGE will retrieve load balancer name from the SQL database and use it when generating a New Move Request.
-
Defect ID
PT134954401 -
Additional Information
If you want to revert changes made by the SQL query above back, please run the following cmdlet in your MMEX Powershell module: Set-MMExProjectOptions -UseAdvancedExchangeServerLookup $false This will set MMEX to retrieve Exchange servers information from AD instead of SQL database as it was doing before installing MMEX update and running SQL query.