Remote Desktop Web Access & APM
We have recently built a RDS solution and have put BIG-IP LTM infront of the web access server (which is also the gateway & connection server). I have two iApp built HTTP virtual servers currently in use - one for internally connected devices and one for externals. The idea being we could leverage APM to put 2FA in place for the external connections. All other authentication is handled by the RDS server - not the F5. The problem I have is that whilst the internal vs works fine the external does not. As soon as I place an access policy on the vs (even just a blank one) I can no longer get a desktop. I still get to the web access RDS logon page and desktop selection, etc but everytime I launch a desktop I get... Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
503 Must Use Post Return Code for 2012 RDS Gateway Implementation
I have a new Microsoft RDS implementation at my company and am having some troubles getting the RDS Gateway health monitors to work correctly. I am using the two Windows 2012 health monitors detailed in F5's own RDS Deployment Guide found at [http://www.f5.com/pdf/deployment-guides/f5-microsoft-remote-desktop-services-dg.pdf]. The RDS Gateway health monitor steps are located on page 10 and 11. When I test these health monitors via the CLI, I am receiving a "HTTP/1.0 503 Must use POST" return. I also placed the same receive string "HTTP/1.0 503 Must use POST" into the Health monitors on the F5 just to make sure the F5 wasn't seeing something different than my CLI testing, attached it to the pool, and the pool came right up fine. When testing from the CLI, I am using the following command (less some company details). For testing purposes, I have made rdshealthmon a domain admin so permissions are not an issue. curl -k https://172.16.3.140/Rpc/ -H "User-Agent: MS-RDGateway/1.0\r\nRDG-ConnectionId: {00000000-0000-0000-0000-000000000000}\r\nHost: rdsgate.companyname.com\r\nConnection: Close\r\n" --basic -u "company\rdshealthmon" -v I am wondering if anyone else has had this issue while following F5's own Deployment guide and if there is a solution around it.