![]() Someone then mentioned that I need the intermediate or root certificate. I have tried this, but still get the same. Mentioned to me that I need to add the SSL certificate onto the WYSE. I do not want a fully desktop, only specific RemoteApp Utilising this, I can successfully connect with no SSL errors, but I get a full desktop. ![]() Then specify the parameters for RDPĪnd this then creates and RDP Shortcut on the desktop. I just do not want a full desktop, I only want to launch individual RemoteApps.Īgain, on the WYSE Thin Client itself, System Setup>Remote Connections>Broker Setup>Broker type=>None. Then specify none as the Broker type instead and configure an RDP session, I can successfully connect and launch into a full remote desktop, so I know the network and credentials are ok. There is then an option to enter the hostname or ip address of the Broker Server and then an Auto Connect List (I'm assuming this would be where I specify an individual RemoteApp) On the WYSE Thin Client itself, System Setup>Remote Connections>Broker Setup>Broker type=>Microsoft Please see answers to your questions below:Ĭonfiguring the WYSE 3040, I specify Microsoft as my Broker type and specify my connection Broker (hostname or ip address), but get "RD Broker sign-on failed" If you have feedback for TechNet Subscriber Support, for coming back. Please remember to mark the replies as answers if they help. rdp file for the remote app you wanted to use in Thin client? After then, what is the exact error message you met when you opening Just to confirm have you opened RD web access page and download the. If you received any certificate error when launching or start the remote app, you could consider to resolve the error message by modify the SSL certificate. Someone mentioned to me that I need to add the SSL certificate onto the WYSE. ![]() How did you start the remote session when using thin client? Did you use mstsc or RD web access page? I just do not wantĪ full desktop, I only want to launch individual RemoteApps. I then specify none as the Broker type instead and configure an RDP session, I can successfully connect and launch into a full remote desktop, so I know the network and credentials are ok. Where did you make such modification? In. (hostname or ip address), but get "RD Broker sign-on failed" When configuring the WYSE 3040, I specify Microsoft as my Broker type and specify my connection Broker Some questions to understand your issue better:ġ. Not sure if anyone can confirm or deny?Īny help would be appreciated, thanks in advance. ![]() I just do not want a full desktop, I only want to launch individual If I then specify none as the Broker type instead and configure an RDP session, I can successfully connect and launch into a full remote desktop, so I know the network and credentials are ok. When configuring the WYSE 3040, I specify Microsoft as my Broker type and specify my connection Broker (hostname or ip address), but get "RD Broker sign-on failed" I was just wondering if anyone anywhere has managed to launch an individual RemoteApp on a device running WYSE Thinos? We are looking to be able to launch an individual RemoteApp on a Dell WYSE 3040 running WYSE Thinos 8.6 essentially in a Kiosk type mode. SSO is configured and we deploy a number of RemoteApps to devices within our Windows Domain and all works perfectly and users can launch RemoteApps from the Start Menu as if they were a local app. VM01 - RD Connection Broker, RD Licencing, RD Web Access, RD Session Host We have a Server 2012 R2 Remote Desktop Services environment with two VMs forming the farm: Hoping someone can help me out here as no suggestions in other forums have helped and I've not been able to reach out to Dell direct. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |