Combining iPass client with Cisco VPN client
Newbie Question - What is the easiest way to create a back to back install of the iPass client and Cisco VPN client?? I would like to create a single MSI that installs both. The iPass client is setup to launch the Cisco client when you connect. Therefore instead of installing one then installing the other, because of the dependency, it would be best to have one MSI that installs both.
I know about the Cisco client being local to install. My thinking is that this combo install would have to run locally. But I have to figure out a way to get the install(s) local.
I imagine this whole package would be wrapped in an MSI that copies the combo install locally and runs. How is that done??
Thank you
I know about the Cisco client being local to install. My thinking is that this combo install would have to run locally. But I have to figure out a way to get the install(s) local.
I imagine this whole package would be wrapped in an MSI that copies the combo install locally and runs. How is that done??
Thank you
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
MSIMaker
19 years ago
Posted by:
greenmagnet
19 years ago
I don't recommend that you bundle these two together.
From past experience these products have a different upgrade cycle. Bundling them together (or most interdependent products for that matter) isn't best practice as it complicates your upgrade management. In a previous job I did three versions of Cisco VPN and one Ipass client.
Secondly and more importantly, the Cisco VPN is a pig to repackage. As of version 4.x Cisco have released it in MSI format and their MSI actually works. All you need to do to get it to install from a network via GPO or similar is stop / start the Netman (I think but it was a while ago) service via MST.
Enjoy!
From past experience these products have a different upgrade cycle. Bundling them together (or most interdependent products for that matter) isn't best practice as it complicates your upgrade management. In a previous job I did three versions of Cisco VPN and one Ipass client.
Secondly and more importantly, the Cisco VPN is a pig to repackage. As of version 4.x Cisco have released it in MSI format and their MSI actually works. All you need to do to get it to install from a network via GPO or similar is stop / start the Netman (I think but it was a while ago) service via MST.
Enjoy!
Posted by:
slothworld
19 years ago
Posted by:
slothworld
19 years ago
UPDATE - I created an MSI that installs both the iPASS client and Cisco VPN with WPS. No errors. The MSI installs very nice and it all works.
The issue I am having now is the un-install. When you un-install this combo install, it leaves behind non- working network cards. I have un-installed and re-installed the network card and can not get the card to work. The un-install process really messed up the card. The TCP/IP settings do not have default gateway. It doesn't matter if the IP is static or DHCP. Static entry it just ignores the default gateway. So a rebuild is the next step.
How can I make this un-install process to work cleanly??
Is this the nature of combo installs??
Is this the Cisco VPN client causing this issue??
Is this the iPASS client causing this issue??
Can I wrap the 2 installs in a VB script and do this kinda manually??
Thank you
The issue I am having now is the un-install. When you un-install this combo install, it leaves behind non- working network cards. I have un-installed and re-installed the network card and can not get the card to work. The un-install process really messed up the card. The TCP/IP settings do not have default gateway. It doesn't matter if the IP is static or DHCP. Static entry it just ignores the default gateway. So a rebuild is the next step.
How can I make this un-install process to work cleanly??
Is this the nature of combo installs??
Is this the Cisco VPN client causing this issue??
Is this the iPASS client causing this issue??
Can I wrap the 2 installs in a VB script and do this kinda manually??
Thank you
Posted by:
WiseUser
19 years ago
This is a pretty standard scenario for this type of package.
There are several things that can help avoid this type of problem:
- Good repackaging tools.
- A well constructed exclusion list.
- Merge modules.
- Proper conflict management.
- Experience.
Fortunately, your testing has prevented this happening to a large number of users in a live environment. Be thankful for that!!
Your package is removing something that it shouldn't. You need to find out what and why - and then prevent it happening.
There are several things that can help avoid this type of problem:
- Good repackaging tools.
- A well constructed exclusion list.
- Merge modules.
- Proper conflict management.
- Experience.
Fortunately, your testing has prevented this happening to a large number of users in a live environment. Be thankful for that!!
Your package is removing something that it shouldn't. You need to find out what and why - and then prevent it happening.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.