The variable RegistryHiveName is not translated.
The problem is probably coming from one of the custom actions. But they are stored in HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Adobe\Acrobat Reader\\Installer\Migrate, as we can see on the screenshot below: They registry keys have to be stored in HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\Adobe\Acrobat Reader\2015\Installer\Migrate to be automatically added in the HKCU of the user at its first launch of the application. Unfortunately, it is not the same with Adobe Acrobat Reader DC. HKLM\Software\clients\mail\microsoft outlook Settings:ĭLLpatchEX: C:\PROGRA~1\MICROS~1\Office14\OLMAPI32.DLLĭid something change between Adobe Reader 11 and Reader DC with the way it uses MAPI ? Does Reader DC not need this outlook64bridge workaround ?įor Adobe Reader, all the registry keys which are added with the Adobe Customization Wizard are automatically added to each user. Once I launch outlook then the key HKCU\Software\clients\mail "default" is changed to Microsoft Outlook which then uses the settings in HKLM\Software\clients\mail\microsoft outlook and send as email works until GPO changes the settings back However, now when the user logs on the HKCU\Software\clients\mail default key is set to outlook64bridge which then points to "C:\Program Files\Microsoft Office\Office14\OLMAPI32.DLL" and Adobe Reader DC is unable to send the email and says default email application is unknownĭLLPath: C:\Program Files\Microsoft Office\Office14\OLMAPI32.DLLĭLLpatchEX: C:\Program Files\Microsoft Office\Office14\OLMAPI32.DLL
GPO to implement the outlook64bridge registry fix(see below link) has been in place since Adobe Reader 11 was installed.Ĭannot send email with microsoft outlook 2010 (64 bit) from Adobe outlook not recognised as default email client Upgraded from Adobe Reader 11 to Reader DC on xenapp6.5 farm with Server 2008R2(64bit) and office (64)
0 kommentar(er)
