Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

6 Posts

146

December 10th, 2024 15:28

WYSE Console Group Token

I'm in the process of creating some new groups in our WYSE console so that I can apply OS/APP/BIOS updates on a limited basis without impacting entire locations and make some needed changes all at once.

As part of this our original Group - GROUP1, had a token of GROUP1TOKEN! and I created a new group, GROUP2, with a token of GROUP2TOKEN!

I then imported the policies from GROUP1 and made the necessary changes in GROUP2 so that the updates would deploy and made some basic configuration changes - new screensaver timeouts, etc.

After placing one of our WYSE devices into the group, the updates apply, it makes all of the necessary changes and then reverts back to GROUP1.

I've gone looking and cannot find anywhere that the old token (GROUP1TOKEN) shows in the config setup.

I feel like I saw something like this once before, but it's been over a year since I made a new group in the console.

Thanks in advance!

1 Rookie

 • 

12 Posts

December 10th, 2024 22:04

Hi,  In the Wyse Console did you go check the group then click advanced tab and expand services tab.  Click on WMS Settings and verify that the group token is the one you are wanting.  I've had to edit this field in the past when importing policy's from another group to a new one.  Not sure that's it but worth a quick check.  Thanks 

Moderator

 • 

888 Posts

December 10th, 2024 17:44

This is not expected behavior.  Please open a support case for engineering review. 

1 Rookie

 • 

6 Posts

December 11th, 2024 12:01

@Mr. TK​ Yes, I was able to work with Support yesterday and they helped guide me to this.  Apparently when you import a policy it imports everything - I would think that this would be an item the developers would filter out.

Moderator

 • 

888 Posts

December 11th, 2024 13:24

Good catch @Mr. TK .   That section of the policy has caused a number of headaches for customers.    It is very useful for programmatically moving devices between groups, or between servers or even cloud,  but if used wrong can cause the behavior you saw.  

Glad it was resolved. 

No Events found!

Top