- This topic has 4 replies, 2 voices, and was last updated 4 years, 2 months ago by
.
-
Posts
-
Hi,
We presently use many Wyse Tx0 thin clients to connect to a few servers and an RDS Server Farm on our network.
To do this we have setup the FTP server and wnos.ini which has in it a list of CONNECT=RDP settings which works fine.
The RDS Farm on-site connection string inside our main wnos.ini is like this:
CONNECT=RDP \
Host=MTRDS2.mt.lan \
Description=”MTRDS2.mt.lan” \
Fullscreen=yes \
Rdp_No_Wallpaper=yes \
Rdp_No_Dragging=yes \
Rdp_No_Animation=yes \
Rdp_No_Theme=yes \
Rdp_No_Fontsmoothing=yes \
LocalCopy=no \
Domainname=mt.lanMTRDS2.mt.lan is the name of our onsite connection broker.
We now have a new externally hosted RDS Server Farm, which we want to connect to as well as the existing on-premise servers.
The new externally hosted RDS farm seems to only let us connect to it if we configure the wnos.ini to use a VDIBroker and ConnectionBroker and have SignOn=yes. But if we use this type of wnos.ini then our list of connectable servers is ignored, as the Wyse then uses the Connection broker, and after NLA signon; logs directly into the Externally hosted RDS Farm.
Is there a way to configure an individual CONNECT=RDP item to use the VDI broker and Connection broker, and not have to use SignOn=yes? Or am I only able to configure it one way or the other?
We are using System version: 8.6_013
My test wyse box has a Mac address of 008064ab950b
So I am using an inv\008064ab950b.ini to test my settings, so I don’t mess with all our working Wyse Tx0’s.
Test 008064ab950b.ini file has this in it:
AddCertificate=”Go Daddy Root CA – G2.cer”
AddCertificate=”Go Daddy Secure CA – G2.cer”;*************************************************************
;* RDP *
;*************************************************************SessionConfig=RDP \
ForceSpan=No \
TSGWenable=No \
EnaleGFX=yes \
EnableRdpH264=yesVDIBroker=https://<new RDS dns host> AutoConnectList=*
ConnectionBroker=Microsoft RDCollections=”Desktop”SignOn=yes DisableGuest=Yes
Domainlist=MT
Warm regards,
Richard Jones
The VDIbroker statement can only be used with SignOn=yes or SignOn=NTLM.
However, if you add
…
Icon=default \
…
to your Connect statement, you will get an icon for each RDP connection on the ThinOSs desktop.
This, along with “SessionConfig=ALL AutoConnect=no” you have all sessions on the desktop and can select which one to start.CG
Hi ConfGen,
Many thanks for your swift reply and assistance.
Adding this one line below solved it for us:
SessionConfig=ALL AutoConnect=no
This means that when we are logged into the Wyse Terminal as preferred login user, it presents us with the Zero Launchpad interface with our old list of connectable connections and adds one on the end of the list of connections. called “Desktop”.
When we click any of the old icons, it prompts for user/pass/domain to that machine and works fine.
If instead of the old icons, we click “Desktop”, it Auto-Logs-onto the new Externally hosted system as the person who is logged into the Wyse terminal. Perfect.
Many thanks again for your help. This has saved us a lot of time and effort.
As point of note, when I tried to use Classic Desktop instead of our usual Zero Launchpal with this methodology, our Wyse Tx0’s locked-up and crashed when trying to connect to the Connection Broker’s Desktop Icon. Odd, but we are used to the “Zero Launchpad” interface anyway, which we get to via Admin menu / Remote Connection / Visual Experience / Zero Launchpad . And Zero Launchapd doesn’t seem to lock up when using both types of connections, brokered or non-brokered, so all is fine.
I owe you a crate of beer 🙂
Warm regards,
Richard Jones
Cool.
You can even add username=$un and password=$pw to your Connect statement. That way the credentials from the login box will be used for the RDP connection.CG
- You must be logged in to reply to this topic.