Terminal Services in Win 2000 1

[david7777777777]

Anyone have any battle scars working with Terminal Services in Windows 2000? Someone is asking me if it would be appropriate to use in our enterprise for users to be transferring database data across our WAN. I'm headed to Microsoft's site now. Thanks.

 

[Hungster]

Terminal Services has two mode
one remote admin
one apps mode

where you need licenses for both, when you buy the license, you need to call Mcirsoft up for the activation key; i personally use apps mode and load Citrix Metaframe on for the users to access my database server, it runs a lot faster

Hung

 

[david7777777777]

I'm reviewing a proposed project where someone is suggesting using just Terminal services on Win2K to allow users in NY and San Francisco to access SQL 2000 data on a server in San Francisco. I think it would be best to use Cirtix. Any good argument points I can use to make sure Citrix wins this argument? I'm worried about losing the argument due to the added cost of Citrix licensing on top of Microsoft licensing. Thanks.

 

[ShackDaddy]

I personally set up MS Term Services to allow a telemarketing firm to access a VB front-end app tied to a SQL back-end. I used a custom locked-down profile and set the app to be the shell that fires off when the user connects, rather than 'explorer.exe' and it works like a charm.

The argument you are trying to win is Citrix+MSTS vs MSTS. Make sure that you really need the specific additional Citrix features before you jump into it, since you will have to pay all the Microsoft licensing costs either way. I would suggest that you might not need the extras. I haven't evaluated the speed difference between the basic M$ RDP and the Citrix add-on though, so I can't help you evaluate that. I just haven't noticed my systems being particularly slow. I usually have around 20 users in the system at a time.

ShackDaddy

 

[Hungster]

That's true, Citrix license does add up plus they are not cheap.

Hung

 

[CitrixEngineer]

"Battle-scars" must include the nice, efficient Terminal Services Licensing mechanism....;-)

Read as many M$ docs on this subject (and similar postings and solutions on this forum) as you can before deployment, and save a lot of time which would otherwise be spent investigating expired or duplicate licenses, or licenses not being available.

This applies whether you choose the Citrix route or not.

I hope this helps

 

[shipmate]

Shackdaddy, could you explain more of how you did this?
I'm in the same boat, with a VB app connecting to a SQL back-end, with 2 citrix servers

Specifically, could you explain how you set the app to be the shell? You did this with a profile?

I'm still learning the in's and out's of citrix, and I inherited a system that was never setup well.....it sounds like I may be able to apply this to my setting.

Thanks

Shipmate

 

[ShackDaddy]

Ok, setting the app to be the shell sounds more complicated than it is. There are two ways of doing it.

1) Create a user account that is local to the Terminal server. Create a policy for that user that limits the user's activities, ie prevent shutdown, hide desktop items, hide everything except the start menu which will only have one app, and that will be in the Startup menu. Now when the user logs on, that app runs automatically. If the user closes it, there are two options open: run the app again from Start -> Startup or Log Off.

2) Create a local or domain user account. Set up the application under that profile so that it is known to work properly. On the client, configure a new Connection in Connection Manager. Point it at the Terminal server, set it to log on automatically with the user account and password that you created, and, on the last page of the wizard, have it automatically run the VB app that you installed. When you use this Connection, you will notice that if you minimize the app after login, there will be no desktop, tool-bar, start menu, etc. On one of my NT4 Term servers, when the user closes the app, the session is logged off as well, but on W2K, once the app is closed, the user just has a blank session and has to 'disconnect' by closing the window. I'm still working on getting around the latter problem.

ShackDaddy

 

[shipmate]

Shackdaddy, thanks for taking the time to explain; I greatly appreciate this


Shipmate

 

[Hungster]

when i use the citrix server
i enable only publish apps
so users can only see the icon for the application which we run Sytiline (FrontStep)
when they click on it, it goes directly to their own profile and logon

Hung

 

[Guest_imported]

Shackdaddy(MIS) I have a small question for you. I have setup a terminal serverl for my small office but I dont know ho to manage profiles for people loggiing in. Ile controlling what they can do once they have logged in. Lie They cannot go to start butoon or the rinters etc. Wher can I get help in doing so.
Thanks.