WNOS.ini file

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #6710
    Avatarmrailton
    Member
    • Total Post: 2
    • Newbie
    • β˜…

    Hi please can some 1 help me understand something about my problem i’m having –

    i’ve used confgen to create a wnos.ini which has the following config:
    ;*************************************************************
    ;* General 1 *
    ;*************************************************************

    autoload=1
    AdminMode=yes Username=admin Password=test
    Privilege=Low Lockdown=yes HideSysInfo=yes HidePPP=yes HidePN=yes HideConnectionManager=yes
    EnableGKey=yes

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

    SignOn=No

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

    ;


    ;- RDP Session 1 –
    ;- Each line but the last must end with a ” –
    ;



    CONNECT=RDP
    Description=”TS #”
    Icon=default
    LocalCopy=no

    the thinclient gets the ini file and is stored locally on it but my intentions are to be able to roll this current config to all the thinclients in the building and then be able to edit the RDP connection to the correct area’s of the floor but once i’ve changed the RDP host address and other settings it doesn’t update this file ( which i think its not meant to, so its possible im looking at this the wrong way )

    I could put all the rdp connections of all the terminal servers but we want to have a bit of control over who can log onto which terminal server where.

    Please i basically want to have it locked down so only a administrator can manipulate the RDP address settings on the desktop ( i’ve got this far but once like i said i restart the settings resort back to the config above )

    πŸ™„ πŸ™„

    #20674
    Avatarmrailton
    Member
    • Total Post: 2
    • Newbie
    • β˜…

    bleh no 1 can help?

    #20677
    ConfGenConfGen
    Keymaster
    • Total Post: 11099
    • Jedi Master
    • β˜…β˜…β˜…β˜…β˜…β˜…β˜…

    Looks like a misunderstanding of the concept.

    A wnos.ini file is always read on boot time if available. So when a client boots, it reads the wnos.ini and overrules locally, conflicting settings.

    When I understand you correctly you want to assign different RDP connection settings to different clients.
    This can be achieved by using clientbased .ini files beside the global wnos.ini.
    Read my “INI File Handling” document in the Products-WTOS section.
    Let us know if you have more Q afterwards.

    CG

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