Outlook Add-ins for Terminal Server Users

[Pixillated]

I wrote a COM add-in that, once registered, starts when Outlook starts,
except for the Terminal Server users, where each user has to manually add the
COM add-in using the COM Add-In form in the Outlook Options menu (can't do a
global install like a regular workstation).

Is there a way automatically select the a COM add-in for each user's Outlook
instance? so we don't have to visit each user session.

Thanks,

 

[Ken Slovak - [MVP - Outlook]]

Make sure the addin is registered in HKCU for each user and make sure that
any data storage does not use \Program Files but uses the user's local data
storage folder. You can get that from the registry by querying
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Local
AppData and appending your application name to that path. That's where you
should store INI files, error logs and any other data that needs to be
written to disk.

That's all you really need to do to make an addin compatible with terminal
server.

 

[Pixillated]

How do I make sure the addin is registered in HKCU for each user?

Each user does see the add-in in the list of add-ins, it just doesn't
automatically start for them. Am I installing it wrong? Or is there something
missing in my IDTExtensibility2 implementation?

Thanks.

 

[Ken Slovak - [MVP - Outlook]]

You install it for each user. That can be done using a Windows logon script
and packaging your installation as an MSI file. If you do that you can call
msiexec.exe and do a silent installation. Your script would write a registry
value to indicate the package was installed or perhaps a dummy 0 byte file
in C:\ root that could be checked when the script starts up so you don't
continually perform the installation.