Software Deployment

Gizmolala,

I recently had to package the Nortel VPN Client, which I'm guessing is going to be similar.

Because of the driver installation issue, I ending up creating an MSI package that copied the vendor install file down to the target machine and then run "setup" as a custom action.

The Nortel client came as an Installshield executable, so I was able to record a setup answer file, as described in the link below:

InstallShield Setup Silent Installation Switches

I created a separate removal answer file for the uninstall custom action.

I hope that points you in the right direction. I found that trying to snapshot such an installation that installed network drivers ended up with a FUBAR TCP/IP stack that couldn't be easily resolved.

Thanks,

Dunnpy

I wrote a startup script that copies the package to the computer then installs from that location. The cisco vpn client will not install over the network, like gizmolala said it fubars the tcp/ip.

Tnx all. I've created a response file for it. Will write a script that will copy it to local machine and install from there.

Cheers.

Giz

Hi folks,
don't invest your time in work wich others have allready done. CISCO VPN 4.x is available as IS setup or as MSI. See:
http://itninja.com/link/this-link8
Just download the MSI version from CISCO.
Regards, Nick

Just spent all day trying to get version 4.8.002.0010 msi to install through group policy. It will not work. Tried admin install, just the msi package as is, modifying both using wininstall. Still get an error to effect of cisco vpn client cannot be installed over a network connection. I had high hopes from the previous post but apparantly only the older versions work.

If anyone comes up with anything else please post.

dangIT

How about creating an MSI wrapper that will copy the CISCO VPN msi to the client then use nested MSI?
As the CISCO VPN msi will be installed from the client this should not prevent the installation as it's not installed over network.

AngelID,

I have tried repackaging using wininstall, but I'm missing something cause it doesn't work. How exactly do you create an msi that copies another msi to a drive then run it?