Software Deployment

Repackaging iPass will cause you problems... There are hooks into the NIC and every machine is different.

Using an MSI to wrap the installer and then adding logic to detect the older version of ipass and using a setup.iss to run a quiet uninstall.

Run the iPass Setup.exe with a /r parameter to install it.
Setup.exe /r
It will create a file here - %windir%\setup.iss ... I usually rename this file to represent what it does (ipass351Install.iss)

use this file to call your setup.exe in C:\Program Files\InstallShield Installation Information\<Product Code> with a /s /f1"path to iss file"
setup.exe /s /f1"C:\Temp\setup.iss"
or if you renamed it...
setup.exe /s /f1"C:\Temp\ipass351Install.iss"

This allows for a Quiet install.

Naviagate to C:\Program Files\InstallShield Installation Information\<Product Code> and call the setup.exe there using the /r again.
Collect the setup.iss file again and name it ipass351Delete.iss

Use this file to run a quiet removal.

Repeat this and collect the iss for the older ipass installs you want to handle.

Deliver both of these files in the MSI.

The setup can just call setup.exe, but for the removal - make sure to use rundll32.exe and call the uninstall just like the uninstallstring in ARP. Otherwise the MSI will not be able to monitor the completion and the MSI will continue while the uninstall is still occuring.

I know this isn't a walkthrough, but I hope the ideas help...:)

Hi all,

I'm with iPass (sales engineering... and I do the MSI packaging for the client).
There was a known issue in iPassConnect 3.50 which was resolved in 3.51. It had to do with the phone book update appearing to not update, when in fact it was. Again...resolved in 3.51 (which is the latest available release at this time).

Please feel free to contact me with any questions regarding the MSI packaging of iPassConnect.

Hi gmorgan618,

Thanks for the reply, I'm sure it'll help loads of people. Me, I'm set on creating a workable msi, I've spent so much time already and am so close, would be silly to give up now.

A bit more info on what I've done:

Ver: 3.51.0.107
--------------------------------------------------------------------------------------------------------------------
Problem: Snapshot doesn't capture network drivers (could have been my filtering too)
Solution: Create a custom action as follows:
CAM_InstallNetworkDrivers 1042 iPassI5.exe /vendor /force /install /silent

I found the switches in the goobdy goo setup.inx file (in %temp% dir when running setup.exe)
--------------------------------------------------------------------------------------------------------------------
Problem: Services just won't work, lots of msgboxes "Contact Support" ect
There are 3 services that I can make out:
1.) iPassPeriodicUpdateApp
2.) iPassPeriodicUpdateService
3.) iPassConnectEngine

1 & 2 won't work properly unless 3 is working well but installing 3 by only using the Service install table doesn't work.

Solution: Create 2 custom actions: Again I found the switches in the goobdy goo setup.inx file

CAM_iPassConnectEngine_Regserver 1042 iPassConnectEngine.exe /regserver
CAM_iPassConnectEngine_Service 1042 iPassConnectEngine.exe /Service

Now 1 & 2 seem to work - I start all 3 services in the Service Control Table
--------------------------------------------------------------------------------------------------------------------

I know I've missed somthing small, maybe a setting in an ini file or a regkey?
I've also tried unregistering and re-registering each dll but still no help.

Well, I hope this helps a few people in the meantime, pls lemmie know if it does, will help me carry on ...

ORIGINAL: chris.penney

--------------------------------------------------------------------------------------------------------------------
Problem: Snapshot doesn't capture network drivers (could have been my filtering too)
Solution: Create a custom action as follows:
CAM_InstallNetworkDrivers 1042 iPassI5.exe /vendor /force /install /silent

I found the switches in the goobdy goo setup.inx file (in %temp% dir when running setup.exe)
--------------------------------------------------------------------------------------------------------------------



Make sure you use this CLI instead:

At install (condition: Not Installed)
iPassI5.exe -vendor iPass silent install

At Removal (condition: REMOVE = "ALL")
iPassI5.exe -vendor iPass silent uninstall

This is the correct CLI.



ORIGINAL: chris.penney
--------------------------------------------------------------------------------------------------------------------
Problem: Services just won't work, lots of msgboxes "Contact Support" ect
There are 3 services that I can make out:
1.) iPassPeriodicUpdateApp
2.) iPassPeriodicUpdateService
3.) iPassConnectEngine

1 & 2 won't work properly unless 3 is working well but installing 3 by only using the Service install table doesn't work.

Solution: Create 2 custom actions: Again I found the switches in the goobdy goo setup.inx file

CAM_iPassConnectEngine_Regserver 1042 iPassConnectEngine.exe /regserver
CAM_iPassConnectEngine_Service 1042 iPassConnectEngine.exe /Service

Now 1 & 2 seem to work - I start all 3 services in the Service Control Table
--------------------------------------------------------------------------------------------------------------------

I know I've missed somthing small, maybe a setting in an ini file or a regkey?
I've also tried unregistering and re-registering each dll but still no help.

Well, I hope this helps a few people in the meantime, pls lemmie know if it does, will help me carry on ...



There are many DLL's to register. No INI edits required (or used).

In the registry info, make sure the following values to not have a trailing backslash and that they do not merely consist of the value [INSTALLDIR]. This causes the failure... they need to have the full path (this is something we're working on fixing):

HKLM\SOFTWARE\iPass\iPassConnectEngine[InstallPath]=[ProgramFilesFolder]iPass\iPassConnect
HKLM\SOFTWARE\iPass\PeriodicUpdate[InstallPath]=[ProgramFilesFolder]iPass\iPassConnect
HKLM\SOFTWARE\iPass\PeriodicUpdate[PhonebookPath]=[ProgramFilesFolder]iPass\iPassConnect

Still no luck [:(]

Is ver3.51 available as an msi?

ORIGINAL: chris.penney

Still no luck [:(]

Is ver3.51 available as an msi?

Chris,

iPass doesn't yet have an official MSI offering for 3.x clients. We plan to have this available (by default) for 4.0 coming in Q1-08. However, it is still possible to repackage 3.x into MSI and we do offer it for active customers should they desire it. Contact your iPass Account Manager, Sales Engineer (US), or Technical Consultant (outside of US) for details.

now working, needed

PeriodicUpdateApp.exe /regserver


[:D] [:)] [:D] [:)] [:D] [:D] [:)] [:D]

Hi Chris,
congrats to having it done.
Could you please post your complete receipt for the MSI packaging to AppDeploys Package Knowledge Base.
Regards, Nick

Chris,

Before posting anything to a generally available knowledge base, I'd highly recommend you test the MSI thoroughly. Not just installing and removing, but actually using the iPassConnect client... connecting with it... updating it's directory both manually and automatically (i.e. letting it update on its own), etc.

There are many factors to the iPassConnect client (i.e. registry settings, file registrations, etc) and if not all of them are precises, the client will visible seem OK, but will not correctly update.

Lastly, there is one more thing to point out. The ipcheck.exe utility in the client, when repackaged in MSI format, needs to be replaced with a "dummy" one that I can provide. It is important you do this. Reason being is that when a new version of iPassConnect is pushed out to a specific profile ID, that iPassConnect client can ONLY update itself (version of software) when it was installed with the EXE InstallShield package. The update was tied to the installer and when you remove the EXE packaging and repackage it in MSI, the update mechanism can receive prompts to upgrade to the newer version, but it will cyclically fail with repetitive message boxes to the user.

Replacing the ipccheck.exe component with the dummy one jus "tricks" iPassConnect into thinking there is no newer version of software available and it will never prompt for it even though a newer version is pushed to the profile. It must be noted that phone book and configuration (policy) updates are not affected and will occur as normal, but software upgrades will not. A newers version of the software, when available, would need to be pushed out via "major upgrade" package (i.e. repackage the newer version and insert the necessary entries in the upgrade table so it can upgrade the older version when the new one is installed/deployed).

Please make sure you adhere to these notes I've mentioned above or your users will be coming back to you in the future with problems about their directories failing to update and/or they start receiving redundant failing software upgrade prompts.

Basim

Hi Basim,

I've taken a laptop down to my nearest Starbucks to test and everything works as far as I can tell. I'm able to access the internet and the phonebook updates on it's own and also manually AOK.

You've mentioned iPCCheck.exe and that it should be replaced by a dummy file. I assume this can just be an empty text file renamed to ipcheck.exe ? Also, I have two iPCCheck.exe files, one in my install dir and the other in the downloader directory. Are you sugesting that both should be replaced by dummy files?

I also understand that certain files will be updated and for this reason, you have previously mentioned that Resiliency should be turned off. I wouldn't want to do this for the entire msi (or machine), but only for those files that get replaced/deleted.

The .mdb files are updated during a 'Phonebook Update' are not versioned so will not be reverted during a repair. Can you clarify which files are updated and when, bearing in mind that no program updates will take place having a dummy iPCCheck.exe file(s) in place?

ORIGINAL: chris.penney

I've taken a laptop down to my nearest Starbucks to test and everything works as far as I can tell. I'm able to access the internet and the phonebook updates on it's own and also manually AOK.

You've mentioned iPCCheck.exe and that it should be replaced by a dummy file. I assume this can just be an empty text file renamed to ipcheck.exe ? Also, I have two iPCCheck.exe files, one in my install dir and the other in the downloader directory. Are you sugesting that both should be replaced by dummy files?

I also understand that certain files will be updated and for this reason, you have previously mentioned that Resiliency should be turned off. I wouldn't want to do this for the entire msi (or machine), but only for those files that get replaced/deleted.

The .mdb files are updated during a 'Phonebook Update' are not versioned so will not be reverted during a repair. Can you clarify which files are updated and when, bearing in mind that no program updates will take place having a dummy iPCCheck.exe file(s) in place?




Did you perform testing before or after you corrected the missing registry settings? Make sure they are there and that "InstallPath" do not have trailing backslashes.

On the ipccheck.exe dummy, it's not just a blank file that you can create... the file needs to return an exit code of 3. There's an EXE and an accompanying DLL. Do receive thiese files, you need to submit a request to iPass via out ticketing system (or contact your Sales Engineer / Technical Consultant).

As for the files that must not be regressed, there are many of them. My recommendation would be to take a snapshot of a system before a phone book update, then perform a full update by holding down the SHIFT button as you manually update the phone book. Then take a snapshot after and see what's new.

--Basim

Yes, the reg keys are present and don't have trailing backslashes.

I've done as you've sugested and taken a snap of a full phonebook update. I see that there are quite a lot of new files added but none have been removed - this will not cause a msi repair so I don't see the problem?

Chris,

Your iPass Technial Consultant has contact me and I've provided him with the necessary info for you. Please keep in mind that any issues you have with the client that may be due to repackaging may be met with the inability with our support team to assist you.

@gmorgan618: Nice try, but when I install iPass using the response file, the EULA request still pops up. Seems that the actions taken on that dialog are not recorded to setup.iss.

@All: Any idea how to suppress this EULA request? Maybe by adding a line to setup.ini?

Answer: Search befor post! Now I know that my company has to contact iPass first to sign a master EULA agreement.

Here's the link to help others

All,

There is no way to suppress the EULA on your own. It requires megal paperwork (master EULA agreement) to be signed by your company's legal team and then be on file at iPass. Then we have to build the EULA suppression into the customization for your iPassConnect client profile.

Please contact your iPass Account Manager for details.

chris.penney, did you get it to work properly? Could you or anybody else use these tricks to get a fully functional MSI for iPass?!

// Petsson