Toggle navigation

Exchange 2010 to Exchange 2016 Co-Existence migration OWA redirect not working

Articles \ Exchange

Abstract: When you try to open the OWA (Outlook Web Access) website via an Exchange 2016 Server with an user account which has the mailbox on an Exchange 2010 server you might get a "Something went wrong" with a CAS14WithNoWIA string in the URL.

Full error is:

Something went wrong
We can't get that information right now. Please try again later.

The URL would be: https://excas.int.contoso.com/owa/auth/errorFE.aspx?CafeError=CAS14WithNoWIA

Troubleshooting & Solution:

According to the Microsoft forum you need to enable Windows Authentication on the OWA web site on the Exchange 2010 CAS server.

As the steps aren´t outlined which are needed to solve the issue, here is a short howto:

1.) Check at first which authentication options you have enabled on your Exchange 2010 CAS server via (keep a note of that so that you can switch back if need):

Get-OwaVirtualDirectory -Identity "excas01\owa (default Web site)" | fl

If you have more then one Exchange 2010 CAS server you might need to check multiple CAS server

If you have the issues as described in the forum, you will end seeing the following:

BasicAuthentication                                 : True
WindowsAuthentication                               : False
FormsAuthentication                                 : True


2.) To fix the issue now, you need to enable Windows Authentication on your Exchange 2010 CAS server (and disable as well FormBased authentication; As we migrate over to exchange 2016 which will handle the form based authentication for us, this shouldn´t be a issue for you). This can be done simply via the following powershell command:

Set-OwaVirtualDirectory -Identity "excas01\owa (default Web site)" -WindowsAuthentication $true -FormsAuthentication $false

If you have more then one Exchange 2010 CAS server you might need to check multiple CAS server

3.) After the command completed you can perform some checks to ensure its fixed

Get-OwaVirtualDirectory -Identity "excas01\owa (default Web site)" | fl

Should show now:

BasicAuthentication                                 : True
WindowsAuthentication                               : True
FormsAuthentication                                 : False

Additional you can open the IIS Manager and check the Authentication features on the OWA subfolder. This should now show a enabled status for Windows Authentication.

5.) Now here comes the tricky part. You need to open the IIS Manager on your Exchange CAS Server, Select the OWA site (A) and need to click on authentication (B).

6.) Select "Windows Authentication" (a) and on the right side click on "Providers" (B). Then add NTLM and Negotiate to the providers (D).

If you have more then one Exchange 2010 CAS server you might need to check multiple CAS server

7.) Restart the IIS (or if you wish the whole Exchange 2010 CAS Server. Keep noted that you need to do that on any CAS in your CAS array!)

 

Note: This should be set on the migration day! If you set that earlier you will disable Form based authentication. Because as outlined here, if you enable Form based authentication, then WindowsAuthentication will be disabled and via versa. As conclusion you can enable only Form based authentication OR Windows authentication but not both!

 

Source1 & Source2

Comments (17)

Patrick
  2. #160
This comment was minimized by the moderator on the site

thanks for sharing! this one get me out of troubles after searching many hours!

  1. Reply
Bastian W.    Patrick
  2. #161
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Valerie
  2. #162
This comment was minimized by the moderator on the site

thank you for this tip! helped me out a lot!

  1. Reply
Bastian W.    Valerie
  2. #352
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Alex
  2. #340
This comment was minimized by the moderator on the site

That drove me nuts, thanks for sharing

  1. Reply
Bryan Y
  2. #348
This comment was minimized by the moderator on the site

Very nice, thank you for this. Was essential for our upgrade to 2016

  1. Reply
Bastian W.    Bryan Y
  2. #353
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Ram
  2. #349
This comment was minimized by the moderator on the site

Hi Bastian,

Thanks for the article. we are in the process of migration from Exchange 2010 to 2016.We have configured the above settings in our environment, redirection works fine but in our environment many user's will use additional
common...

Hi Bastian,

Thanks for the article. we are in the process of migration from Exchange 2010 to 2016.We have configured the above settings in our environment, redirection works fine but in our environment many user's will use additional
common group mail id, when we use the above said solution for redirection it works for single sign-on only. User's are unable to login with other ID's apart from id which they have logged in.

Read More
  1. Reply
Bastian W.    Ram
  2. #351
This comment was minimized by the moderator on the site

Hi, what did you mean with "additional common group mail id"? Did you mean an alternate login ID as mentioned here (https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configuring-alternate-login-id)?

  1. Reply
Craig
  2. #397
This comment was minimized by the moderator on the site

Thank you Bastian. This saved me hours of troubleshooting time and a call to Microsoft.

  1. Reply
Bastian W.    Craig
  2. #509
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
George
  2. #508
This comment was minimized by the moderator on the site

When I run the commands, I get the following error:

The virtual directory for the mini version of Outlook Web App can'

Abstract: When you try to open the OWA (Outlook Web Access) website via an Exchange 2016 Server with an user account which has the mailbox on an Exchange 2010 server you might get a "Something went wrong" with a CAS14WithNoWIA string in the URL.

Full error is:

Something went wrong
We can't get that information right now. Please try again later.

The URL would be: https://excas.int.contoso.com/owa/auth/errorFE.aspx?CafeError=CAS14WithNoWIA

Troubleshooting & Solution:

According to the Microsoft forum you need to enable Windows Authentication on the OWA web site on the Exchange 2010 CAS server.

As the steps aren´t outlined which are needed to solve the issue, here is a short howto:

1.) Check at first which authentication options you have enabled on your Exchange 2010 CAS server via (keep a note of that so that you can switch back if need):

Get-OwaVirtualDirectory -Identity "excas01\owa (default Web site)" | fl

If you have more then one Exchange 2010 CAS server you might need to check multiple CAS server

If you have the issues as described in the forum, you will end seeing the following:

BasicAuthentication                                 : True
WindowsAuthentication                               : False
FormsAuthentication                                 : True


2.) To fix the issue now, you need to enable Windows Authentication on your Exchange 2010 CAS server (and disable as well FormBased authentication; As we migrate over to exchange 2016 which will handle the form based authentication for us, this shouldn´t be a issue for you). This can be done simply via the following powershell command:

Set-OwaVirtualDirectory -Identity "excas01\owa (default Web site)" -WindowsAuthentication $true -FormsAuthentication $false

If you have more then one Exchange 2010 CAS server you might need to check multiple CAS server

3.) After the command completed you can perform some checks to ensure its fixed

Get-OwaVirtualDirectory -Identity "excas01\owa (default Web site)" | fl

Should show now:

BasicAuthentication                                 : True
WindowsAuthentication                               : True
FormsAuthentication                                 : False

Additional you can open the IIS Manager and check the Authentication features on the OWA subfolder. This should now show a enabled status for Windows Authentication.

5.) Now here comes the tricky part. You need to open the IIS Manager on your Exchange CAS Server, Select the OWA site (A) and need to click on authentication (B).

6.) Select "Windows Authentication" (a) and on the right side click on "Providers" (B). Then add NTLM and Negotiate to the providers (D).

If you have more then one Exchange 2010 CAS server you might need to check multiple CAS server

7.) Restart the IIS (or if you wish the whole Exchange 2010 CAS Server. Keep noted that you need to do that on any CAS in your CAS array!)

 

Note: This should be set on the migration day! If you set that earlier you will disable Form based authentication. Because as outlined here, if you enable Form based authentication, then WindowsAuthentication will be disabled and via versa. As conclusion you can enable only Form based authentication OR Windows authentication but not both!

 

Source1 & Source2

Comments (17)

Patrick
  2. #160
This comment was minimized by the moderator on the site

thanks for sharing! this one get me out of troubles after searching many hours!

  1. Reply
Bastian W.    Patrick
  2. #161
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Valerie
  2. #162
This comment was minimized by the moderator on the site

thank you for this tip! helped me out a lot!

  1. Reply
Bastian W.    Valerie
  2. #352
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Alex
  2. #340
This comment was minimized by the moderator on the site

That drove me nuts, thanks for sharing

  1. Reply
Bryan Y
  2. #348
This comment was minimized by the moderator on the site

Very nice, thank you for this. Was essential for our upgrade to 2016

  1. Reply
Bastian W.    Bryan Y
  2. #353
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
Ram
  2. #349
This comment was minimized by the moderator on the site

Hi Bastian,

Thanks for the article. we are in the process of migration from Exchange 2010 to 2016.We have configured the above settings in our environment, redirection works fine but in our environment many user's will use additional
common...

Hi Bastian,

Thanks for the article. we are in the process of migration from Exchange 2010 to 2016.We have configured the above settings in our environment, redirection works fine but in our environment many user's will use additional
common group mail id, when we use the above said solution for redirection it works for single sign-on only. User's are unable to login with other ID's apart from id which they have logged in.

Read More
  1. Reply
Bastian W.    Ram
  2. #351
This comment was minimized by the moderator on the site

Hi, what did you mean with "additional common group mail id"? Did you mean an alternate login ID as mentioned here (https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configuring-alternate-login-id)?

  1. Reply
Craig
  2. #397
This comment was minimized by the moderator on the site

Thank you Bastian. This saved me hours of troubleshooting time and a call to Microsoft.

  1. Reply
Bastian W.    Craig
  2. #509
This comment was minimized by the moderator on the site

You are welcome

  1. Reply
George
  2. #508
This comment was minimized by the moderator on the site

When I run the commands, I get the following error:

The virtual directory for the mini version of Outlook Web App can't be found in the same Web site.

Any advise?

  1. Reply
Bastian W.    George
  2. #510
This comment was minimized by the moderator on the site

Not that easy without checking the logs. However I would say something is broken. I would Remove CAS role from Exchange 2010 and restart the server. Then install the CAS role again and retry it. I know it might be not the solution you are looking...

Not that easy without checking the logs. However I would say something is broken. I would Remove CAS role from Exchange 2010 and restart the server. Then install the CAS role again and retry it. I know it might be not the solution you are looking for but would be my advise with so less information.

Read More
  1. Reply
Jason
  2. #560
This comment was minimized by the moderator on the site

Thank you very much, this resolved my issue. Wish Google would rank it higher however. =D

  1. Reply
Bastian    Jason
  2. #561
This comment was minimized by the moderator on the site

you are welcome, and thanks for leaving a note. This might help to push it on a higher position ;-)

  1. Reply
Michiel Peuters
  2. #742
This comment was minimized by the moderator on the site

Thank you!, works perfectly

you just have saved me a couple of hours of frustration.

Michiel

  1. Reply
Bastian W.    Michiel Peuters
  2. #746
This comment was minimized by the moderator on the site

Great to hear it was a timesaver :-)

  1. Reply
There are no comments posted here yet

Leave your comments

  1. Posting comment as a guest.
Attachments (0 / 3)
Share Your Location