Windows Server 2008 R2 RDS Connection Broker and HP thin clients

[localzuk]

We have a bunch of HP thin clients running ThinPro which connect to an RDS farm, with a Connection Broker working in between them.

 

I have an issue that when a connection is redirected to a different server, instead of it being seamless, the session shows them the login screen for that server instead and they have to log in again.

 

What is going on? I've followed all the instructions, and there are no errors in the logs on the connection broker - it has lots of successfully redirected messages in the event viewer.

[DMcCoy]

If they aren't RDP 7 or later clients they probably don't support brokers properly, so the username and password have to be supplied again if you get moved to a different server to the initial connection.

 

After spending some considerable time trying to get old rdp clients working there isn't a solution without using the later protocol or typing twice.

[localzuk]

I'm trying a solution that someone else suggested now - using FreeRDP custom installed on them, as it supports NLA and therefore brokering.

[FN-GM]

I assume you have tried updating the client themselves?

[localzuk]

I've got it working with xfreerdp. The default RDP client on the clients doesn't support NLA.

[kmount]

You'll probably have better performance with xfreerdp too. It's under regular development and has some extra functionality over rdesktop. (NLA, RemoteFX, and hopefully very soon .... Gateway support)

[localzuk]

You'll probably have better performance with xfreerdp too. It's under regular development and has some extra functionality over rdesktop. (NLA, RemoteFX, and hopefully very soon .... Gateway support)

 

Didn't realise it was that up to date! RemoteFX support is pretty interesting, as it means our ThinStation machines and our HP ThinPro machines aren't useless if we decide to head towards VDI at some point. Woop!

[kmount]

Yeah, it's very interesting.

 

I still find myself typing rdesktop on my workstation though, I should really symlink it to freerdp

 

FreeRDP & https://github.com/FreeRDP/FreeRDP/wiki are useful.

 

Keep an eye on https://github.com/FreeRDP/FreeRDP/commits/master for early vision on stuff going on

[localzuk]

I ended up doing this http://www.edugeek.net/forums/thin-client-virtual-machines/107013-hp-t5735-custom-debian-install-allow-nla-session-broker-work-rds.html

 

Works great.

[robk]

If they get gateway support in there, and its then compiled for mac os X that would get round the lack of a good mac RDP client as well..

[nicklec]

If they get gateway support in there, and its then compiled for mac os X that would get round the lack of a good mac RDP client as well..

 

The osx rdp client is fine, it has almost exactly the same features as the windows one?