WMS 3.1 and Wyse 5070 Win 10 issues

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #105236
    Avatarclong
    Participant
    • Total Post: 11
    • Regular Joe
    • ★★

    I am seeing a lot of issues with a new deployment of WMS 3.1 and Wyse 5070 Win 10 IOT devices. The devices register ok and some even seem to be getting a test policy i have configured ( ican see the rdp connection) but very little else is working. For example, restart or Query, any app policies i create seem to get stuck in pending and time out. VNC was working until i changed a setting in my test policy (enabled kiosk mode in WES) now it is saying “No supported sub-auth types”.

    I am seeing a lot of the following error on each device. The device is registered against the ip address of the WMS server. Could this be part of the problem?

    #105237
    Avatarclong
    Participant
    • Total Post: 11
    • Regular Joe
    • ★★

    I re-registered the device using the hostname and i am having a lot more success now.

    Does anybody know if the hagent service is required for WMS or if it is for the older WDM version? I enabled this also but not sure if it is required. Service was set to manual on the thin client before i changed it.

    #105279
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    HAgent is the old name/agent. The most recent one (for communicating with WMS) is called WDA (Wyse Device Agent).

    CG

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