Multiple Configuration wnos.ini deployment on one site

  • This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #1011
    AvatarSammy
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    hello everyone,
    Was introduced to you site late week – i am a new be to this Thin Client computing and need your help.

    I want to run two different configurations – Just using a FTP server – with using just one ini base config is working fine, but HOW do i get half the clients to pick up one ini and the others the other.

    Thanks in advance
    8)

    #12074
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    Hi,

    some options:
    – Create FTP subfolders like ftprootwyseconfig1wnos and …config2wnos. Now configure one group of units to look for folder wyseconfig1 and the other for wyseconfig2
    or
    – Use my tool and create MAC based configs with DDClite function (see help file inside the tool)
    or
    – Use Wyse Device Manager Enterprise Edition and the inbuild Default Device Configuration (DDC)

    HTH
    CG

    #12101
    Avatarsaturno
    Member
    • Total Post: 3
    • Newbie

    Sorry, I don’t want to to hijack the thread, but I have the same question.

    I can’t get this to work. (different config to different machines)

    I’m creating a file in /wnos/inc name is the real mac address of the client I am testing, i.e.: 0080646711c3 without any extension or wahtever. The file name is just the plain mac address of my terminal. I include it in the main wnos.ini file with:

    include=$mac

    After booting, I can see in the “system log” tab that the terminal do not “call” for it in the boot process.

    The terminal is an Winterm S10 (System Version VDI: 5.1.028f ROM: 1.14i )
    After reading the information that I could find about this (and the hints in confgen), I think that probably the system version does not support this feature. Can someone confirm this?

    Once I haven’t any maintenece agreement with wyse is there any other way to get different configs to different machines?

    Thank’s for any information.

    #12102
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    I am not in front of any unit to test but do you have a VDI Broker field in your WTOS network setup? If yes, you can use my ConfGen tool and DDClite.
    I will check whether mac$ is supported in 5.1 code.

    Cheers
    CG

    #12105
    AvatarSammy
    Member
    • Total Post: 28
    • Regular Joe
    • ★★

    Hi,
    I do know that i can configure lots of different configurations for WNOS but i am trying to get different department units to select a certain config.
    If everyone needs the same config that is all fine, easy peasy 🙂

    Thinking the only way that this can really work is by sub-netting the network and creating DHCP Scopes and 162 TAGs for each Subnet.

    If i am making more work for myself then i would love to know.

    #12107
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    Two options for you Sammy:
    – Use Wyse Device Manager with Default Device Configuration. Benefit would be that you are extremely flexible which unit will get which config. Not related to any subnets
    – Different option tag 161 and/or 162 for each subnet. Benefit is that it is free of charge.

    CG

    #12121
    Avatarsaturno
    Member
    • Total Post: 3
    • Newbie

    Hi ConfGen, and thank’s

    I think you were referring to my question, when you talked about the “VDI Broker field in your WTOS” network setup.
    The answer is no, I don’t have the VDI Broker field in my network setup… but seems that I should have.

    Can you clarify a little that parameter?
    Seems to me that that parameter should point to a server that will return something to the client… (?)
    Can you point me anything that I should know?

    Tomorrow I will be a great part of the day out of my office, but Thursday I’ll continue trying.
    (I’m talking about tomorrow because I am in Portugal, so here is almost time to sleep ;), when there you’re probably waking up!)

    Thank’s for your help.

    #12132
    ConfGenConfGen
    Keymaster
    • Total Post: 11007
    • Jedi Master
    • ★★★★★★★

    VDI Broker is a new feature that enables you to contact a Connection Broker server during boottime. This connection broker can return some informations to the client eg. wnos.ini parameters or (and this is the real attend) a Vmware based XP Pro Session.
    For more information on VDI look at vmware.com.

    I am using this VDI Broker field together with ConfGen to send mac based ini files to the clients.

    Regards
    CG

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