Forum Discussion
NimbostratusRDP Gateway 11.6
Hi has anyone gotten RDP Gateway to work on 11.6 APM?
Following the steps in the article doesn't work. The thing is when i connect from a windows mstsc.exe RDP client, the APM doesnt recognize that its a Client Type of "Microsoft RDP client".
instead it flows through the "full or mobile browser" and then client os of "fallback". But even if i apply the polices on the fallback branch it wont connect through?
So just curious has anyone actaully gotten this RDP Gateway to work? and if so, did you have to make adjustments to the steps in the article?
6 Replies
Michael_KoyfmanCirrocumulus
Yes, it certainly works - I do have it working. Is your goal to service multiple client types on the same virtual? For simplicity sake you can just get rid of the client detection piece and start with VPE actions after that to see if you can get it to work that way.. - you can always get it back in. Also, it would help to know what RDP clients you are testing with? Seeing the client-type info from the access policy reports on failed sessions would also be helpful.
THiHi Michael We are about to test F5 RDS proxy/RDG . There seem to be three documents/ways to implement RDG: - iApp (https://clouddocs.f5.com/api/iapps/Microsoft-Remote-Desktop-Gateway-APM-Gateway-iApp.html) - deployment guide (https://www.f5.com/pdf/deployment-guides/f5-microsoft-remote-desktop-services-dg.pdf) - implementation manual (https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-implementations-11-6-0/6.html) Which of these would be recommended to implement the F5 RDP proxy/RDG? Does the F5 implementation support Remote Apps?
Michael_Koyfma1Cirrus
Yes, it certainly works - I do have it working. Is your goal to service multiple client types on the same virtual? For simplicity sake you can just get rid of the client detection piece and start with VPE actions after that to see if you can get it to work that way.. - you can always get it back in. Also, it would help to know what RDP clients you are testing with? Seeing the client-type info from the access policy reports on failed sessions would also be helpful.
- THiHi Michael We are about to test F5 RDS proxy/RDG . There seem to be three documents/ways to implement RDG: - iApp (https://devcentral.f5.com/wiki/iApp.Microsoft-Remote-Desktop-Gateway-APM-Gateway-iApp.ashx) - deployment guide (https://www.f5.com/pdf/deployment-guides/f5-microsoft-remote-desktop-services-dg.pdf) - implementation manual (https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-implementations-11-6-0/6.html) Which of these would be recommended to implement the F5 RDP proxy/RDG? Does the F5 implementation support Remote Apps?
- Michael_Koyfma1
Using the iapp is the way to go here. Regarding Remote Apps - the access method 2 from the following link: http://technet.microsoft.com/en-us/library/cc755055.aspx should work with the APM RDG Gateway deployment.
Kevin_Davies_40Nacreous
If you are using Windows 7 you need to follow the recommendations of the APM Client Compatabilty Matrix.
This says you need KB2592687 ~ Remote Desktop Protocol 8.0. Which as a prerequisite needs hotfix KB2574819 ~ DTLS support. When they have been applied you need to follow the instructions for the first which require you to enable Remote Desktop Protocol policy using the local Group Policy Editor. I set this to TCP Only and it worked a treat.
