I am running into an issue when deploying Novell SecureLogin 7 via SCCM. The package is a .msi from the vendor and when I attempt to install it from Run Advertised Programs it fails because it thinks it is doing an upgrade. The target PC has no instances of this program on it. When I run the same .msi locally and manually on the PC using the same command line switches and parms, it installs without issue. I get the following information around line 310 when I dump the install to a log:

From the SCCM install attempt:

MSI (s) (6C:A8) [16:24:14:454]: Doing action: ISSetAllUsers
Action ended 16:24:14: ISSetupFilesExtract. Return value 1.
MSI (s) (6C:9C) [16:24:14:485]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI470E.tmp, Entrypoint: SetAllUsers
Action start 16:24:14: ISSetAllUsers.
1: InstallShield - ISSetAllUsers (Begin)
1: Opening Database
1: {14C6BA65-F67A-45EF-A1FD-882CF1A4735B} 6.1.000 7.0.100 769
MSI (s) (6C!AC) [16:24:14:516]: PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. Its value is 'Yes'.
1: Novell SecureLogin {AE66C378-3E3B-40D7-8C11-5DB146EE2F72} 0 \ ***Related***
1: ALLUSERS=1
1: Closing Database
1: InstallShield - ISSetAllUsers (End)
MSI (s) (6C:A8) [16:24:14:516]: Doing action: AppSearch
Action ended 16:24:14: ISSetAllUsers. Return value 1.

From the local/manual install:

MSI (s) (A4:A8) [16:43:33:814]: Doing action: ISSetAllUsers
Action ended 16:43:33: ISSetupFilesExtract. Return value 1.
MSI (s) (A4:18) [16:43:33:845]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB128.tmp, Entrypoint: SetAllUsers
Action start 16:43:33: ISSetAllUsers.
1: InstallShield - ISSetAllUsers (Begin)
1: Opening Database
1: {14C6BA65-F67A-45EF-A1FD-882CF1A4735B} 6.1.000 7.0.100 769
1: Closing Database
1: InstallShield - ISSetAllUsers (End)
MSI (s) (A4:A8) [16:43:33:845]: Doing action: AppSearch
Action ended 16:43:33: ISSetAllUsers. Return value 1.

Here is the command line I execute from both SCCM and locally:

msiexec /i "NovellSecureLogin.msi" /qn X_INSTALLTYPE="MAD" X_USEGPO="Yes"

I tried using the 'ISUPGRADE="No"' parm with this and it just sets it back to "Yes" while executing

Unfortunately I'm a noob at packaging - please help me determine how to prevent the install via SCCM from trying to perform an upgrade.

Thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

Answer this question or Comment on this question for clarity