- This topic has 3 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
Hi,
We are migrating from Xenapp 6.5 to Xenapp 7.15.
We are currently running WMS 1.2 with Wyse 3040 thin clients on thinos 8.6_303.
We have 2 configuration groups. One for xenapp 6.5 that points to webinterface and one for Xenapp 7.15 that points to storefront.
The current DHCP scope option 199 Group Token points to the config Group for Xenapp 6.5.
After we migrated all the thin clients to the new Xenapp 7.15 config group, I want to remove the old Xenapp 6.5 group and change the DHCP scope option to point to the Xenapp 7.15 group.
Under the Xenapp 7.15 group however I created a child group that contains all the autologon thin clients. This group has a different group token than the parent group.
I was wondering, if I change the dhcp scope option 199, if the autologon thin clients will change their group token to the Xenapp 7.15 one after picking up the new token from DHCP.
I know changing the group removes the autologon settings, so want to avoid this.
Thanks
I also noticed that some thin clients move back to the Xenapp 6.5 group automatically after being added to the xenapp 7.15 group manually.
Happens around half an hour after the move.
Is this due to the dhcp scope options or the config not being cached properly on the thin client?
Clients that got the WMS FQDN and Group Token once via DHCP or DNS will never use that again. Otherwise, if you move a client to a different group and reboot the client afterwards, it would jump back to the DHCP configured group.
CG
- You must be logged in to reply to this topic.