Outlook 2013 Not Saving Password

[Frick]

I have a new client where Outlook 2013 will not save the user credentials. I have narrowed it down to being a setting in Windows Credential Manager where the credentials Persistence is set to "Local Login" but needs to be "Enterprise".

This looks like an issue with Outlook 2013 as there is no issue on systems with Office 2010. I did see some references on Google to old bad patches that may cause this issue, but I have verified the systems are fully updated and the listed bad patches are not present.

The other possibility I have found is it could be a Group Policy security setting. I have looked through the policies but have been unsuccessful in identifying what enforces this setting.

Anyone with any insight? Thanks in advance!

 

[BlackLabTechs]

Did you try the resultant set gpo report? I can't remember exact name but select user and end device and it will report all gpo settings in effect. Its in the gpo
manager

 

[Frick]

Did you try the resultant set gpo report? I can't remember exact name but select user and end device and it will report all gpo settings in effect. Its in the gpo
manager

I ran the tool and found nothing in group policy. This has to be an Outlook 2013 issue.

 

[AnthonyK]

Create a new profile in the Mail applet in the control panel and sign him in. Then open outlook selecting the new profile and see if it works.

 

[Frick]

Create a new profile in the Mail applet in the control panel and sign him in. Then open outlook selecting the new profile and see if it works.

I have already done that. The client was using a pop3 provider and passwords saved without issue. We migrated them to O365 and it is the new exchange profile that won't save the password.

 

[TurricanII]

Shot in the dark - is the Autodiscover DNS all set up OK? Maybe Outlook is being directed to a duff server when opening.

 

[Frick]

Shot in the dark - is the Autodiscover DNS all set up OK? Maybe Outlook is being directed to a duff server when opening.

Autodiscover is all good.

I also verified it is a outlook 2013 issue as a new 2010 and 2016 work fine.

This is really making me scratch my head!?!?

 

[MikeLierman]

Does he have another computer you could try it on? Does the same issue present itself? If no, then it's something with the computer and the underlying software. I recently had a client that had issues with Excel and Outlook crashing and behaving very weird.

To resolve the issue, we ran the PST repair tool on his Outlook database files, ran SFC /ScanNow on all the machines. Then, followed up with DISM /Online /Cleanup-Image / RestoreHealth. Then rebooted each of the problematic machines. Uninstalled Office completely, ran the MS office removal tool. Then deployed the latest Office installer. Problem solved. Corruption is a weird beast. You'd be surprised what corrupted files can do, and what odd ball problems will appear.

 

[Frick]

This is not a single computer issue. It is all the clients systems that are running Office 2013.

I have confirmed it is office 2013 as the issue does not occur when 2016 is installed. When 2016 is uninstalled and 2013 reinstalled the issue returns.

The client previously purchased 18 full Office 2013 licenses so Office 365 or a new version purchase is not an option.

 

[johnrobert]

Microsoft should sort this out for free

 

[Metanis]

This https://kb.intermedia.net/article/2353 is an excellent start. Since OP claims the problem only happens in O2k13 then I think it's safe to conclude it's not a Domain GPO. It would be interesting to install O2k13 then reboot, then delete all applied machine policies, reboot again and fire it up. Also it might be interesting to manually create the required Credential using Credential Manager rather than having Outlook add it for you.

Put this in a script to totally eliminate any policies on the machine...

del /S /F /Q "%ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History\*.*"
del /S /F /Q c:\windows\system32\grouppolicy\*.*
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Group Policy" /f
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy" /f
reg delete "HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Group Policy" /f
reg delete "HKCU\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Group Policy\DataStore" /f
reg delete "HKLM\Software\Policies\Microsoft" /f
reg delete "HKCU\Software\Policies\Microsoft" /f
reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies" /f​