wnos.ini multiple configs?

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1700
    mikes1p
    Member
    • Total Post: 4
    • Newbie

    I want some of our Wyse thin clients to use different connections and/or settings, how do you have multiple configurations using wnos.ini?

    I am exploring using wnos.ini and have a basic understanding of what the file does, also I have the DHCP options set. I have WDM running . We have a mixture of 1200LE, S10, S30, and S50’s so we have a variety of thin client OS’s.

    Most just connect to our Terminal Server via RDP and that is all they do. Two 1200LE’s have more than one connection so they can RDP to a PC or another server, as well as a connection to our Terminal Server. The last scenario is three S30’s run Internet Explorer in kiosk mode in employee break rooms, we want these completely locked down.

    I have not been able to find any web pages or documents that explain how to do more than one configuration using wnos.ini. Can someone point me in the right direction?

    Thanks
    Mike S

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

    Hi Mike,

    that is an easy one.
    The CE device can be configured locally once. Then you can extract/pull the config via WDM and push this out again to any other device. So CE isn’t an issue at all.
    With WTOS you cannot use different wnos.ini files when always using the same FTP server. But you can use client or user specific .ini files.
    In your case I would recommend using a client specific one.

    Add

    Include=$mac.ini

    to your wnos.ini file and create a subfolder with in your wnos folder called “inc”. Now place one .ini file for each client in there containing the client specific settings. Name these files according to clients MAC address, eg 008064123456.ini.
    Normaly the .ini parser starts reading the wnos.ini first until it reaches the Include command. Then it reads the mac.ini/user.ini and returns afterwards to the wnos.ini reading the rest. If you like to exit the parsing process after reading the mac/user.ini you can place a “Exit=all” at the end of these files.

    HTH
    CG

    #14877
    mikes1p
    Member
    • Total Post: 4
    • Newbie

    Thanks! Yes that looks pretty easy.

    One question, with that scenario the WinCE’s won’t read the wnos.ini? Or do I need to exclude them somehow

    mike

    @ConfGen wrote:

    Hi Mike,

    that is an easy one.
    The CE device can be configured locally once. Then you can extract/pull the config via WDM and push this out again to any other device. So CE isn’t an issue at all.
    With WTOS you cannot use different wnos.ini files when always using the same FTP server. But you can use client or user specific .ini files.
    In your case I would recommend using a client specific one.

    Add

    Include=$mac.ini

    to your wnos.ini file and create a subfolder with in your wnos folder called “inc”. Now place one .ini file for each client in there containing the client specific settings. Name these files according to clients MAC address, eg 008064123456.ini.
    Normaly the .ini parser starts reading the wnos.ini first until it reaches the Include command. Then it reads the mac.ini/user.ini and returns afterwards to the wnos.ini reading the rest. If you like to exit the parsing process after reading the mac/user.ini you can place a “Exit=all” at the end of these files.

    HTH
    CG

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

    wnos.ini is only read by WTOS and Linux systems. All others (CE and XPe) will ignore them.

    CG

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