Hey Jim!
I now use two very simple group.ini-files.
group1.ini
————————————————————–
PnLiteServer=https://myserver1.fqdn/Citrix/store
DESKTOP=image1.png
FormURL=logo1.png
————————————————————–
group2.ini
————————————————————–
PnLiteServer=https://myserver2.fqdn/Citrix/store
DESKTOP=image2.png
FormURL=logo2.png
————————————————————–
In wnos.ini I had:
SelectGroup= yes description=”Environment 1″ groupname=group1 description=”Environment 2″ groupname=group2
Groupname points to the group.ini-file.
The SelectGroup-parameter creates a dropdown box on the login-box, with 2 choices:
– Environment 1 (points to group1.ini, and connects to https://myserver1.fqdn/Citrix/store)
– Environment 2 (points to group2.ini and connects to https://myserver2.fqdn/Citrix/store)
So…how to structure everything to get this working with WMS.
I will say this feature is the most important to my user environment. My users have 1 thin client only, but connects with it to until 4 different environments through SelectGroup.
When I attach group1.ini to a subgroup, and assign a TC to it, the thin client tries to connect to “Environment 1”. I just need my client to read group2.ini as well somehow, and sew it together with a SelectGroup-parameter somewhere…:-)