Dales 
655 pts. |
yes definately the above is very important unless they want to land themselves in the brown sticky stuff. Ideally when you install terminal services it should be on a brand new server with only server 2003 and drivers installed on it. After you have set up terminal services you should install all applications either by the add remove programs dialog in the control panel or by typing “change user /install” to install in TS mode or “change user /execute” to revert back.
But they will need to check that the package is going to handle being used in a TS environment, I think generally anything with an MSI install file SHOULD be ok, but dont bet your wages on it.
might be worth reading up on policy settings to because you can set TS to execute one program only so thats all they get when they logon to the server (no start menu, nothing) so that should give them less to tinker with!
Windows Server 2003, Terminal Services
I'm pretty new to Terminal Services and I've been asked by a client to set up a Terminal services connection for three users so that they can all access the company's accounting software which will be running on a Windows 2003 server. I think I've got a good idea how to set up the server side and even how to set up the remote connection for each user but the thing that I'm not sure about is whether I have to do/enable anything with the actual accounting package to allow simultaneous connections to it? Could you just advise me if there's anything I need to do or whether Terminal Services automatically takes care of this issue? 
0
