Software Deployment

I have been dealing with this. The Cisco engineer response is that you cannot. What you need to do is create a "mycomanyvpnprofile.xml" off of the templates included with the application, fill in your stuff.
Then it goes in the
“C:\Documents and Settings\All Users\Application Data\Cisco\Cisco AnyConnect VPN Client\Profile\myconpanyvpnprofile.xml “ xp “C:\ProgramData\Cisco\Cisco AnyConnect VPN Client\Profile\mycompanyvpnprofile.xml”- vista and 7
Enterprise deployment guide is here:
http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect25/administration/guide/ac08managemonitortbs.html#wp1059347

Hope this helps!

this sounds like a job for a first startup snapshot. Start a snapshot, change the setting in the application and finish your snapshot. Then look for the (relevant) changes that were made to the system and incorporate them into your MSI.

Hi, how would that work? This setting is saved per user it seems? I want the msi to contain this connection string for all users.

ORIGINAL: FunWithApps

I have been dealing with this. The Cisco engineer response is that you cannot. What you need to do is create a "mycomanyvpnprofile.xml" off of the templates included with the application, fill in your stuff.
Then it goes in the
“C:\Documents and Settings\All Users\Application Data\Cisco\Cisco AnyConnect VPN Client\Profile\myconpanyvpnprofile.xml “ xp “C:\ProgramData\Cisco\Cisco AnyConnect VPN Client\Profile\mycompanyvpnprofile.xml”- vista and 7
Enterprise deployment guide is here:
http://www.cisco.com/en/US/docs/security/vpn_client/anyconnect/anyconnect25/administration/guide/ac08managemonitortbs.html#wp1059347

Hope this helps!



Hi, thanks for the info. I have now created the xml configuration file. After reading your link, I don't see how I connect that profile to the msi package?
The idea was to deploy this with a deployment program. (e.g. I want to avoid having the users to go to vpn.mycompany.com web site for initializing the connection )

I don't see how I connect that profile to the msi package?

the idea is to create your transform file and add the XML-file in there. You basically open your msi, add a new component that contains the XML file and set the component's installdir to what it needs to be (from Diane's post). You then save these changes as an MST file and install your msi with the TRANSFORMS=<path to mst file> command line parameter. Don't forget to link the new component to one of the MSI's features, or its contents won't show up on the machine.

Just how easy or hard adding this component is depends on which authoring tools you have access to. As a side note, since it's an XML you also have the option of using the specialised MSI tables for creating and manipulating those, but since it probably has static contents, adding it as a file is an equally good option.

PJ

...and don't forget to avoid hard-coding the profile path. To do so ties the package to Windows 2000/XP (assuming you had used 'C:\Documents and Settings...'). Use the ALLUSERSPROFILE environment variable instead.