I discovered a bug in Exchange 2016 CU2 where if you
change the MAPI virtual directory URLs using the Exchange Admin Center (EAC), it clears all forms of
authentication from the MAPI virtual directory. This will cause all Outlook clients to constantly prompt for credentials because there are no ways for Outlook to authenticate.
All authentication methods are disabled |
The default IISAuthenticationMethods for the MAPI virtual directory are NTLM, Negotiate, and OAUTH.
Steps to reproduce the issue:
- Double-click the MAPI virtual directory from the Exchange Admin Center to confirm that authentication is set to NTLM and Negotiate. Note that OAUTH is not shown as an authentication method in EAC. Click Cancel to close the dialog box.
- Double-click the MAPI virtual directory and change the internal and/or external URL and click Save.
- Observing the command console, the cmdlet executed is: Set-MapiVirtualDirectory -ExternalUrl 'https://mail.contoso.com/mapi' -IISAuthenticationMethods @() -Identity 'fe29d135-6f9c-4191-a68e-b028d94bd7ff'
- If you examine the authentication settings before you click Save, the authentication settings will be written as NTLM and Negotiate (missing OAUTH).
- Observing the command console, the cmdlet executed is: Set-MapiVirtualDirectory -ExternalUrl 'https://mail.contoso.com/mapi' -IISAuthenticationMethods @(Ntlm,Negotiate) -Identity 'fe29d135-6f9c-4191-a68e-b028d94bd7ff'
If you change the URLs via the Exchange Management Shell (without using the
-IISAuthenticationMethods parameter) the URLs are updated without affecting the
authentication methods.
I reported this bug on Connect and Microsoft confirmed this is an issue with Exchange Server 2016 CU2.
To set the authentication methods for all MAPI virtual directories back to their defaults, run the following cmdlet from EMS:
Get-MapiVirtualDirectory | Set-MapiVirtualDirectory -IISAuthenticationMethods @(Ntlm,Negotiate,OAuth)
All MAPI virtual directories set back to default authentication methods |
I reported this bug on Connect and Microsoft confirmed this is an issue with Exchange Server 2016 CU2.
No comments:
Post a Comment
Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.