B
Brian McCullough
Hello,
My client has a COM Add In that they are trying to install on a Windows box
with Terminal Services installed (the machine is to be a Citrix Server).
The box admin has installed an Outlook COM Add In (developed by another
vendor several years ago) on the box which places a custom button on the New
Mail Message Inspector.
The COM Add In installer registers it to HKLM rather than HKCU so that it
should be available to all users on the box (with a LoadBehavior of
"Startup"). When the admin logs onto the box remotely (from an app similar
to Remote Desktop I believe), the admin has no problems seeing and working
with the Add In in his new mail messages.
However, when the admin uses a set of "lesser priveleged" credentials to
remote into the box, the button for the COM Add In is not shown in the new
mail message Inspector's toolbar.
Has anyone experienced anything similar on a box with Terminal Services?
The client has another "Add In" from another company who said that in order
for the "Add In" to work, the client would have to uninstall Terminal
Services, reinstall the Add In, then re-install terminal services.
Any thoughts or ideas welcome!!!
TIA
My client has a COM Add In that they are trying to install on a Windows box
with Terminal Services installed (the machine is to be a Citrix Server).
The box admin has installed an Outlook COM Add In (developed by another
vendor several years ago) on the box which places a custom button on the New
Mail Message Inspector.
The COM Add In installer registers it to HKLM rather than HKCU so that it
should be available to all users on the box (with a LoadBehavior of
"Startup"). When the admin logs onto the box remotely (from an app similar
to Remote Desktop I believe), the admin has no problems seeing and working
with the Add In in his new mail messages.
However, when the admin uses a set of "lesser priveleged" credentials to
remote into the box, the button for the COM Add In is not shown in the new
mail message Inspector's toolbar.
Has anyone experienced anything similar on a box with Terminal Services?
The client has another "Add In" from another company who said that in order
for the "Add In" to work, the client would have to uninstall Terminal
Services, reinstall the Add In, then re-install terminal services.
Any thoughts or ideas welcome!!!
TIA