Software Deployment

Are you using SMS or something like that to distribute the application, if so you should be able to set the program up so that it downloads the application to the desktop before running the installation?

mathurd,

The other option is to create a package that puts the install files locally, and then a CA to run the setup with desired answer file, or whatever.

Remember to include a CA that uninstalls the VPN client as part of the uninstall for your MSI.

I used this method for a Nortel VPN client a while ago.

John's suggestion is the best way to do it, but if you don't have SMS/SCCM then the only other option is to run it locally from the target machine, as it does drop the network connection as part of its installation.

Hope this helps,

Dunnpy

Stop, for a moment, and read what you wrote:While installing the Cisco VPN Client 5.0.5, it throws Error 28006: Trying to install the VPN Client from a network drive momentarily disconnects network drives and can cause the installation to fail. Copy the installation files to a local drive and restart the install.
This is because of a custom action added in the package. That custom action should not be hidden according to client requirement but still we need to install it from network drive.Now, again:Trying to install the VPN Client from a network drive momentarily disconnects network drives and can cause the installation to fail. Copy the installation files to a local drive and restart the install.
This is because of a custom action added in the package. That custom action should not be hidden according to client requirement but still we need to install it from network drive.Can you not see that those two statements are mutually exclusive? You have NO CHOICE: the package must be copied locally and executed from there, the same as *any* VPN client.

I suspect a search of AppDeploy for 'VPN' would have turned up pretty much the same advice.

mathurd,

I was facing the same problem. I did some search and found out that there are two CAs names as "CsCaDll_GetInstallDriveType" and "CsCaDll_GetInstallDriveType1". I deleted these two frm MST and then deployed the package thru Managesoft. the package installed fine without any error. But a reboot is required.

Try this!

Hi deepesh,
you can safely use dnmech's aproach to solve this.
This condition is completely unnecessary, because the MSI comes with an embedded CAB file.
This CAB will be extracted to the local temp folder and installed from there.

This unnecessary condition is one of many horrible errors, which this MSI has. It's just unbelievable, that this stems from a billion dollar company!

The only situation, which this disconnected network would be a problem, are installing from AIP, which is not necessary, because every new version comes with hole MSI and not as a patch.
Or having the local temp folder on network drive, which is rather hypothetical.

Good luck with this beast...
Regards, Nick