Hello thar:
We are a Secondary School and have over 200 HP t5135 thin clients across three sites.
We have them set to "Auto" and "Persist" an RDP connection to a local Server 2003 Terminal Server, local to each site that is. This means that it boots up, logs into it's own HP ThinConnect OS as "user", then connects an RDP session to a Terminal Server, presenting the login box. After every weekend, anything up to about 15 t5135 thin clients are frozen:(. The only way to restore them is to get to them with a USB Flash drive with a good image generated from another thin client.
They freeze in varying states, but the common factor is that most will not boot if you power them off and on again. This is a completely unacceptable rate of failure, and we are sorely dissappointed with the product on three counts, I don't recommend them, steer WELL clear:
It freezes:eek:
There is no tamper free Kiosk mode (We don't want the little darlings to be able to see the DNS and IP info for the thin client, we just want a big fat connect button and _nothing_ else.)
You can't shut them down remotely (with over 200 across 3 sites this is a lot of electricity)
The freeze appears to be related to the fact that terminal services boots you off an RDP session that you don't log in to, after about 1 minute. The Auto feature reconnects you, but after it has done this a few hundred or thousand times, the thin client slows down, then freezes. It is, at an educated guess, symptomatic of a memory leak, either in the application that lauches rdesktop, or rdesktop itself. I doubt the latter as I think that a new rdesktop process is spawned after each disconnect.
Is there anyone out there who can suggest a fix, or an easy to configure, compatible alternative OS that will install from a USB boot? Any help with anything would be greatly appreciated.