Terminal Server - Install applications

[JPL910]

I am very new to Terminal Serverices...

Goal: Allow remote users to securely access the network and applications, including email, while using the least amount of resources. (We are currently using GoToMyPC which requires all remote uses to have a physical workstation at the office - not very cost effective)

I purchased a new server with Server 2003 64bit (32gb RAM) and the Terminal server licenses. I have installed the O/S and licenses but am now running into problems installing the apps. The primary application my users will need to use does not install on or support server 2003 64 bit. What are my options at his point?

Do I need to do anything to their profile in active Directory to allow them access to this?
What is the best way to configure access? (VPN tunnel then RDP or NAT/RDP directly to the server?)

 

[mofusjtf]

Typically, the non-64-bit applications will install in compatiblity mode. You should see a program files folder and a program files (x86) folder on your C drive. At least all my 64-bit servers have that. Have you contacted support?

Also, do you have an open license for Win2k3? You could download Hyper-V and setup a 32-bit TS in a VM. If you have the appropriate number of licenses you could setup multiple TS VM's and spread your users accross them to help with performance since the 32-bit will only net you 4GB of RAM essentialy wasting 28GB of RAM. This is just one possibility.

The easiest way is to open 3389 on your firewall and forward it to your Terminal Server. This is a secure connection but it is more secure if you first establish a VPN connection. It will also be easier to with a VPN is you go the VM route with multiple TS VM's.

I would also do some reading on Terminal Server Profiles. You should use this instead of the local profiles. A quick Google search will get you the information you need.

 

[dberg35]

One other thing to look at is was the server in app mode? If not the that could be the issue with that application. I also agree with mofusjtf using a Virtual solution but that depending on how many users. I currently have 3 TS serves one 64bit and no problem with any apps plus it only has 8gigs of RAM and supports about 60 users running multiple apps.

 

[Zelandakh]

That is massive overkill and 64 bit will hamper you. However...

RDP to the server using mstsc /console. Once in there, go to a command prompt and type "change user /install". Install the app. You may need to copy the installer to the HD and run the setup.exe in compatibility mode using right click, properies...

Once installed, go back to command prompt and type "change user /execute".

Executing users is ALWAYS the last task of the day.

 

[JPL910]

Thanks for all the advice. I will try to install as suggested by Zelandakh first as that seems the most straight-forward.

I have purchased licenses for 30 remote users and will probably have about half of that actually using it.

I see a tab in AD labeled "Terminal Services Profile". Should I do anything here for the users or is it optional?

 

[mofusjtf]

Using Terminal Services Profile is probably a good idea. Profile problems can be a pain on a terminal server.

http://technet.microsoft.com/en-us/library/cc776120.aspx

 

[JPL910]

Thank you for all the help so far. My current issue is that when a user logs onto the terminal server with RDP, one particular application does not work unless the user is a member of the domain admin group.

- I have a user, userx, that can log onto the terminal server and run all but one application. The application has a SQL backend but it cannot get past the logon screen. When I add userx to any other domain group, I am still unable to logon to this application. As soon as I put userx into the Domain Admin group, the application works without error.

I then tried RDP for userx onto other computers (non servers - XP Pro workstations) and was able to run the application without issue and without being in the Domain Admin group. On these computers, userx is not even set as a local admin.

I have tried putting userx as a local administrator on the terminal server, and still no luck. It seems to only work when the user is a member of Domain Admins.
Note: The user is a member of remote desktop users

Any ideas?

 

[JPL910]

I guess this one has everyone stumped?!?

Thank you kindly.

 

[withanh]

Executing users is ALWAYS the last task of the day.

Snort!