OWA 2016 with Office mail app asking for user name password when we try to open the archive email

[pabbinedi]

Hi 

Recently we have moved some test users to exchange 2016 and we configured office mail app to view the archive emails through OWA. But we noticed when ever we open the archive email it's asking for user name and password. Can some one please suggest on how to resolve the issue .

[VirgilDobos]

Hi mate,

EV uses Windows Integrated Authentication. Hence, this is expected if the user is accessing Office Mail App with another user than the one logged on the machine. Even in that case, the authentication prompt will only appear once per session.

[pabbinedi]

Hi VIrgil,

Authentication prompt is coming everytime not only in OWA even in Outlook as well. Any idea?

[VirgilDobos]

Hi there, this can happen for many reasons. Have you gone through this article: http://www.veritas.com/docs/000081334 ?

[pabbinedi]

Hi Virgil,

Since we are migrating from exchange 2010 to 2016. We have not seen this behaviour while we are in exchange 2010(In Exchange 2010 it never used to ask password) once we are moved to exchange 2016 it's keep on prompting for password when ever we are trying to access archive. However as per article provided by you we are using RPC/HTTP and MAPI/HTTP. Is there any fix if we are using different protocol than TCP/IP

Remote Procedure Call (RPC) over Hyper Text Transfer Protocol (HTTP) is being utilized 
 

1. On the users desktop, hold Ctrl+Shift and right-click the Outlook icon in the system tray.
2. Select the Connection Status option.
3. Verify that the Connection is set to TCP/IP, if it is set to HTTP/S then RPC over HTTP is being Utilized.
4. This is expected behavior to be authenticated in an RPC over HTTP environment.

[VirgilDobos]

This should not be the reason for the password prompt. Have you gon through all the points in the article?

[pabbinedi]

Yes i've gone throuh all the post..

Only Solution 5 and 9 are relevant to me at the moment.

[VirgilDobos]

If you have gone through the article, I suggest you log a case with Veritas as the behaviour is not expected.