I've found many articles around enabling/disabling it, but the only FORCE option I can think of is to set the LoadBehavior registry key AND LOCK DOWN IT'S PERMISSIONS all via a GPO. "I'd like to find a way to FORCE that add-in be enabled on EVERY Outlook startup." We then go over and re-enable it when they call asking where it went.Īside from the obvious idea of constantly educating the staff, my first thought was:
This doesn't happen too often, but when it does, our staff has gotten used to "taking Outlook's advice" and disabling it. But if one user installed the add-in, and another try to run it, in Outlook 2003, it doesn't appear in the COM Add-in dialog box, while in Outlook 2007, it is 'Unloaded'. From an article MSDN, the registry keys are all under HKCU. Outlook has a feature that will let you know if an add-in is causing start delays, then prompt to disable it. To test, I used a console application to add the registry entries needed. In most cases, they load and function 100% as expected. We use the "WinZip Companion" add-in with Outlook 2007 to encrypt/password sensitive attachments.
0 kommentar(er)
