WYSE Won’t pull in Config from Additional Policies

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #108186
    [email protected]
    • Total Post: 1
    • Newbie

    I have been running WMS 1.3 for 3 years now, managing WYSE 3030’s with WES7. I have a policy set under Default Policy Group that is deployed to our 3030’s with no issues. We are transitioning from RDS to VMWare, and we need a new policy. No matter what I do, I cannot seem to create a new policy that will push a new config out to the 3030’s. I can create the policy, assign the device to the policy, the device registers successfully, but the config doesn’t get pulled in.

    If I go to the device, and create an exception under the policy that has always been used, then that will work, and the config gets pushed out to the device.

    “WES7 Thin Clients” is the policy that works, and “WES7 Horizon” is the policy that doesn’t work.

    Just to be certain that it wasn’t something in the settings, I created an exact duplicate of the “WES7 Thin Clients” settings, switched the 3030 to that duplicate policy, the device registers to the new policy, but still doesn’t pull in the config.

    Not sure what I did wrong.

    • Total Post: 53
    • Back Stage Pass
    • ★★★★

    Check the group token, it might be the issue.

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