VPN establishment capability from remote desktop is disabled. A VPN connection will not be established. This is what I did to get it functional. Go to your virtual machines and edit the Settings. Under Networking, ensure that you are using Share Networking (NAT) Under Integration Features, ensure that Enable at startup is NOT checked. VPN establishment capability from a remote desktop is disabled. A VPN connection will not be established. Cisco’s documentation mention these limitations are specified in a profile XML file which is downloaded from the VPN server during the connection establishment. VPN establishment capability from a Remote Desktop is disabled. A VPN connection will not be established. This, behaviour is default, and despite me trawling the internet to find a solution (most posts quote changing the local AnyConnectProfile.tmpl file, this file does not exist using Version 3 (I was using v 3.0.4235). Update: With Early versions of AnyConnect version 4 it does not tell you. VPN Establishment capability from a Remote Desktop is disabled. A VPN Connection will not be established. Solution: By default, VPN establishment capability is disabled once you remote into a remote desktop session. To enable Cisco Anyconnect VPN through a remote desktop you must first create an Anyconnect Client Profile. VPN Establishment capability from a Remote Desktop is disabled. A VPN Connection will not be established. I did a lot of research, and found out that in order to allow this, you need to first setup a Client Profile on the Cisco ASA.
I ran into a problem recently while I was using remote desktop on one of my servers hosted up on Azure. While I was on that server, I needed to make a VPN connection back to our corporate network. Unfortunately, after I installed the Cisco AnyConnect client, and I tried to make the connection, I was greeted with the following error:
VPN Establishment capability from a Remote Desktop is disabled. A VPN Connection will not be established.
![Not Not](/uploads/1/1/7/7/117795311/610234607.png)
Cisco Anyconnect 4.6 Vpn Establishment Capability From A Remote Desktop Is Disabled
![Persons Persons](/uploads/1/1/7/7/117795311/899006562.png)
Vpn Establishment Capability From A Remote Desktop Is Disabled Accessible
I did a lot of research, and found out that in order to allow this, you need to first setup a Client Profile on the Cisco ASA. Here are the steps I went thru to get this completed.
Vpn Establishment Capability From A Remote Desktop Is Disabled
- Launch the Cisco ASDM
- Click on Configuration.
- Expand “Network (Client) Access”
- Click on “AnyConnect Client Profile”
- Since, I did not have any existing profiles, I clicked the Add button.
- Pick a name for the Profile.
- Select the Group Policy that this profile will apply to, and click OK
- Before editing the profile, click on the Apply button to generate the XML file.
- Under “Preferences (Part 1)” go to “Windows VPN Establishment” and select AllowRemoteUsers from the drop down, and then click OK.
- Click on the Apply button to update the XML file.
- You should now be able to test connecting to your network from within a Remote Desktop session.
- Assuming everything works as expected, I recommend hitting the Save button to write your configuration to memory.