Hi,
I'm trying to deploy Lotus Notes Client 8.0.2 silently (eventually will be pushed via SMS.) I am running into an issue where the installer is trying to access the web to update or check for Java SE. The firewall software is blocking the access by default. I tested this install in a disconnected state and it installed OK after cliking "keep blocking" on the firewall prompt, so I guess it really does not need this update and is just checking for a newer version. I examined the MSI for any obvious properties that can be set and nothing stick out. Does anyone know how to supress the installer from trying to access the web? I am running the setup.exe with the following switches: /S /V/qn

Thanks much
.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The fact that the installer takes those switches strongly suggests that is ultimately MSI-based. The Package KB entries concur. http://itninja.com/link/help---ibm-lotus-domino-and-notes-information-center

Thus, I'd run the installer as far as the first screen then search your %TEMP% folder for an MSI. Copy that MSI somewhere and rename it using an obvious name. You can then examine the MSI in your authoring tool of choice. Once you have located the Custom Action which is running the updater, you can create a transform for the MSI in which you disable its execution. I normally do that by applying an impossible-to-meet condition, e.g. 0=1.

The 'Related links' section of the KB points to an IBM document. Maybe there's some further info there?
Answered 05/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Yes this is MSI based. I have already examined the MSI. All the custom actions either set a property or are DLL based. Nothing in the MSI that I can see refers to the Java SE web connection. The process must be being launched from one of the DLL based custom actions. I work as a contactor for IBM, and even I cannot get the Lotus team to answer this question. I was just hoping someone on this board might of run into this issue.
Answered 05/28/2009 by: MrMibs
Senior Yellow Belt

Please log in to comment
0
I would run the install with verbose logging and grab it at the point where the MSI goes to perform the update and fails. Keep the "Update failed" dialog on the screen, which will temporarily halt the MSI's execution. The dozen or so lines above the last entry should tell you which CA is responsible. BTW, don't use NotePad to view the log. It can't open MSI logs while they're in use.
Answered 05/28/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity