RDP configuration lost after restart/shutdown

  • This topic has 4 replies, 4 voices, and was last updated 2 years ago by Andy.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #87834
    tomasmichiels
    Participant
    • Total Post: 2
    • Newbie

    Dear Mr Möllerbernd

    I am having an issue with a DELL Wyse 3040 thin client.
    I try to add an RDP connection with the “add connection”  -> “add RDP connection” option.
    When I restart the thin client, all of this config is removed.

    Who can this be configured so that the settings are saved when restarting/shutting down the thin client.

    I am using build version 9.1.1131

    Thanks in advance.

    Kind regards
    Tomas Michiels

    #88036
    dragon3303
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    That’s a “feature” of their newer ThinOS versions.  Hopefully they remove that feature in the future and allow that configuration option from connection manager.  In the meantime, I was able to load the config from USB (have to factory reset the thin client with the network disconnected and choose to load config from USB drive) and then the config stayed.  I just added the RDS connections to the config that I was loaded so it would look something like this:

    ;*************************************************************
    ;* *
    ;* This wnos.ini file was generated with the *
    ;* Configuration Generator 8.5.02 *
    ;* Copyright by Thomas Moellerbernd *
    ;* *
    ;* https://technicalhelp.de *
    ;* *
    ;*************************************************************

    ;*************************************************************
    ;* General 1 *
    ;*************************************************************

    autoload=2
    EnableLocal=yes

    ;*************************************************************
    ;* General 2 *
    ;*************************************************************

    MirrorFileServer=yes

    ;*************************************************************
    ;* Peripherals *
    ;*************************************************************

    Language=Us

    ;*************************************************************
    ;* Network *
    ;*************************************************************

    SignOn=No

    ;*************************************************************
    ;* RDP *
    ;*************************************************************

    ;————————————————————-
    ;- RDP Session 1 –
    ;- Each line but the last must end with a ‘\’ –
    ;————————————————————-

    CONNECT=RDP \
    Host=whatever your host is \
    Description=”Your Description” \
    AutoConnect=yes \
    Reconnect=yes \
    Fullscreen=yes \
    Username=username
    Password=password
    Domainname=domain
    LocalCopy=no

     

    You can in multiple RDS sessions if you need using that same config style for each session needed.

     

    #91181
    tomasmichiels
    Participant
    • Total Post: 2
    • Newbie

    Dear Dragon333,

    Thank you for the info. I tried to import the wnos.ini file with a USB stick, but it won’t work.

    I first receive to give up a password, which I do, afterwards I receive the message ‘Failed to import system configuration’

    Are the special requirements necessary on the usb file to successfully import the wnos.ini file.

     

    Kind regards,

    Tomas Michiels

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

    9.x does not support any wnos.ini file anymore. Everything has to be configured locally or (much better and easier) through WMS.
    Install WMS and configure the clients this way and your RDP connections will stay.

    CG

    #107180
    Andy
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Well this is good news, I don’t think.

    We sell control systems. We have been using Wyse terminals for at least 15 years, probably longer. With each system we sell, we probably have about 4 or 5 of them. One in particular is critical – it’s an operator interface. I don’t want the operator being able to get to ANY configuration information of any kind at all. Previously, for this terminal we used the wnos.ini file to completely lock it down. Now it seems I have to install a rather large piece of software on some PC somewhere just for one terminal.

    I am not impressed. I wonder if the competition are any more helpful?

     

     

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