Connect to Windows Server 2016 RDS loadbalanced farm

[PatrickK]

Hello,

We have setup a Windows 2016 RDS farm with a broker and a couple of of host servers. I cannot connect to the farm using ASG Remote Desktop as I would with a RDP client. In the RDP-file generated by this environment (and made available by the Web Access) I see a loadbalancer plugin being mentioned. To be clear, when I use the native Windows Remote Desktop Client I can connect to the farm.

In the RDP-file I see this:
---
full address:s:{FQDN}
workspace id:s:{FQDN}
use redirection server name:i:1
loadbalanceinfo:s:tsv://MS Terminal Services Plugin.1.{RDS FARM NAME}
use multimon:i:1
---

I have replaced the fully qualified domain name to our servers with {FQDN} and the name of the RDS farm with {RDS FARM NAME}.
The fourth line contains the "loadbalancer plugin" as I'm calling it.

I have seen before that plugin information for the Remote Desktop Client is stored in registry path [HKCU\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns], but in this case I can not find anything relevant.

Is there a way to connect such loadbalanced farms that use these plugins using ASG Remote Desktop ?

[DevOma]

I think currently not - but we will check that and try to implement asap...

[serverteam]

Hello,
I also tried to import a RDP with loadBalanceInfo parameter, I've got the error: Field LoadBalancerInfo not in parser list > will be ignored
Do you plan to add the support in a future version?
Thanks in advance
Jonathan

[DevOma]

Yes of course thanks for informing - I will check how we can use this field

[DevOma]

We've added the field in UI and for the RDP import function - but I can't test it currently because I do not have a RDS farm...

[serverteam]

Thanks,
If you have a beta version, I can test it.
Rgds

[c2petit]

Hello,

We try new ASG-RD 2018 patch 7.1 and also private patch 7.2. A new field "load balancer info" is now present in RDP connection properties but all parameters we tried result in a RDP protocol error when connecting.

Can you tell us how to fill this field correctly ? We didn't find any information about that in help documentation.
It would be really great if we could connect to our RDS Broker farms with that.

Thanks,

[DevOma]

Ok - we will have a look at that in the next days - currently we are in the final days for the upcoming release..

[c2petit]

Hello,

I see that a new release of ASG-RD has come (2019 version) with a fix on "load balancer info" field, thanks for that. But unfortunatly we still don't have any information about how to fill this field. 

Thanks for your help.

[DevOma]

Yes I know - currently we have Prio1 on a Patch for the version 2019 - afterwards we will begin to work on issues like LoadBalancerInfo - the documentation of that field is not really clear - so we need some more investigation on that...

[radman]

Hallo,
Gibt es zu dem Problem schon Neuigkeiten. Ich nutze Version 12.0.6279.1 und kann mich noch nicht über einen RD connection Broker verbinden. Der RDP Import schlägt auch noch fehl.

[DevOma]

Nein - es gibt noch keine Lösung dafür - aber was scheitert denn beim RDP-Import? Der sollte eigentlich funktionieren...

[DevOma]

We have done some changes on the laod balancer field - found documentation how to set this field - would be nice if somebody like to test it because we don't have a RD connection broker for testing

I could send a link to a private fix - just let me know...

[a1ex]

We have done some changes on the laod balancer field - found documentation how to set this field - would be nice if somebody like to test it because we don't have a RD connection broker for testing

I could send a link to a private fix - just let me know...

I'd be interesting in testing this

[rnollen]

We have done some changes on the laod balancer field - found documentation how to set this field - would be nice if somebody like to test it because we don't have a RD connection broker for testing

I could send a link to a private fix - just let me know...

I'd be interesting in testing this

I am testing it with 2019 Patch 3, but for me it doesn't seem to work. When I use a RDP file I also set this value: use redirection server name:i:1 ; default this is 0 . This because the Broker needs to redirect the session to the session host. Also I don't know exactly what the format is of the load balancer line in ASG. In my opinion it will start with: tsv://MS Terminal Services Plugin/etcetc, but I am not sure. In a RDP file it is loadbalanceinfo:s:tsv://MS Terminal Services Plugin/etc I don't think the first part needs to be set in ASG?

[DevOma]

You're right - the first param in rdp-file is the field - second is type (=>string) and then the value - so you could try with "tsv://MS Terminal Services..."

[rnollen]

You're right - the first param in rdp-file is the field - second is type (=>string) and then the value - so you could try with "tsv://MS Terminal Services..."

Thanks! But it doesn't seem to work only with this. In my setup I also need the use redirection server name:i:1 setting. Is this enabled by default? When set to 0 you will get a redirect error, when this set to 1 it works. So I think both value's are necessary... The good thing is that the Load balancer setting is OK I think. Got the same redirection error when using ASG or an RDP file if I play with the mentioned setting

[DevOma]

Ok I tried to find the setting - without success - tried to set directly in different naming conventions - didn't work either…

We will open an MS-Case to see if there is a way to set this property - because of vacation next time I guess it will take some weeks for getting an answer or solution… but we take care on this

[rnollen]

Ok I tried to find the setting - without success - tried to set directly in different naming conventions - didn't work either…

We will open an MS-Case to see if there is a way to set this property - because of vacation next time I guess it will take some weeks for getting an answer or solution… but we take care on this

Any news regarding this?

[DevOma]

Sorry, not yet - will try to go on with this issue asap….