• Cisco Anyconnect Vpn Profile Editor

This package is an example of one where I would consider using the vendor-provided package as its scripts make changes to various things in the network stack. If we want to customize, what I might do is create a 'helper package' that is essentially a snapshot from the point of finishing the install the vendor package to the point it is ready for the end user to login with. That way you can populate preference files and such.

You could also consider installing with Cisco's AnyConnect profiles as well, but may take some more advanced packaging. A snapshot is not a great choice here simply because AnyConnect does have an impact on network settings. This is currently what I'm using for AnyConnect. #!/bin/sh ## postinstall pathToScript=$0 pathToPackage=$1 targetLocation=$2 targetVolume=$3 # Install the software installer -package '/private/tmp/AnyConnect/AnyConnect.pkg' -target / -applyChoiceChangesXML '/private/tmp/AnyConnect/choices.xml' # Hide the opt folder chflags hidden /opt # Remove the files from /private/tmp /bin/rm -rf '/private/tmp/AnyConnect' exit 0 ## Success exit 1 ## Failure choices.xml choicefireamp choicewebsecurity choiceposture choicenvm choiceumbrella. I think 's post coming from a Cisco employee is probably the gold standard saying that it is not a good idea to repackage this.

I only go to a repackage personally if no other technique gets the software the way I want it on a system and that is very rare. I would be interested to see 's response to the original poster if he is offering custom help. I don't have to deploy AnyConnect too often, but having a bonafide recipe to get it deployed from a Mac guy at the vendor itself is the best that can be sought. Sorry it took a while for the reply but wanted to make sure the process worked for. Below is the process we use to package AnyConnect with only certain modules. External Requirements: Packages (XML Editor (Such as TextWrangler, BBedit) Overview: Create Choice Change XML (See end of post) Create Pre and Post flight scripts (See end of post) Create wrapper package to install vendor AnyConnect.pkg with Choice Change XML Create Choice Change XML: Like the attached plist, you create an xml file saved as whatever name you like but ensuring it is in the proper plist format.

I’ve already created it this time with the modules you want enabled. Create Pre and Post Scripts: I’ve attached examples of these scripts. You’ll see where to use them below.

The preflight closes AnyConnect if it is already installed and running. The postflight installs the vendor package with the choices XML file so you only install what you want. Create Wrapper package: Create folder for AnyConnect Packages project. Here is how I structure my folders: Open the Packages app to create a new Raw package and name it anything you like: Choose an identifier (ours is com.cisco.x.x because we are Cisco. I would use something unique to you) and supply a version number for your package.

I make the version number match the version of AnyConnect: There is no payload to specify so you can skip this screen. On the Scripts tab add your Pre and Post scripts and add the Choices xml and vendor package as addition resources: (The file can be named whatever you would like. This was an example for ) Save the project and then choose to build it. You should now have a package, though unsigned, that will install only the modules you want.

If you need to install profiles or other files you can create further packages or simply add to the payload. Packages can apply a cert to your package if you have one or you can sign it after you build it. I know this thread is a bit old but I was able to successfully deploy the Cisco AnyConnect VPN module and the ISE Posture Module (the only two we use) separately by extracting them with Pacifist.

Yes I have to upload two separate.pkg's to the JSS but the result was smooth and everything works great. Open.DMG with Pacifist and navigate to the AnyConnect.pkg. The dropdown will show you the packages for all of the modules within the main AnyConnect.pkg.

Choose the ones you want to deploy later and use the 'Extract Subpackages' option. Upload to the JSS and create your policy for deployment.

Cisco Anyconnect Vpn Profile Editor

Hope this helps anyone not keen on editing XML and plist files.