General discussion

Locked

Terminal services / client server?

By TobeJ ·
Hi there,

I have been asked to network an application that runs off of a Windows NT "workstation". The user seems to think that the app can run with just a dumb terminal, but I am not sure about it myself. Are all applications avalible through a terminal service "I thought that it was the way that the app is built"? I have only worked with client / server not terminal. I have setup terminal emulators... But not citrix or anything like that.

Can someone point out what are the determining factors of what makes a application avalible for termianl or client server, and maybe a little insight into terminal setup...

Tx

Toby

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Terminal services / client server?

by Blaine Moore In reply to Terminal services / clien ...

Terminal services client pretty much provides a dumb window client to your server. If you set the user's environment, however, an application is started when they log in to the server and that is the only application they are presented, they are not given the desktop or anything else. When they exit the application they are automatically logged out.

Not sure exactly what settings you need in NT, but I am going to assume it is similar to the windows 2000 active directory for terminal services.

In 2k, go to active directory users and computers, open the properties page of the user that you are setting up for terminal services, go to the environment tab, and enter in the information for what program and working directory the user should start in when they log in to terminal services. Also make sure they are in the terminal services group.

Collapse -

Terminal services / client server?

by TobeJ In reply to Terminal services / clien ...

Poster rated this answer

Collapse -

Terminal services / client server?

by Rabbit_Runner In reply to Terminal services / clien ...

Toby, The answer above is quite correct. I only want to add that Windows NT4 (standard) will not support Terminal Server. Windows 2000 server comes with 2 administrative licenses for Terminal Server. NT4 does not have any. To run Terminal Server on NT4, you will need to purchase the Terminal Server edition of NT4. It is not common, but may still be available.

To keep the application on the Windows NT workstation, and run it through some type of terminal program, you will need to get a 3rd party program to give the user access to that workstation. An example would be Citrix, VNC, Carbon Copy, Dameware, pcAnywhere, etc.

Citrix runs on top of NT4. You would need to purchase that if you do not already have it. VNC is free, but not very secure. The otheres will require you to purchase them as well.

To answer the part of the question about determining if an application will run on Terminal Server. If the program will run on a local computer, you would also need to find out if the program will run with multiple sessions. If it can, then it probably will work with terminal emulators.

Just information, hope it helps.

Collapse -

Terminal services / client server?

by TobeJ In reply to Terminal services / clien ...

Tx for the help.

Collapse -

Terminal services / client server?

by E.Eliveld In reply to Terminal services / clien ...

To make life easier you could consider to use 'publiced applications'. No hasly with login into an alternatief desktop, just running the application like is was a 'real' shortcut.

Collapse -

Terminal services / client server?

by TobeJ In reply to Terminal services / clien ...

Poster rated this answer

Collapse -

Terminal services / client server?

by TobeJ In reply to Terminal services / clien ...

This question was closed by the author

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums