The add-in installer deploys registry keys to the ‘Local Machine’ hive by default, making the add-in available to all users of that machine.
When installing to virtual or remote desktop infrastructures, the add-in may be downloaded from the website and installed to a server without deploying the registry keys that manage its behaviour; this may be achieved using the following command line:
BeOutlookAddin.exe /install BESETREGISTRY=0
Exposure of the add-in to users may now be managed by adding the following mandatory registry keys to group policies etc:
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\Beyond Encryption]
"FriendlyName"="Beyond Encryption"
"Manifest"="file:///C:\\Program Files\\Beyond Encryption\\BEsecuremail.vsto|vstolocal"
"Description"="Beyond Encryption"
"LoadBehavior"=dword:00000003
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Outlook\Resiliency\DoNotDisableAddinList]
"Beyond Encryption"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Resiliency\DoNotDisableAddinList]
"Beyond Encryption"=dword:00000001
There is an auto-update feature that IT administrators should also disable to allow them to manage the rollout of updates to the add-in:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Beyond Encryption\Outlook Add-In
“UpdateNotifications_Enabled"="false”
Please note: If you are running a 32-bit version of Office in a 64-bit environment then all keys are located within the WOW6432Node equivalent and the manifest is found in "C:\\Program Files (x86)\\Beyond Encryption\\BEsecuremail.vsto"