All Wyse 3040 are unmanaged after Upgrade to 8.6_013

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #48948
    PascalKasto
    Participant
    • Total Post: 1
    • Newbie

    Hi guys,

    Maybe anybody can help me or has the same issue…

    After an upgrade from 8.5_009 to 8.6_013 all my Wyse 3040 are listed as unmanaged.
    The configuration allocation with dhcp-option-group-token worked in 8.5, but after the upgrade to 8.6 each device lose the configuration group and need to be assigned manually. After  an downgrade back to 8.5_009 , the TCs are assigned to the correct config group again. The BIOS version is 1.2.5.

    Is there a known bug or maybe an workaround?

    Thanks for your help

    Pascal

     

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

    This works fine for me.
    Do you still see the correct WMS information locally on the client?

    CG

    #49491
    djdacore
    Participant
    • Total Post: 23
    • Regular Joe
    • ★★

    I had the same issue last week and I decided to install a new WMS server and point the DHCP tags to that new server (example: server1.domain.local:1883 and server1.domain.local:443). After letting them restart with option ‘factory defaults’ tagged on, the Wyse 3040’s are registered in the new server. No problems anymore like unmanagable. All is working again after this action.

    #51660
    s432
    Participant
    • Total Post: 1
    • Newbie

    I had this issue a spent 2 weeks troubleshooting it with Dell so I thought i’d expand on the replies above. We were using WMS 1.1 with thinOS 8.5_009 using a group token that was deployed in the DHCP options. Everything was working fine until I tried to upgrade to 8.6_206 at which point the Wyse clients would go in to an “unmanaged” state and had to be moved manually to the correct group. Steps to resolve the issue:

    -Upgrade WMS from 1.1 to 1.4.1 (latest version at the time of writing)

    -Update the grouptoken in your DHCP server and in the WMS Group (the new WMS update requires an uppercase letter, lowercase letter, special character and a number)

    -Update the “App Policies>Thin Client>%Your Policy%” with the new package in WMS and set it to apply to new devices

    -Delete and recreate the DNS record(s) that point to your WMS server (Important!)

    -Factory reset Wyse clients and delete them from WMS

    After these steps the Wyse clients registered correctly

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