Answered

We are trying to deploy Bizagi PM 2.6 using a batch script via SCCM on several W7 32-bit machines.

We have created an ISS response file to deploy

"%_MSIFiles%\BizAgiProcessModeler\BizAgiPMSetup.exe" /s /f1"%_MSIFiles%\BizAgiProcessModeler\BizAgiPMSetup.iss"

But on 20 to 25 % of the machines the install fails with returncode 255 or 267.

When we log on to the machine and deploy the exe manually we have no problems.

For the moment the script will check if there is a retruncode 255 or 267 and in that case the script will copy all files manually in program files and create a shortcut.

Any ideas why the scripts fails with returncode 255 or 267 ?

Best Answer
photo

Dear Stef

We have two options, please check any of those:

Option 1:

You may choose to run the following for a silent installation:1. Install the software normally in recording mode and save the user inputs in a file:

  • BizAgiPMSetup.exe /r /f1"D:\BizAgiPMSetup.iss"
  • /r : Recording mode
  • /f1 : path where the file with the installation configuration will be saved. It must be an absolute path.

2. Execute the following command:

  • BizAgiPMSetup.exe /S /f1"D:\BizAgiPMSetup.iss"
  • /S : silent mode
  • /f1 : path of the configuration file.

Now, to perform a silent uninstall you can choose to:1. Uninstall the software normally in recording mode and save the user inputs in a file:

  • BizAgiPMSetup.exe /uninst /r /f1"D:\BizAgiPMSetupUnInstall.iss"
  • /uninst : uninstall mode
  • /r : recording mode
  • /f1 : path of the configuration file.

2. Execute the following command:

  • BizAgiPMSetup.exe /S /uninst /f1"D:\BizAgiPMSetupUnInstall.iss"
  • /uninst : uninstall mode
  • /S : Silent mode
  • /f1 : path of the configuration file

Related topics information:Setup.exe and Update.exe Command-Line Parameters:http://helpnet.acresso.com/robo/projects/HelpLibDevStudio9/IHelpSetup_EXECmdLine.htm Traditional Silent Mode for InstallScript MSI Installations (Setup.iss):http://documentation.installshield.com/robo/projects/helplibdevstudio9/SetupIss.htm

Option 2:

First create an administrative Installation.Example:BizAgiPMSetup-x64.exe /v"/a for x64

Now run the MSI createt in the administrative installallation path with the parameter ISSETUPDRIVEN=1to avoid the "Run Setup.exe Popup"

Example:

MsiExec.exe /i "Bizagi Process Modeler.msi" ISSETUPDRIVEN=1 /qbThats all, it´s working great with SCCM.Regards

photo
0

Dear Stef

We have two options, please check any of those:

Option 1:

You may choose to run the following for a silent installation:1. Install the software normally in recording mode and save the user inputs in a file:

  • BizAgiPMSetup.exe /r /f1"D:\BizAgiPMSetup.iss"
  • /r : Recording mode
  • /f1 : path where the file with the installation configuration will be saved. It must be an absolute path.

2. Execute the following command:

  • BizAgiPMSetup.exe /S /f1"D:\BizAgiPMSetup.iss"
  • /S : silent mode
  • /f1 : path of the configuration file.

Now, to perform a silent uninstall you can choose to:1. Uninstall the software normally in recording mode and save the user inputs in a file:

  • BizAgiPMSetup.exe /uninst /r /f1"D:\BizAgiPMSetupUnInstall.iss"
  • /uninst : uninstall mode
  • /r : recording mode
  • /f1 : path of the configuration file.

2. Execute the following command:

  • BizAgiPMSetup.exe /S /uninst /f1"D:\BizAgiPMSetupUnInstall.iss"
  • /uninst : uninstall mode
  • /S : Silent mode
  • /f1 : path of the configuration file

Related topics information:Setup.exe and Update.exe Command-Line Parameters:http://helpnet.acresso.com/robo/projects/HelpLibDevStudio9/IHelpSetup_EXECmdLine.htm Traditional Silent Mode for InstallScript MSI Installations (Setup.iss):http://documentation.installshield.com/robo/projects/helplibdevstudio9/SetupIss.htm

Option 2:

First create an administrative Installation.Example:BizAgiPMSetup-x64.exe /v"/a for x64

Now run the MSI createt in the administrative installallation path with the parameter ISSETUPDRIVEN=1to avoid the "Run Setup.exe Popup"

Example:

MsiExec.exe /i "Bizagi Process Modeler.msi" ISSETUPDRIVEN=1 /qbThats all, it´s working great with SCCM.Regards

photo
0

Thanks Juan,

option 1 did not work properly. Failure on 20 % of the machines.

I tried option 2 and it seems to work. We are piloting on several machines. Thanks for your help.

Kind regards,

Stef