-
Title
Native move collection fails to create move requests but shows no errors -
Description
On attempt to move the mailbox it has the 'Migration Stage' of 'In Progress' and that does not change. Nothing is happening, no move requests actually exist and no errors are present in the MAgE.log
Upon closer inspection of MAgE log it can be observed that Powershell requests are not completing, i.e. any activity ends on the line saying "PowerShell runspace state changed to 'Opening' " but it is never followed by success or failure
Log file is looking similar to the following:
2017-10-04 09:47:15.0650 PxAFC Tx23 A5 C1 M3 Info Uri: http://exchange01/powershell?serializationLevel=Full, Cred: company\svc_qmm
2017-10-04 09:47:15.1275 PxAFC Tx23 A5 C1 M3 Trace >PowerShell runspace state changed to 'Opening'. Reason: ''2017-10-04 09:47:15.1275 PxAFC Tx23 A5 C1 M3 Trace Loaded assembly 'System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=a03e5f7f21d50a3a'.
2017-10-04 09:47:22.9154 PxAFC TxB A5 C1 M3 Info All mailboxes are completely processed or being processed now according to criteria defined by minimum processing intervals for MAgE.
2017-10-04 09:47:39.4528 PxAFC TxB A5 C1 M3 Info All mailboxes are completely processed or being processed now according to criteria defined by minimum processing intervals for MAgE.
2017-10-04 09:47:55.9725 PxAFC TxB A5 C1 M3 Info All mailboxes are completely processed or being processed now according to criteria defined by minimum processing intervals for MAgE.
2017-10-04 09:48:12.4968 PxAFC TxB A5 C1 M3 Info All mailboxes are completely processed or being processed now according to criteria defined by minimum processing intervals for MAgE. -
Cause
This can be caused by Powershell connection issues. MAgE will try various authentication methods in order and needs a success or failure response to switch to the next one. If there is no response at all, it will keep waiting for one.
-
Resolution
Test the Powershell connection from MAgE host to Exchange server listed in the the logs by running following commands:$cred = Get-Credential
Enter-PSSession -ConnectionUri http://EXCHANGESERVER/powershell?serializationLevel=Full -ConfigurationName Microsoft.Exchange -Credential $cred
$cred = Get-Credential
Enter-PSSession -ConnectionUri https://EXCHANGESERVER/powershell?serializationLevel=Full -ConfigurationName Microsoft.Exchange -Credential $cred
$cred = Get-Credential
Enter-PSSession -ConnectionUri http://EXCHANGESERVER/powershell?serializationLevel=Full -ConfigurationName Microsoft.Exchange -Credential $cred -Authentication Kerberos
$cred = Get-Credential
Enter-PSSession -ConnectionUri https://EXCHANGESERVER/powershell?serializationLevel=Full -ConfigurationName Microsoft.Exchange -Credential $cred -Authentication Kerberos
All of them should return success or failure, if they hang with no response, consider addressing Powershell issues or moving MAgE to a server where Powershell works as expected.