Terminal Server / Remote Desktop Connectivity

I have just setup Terminal Server and it is working on the trial. Upon connecting with the provided "Remote Desktop" software I was happy to see it worked and all....however...

I want to use this as a "solution"...right now remote desktop requires you log into the OS (I can get around that most likely)...however if I launch the connection via a batch in the 95/98 startup folder all is well and good until they logoff or disconnect.

I need to keep the login active. This will be used in an elementary school...it would eb best to NOT have an OS and just boot into a remote desktop connection to our server. Is there any way to make it so when the connection is closed it automatically relaunches Remote Desktop to the server again for the next user...or is there something out there to just boot into a RD connection to the terminal server...

Please let me know, I am dealing with limited funds this coming year and need to make some sort of solution work that will not be a major learning curve.
LVL 4
ssammonsAsked:
Who is Participating?
 
rmalenchekCommented:
You could remove the ability to disconnect or log off through the use of security policies, which is pretty straight forward. You could use your admin console to administer those you need to log off.
0
 
ssammonsAuthor Commented:
Well...these would be used in the back of a classroom where kids would be off and on with their network logons...so I can not administrate that. They will need that ability, is there any other way?
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

 
rmalenchekConnect With a Mentor Commented:
You could boot using PXE compliant network devices. This would allow you to skip the Win95 altogether and go straight to the terminal server for authentication. Does this sound more like what you are looking for?
0
 
ssammonsAuthor Commented:
rmalencheck,
That sounds great, but I am trying to use the old systems we currently have, which are old Dell Dimension GX1's with PII 233-300 Mhz systems.
0
 
ssammonsAuthor Commented:
I will check those out and let you know. If anyone else has suggestions let me know. Thanks!
0
 
2hypeConnect With a Mentor Commented:
For my thin clients I use Tftpd32.  Its Free.  I just installed it on my Server and you can set your clients to network boot or use a boot disk.  It Connects me fine to my 2000 Terminal Server.

http://perso.wanadoo.fr/philippe.jounin/tftpd32.html
0
 
Carlo-GiulianiConnect With a Mentor Commented:

I think the *easiest* way for you to do this is to leave the existing OS installed on the PC...I assume it is Win95 or Win98.  You can install the remote desktop client and set up the client to launch in full screen mode and automatically connect to your Teminal Server whenever the PC is started.

To test this, check out the "Options-->>" button on your remote desktop client.  You can set the server, userid, and password for the connection and then save the settings as a .RDP file.   Now open the .RDP file.  This is a simple text file an all the parameters are explained at http://dev.remotenetworktechnology.com/ts/rdpfile.htm
You can set it to full screen, with no visible connection bar,

You should be able to just put an .RDP file into the "Startup" folder for each PC, so they will boot automatically launch the remote desktop client in full-screen mode when they are started.
 
Windows 95 and Windows 98 cannot be secured against user tampering.  I am assuming that making these PCs really bulletproof (or childproof) is beyond the scope of your question.

0
 
brownmattcConnect With a Mentor Commented:
You can change the "Shell" registry setting on each of the machines from Explorer.exe to mstsc.exe.  This will launch the RDP client on bootup rather than Explorer (the desktop you usually get).

If you do this you will NOT be able to get the desktop of the system except for in safe mode.

0
 
Carlo-GiulianiCommented:
I like the suggestion from brownmattc!
0
 
ssammonsAuthor Commented:
Carlo-Giuliani: I don't need to make it childproof, but if possible I need to make it so when the TS client uses "logoff" or "disconnect" they don't get back to a desktop and get lost. I know I could delete the entire desktop, all programs etc. and just leave a shortcut to the batch and or RDP file. I am just looking for the most non-user issue with a work around.

brownmattc: do you have links to reference how I can do that? I don't mind not having a desktop, and if it work the way I need it beat the heck out of re-doing all the systems with Linux and installed an extra service on the server. If you know the registry path that is fine, I am sure I can handle that :)

The reason I need it this way, is kids are not going to pay attention between a 98 desktop and a 2003 server desktop, so I need to make sure they stay on the 2003 server and its log-in prompt that I have them set-up to see on connection via the MSTSC.exe file with the RDP files.

Just a note to other if they post...I already did the all programs > startup solution before this question along with the command line approach in a batch. I found the batch works best, but it needs to be placed in the startup folder and not done at login, because 98 keeps processing beyond the batch file from the server and loads its startmenu ontop of the RD connection start menu.
0
 
ssammonsAuthor Commented:
brownmattc: Ok, I found my answer for getting the shell changed...and thats cool that it loads...problem still is if the student logs off connection they are then put at a blank desktop with nothing to do and no way to re-connect.

Does anyone have a way to make it so when the TS client ends a connection it re-launches?

If not I will have to pursue the linux option next, but I am trying to stay native to one platform.
0
 
ssammonsAuthor Commented:
I am awarding points to all valid answers. I still am searching for a windows solution. I would also like to referrence people to this alternative as well.

http://www.experts-exchange.com/Networking/WinNT_Networking/Q_20270280.html?query=Terminal+Server+on+3.11&clearTAFilter=true

Thanks for the help guys. I will have to give that linux option a try shortly.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.