asked on

ThinStation Autostart Windows Application in RDP

We have a number of older PCs and even some Wyse Winterm thin clients that have the Linux ThinStation distro installed. We've been using these to allow users to connect to one of two Windows 2003 Terminal Servers. I would like to configure one workstation to auto-connect to a particular TS server, auto login, and open a Windows application (in application mode). I understand how to configure a particular host to use a custom config file. What I'm looking for is what to put in the ThinStation config file. Are there parameters I could use that would imitate the Programs tab of the Windows RDP Client app (Start the following program on connection)?

Tony J

https://www.experts-exchange.com/questions/24635212/Thinstation-Citrix-Implementation.html

Tony J

I might have mis-read the other posting. I was sure it said autoconnect.

kwikstix

ASKER

Thanks for responding. I saw that other post, but I'm not using ICA. I need to use a standard RDP connection.

Tony J

Here you go:

RECONNECT_PROMPT=On
SESSION_0_TYPE=rdesktop
SESSION_0_AUTOSTART=On
SESSION_0_RDESKTOP_SERVER=<ip of terminal services server>

Taken from:

http://sourceforge.net/apps/mediawiki/thinstation/index.php?title=thinstation:Conf

kwikstix

ASKER

Thanks again for responding, but the key that I'm looking for is to start an application immediately upon connecting - without launching the desktop. Using the Windows Remote Desktop Client, this is done by configuring an application executable in the Program tab of the connection properties. Once valid credentials are entered, the user is able to see the application, but nothing else. When the application is closed, the user is immediately logged out. This is what I'd like to do using ThinStation.

ASKER CERTIFIED SOLUTION

Tony J

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kwikstix

ASKER

I've looked into the GPO option. I think I could get the user's session sufficiently locked down using GPO to be a kiosk. Thanks for the tip!

kwikstix

ASKER

Thanks for the solution. This wasn't exactly what I was looking for, but is a decent work-around.