Terminal Server settings

[MasterRacker]

I have a Win2003 terminal server setup to serve desktops to remote vpn users for certain apps.

One of my apps appears to need local admin permissions to run (or at least install all components).

Is there a way to configure a user to be a local admin to their own TS session without being a local admin on the server itself?

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[dberg35]

Is the app being used on the Terminal Server I assume? If this is the case go the folder in the program files and give users full rights to it. I do not suggest giving any user admin rights to the server.

 

[MasterRacker]

It's a web based app. The problem is that there is some initial setup that needs to be done in each user profile. I have to log in as the user, browse to the app, allow it to download some .NET controls and active-x controls.

Even on a discrete PC with multiple users, I need to repeat the process with each user profile. Even with the site added to IE trusted sites and Trusted Sites security set as low as it can go, I've had issues with users who were not local admins being able to do the initial setup.

I agree that the users should not be local admins to the server, I I think I'm going to need to make them local admins to their own virtual desktops.

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[dberg35]

You stated Virtual Desktop so they are accessing this on a Terminal Server? If it requires DOT Net then if you install it on the server or pc it should work for everyone.

 

[MasterRacker]

I may be mixing my terms. We are using Windows 2003 Terminal Server sessions reached via RDP. My understanding was that virtual desktops are used in the background to isolate the sessions.

.NET is on the server. A batch file needs to be run per user to set .NET security for the app. IE needs to be configured per user to place the site into Trusted Sites. After that, certain components have to download through IE while running the app. It is those that won't download and install properly. Based on a similar experience with a physical PC also running this app, versus others that worked fine, it appeared that the users need to be local admins to get all the components to load properly.



Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]