When setting up Public Folder Synchronization job I select the proper target Exchange server from the list of servers in the organization, however Migration Manager console application tries connecting to the other (wrong) CAS server and logs the following in EMWMigration.log file:
2018-05-25 07:59:33.8992 Px1EBC Tx1 A- C- M- Info aeEMWGUIForms.CMapiSettings.Log event|Severity: 5| Source: CSession::Logon| Number: 4800 - Logging on to the mailbox '/o=[Organization]/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=[PF_Admin_Mailbox] (Server: '[Wrong_Exchange_Server_Name]', user: '[domain\service_account]', has assocciated PFDB: 'True', connection flags = 0).
MMEX Project Manager application gets the CAS server name from the RPCClientAccessServer property of the Exchange server you select from the list of Exchange Organization servers when setting up PF synchronization job. Normally, this value is set to the server itself. However, if a different server is set up in this property, MMEX will try connecting to another server specified there and log on to the PF Administrator mailbox. IN this case mailbox logon fails with MAPI_E_LOGON_FAILED error because PF Administrator mailbox is homed on a different server.
To check this value, please run:
Get-MailboxDatabase <name of the mailbox DB homing PF Administrator mailbox> -RPCClientAccessServer
To resolve the issue, set the RPCClientAccessServer property value to be the name of the Client Access Server you're setting the PF Synchronization job with and homing PF Administrator mailbox you created especially for this purpose.
To do that, please run:
Set-MailboxDatabase <name of the mailbox DB homing PF Administrator mailbox> -RPCClientAccessServer <name of the CAS Exchange server>
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center