- This topic has 4 replies, 2 voices, and was last updated 2 years, 7 months ago by
.
-
Posts
-
Hey!
I’m struggling with reconstructing what I used to have in wnos.ini, in WMS for ThinOS 8.6 (TC 5010).
– My users have two or more login options on their TC. In the login box they can choose from different environments by selecting from a dropdown-menu. That menu I configured in wnos.ini with the parameter SelectGroup.
– I also had to create {Group}.ini-files which I put in the INI-folder on my FTP-server. Worked like a charm.
– Each {Group}.ini-file contained different PNLiteServer and DESKTOP (background picture) parameters, to let users choose different environments to log into. The TC background changed accordingly to the environment they chose.
WMS let me create Groups and subgroups for fw 8.6+. I can upload one {Group}.ini for each group. And under “Advanced settings” I can write parameters from wnos.ini, like SelectGroup. Inserting the SelectGroup parameter her, creates the correct dropdown options in the login box, but I can’t get them to talk to the corresponding {Group}.ini-files that I have uploaded and connected to the subgroups….bah..
I’m struggling to get this to work. Anyone in here who have the same use case as me? I’ve tried so many combos of configurations now. The documentation just state you can add {Group}.ini, but only one for each group or subgroup.
– For 5070 TC’s with fw9+ I’ve managed to make something similar to work with a Parent Group and child groups and configuring different Broker servers in the child groups , but those options don’t support fw8.6+.
Anyone? 🙂
Cheers
KennethGreetings, post a copy of the groups.ini you are using, I would like to see what happens in my lab.
Jim
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…:-)
There is an earlier post back in 2019 where Thomas had an example that may work.
“OK, if you want to have a drop-down to select the broker, you would have to use a different syntax.
Remove the VM Brokers you have entered already.
Add this to the Advanced section:
Line 1: SelectServerList=VDI \
Line 2: Description=”Tampa” Host=”https://tampa-vdi.gopherresource.com” \
Line 3: Description=”Eagan” Host=”https://eagan-vdi.gopherresource.com””Basically use Select Server and Not Select Group
THANKS, Jim!!! This works in a way.
I still prefer SelectGroup, because in the {group}.ini I can add specific settings to each environment my users choose to log in to, like graphical profile (background, logo, screensaver).
But SelectServerList provide the main feature I was missing, like to choose broker from a drop-down.
SelectServerList=PNA solved this!
Thanks for pushing me in the right direction!
Kenneth
- You must be logged in to reply to this topic.