Greetings,
I first posted this in the Office365 community forums and was directed here.
We are experiencing an issue where Outlook 2013 (Office365 install) is prompting for user credentials every time it is opened, despite checking the option to remember the credentials. So far we've tried a number of troubleshooting steps, but nothing has resolved the issue. The issue is happening to multiple users on multiple computers.
We are running:
- Outlook 2013 (32-bit) (Office 365 install)
- Windows 7.1 Professional (x64)
- Computer is domain joined (Server 2012 R2 Domain Controllers)
- Mail is hosted on Office 365
We've tried:
- Clearing the Outlook and Office credentials from Credential Manager.
- Removing the mail profile and the saved credentials from Credential Manager, then re-adding the mail profile.
- We've tried adding the mail profile with both a manual configuration of the server settings and allowing Outlook to automatically configure them.
- Ensuring that "Always prompt for logon credentials" is unchecked.
- Setting "Always prompt for logon credentials" to disabled via registry (see http://support.microsoft.com/kb/2984912)
- Confirming that Autodiscover is able to connect (http://www.microsoft.com/en-us/showcase/details.aspx?uuid=e8db028a-06f4-45fb-aff1-e8ac896d29c5)
- Deleting the Autodiscover.xml file so that it is recreated
- Doing an Online Repair of Office 365.
- Reinstalling Office 365
- Recreating the user's Windows profile.
- Ensuring all applicable Windows updates and Office updates are installed.
- Changing Proxy Authentication from Basic to NTLM (will not connect with NTLM)
The machines this is occurring on are on a new domain that we are in the process of setting up. The user accounts are still on the old domain. Cross-domain trusts are set up in both directions and all other services are working fine. GPO settings across both domains have been set up to be identical. The issue occurs on computers that were built directly on the new domain as well as computers built on old domain and migrated over. Machines that are not domain joined or are still on the old domain are not experiencing the issue.
If any of you could provide any insight or other steps that we could try I'd greatly appreciate it.
Thanks