Help to locate wnos.ini file

Tagged: , ,

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #46921
    wink
    Participant
    • Total Post: 39
    • Frequent Flyer
    • ★★★

    Hi peps,

     

    Might as well state this first of all. i’m completly new when it comes to using wyse clients / ThinOS.

    I was looking around for at solution to be able to use VNC to remote control my Dell Wyse 3040 clients.

    I managed to find a post on this site, regarding a user looking for the same remote option as i went for. The answer was to add the following 2 lines to the wnos.ini file.

    MaxVNCD=1
    VNCpassword=password

     

    Even for me, that seems to be pretty simple to do, but i’m not really sure where to locate the wnos.ini file? Is there like a default path? do i have to create the wnos.ini file first and then place it somewhere on the client?

    I assume this will be easy to answer for someone that has the know how when it comes to working with these thing, but i’m clueless at this point 🙂

    So any help is much appriciated!! 🙂

    #46928
    smith_ll
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    How are you managing the clients? Via WDM or WMS?

    #46929
    wink
    Participant
    • Total Post: 39
    • Frequent Flyer
    • ★★★

    Hi smith_II

    I was planning to use WMS (Wyse management suite). But i haven’t been able to get a connection between the client and the server where WMS is installed yet either…..

    I’m also a bit confused as to if i put in the right things into the CCM field and MQTT.

     

    Should this be the EU keys or the name of the server with WMS installed? Also, what needs to be created beforehand for this to work? if anything else than a Group in WMS.

    Eu:

    CCM Server:    eu1.wysemanagementsuite.com

    MQTT server: eu1-psn.wysemanagementsuite.com:1883

    or

    CCM Server:    https://<OwnServerName&gt;.<DomainName>.local:443

    MQTT Server: <OwnServerName>.<DomainName>.local:1883

    #46930
    smith_ll
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    If your licensed for it there’s no reason why you can’t use the eu1 WMS, if not you can use you locally hosted WMS on a server. Set you DHCP options on the IP range the terminals will be on to point to it, and on boot they will pick up the configuration you made within the WMS console.

    That video will help you with the initial setup and how to configure the DHCP options also. Very helpful little demo.

    #46931
    wink
    Participant
    • Total Post: 39
    • Frequent Flyer
    • ★★★

    As of now, we are running on the free license, as it will be in a testing fase before going into our live environment. Ill have a look at the DHCP options, thanks! 🙂

    #46932
    smith_ll
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    I’ll be corrected if I’m wrong but using WMS doesn’t seem to create a wnos.ini file you can edit using confgen in the same way (At least I’ve not been able to find it). All the configuration is done within WMS –> Groups & Configs. It’s viewable as a WNOS.ini on the device itself but I’ve not found the old .ini I was used to when using WDM.

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

    WMS does not create a wnos.ini.
    You can either do it manually with a text editor or use my Configuration Generator.
    Check your client locally at Start-System Setup-Central Configuration-Fileserver. Is there something listed other than the IP of your DHCP server? If yes, this is your webserver that hosts the wnos.ini. If not, you are not using it today.
    You will find a „First Steps“ document in the ThinOS download section on this site that should help.
    If you want to use WMS then install it on a local server and enter the server name or IP under Start-System Setup-Central Configuration-WMS. The client should check in to WMS then automatically on next boot.

    CG

    #46934
    wink
    Participant
    • Total Post: 39
    • Frequent Flyer
    • ★★★

    Good to know.

    Let’s say i go ahead and create  a wnos.ini file, where would i have to store this / link it to the client?

    When going into Start -> System setup -> Central Configurations -> Fileserver. It does show the ip of our DHCP server with ftp:// in front of it. But the dhcp server isn’t setup to do ftp, is that necessary?

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

    Check the First Steps doc as it will clear up a lot.
    Feel free to ask more questions after that.

    CG

    #46955
    wink
    Participant
    • Total Post: 39
    • Frequent Flyer
    • ★★★

    Hi again ConfGen,

    I have had a look though the First step guide you suggested, and man it helped me quite a bit :D.

    I now managed to get the connection between the clint and wms server, so everything good on that part.

    So my last question would be how i can get VNC viewer to work on the client without a wnos.ini file as you mentioned it wouldn’t be there as default when useing wms.

    In case i need to use the Conf. generator to generate the wnos.ini file, then i have a few questions as well:

    – Where would i then have to put it on the client?

    – Is a ftp server needed for a centralized management of .ini files?

    – Would the settings you do in wnos.ini be the same as you can push out though Policy groups?

     

    Br.

    Wink

    #46956
    wink
    Participant
    • Total Post: 39
    • Frequent Flyer
    • ★★★

    Nevermind, i have found all of the answers i was looking for. Thanks help everyone 😉

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