/build/static/layout/Breadcrumb_cap_w.png

Silent install of Cisco VPN client: Default connection entry

I'm deploying Cisco VPN client v. 5.0.07.0440 and I'm having an issue defaulting it to a certain connection. I edited the vpnclient_setup.ini to look like this:

[WiseInstaller]

RuntimeNTVersion=2.0.2600.2

ProductFile=vpnclient_setup.msi

ProductCode={5FDC06BF-3D3D-4367-8FFB-4FAFCB61972D}

ProductVersion=5.0.7

ProductName=Cisco Systems VPN Client 5.0.07.0440

Remove Previous=0

AdminError=You must have administrator rights to run this installation. Please login as an administrator and re-run this installation.

ExistError=%s Version %s is already installed. You must uninstall the existing version before installing %s Version %s. Do you want to uninstall the existing version of %s?

SpaceError=Could not create temporary file, not enough free temporary disk space. Please free up disk space and rerun this installation.

WiseInitPrefix=Initializing

WiseInitSuffix=Wizard...

WiseInitLangPrompt=

WiseInitLangDefault=English,1033

DefaultConnectionEntry=MJFF-NYC-VPN

Language1=Japanese,1041

LanguageFile1=vpnclient_jp.mst

Language2=French (Canadian),3084

LanguageFile2=vpnclient_fc.mst

RuntimeNT=instmsiw.exe

RuntimeSizeNT=1822520

DelayReboot=

So as you can see I added the DefaultConnectionEntry to the file and ran the silent install which went well but it's still defaulting to MJFF-FO-VPN and not MJFF-NYC-VPN. Do I need to modify the .ini file further?


0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ