Please get me up to speed…

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #107554
    Jim Lathan
    Keymaster
    • Total Post: 314
    • Jacked into The Matrix
    • ★★★★★★

    Hi all,

    So, for about 15 years now I’ve had Wyse ThinOS clients and have configured these with a wnos.ini file served off a ftp server.  It was simple, quick, and it worked.  All I need those Wyse terminals to do is to connect to an RDP server.

    Now i’ve not bought any Wyse terms for the last couple of years or so but needed to do so recently, and i’ve been shipped a Dell Wyse 3040 which is apparently PCoIP optimised (according to a sticker on the underside), yet after booting it up it comes to a nice fancy graphic of some hot air balloons, and asks for username/password/domain, with no other ability to factory reset the device via the G key or anything of the sort.

    Now, I realise that the ftp/wnos.ini was primitive and on some reading it seems it’s gone the way of the dodo, and is replaced with Wyse Management Suite.  I’ve downloaded that and stuck it on a server here, and have followed this (https://www.youtube.com/watch?v=ZrdGYelNKHY) video to set up my DHCP options, but the device doesn’t register itself in WMS.

    Can someone tell me whether I need to change this Wyse’s firmware for something that’ll interoperate with this WMS server? or how to troubleshoot this at all? (it was all SOOOO much easier with the wnos.ini file).

    Thanks in advance! I’ve got a week or so to sort this before these devices need to be deployed.

    Mike.

    #107555
    Jim Lathan
    Keymaster
    • Total Post: 314
    • Jacked into The Matrix
    • ★★★★★★

    Hello,

    I started this type of projet last year and it’s a heavy project at the end …. (1400 Wyses)

    in wnos.ini you can add this line

    CCMEnable=Yes CCMServer=https:fqdn GroupPrefix=defa GroupKey=]d`K9G5w CAValidation=No Discover=No

    With this configuration all your wyses will arrive in  unmanaged group, you keep wnos.ini at the beginning if you are in firmware 8 (3040 for example)

    After you have to make modifications in default device policy to transfer wnos.ini settings

    Once you have move your wyse to defaut device policy wnos.ini is not used

    #107557
    Jim Lathan
    Keymaster
    • Total Post: 314
    • Jacked into The Matrix
    • ★★★★★★

    Permsetr provided some good information on how to manage these, I hope that helped. I’m new to the WMS centralized management myself but overall it’s pretty easy to use once you get your devices to check in automatically.

    One thing I will mention is that it seems there are a handful of issues with ThinOS 9.1 version (the hot air balloon wallpaper) that haven’t been given any real attention yet. I’ve started downgrading my 3040’s back to version 8.6 unil these get addressed. Mainly, my dual-monitor users have resolution problems with their secondary screen.

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