lock down s90, telnet client only

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #5695
    wyseted
    Member
    • Total Post: 7
    • Newbie

    Hello,

    I would like to set up a few S90 thin clients so that when booted a telnet connection would be made to a server on the local network. I would prefer that nothing else is available to the user, and if he tries to get out it simply reboots and throws him back into the same thing.

    I did this on some older Wyse thin clients that used CE, but am having trouble figuring out how to do this with XPe.

    Thanks in advance,
    -Ted

    #17772
    wyseted
    Member
    • Total Post: 7
    • Newbie

    I am onsite at my customers plant, it is a Saturday, and I am 250 miles from home. Sorry if it is a stupid question, but can anyone help?

    #17773
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Hi,

    you would have to replace the Explorer shell in the registry. This would start your application instead of the Explorer and each time the user stops your app it will directly reload it.
    Log in as an admin and disable the Write Filter (EWF or FBWF) before doing this as otherwise no changes are stored.

    CG

    #17774
    wyseted
    Member
    • Total Post: 7
    • Newbie

    Thanks,

    I was able to get to the same conclusion yesterday, and after 12+ hours I had one of the TCs functioning as I wished.

    I am now trying to reproduce that on the other S90s, and I have one that is problematic. I have a Powerterm connection that works as desired under the Administrater and User profiles, but when I create a new user it will not hold a NUMLOCK, and I cannot get the numeric keys to work.

    I have deleted the new user, created several others, given that user all kinds of privileges (from Admin to User), and whatever I do the numeric keypad won’t turn on.

    I set it to come on under HKEY, and it lights up and stays lit until the user starts loading. Any ideas? Pulling my hair out, on about hour 20 this weekend.

    #17775
    wyseted
    Member
    • Total Post: 7
    • Newbie

    I was able to find an old post by “Joe” that described a fix to my problem. Here is the link: (http://www.freewysemonkeys.com/modules.php?name=Forums&file=viewtopic&t=433&highlight=number+lock+powerterm)

    Under some users the value for InitialKeyboardIndicators was not a string, but somehow had been set to a DWORD. Deleting these and creating new ones seems to have me back on track. The Numlock now takes/holds.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.