Variable for Central Managment

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #42165
    elproducto
    Participant
    • Total Post: 92
    • Back Stage Pass
    • ★★★★

    I am currently using DHCP Option tags and HTTP server to provision WTOS devices on various subnet, supporting various different configurations. I decided against the enterprise version of WDM. One thing lost with enterpriss edition is the ability to handle various configuration for WTOS device and configuration via DDC. I wanted to switch to a central configuration model that does not rely on option tags, and do not want to wait for WDM Workgroup version that will support this functionality better (Profile Manager)

    I was wondering if a group of stations have similar naming convention would it be possible to setup a variable to redirect these device to a specific configuration. An example of the naming convention would be FTWTCXXX, XXX representing a unique number per station. So all station with FTWTC in the name would get the same configuration. Seems the only way to tackle this would be to create individual INI files per station. This does not scale well, and coding a unique password per station is time consuming with 100+ stations + Password_Gen. It would be nice to have one configuration like FTWTC$.ini that would setup a 1 to many configuration for this use case and other use cases.

    I was thinking to leverage IIS to handle the logic but when checking the log files for IIS it seem IIS does not pickup the hostname for device it is serving.

    #42166
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    That’s pretty easy.
    You can use the Left/Right parameter.
    In your case it could something like
    Include=Left($TN,5).ini
    Now create some maschine based INI files like, FTWTC.ini and GTWTC.ini and HTWTC.ini.
    All clients with a name starting with FTWTC will get the FTWTC.ini, all clients with name starting with GTWTC will grap GTWTC.ini and so on.

    Put this Include parameter in your default wnos.ini at top and end all maschine INIs with Exit=all.
    That makes sure, that nothing besides the parameter from the maschine INIs will be used by the clients.
    If you have global parameters that all clients are using, put them on top of the Include in your wnos.ini.

    CG

    #42182
    elproducto
    Participant
    • Total Post: 92
    • Back Stage Pass
    • ★★★★

    Thanks I am going to go test that our now. Why can’t Dell/WYSE document this clearly? Imagine how many ppl ran away from this solution due to poor documentation.

    #42183
    elproducto
    Participant
    • Total Post: 92
    • Back Stage Pass
    • ★★★★

    Thanks that worked as expected.

    Any recommendations on how to handle group identifying information located in the middle of the hostname. An Example would be “DSHFTWTC01” group identifying string would be “FTWTC”.

    While thinking about this I am now worried a 1 to many config would be a single point of failure for targeted devices. Is there anyway with INI configuration to have devices leverage a pool of credentials without creating a config per file

    #42185
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    This is both not possible.
    Variable handling is described in the WTOS INI Guide.

    CG

    #42191
    elproducto
    Participant
    • Total Post: 92
    • Back Stage Pass
    • ★★★★

    I had to tweak the syntax you sent to make this work for me on WTOS firmware 8.0_512. How do you handle mass generation of password encryption hash stings?

    Include=&Left($TN,5).ini

    #42197
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    There is no way to do mass generation of password encryption at the moment.
    What passwords/what scenarios are you thinking about?

    CG

    #42230
    elproducto
    Participant
    • Total Post: 92
    • Back Stage Pass
    • ★★★★

    Just the login credentials to have thin client authenticate against virtualization broker VDI, RDS, and Citrix.

    #42233
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Two ways:
    – use anonymous login
    – create an AD user with the same name as the client. Then use Username=$TN for login. Password has to be the same for each account of course.

    CG

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