Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Connecting from ThinClient to windows 2012 RDS

Unanswered Connecting from ThinClient to windows 2012 RDS

  • Thursday, January 17, 2013 7:57 AM
     
     
    Sign In to Vote
    0

    First question, shared desktops based on session, I have windows 2012 rds installed, I am able to connect to shared desktop from rdweb. But how do I connect from HP thinpro client? I have two RDSH servers, but I can only put one Ip address under thinpro connection settings..

    The other question is about the VDI connection, how do I connect to windows 2012 VDI(windows 7 VMs)? Again, from rdweb is fine, because once VDI is created, it also creates an icon under rdweb, but how to connect these Vms from thin client?

     

All Replies

  • Thursday, January 17, 2013 8:17 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,

    The way this works with RDS on Windows Server 2012 is that your clients connect to the server running the RD Connection Broker role. This is because the RD Connection Broker role on Windows Server 2012 now also handles the initial connection. Of course directly connecting to the RD Connection Broker won't be allowed for a standard user. In order to let the RD Connection Broker know that a new session needs to be passed on to one of your two RD Connection Broker servers additional .RDP properties need to be specified. See below for an example

    full address:s:FARM.LAB.LOCAL
    workspace id:s:    FARM.LAB.LOCAL
    use redirection server
    name:i:    1
    loadbalanceinfo:s:tsv://MS Terminal
    Services Plugin.1.Wortell_sLab_Ses
    alternate full
    address:s:    FARM.LAB.LOCAL

    If you need more background information on this, the following blog post describes how this exactly works:
    http://microsoftplatform.blogspot.nl/2012/04/rd-connection-broker-ha-and-rdp.html

    The Desktop (or Remote apps) that are available in your RD Web Access are preconfigured with these .RDP properties specific to your environment.

    In order to make the thin client connect to the environment (and through the RD Connection Broker) it obviously also need to specify these parameters. If this is a thin client running Windows Embedded (with at least a RDP protocol version 7) what you could do is provide that thin client with a .RDP file that has these additional parameter set. An easy way to find out the exact parameters you need for your environment is to browse to the folder  C:\Users\<username>\AppData\Roaming\Microsoft\Workspaces\<Workspace-ID>\Resource a client where you've connected through a web feed URL before.

    More information on ways to distribute Desktops and Remote Apps can be found here: Distribution of Remote Apps and desktops in Windows Server 2012

    For your second question, this is basically the same, you'll also need to specify the additional parameters to let the RD Connection Broker know to what VDIyou want to connect.

    Kind regards,
    Freek Berson
    The Microsoft Platform
    Twitter
    Linked-in
    Wortell company website

     
  • Thursday, January 17, 2013 8:24 AM
     
     
    Sign In to Vote
    0
    Thanks Freek, great info, will try tomorrow and post back!
     
  • Thursday, January 17, 2013 11:53 PM
     
     
    Sign In to Vote
    0

    If i have only one RDCB, should I just point all user connections to RDCB's DNS name?





    • Edited by ohohoh Thursday, January 17, 2013 11:54 PM
    • Edited by ohohoh Thursday, January 17, 2013 11:54 PM
    • Edited by ohohoh Friday, January 18, 2013 2:40 AM
    • Edited by ohohoh Friday, January 18, 2013 2:42 AM
    •  
     
  • Friday, January 18, 2013 5:28 AM
     
     
    Sign In to Vote
    0

    The other thing I'm noticed is that I could not connect to RDCB from thin client.

    Server 1: RDCB, RDWA

    Server 2: RDSH

    If i connect by using the .rdp file(pointing to server1), it will take to server2's published desktops.

    if i connect from thin client (thinpro, configured as RDP 3389 to server1), it will give me an message saying logon user limit reached.