Friday, September 20, 2013

Dell / Wyse ThinOS version 8 and the RD Connection Broker in Windows Server 2012

HomeAs you might know connecting to a RDS environment running on Windows Server 2012 (R2) requires users to always connect to the (farm of) RD Connection Broker Servers initially, from where they will be redirected to a RD Session Host in a farm. In order for the RD Connection Broker to be able to redirect the session to the correct RD Session Host farm it needs to be aware of the Session Collection. More info, also sees RD Connection Broker HA and the RDP properties on the client.

DellWyse ThinOS version 8 comes with a full featured RDP8 client and supports the RD Connection Broker 2012. To connect ThinOS8 to a Windows Server 2012 RDS environment you can specify the following .ini parameters;

VDIBroker= AutoConnectList="Full Desktop"

The parameter VDIBroker should point to your RD Connection Broker Server(s) and optionally you can use AutoConnectList to auto run a certain Remote App or Full Desktop. The parameter ConnectionBroker specifies that the broker is a Microsoft RD Connection Broker. Setting the parameter SignOn to Yes allows Thin OS to pass the login credentials, entered when logging on the Thin Client, to the RD Connection Broker

If a user is authorized for multiple Session Collections within a single deployment ThinOS8 will retrieve and show all authorized Remote Apps and Desktops from all Session Collections combined together.

More info:


  1. The RD Connection Broker in Windows Server 2012 R2 accepts SSO on smartcard?? Previous versions only accept SSO when user / password.

    If it works with this version, also works with Thin OS 8??


  2. Blog posts and articles you draw me so much more knowledge, keep your blog so I can visit again to see your blog posts and articles later .. thanks for the info.

    Thin Client Software & Zero Clients

  3. how can i allow singn on option to "yes"

  4. I have this working great in my environment but would like to know if you can bypass the gateway for the wyse terminals since they are all local?

    1. How did you get this working please, I get "RD Broker sign on failed" with an error in eventlog of "unable to setup connection (err=-5902)

  5. Hi,
    I have this working great in my environment too but I wonder if it's possible to set an autologon with a specific username and password in the .ini file?


  6. Would love any assistance on this anyone is able to provide. Basically i'm trying to connect WYSE C10LE thin clients to a Server 2016 RDS Farm. I've applied the latest firmware i can find for these models (8.0.307). If I connect directly to the Session Host server, everything works fine, however i'm having great difficulty successfully connecting to our connection broker.

  7. Andrew did you manage to get this resolved? I have the exact same issue with my Wyse C10LE.

  8. To connect to the broker, it is necessary to add Broker and CA certificates in the Wyse box

  9. While the integration with remoteapp is great there are some major flaws in the end to end solution. Firstly, if the account is set to change password at first logon, the wyse client simply will not allow the user to log on at all, secondly if the user changes his/her password in any remoteapp program and locked the thin client device, it can only be unlocked by the original password. Any suggestions on the latter issue? I've tried the LockTerminal=no but it seems to have no effect.

  10. No i never got this resolved on our C10LE. We are purchasing new WYSE 3040 units as they seem to work much better for what we're trying to do.