- This topic has 7 replies, 3 voices, and was last updated 4 years, 7 months ago by ConfGen.
-
AuthorPosts
-
January 14, 2020 at 3:06 pm #51544
Hello,
I am trying to configure ThinOS to point directly to our RD Connection Brokers which are setup in HA. We currently only have one RD Web Access server and I do not want to have that as a point of failure for people to be able to connect. We currently use Windows 7 Embedded on all of our Wyse with our predefined RDS connection on the desktop. I want to move them all to ThinOS but not being able to connect directly to the RDCB collection is preventing us from doing this.
This is our RDS config, how do I translate this to my ini for ThinOS?
redirectclipboard:i:1
redirectprinters:i:1
redirectcomports:i:0
redirectsmartcards:i:1
devicestoredirect:s:*
drivestoredirect:s:*
redirectdrives:i:1
session bpp:i:32
prompt for credentials on client:i:1
server port:i:3389
allow font smoothing:i:1
promptcredentialonce:i:1
videoplaybackmode:i:1
audiocapturemode:i:1
gatewayusagemethod:i:2
gatewayprofileusagemethod:i:1
gatewaycredentialssource:i:0
full address:s:RDS.***.CORP
gatewayhostname:s:rds.***.com
workspace id:s:RDS.***.CORP
use redirection server name:i:1
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.RDS
use multimon:i:1
alternate full address:s:RDS.ROYAL.CORP
signscope:s:Full Address,Alternate Full Address,Use Redirection Server Name,Server Port,GatewayHostname,GatewayUsageMethod,GatewayProfileUsageMethod,GatewayCredentialsSource,PromptCredentialOnce,RedirectDrives,RedirectPrinters,RedirectCOMPorts,RedirectSmartCards,RedirectClipboard,DevicesToRedirect,DrivesToRedirect,LoadBalanceInfoJanuary 14, 2020 at 4:44 pm #51545If you are using a wnos.ini file, then add:
ConnectionBroker=Microsoft Host=RDS.***.CORP
SignOn=YesCG
January 14, 2020 at 7:14 pm #51554I do have Wyse Management Suite installed on a server as well. How would I configure this? RDS.DOMAIN.CORP is setup with DNS round robin to point to RDSCB01 and RDSCB02. In WMS I have the Microsoft Broker configured to use RDS.DOMAIN.CORP as my broker server and the sessions to connect automatically is set to RDS (My collection name). But when I update it on the wyse and try to login it comes back with RD Broker Sign-On failed. Nothing is shown in the logs on why this is failing or that it is even trying to connect.
January 14, 2020 at 9:01 pm #51555For our ThinOS clients we just use the direct RDP configuration and point it to the round-robin name (RDS.DOMAIN.CORP). Seems to work better than using the RD connection broker setup, for us anyway.
January 14, 2020 at 10:02 pm #51558When I try to do that it is connecting directly to the Connection Broker and not going onto one of the RDS Hosts in the farm.
January 23, 2020 at 5:28 pm #51612You have to set up the MS Broker in WMS.
Open your profile and go to “Microsoft Broker”. Enter the URL of your MS Broker in the field. Remove the direct RDP connection.CG
January 23, 2020 at 7:07 pm #51620Ok I have that setup, but anytime I try to connect it says RD Broker Sign-On Failed. What could I be missing here? The Event Log does not show anything, and Event Viewer on my CBs do not show any event.
January 23, 2020 at 7:36 pm #51621Make sure that the RDweb role is installed on your broker or a different server. Point the client to that RDweb role.
CG
-
AuthorPosts
- You must be logged in to reply to this topic.