Once the Active Directory credentials have been entered and the Apply button pressed the following error appears:
"Unable to login to Active Directory with credentials provided."
If Exchange 2013 is the target see Workaround 3 specifically.
Workaround 1:
1- Check if User Account Control (UAC) is enabled on the workstation. If it is, turn it off.
2- Try running the NME Migration Manager "As Administrator".
3- Double check that the Exchange Settings screen is able to Apply the settings successfully. Add a "space" to the end of one of the fields on the Exchange Settings screen in order enable the Apply button.
4- The Exchange Server settings screen must return the status of, "Successfully saved Exchange settings", before NME will be able to successfully connect to Active Directory.
Workaround 2:
1- If you are using a configuration template for the MNE process that is failing, try going through the wizard without using a template.
2- If this works, then it may be best to create a new template, which will incorporate any new changes that were made to the MNE Global Default Settings, including any password changes.
Workaround 3:
1- Switch to the Exchange section and locate the Mail server field
2- In the Exchange Server field, you will find a GUID
3- Remove the GUID
4- Click on Apply in the Exchange Section
5- Go back to the Active Directory Section and input all the relevant Server and Account information
6- When complete, click Apply
Workaround 4:
If the customer is trying to migrate to Exchange through a load-balancer, then ask them to replace the FQDN of the load balancer by the FQDN of one the Exchange servers to point MNE directly to exchange bypassing the load balancer.
Workaround 5:
Open a remote PowerShell session to the Exchange CAS server specified within Exchange Server section from the problematic console. This should NOT fail. If failure happens, use another Exchange CAS server you may have within Exchange Server section.
Workaround 6:
The error could also be referring to an incorrect Exchange server specified. Ensure the FQDN of the Exchange Server is used.
Workaround 7:
Clean up the current user profile in the Windows User Profile, and re-login again with the account to avoid the corruption in the user profile folder.
Workaround 8:
Make sure that the MNE Server is separate machine from the Exchange server, but a member of the same domain as AD and Exchange.
Workaround 9:
If the CAS array name set in the Exchange Server section is not set as a SPN you will have this issue. The log file will inform that MNE box cannot connect remotely via Powershell.
