We have an existing SSL VPN on our BIG-IP that needs ( as I understand ) to be configured for use with the BIG-IP Edge Client due to the SSL VPN not supporting modern browsers for RDP access. Basically, our users are having to use I.E 11 to use the SSL VPN for RDP app tunnels because newer browsers ( e.g. Chrome, FireFox, Edge ) do not support the plug-in's necessary for the SSL VPN do do it's job. We downloaded the BIG-IP Edge Client, pointed it to our SSL VPN address and it attempts to connect but fails and give us the error "You do not have access to the Network Access Connections. Please contact your system administrator." We have little knowledge of these BIG-IP systems and most of what they are configured to do was setup by F5 Professional Services. We are stuck with our limited knowledge and no budget to pay for assistance, so we are trying our best to get this to work and asking for any assistance that can be provided, whether it be as simple as pointing us in the right direction or if someone has been in this situation before and letting us know what they did to overcome the obstacle. Any input is greatly appreciated.
You do not need to use Edge Client. Because you can use Chrome, Firefox or Edge for Native RDP access with APM.
Create and configure a native RDP resource( Access > Connectivity / VPN > VDI / RDP > Remote Desktops ) Then add it to your webtop.
how to create a RDP access link
Is this issue the result of a recent change, or was it broken/limited to using IE 11 from the initial set-up? From your description, it sounds like the VPN was successfully configured to use IE 11, and you are trying to implement other browsers. But if the SSL VPN configuration as a whole hasn't been working, then I'm more inclined to think its an issue with your Network Access Resource configuration, and I'd recommend going through the APM configuration guide on network access. Then again, it could be something as simple as forgetting to pay licensing fees. At the very least, this will give you some more knowledge for troubleshooting, and if it's too difficult it might at least sway whoever's dictating your budget.
My second go-to for SSL VPN troubleshooting would be to check what version of Big-IP you are running and ensure you have the proper SSL VPN edge client for each. I believe ver. 11-12 require different versions than 13+, as you can see here.
Feel free to ask if you have any follow-up questions,