nashvilleret.blogg.se - Outlook identity registry key

#OUTLOOK IDENTITY REGISTRY KEY HOW TO#
#OUTLOOK IDENTITY REGISTRY KEY UPDATE#
#OUTLOOK IDENTITY REGISTRY KEY WINDOWS#

Modern Authentication is enabled by default. HKEY_CURRENT_USER\Software\Microsoft\Exchange\AlwaysUseMSOAuthForAutoDiscover

It is recommended that users force Outlook to use Modern Authentication by setting the DWORD value of the following registry key to 1.

#OUTLOOK IDENTITY REGISTRY KEY WINDOWS#

HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\Versionįor more information, see Enable Modern Authentication for Office 2013 on Windows devices. HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\EnableADAL Modern Authentication can be enabled by setting the DWORD value to 1 in the following registry subkeys: Modern Authentication is not enabled by default.

Users use Basic Authentication and may be prompted multiple times for credentials.

Modern Authentication is not supported.

Before you modify it, back up the registry for restoration in case problems occur. So far the game plan is to export the entire registry, look for keys with a particular file path and change them until I discover by trial/error which key breaks the process since it doesn't appear to be documented anywhere I've looked online.Serious problems might occur if you modify the registry incorrectly. I've got half a dozen people experiencing the same problem at the moment - if I knew which key is being used I could easily replicate the problem on my own device.

#OUTLOOK IDENTITY REGISTRY KEY HOW TO#

People seem to know how to get from A to Z, but not the in-between in this case. Everything else is irrelevant until I know the specific key being used to get to Outlook. I need to know the exact registry key the getVersion part actually checks. My immediate question is when the CreateObject command is used that has a getVersion to check the registry for info on the currently installed version of Outlook - which should lead to a value on the registry key that has a file path. I've posted a similar entry on social.technet and on the community site. Thank you kindly for your advice in advance! There are redundant keys that reference the same file path - hoping someone can tell me for certain which specific key the command checks to find the version/file path so it can be manually corrected. The work-around found was to copy the current build folder, re-name it to the previous build noted in the error so it matches and no longer dead-ends, restoring the function, but an error still occurs after the fact due to there still being a mis-match existing. Conclusion for a resolution is to manually correct the registry to point to the correct folder that matches the current build of Outlook.Įxample: forced error to show where it is looking- C:\Program Files\WindowsApps\_16051.11629.20214.0_x86_8wekyb3d8bbwe\Office16\Outlook.exeįorced error to demonstrate where the registry value looksįolder/file path it SHOULD be looking at instead. Repetitive online repairs of Office do NOT affect this key and the issue persists. This leads to the program instantly terminating and in the Event Viewer showing a KERNELBASE.dll and.

#OUTLOOK IDENTITY REGISTRY KEY UPDATE#

The program attempting to create a new email then hits a dead-end as the folder for the previous build is no longer there, it was removed as part of the Office update process. The thinking is that the registry key's value was not updated to then match this change. After an update, the build version updated and generated a new folder which contains dll files and a separate OUTLOOK.exe file used for this automation process.

That then goes to a folder for Outlook which contains the current build version of the program on the system. Part of this involves a getVersion check in the registry to a key that has a value of a file path under C:\Program Files\WindowsApps\ Program uses CreateObject to create a new email form using Outlook.