Forum Replies Created
-
Posts
-
Dell confirmed to me also today, that 3040 went EOL mid december, and OptiPlex 3000 will be available from today.
This said:
No updates on Dell’s webpages. They have now removed 3040 as current model, and I can’t find any information / specs about the OptiPlex 3000.
Anyone in here who knows something about the new model??
Dell says it’s performing 30% better than the 5070, and comes with ThinOS from the beginning. From May it will also be delivered with Win 10 IoT.
Hey!
What does the File Servers/Path-setting say after upgrading til _807?
From fw _606 Dell stopped “supporting” FTP and inserted HTTPS in the File Servers/Path link by default.
If you have configured File Servers/Path to be “dns-name.fqdn”, after upgrading fw it would say “H TTPS://dns-name.fqdn”.
If this is the case, you can solve this by either setting up a HTTPS-service, or put FTP:// in the link. The link in the config should then be “F TP://dns-alias.fqdn”.
(had some trouble posting links in this reply, so had to write H TTP and F TP instead of HTTP and FTP…)
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
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…:-)
Any luck with getting rid of this unwanted behaviour? This is pretty anoying!
“Starting broker sign-on” shows after restart, and the users have to wait until it times out with “Could not add account. Please check you account and try again.” Off course it won’t work, since no credentials have been entered.
Broker-url same as you have. Standard address to Storefront.
If you switch to old fashioned legacy url with pnagent, the behavior stops:
https://myserver.something/Citrix/store/PNAgent/config.xml
TC 5070 -> fw 9.1.3112, Citrix Workspace App 21.6.0.28
I’m very surprised to see that this hasn’t been fixed since this thread was started in April…
Welcome to the Captains Lounge, Jim!
One thing that always made me come back to this forum over so MANY years, was that Thomas had his foot inside Dell. I’m happy to see you have one or more feet into Dell as well. That is just AWESOME for this forums continuity.
Getting news about new firmware releases from Dell / Wyse, has always been like impossible. This site is the only place I know where I can get such information. Hopefully this site will continue to be that place..
In WMS, under
Portal Administration -> Setup (scroll to the bottom)
you can also change the base URL of the MQTT-service. Ex from servername.fqdn to dns-alias.fqdn.
Thanks a lot to Thomas!…and good luck to many more professional years to come…! 🙂
It is so hard to find anything useful on the Internet concerning Dell Wyse-thin clients, config options, recommendations and news updates. Dell (Wyse) own documentatin don’t cover all scenarios (ex. the use of SelecGroup / group.ini 🙂 ) This forum has been all that for so many years!!! Sad to see The ConfGen moving on, but I’m also happy to see great ppl moving on with their careers.
I noticed a news post in here posted by a new admin about downgrading WNOS fra 9.1x?? New admin, speak up!! 🙂
Thanx for your quick reply! We still haven’t got this sorted out. Everything works, though, but we’re curious why we didn’t get the 2016-RDS licenses to work.
(Thanks for running this site, Thomas! I’ve been using it for many years, working with tc’s from Wyse/Dell the past 10 years.)
