VSTO install on terminal server

[Bon733]

We have created an Outlook 2003 add-in using VSTO along with all the security
requirements using the instructions on this site:
http://weblogs.asp.net/mnissen/articles/427504.aspx

We have tested the install on seperate XP Pro machines with no problems at
all. We also tried a Windows 2003 server not running WTS. We are now trying
to install it on a Windows 2003 terminal server and have had little success.
Most of the registry entries are insterted along with the program and the
pre-reqs (i.e. .NET 2.0, IAP, VSTO Runtime) . However the add-in does not get
added to the list of COM-Addins and it is not in the disabled list under help
and about. We have even set the project setup to install for all users.

Is there anything special about installation on a WTS environment (besides
the change user /install or through add remove programs)

[Ken Slovak - [MVP - Outlook]]

The registry entries for the addin have to be written to either HKCU or
HKLM. For HKCU you would have to write out those values for every different
Windows logon. Are your entries for the addin (LoadBehavior and so on) being
written out to the user computer/logon? If not that's the problem.
--
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

Post by Bon733
We have created an Outlook 2003 add-in using VSTO along with all the security
http://weblogs.asp.net/mnissen/articles/427504.aspx
We have tested the install on seperate XP Pro machines with no problems at
all. We also tried a Windows 2003 server not running WTS. We are now trying
to install it on a Windows 2003 terminal server and have had little success.
Most of the registry entries are insterted along with the program and the
pre-reqs (i.e. .NET 2.0, IAP, VSTO Runtime) . However the add-in does not get
added to the list of COM-Addins and it is not in the disabled list under help
and about. We have even set the project setup to install for all users.
Is there anything special about installation on a WTS environment (besides
the change user /install or through add remove programs)

[Ken Slovak - [MVP - Outlook]]

I don't use Terminal Server so I have no idea. A TS group might know.

VSTO adds all sorts of complications. You need trust for the installation
folder and all installed components plus all the dependencies and
pre-requisites. How that plays out with TS is probably even more complex.
--
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

Thanks I'll check it out on the server.
Wouldn't setting the property in the install\setup program to everyone
(sorry I forgot the name of the property) and doing the install from
add\remove put the entries in the HKLM as well as the HKCU? Or is there a
trick to this type of install for VSTO add-ins?

[f***@deenax.com]

I've the same problem. The Registry Keys are not written to HKCU.

Our problem: We have to install the addin for all users (they are not
member of the Admin or Power User Group)


Greetings
Franz

Post by Ken Slovak - [MVP - Outlook]
I don't use Terminal Server so I have no idea. A TS group might know.
VSTO adds all sorts of complications. You need trust for the installation
folder and all installed components plus all the dependencies and
pre-requisites. How that plays out with TS is probably even more complex.
--
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

Thanks I'll check it out on the server.
Wouldn't setting the property in the install\setup program to everyone
(sorry I forgot the name of the property) and doing the install from
add\remove put the entries in the HKLM as well as the HKCU? Or is there a
trick to this type of install for VSTO add-ins?

[Ken Slovak - [MVP - Outlook]]

Addins get installed in one of 2 places: HKCU for that user, or HKLM for all
users on that computer. I have no idea if you can use HKLM with TS and
whether or not VSTO addins can register in HKLM. I want to say no, but I'm
not positive.

If you can't write to HKCU and a VSTO addin can't work with registration in
HKLM then you need to select a different development platform.
--
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

Post by f***@deenax.com
I've the same problem. The Registry Keys are not written to HKCU.
Our problem: We have to install the addin for all users (they are not
member of the Admin or Power User Group)
Greetings
Franz

[Cindy M.]

<O$***@TK2MSFTNGP04.phx.gbl>
<067DC637-6715-4B65-BC46-***@microsoft.com>
<***@TK2MSFTNGP04.phx.gbl>
<***@l53g2000cwa.googlegroups.com>
<#***@TK2MSFTNGP04.phx.gbl>
Newsgroups: microsoft.public.vsnet.vstools.office
NNTP-Posting-Host: 53-66.2-85.cust.bluewin.ch 85.2.66.53
Lines: 1
Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newshub.sdsu.edu!msrtrans!TK2MSFTFEEDS01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: number1.nntp.dca.giganews.com microsoft.public.vsnet.vstools.office:4106

Hi Ken,

Post by Ken Slovak - [MVP - Outlook]
Addins get installed in one of 2 places: HKCU for that user, or HKLM for all
users on that computer. I have no idea if you can use HKLM with TS and
whether or not VSTO addins can register in HKLM. I want to say no, but I'm
not positive.
If you can't write to HKCU and a VSTO addin can't work with registration in
HKLM then you need to select a different development platform.

There's a post from Andrew Whitechapel on this in the forum

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=561407&SiteID=1

But it would probably be a good idea to also see this discussion (Office 2003
on VISTA):

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1075538&SiteID=1

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

[Ken Slovak - [MVP - Outlook]]

Ah, thanks, Cindy. I thought I remembered reading something about that but I
didn't remember it exactly.
--
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

Post by Cindy M.
Hi Ken,

Post by Ken Slovak - [MVP - Outlook]
Addins get installed in one of 2 places: HKCU for that user, or HKLM for all
users on that computer. I have no idea if you can use HKLM with TS and
whether or not VSTO addins can register in HKLM. I want to say no, but I'm
not positive.
If you can't write to HKCU and a VSTO addin can't work with registration in
HKLM then you need to select a different development platform.

There's a post from Andrew Whitechapel on this in the forum
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=561407&SiteID=1
But it would probably be a good idea to also see this discussion (Office 2003
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1075538&SiteID=1
Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org
This reply is posted in the Newsgroup; please post any follow question or reply
in the newsgroup and not by e-mail :-)

[unknown]

We have exactly the same problem.

We have developed a VSTO 2005 add-in for Outlook 2003 which works perfects on our machines, but will not work on the Terminal Server (Windows 2003 Server) used by our client.

The strange thing is that we don't get a Com-error or something like that, but the Add-On just will not appear in the list with COM Add-Ons in their Outlook 2003 Client. Exactly like the original client.

We do the following to add our Add-In to Outlook.
1) Installed the Office 2003 Primary Interop Assemblies redistributable package.

2) Installed the VSTO 2005

3) Installed our plugin. This uses the installer created by VSTO for Visual Studio 2005.

4) Added the Runtime Security policies to .NET 2.0 for our signed DLL's. We give Full Rights to our signed DLL's on the Enterprise, Machine and User 'All Code Groups'.

5) For each user we add the registry keys in HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\OURPLUGIN

All software is installed using "control Panel/Add Remove programs" with admin rights because it's a terminal server.

We have also installed the Add-In on another machine within their organization (Also Running Windows 2003 Server) and there it's working without any problems. But that Server is not configured as a Terminal Server.

Is the solution for this problem already found, and could you please share the solution for this?

Regards,

John Belmer
Avance Information Management
---
Posted via DotNetSlackers.com