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

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

Thanks for your reply Ken. The thing is I have difficulties setting the
Registry to block this Add-in. In the Outlook Add-in Manager it is
mentioned as "Workshare Protect Outlook Extension", but I cannot find
this value in the HKLM or the HKCU registry.

I do think I've found the exact DLL for the add-in (by setting NTFS
deny execute permissions, an error occured, and by using the OfficeIn
tool from http://www.nirsoft.net), so I created the following RegKey to
prevent the add-in from loading:

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outloo k\Addins\Workshare.OutlookAddIn]
"FileName"="WPOutlookAddin.dll"
"LoadBehavior"=dword:00000002
"CommandLineSafe"=dword:00000000

By using this key Outlook seems to prevent loading the DLL in the users
profile folder "\Application Data\Microsoft\Add-in\", but the DLL is in
the application's program folder "D:\Programs Folder\Workshare". How do
I point to the right location of the DLL by the Registry?

TIA
Wouter

Ken Slovak - [MVP - Outlook] schreef:

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

I have no idea what the addin is or where it's registered or how. I'd
suggest uninstalling it and then running something like RegMon and seeing
where it gets installed and under which registry keys.

--
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
ps.com...
Thanks for your reply Ken. The thing is I have difficulties setting the
Registry to block this Add-in. In the Outlook Add-in Manager it is
mentioned as "Workshare Protect Outlook Extension", but I cannot find
this value in the HKLM or the HKCU registry.

I do think I've found the exact DLL for the add-in (by setting NTFS
deny execute permissions, an error occured, and by using the OfficeIn
tool from http://www.nirsoft.net), so I created the following RegKey to
prevent the add-in from loading:

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outloo k\Addins\Workshare.OutlookAddIn]
"FileName"="WPOutlookAddin.dll"
"LoadBehavior"=dword:00000002
"CommandLineSafe"=dword:00000000

By using this key Outlook seems to prevent loading the DLL in the users
profile folder "\Application Data\Microsoft\Add-in\", but the DLL is in
the application's program folder "D:\Programs Folder\Workshare". How do
I point to the right location of the DLL by the Registry?

TIA
Wouter