index > ClickOnce and Setup & Deployment Projects > Change command in combination with ClickOnce

Change command in combination with ClickOnce

I'm trying to understand what effect the Change command has on ClickOnce deployment in a terminal services environment.

I tried the following:

I logged on the TS server as Administrator
I issued the command change user/install
The TS switched over to Install mode.
I installed a new ClickOnce application
I issued the command change user /execute to switch back to execute mode in TS.

I then logged on as a non-administrator user. This non-admin user has not used the ClickOnce application before, but in his start menu I now see my ClickOnce application. When I click on the icon, the ClickOnce application is installed and then launched.

Is it a good idea to do the above if I want 50 different users to be able to easily start my ClickOnce application in a terminal server environment? Or is it a bad idea to combine the change user command with ClickOnce?

I tried this both in Windows Server 2003 and 2008 R2 and did not see any obvious problems.

Nitramafve Wednesday, September 16, 2009 3:01 PM

I don't think it matters. IF the point is just to get a shortcut to show up for the user, I don'g see that this can hurt anything.

The only thing it's really doing is providing a link to the installation URL. ClickOnce applications are installed under the user's profile. So when each person logs in and clicks on your shortcut, they are basically installing the ClickOnce application under their profile.

You can install it under the administrator account until the cows come home, and it won't change the fact that each user has to have their own copy. Just FYI.

RobinDotNet

Click here to visit my ClickOnce blog!