Tagged: ThinOS Leostream WMS
- This topic has 12 replies, 6 voices, and was last updated 1 year, 5 months ago by
Jim Lathan.
-
AuthorPosts
-
January 17, 2018 at 5:10 pm #45948
Hello everyone,
I am trying to configure Leostream which will give VM access to my thin Wyse ThinOS clients through the Wyse Management Suite console. The problem I have is that there is no “other” Connection Broker like Vmware or Microsoft. I see this option locally on the thin client but not on the WMS.
How to configure this in WMS?
Thank you!
January 18, 2018 at 12:30 pm #45955In WMS there is no option to select Leostream.
Go to the Advanced section in the WMS profile and you will see 20 empty lines.
Add in line 1
VDIBroker=Enter_VDI_Broker
and in line 2
ConnectionBroker=DefaultShould work.
CG
March 22, 2019 at 4:49 pm #49374I know this has questions has been ask a year ago but I’m hoping you can help me. I’m moving away from vWorkspace connection broker and will replacet it with Paralles connection broker. Is there a way I can use Dell Management Suite with Paralles connection broker. I do not see a section for Paralles connection broker.
March 26, 2019 at 8:42 pm #49394You could try to add
ConnectionBroker=Default Host=Enter_VDI_Broker
to the Advanced section.CG
December 9, 2020 at 5:18 pm #53767So I’ve got this added in the advanced section (But instead of “Enter_VDI_Broker” its a local IP address of our connection broker) and then how do I go about connecting to a LeoStream session? From talking to Leostream they sugest not using WMS and having Leostrean distribute the wnos.ini files, but I’d prefer to stick with WMS.
December 10, 2020 at 5:50 pm #53792Put the string in one line only!
ConnectionBroker=Default Host=Enter_VDI_Broker
CG
December 10, 2020 at 6:18 pm #53793So here is the new line. And this is in the advanced configuration of the devices, not WMS, is that an issue? Also that still doesn’t change anything, should the WYSE terminal try to connect right after it boots, or is there something else I have to change?
December 10, 2020 at 6:48 pm #53797It does not matter if you use the global policy or a device policy.
Do you see a login prompt at the client?
If not, either enable login in the policy, or for testing add
SignOn=yes
in the second Advanced line.CG
December 10, 2020 at 7:18 pm #53800Hey! That works perfectly, thank you so much! I assume I’ll have more questions at some point, but for now everything is working perfectly.
April 16, 2021 at 10:06 am #105111Is ConnectionBroker=Default still available on ThinOS 9.1?
April 22, 2021 at 1:09 pm #105165No
CG
January 30, 2023 at 1:07 pm #108017So is there a way to use a custom connection broker on 9.X?
April 4, 2023 at 1:44 am #108079Please tell us more…
-
AuthorPosts
- You must be logged in to reply to this topic.