If you set the LoadBehavior registry value to 2 instead of 3 it will be
visible in the COM Add-Ins dialog but not loaded on startup, only on demand
from that dialog. Setting it to 0 will hide it from the dialog.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Wouter" wrote in message
oups.com...
Hi,

We are migrating from a fat client to a terminal server (Windows Server

2003 with TS) environment. In the old situation we had some user's pc's

installed with a third party tool that uses an Outlook Add-in DLL. In
the new situation this third party tool is installed on the terminal
server and hence available for all users. Problem is, we only have
licenses for a few users and not all of them.


I've tried using NTFS rights to restrict access to the third party's
program folder, but this results in an error when starting Outlook
2003. Is there a way to prevent loading these Outlook Add-in DLL's
programmatically, either by using GPO or by setting (temporary)
Registry Keys using PowerFuse (both options are available)?


TIA,
Wouter