Disable, remove or modify a Launch conditions of an msi package
Hi
I have
extracted the 'Toshiba UnifiedPOS for Windows.msi' from the InstallShield
'Setup.exe' and created a mst with all the settings required for our setup. But
the msi package have a launch condition which requires a 'UposSetup.iss' file
to be present on the 'Windows volume/WinRoot' when running in silent mode. The
'UposSetup.iss' is created both by the msi package and the setup.exe, based on
the choices made in the setup dialogs. If I delete this launch condition in the
mst file, is the msi installer able to complete successfully when running in
silent mode under my admin credentials. But when I deploy this msi package with
sccm and the msi installer running in silent mode under the system account, the
launch condition still comes into effect.
My question is therefore: Can I force or permanently disable, remove or modify this launch condition in the mst file, so it also carries through and does not come into effect when the installations runs with system account credentials? Or can I modify the mst file, so it looks for the 'UposSetup.iss' file in the file path where the msi package is located, which varies from client to client when deployed with sccm?
Error:
Installation log file
=== Logging started: 07-05-2019 17:49:17 ===
Action start 17:49:17: INSTALL.
Action start 17:49:17: NetHoodFolder.D49A5578_D28E_4C88_9DAE_3249953B70DA.
Action ended 17:49:17: NetHoodFolder.D49A5578_D28E_4C88_9DAE_3249953B70DA. Return value 1.
Action start 17:49:17: PrintHoodFolder.D49A5578_D28E_4C88_9DAE_3249953B70DA.
Action ended 17:49:17: PrintHoodFolder.D49A5578_D28E_4C88_9DAE_3249953B70DA. Return value 1.
Action start 17:49:17: RecentFolder.D49A5578_D28E_4C88_9DAE_3249953B70DA.
Action ended 17:49:17: RecentFolder.D49A5578_D28E_4C88_9DAE_3249953B70DA. Return value 1.
Action start 17:49:17: WindowsFolder_x86_VC.AFA96EB4_FA9F_335C_A7CB_36079407553D.
Action ended 17:49:17: WindowsFolder_x86_VC.AFA96EB4_FA9F_335C_A7CB_36079407553D. Return value 1.
Action start 17:49:17: SystemFolder_x86_VC.AFA96EB4_FA9F_335C_A7CB_36079407553D.
Action ended 17:49:17: SystemFolder_x86_VC.AFA96EB4_FA9F_335C_A7CB_36079407553D. Return value 1.
Action start 17:49:17: WindowsFolder_amd64_VC.BFF61907_AA2D_3A26_8666_98D956A62ABC.
Action ended 17:49:17: WindowsFolder_amd64_VC.BFF61907_AA2D_3A26_8666_98D956A62ABC. Return value 1.
Action start 17:49:17: System64Folder_amd64_VC.BFF61907_AA2D_3A26_8666_98D956A62ABC.
Action ended 17:49:17: System64Folder_amd64_VC.BFF61907_AA2D_3A26_8666_98D956A62ABC. Return value 1.
Action start 17:49:17: OSInfo.
Action ended 17:49:17: OSInfo. Return value 0.
Action start 17:49:17: SetUSEINI.
Action ended 17:49:17: SetUSEINI. Return value 1.
Action start 17:49:17: issValidation.
ISS FILE VALIDATION
TRACE, CLIENTLEVEL:3 LEVEL: 1 LEVEL3: 2
ERROR: Aborting installation. ISS file is not found
Action ended 17:49:17: issValidation. Return value 3.
Action ended 17:49:17: INSTALL. Return value 3.
=== Logging stopped: 07-05-2019 17:49:17 ===
Answers (3)
Would try full logging /L*vx and make sure the transform is applied when running.
I’m struggling with the same kind of problem, though using Setup.exe. It seems like the responsefile must exist in root of system drive and be named is UposSetup.iss (C:\UposSetup.iss) I didn’t get even the “optional location” -switch working.. Really weird. Deployment is not tested yet, but I’ll test and let you know.
With the .msi, which I grabbed of the package, worked like a charm, with existing responsefile. Like said, it must be as this: C.\UposSetup.iss
Deployment tested with Task Sequence, with the following matra:
cmd /c xcopy /y UposSetup.iss %SystemDrive%\ && cmd /c msiexec /i "Toshiba UnifiedPOS for Windows.msi" /l+! "%windir%\Debug\UnifiedPOS_For_Windows_1_14_4_10168.log" REBOOT=R /qb && cmd /c del %SystemDrive%\UposSetup.iss /s /q
From the log:
Action start 13.38.36: OSInfo.
Action ended 13.38.36: OSInfo. Return value 0.
Action start 13.38.36: SetUSEINI.
Action ended 13.38.36: SetUSEINI. Return value 1.
Action start 13.38.36: issValidation.
ISS FILE VALIDATION
TRACE, CLIENTLEVEL:3 LEVEL: 1 LEVEL3: 2
ISS FILE EXIST
VERSION IS VALID
Action ended 13.38.36: issValidation. Return value 1.
Action start 13.38.36: SMBIOSDetect.
Action ended 13.38.36: SMBIOSDetect. Return value 1.
Action start 13.38.36: ISSetAllUsers.
InstallShield 13.38.36: Begin SetAllUsers()
InstallShield 13.38.36: Getting records from Upgrade table
InstallShield 13.38.36: UpgradeCode: {ED84BFD4-1844-4DAB-8B97-5E3D1DCCB2C8} MinVersion: 1.14.3 MaxVersion: Language: Attributes: 2
InstallShield 13.38.36: No related products for UpgradeCode {ED84BFD4-1844-4DAB-8B97-5E3D1DCCB2C8} found
InstallShield 13.38.36: UpgradeCode: {ED84BFD4-1844-4DAB-8B97-5E3D1DCCB2C8} MinVersion: 1.9.0 MaxVersion: 1.14.3 Language: Attributes: 768
InstallShield 13.38.36: No related products for UpgradeCode {ED84BFD4-1844-4DAB-8B97-5E3D1DCCB2C8} found
InstallShield 13.38.36: End SetAllUsers()
Action ended 13.38.36: ISSetAllUsers. Return value 1.
Action start 13.38.36: AppSearch.
Action ended 13.38.36: AppSearch. Return value 1.
Action start 13.38.36: SetUSEINI.D49A5578_D28E_4C88_9DAE_3249953B70DA.
Action ended 13.38.36: SetUSEINI.D49A5578_D28E_4C88_9DAE_3249953B70DA. Return value 1.
Action start 13.38.36: VerifyIniFile.D49A5578_D28E_4C88_9DAE_3249953B70DA.
1: 16.6.2019 13.38.36 IniUtils/VerifyIniFile: Verifying file 'C:\UposSetup.iss'.
1: 16.6.2019 13.38.36 IniUtils/VerifyIniFile: .ini file is valid.
Action ended 13.38.36: VerifyIniFile.D49A5578_D28E_4C88_9DAE_3249953B70DA. Return value 1.
Action start 13.38.36: SetSMBIOSx64.
Hope this helps You!