We have worked with a few customers on the Cisco VPN client and haven't had success getting a Prism-created package to work when moved from the system it was built on to another system with the same OS and same network card. Without doing major clean-up on the package, it would knock the system off the network. We were able to clean entries out of the package to prevent it from disabling the network settings on the target, but this resulted in the VPN client not functioning.
We were able to successfully push the VPN command-line setup out through a Prism Channel as a Command Task. Set the Task to run under the context of a domain admin.
REM run Cisco VPN msi installation
REM qb!- no cancel button, no dialogs
msiexec /i
PTS:
/Run %comspec% /c MsiExec.exe /uninstall {3E5562ED-69AB-4CEC-91E2-64E18EC5ACC6} /qn/InstallPackage \\prism\files\installs\CiscoVPN\VPNCleanup.pwc
/Run %comspec% /c \\prism\Files\Installs\CiscoVPN\vpn-Install.bat/InstallPackage \\prism\files\installs\CiscoVPN\vpn-IT.pwc
PWC files simply copy the profiles to the needed locations so that VPN is preconfigured.
vpn-install.bat:
@echo offrmdir "c:\Program Files\Cisco Systems\VPN Client\Profiles" /S /Qmd c:\tempxcopy \\server\share c:\temp\CiscoVPN\ /H /Eclsecho Installing Cisco Virtual Private Network for Employees"c:\temp\CiscoVPN\vpnclient_setup.msi" /qnRMDIR "c:\temp\CiscoVPN" /S /Q
Hope this helps :-)