AnyConnect config profile

Honestly, no. It adds it to Network Prefs in my experience and still requires you to use the app. I use an XML I packaged up and that seems to work perfectly every time.

Just bumping this thread. I'm seeing the same results as @jubei in relation to using a configuration profile (VPN payload with AnyConnect option). I can work around it, but not sure as to why it's even an option?

We do the same and it works fine.

@dpertschi I'm doing the same thing along with a bundled choices.xml since we don't use Fireamp and WebSecurity. I'm also adding in the posturing files as well.

<array>
    <string>choice_fireamp</string>
    <string>choice_websecurity</string>
</array>

Why is packaging this so hard? I'm working off of an old package my predecessor created for 3.15. The package has the applications folder, library folder and opt. I see that he created a .xml in /opt/cisco/anyconnect/profiles. I copy that and put it in the new package with the same permissions and rights. When I go to test the client is upgraded but my server information is gone. Tunnel down in finder and find that .xml is there. What am i doing wrong?

How are you all pushing out the anyconnect profile that contains the server info? I know about the ~/.anyconnect file, and can push that out with the client, but I've read about the profile xml also being in /opt/cisco/anyconnect/profile and I've saved an edited xml file there, but it still doesn't read it. Every site I've come across says to save it there, but it never works for me. Still have to punch in the server address.

Also, and maybe this is an easy one, it'd be nice to find a way to have it start up, but not show the connection window, just put the icon in the finder bar so it's there if the user needs it.