I'm trying to use SCCM 2012SP1 to install the software package to support a new device we've purchased.  I believe this is an installshield package.  The readme for the installer suggests using the "/r /f1<filepath>" parameters to record a response file and then installing with the "/s /f1<filepath>" parameters for a silent install. 

Following those steps, I have been able to manually perform a silent install of the package.  When I build the application in SCCM using the same command line syntax and setup.iss file and deploy it to a client, the install fails with a return code of -3. 

That return code appears to indicate that there is required information missing from my setup.iss file.  Here's what the .iss file looks like:


 [{85DCB570-3344-4820-8700-012BEDB0653D}-DlgOrder] Dlg0={85DCB570-3344-4820-8700-012BEDB0653D}-SdWelcome-0 Count=6 Dlg1={85DCB570-3344-4820-8700-012BEDB0653D}-SdCustomerInfo-0 Dlg2={85DCB570-3344-4820-8700-012BEDB0653D}-SdAskDestPath-0 Dlg3={85DCB570-3344-4820-8700-012BEDB0653D}-SdComponentMult-0 Dlg4={85DCB570-3344-4820-8700-012BEDB0653D}-SdStartCopy2-0 Dlg5={85DCB570-3344-4820-8700-012BEDB0653D}-SdFinish-0 [{85DCB570-3344-4820-8700-012BEDB0653D}-SdWelcome-0] Result=1 [{85DCB570-3344-4820-8700-012BEDB0653D}-SdCustomerInfo-0] szName=NAME szCompany=COMPANY nvUser=1 Result=1 [{85DCB570-3344-4820-8700-012BEDB0653D}-SdAskDestPath-0] szDir=C:\Program Files (x86)\ePadLink\ePad\ Result=1 [{85DCB570-3344-4820-8700-012BEDB0653D}-SdComponentMult-0] Citrix-type=string Citrix-count=5 Citrix-0=Citrix\Citrix_ePadUSB Citrix-1=Citrix\Citrix_ePadInk Citrix-2=Citrix\Citrix_ePadII Citrix-3=Citrix\Citrix_ePadLS Citrix-4=Citrix\Citrix_ePadVision TerminalServices-type=string TerminalServices-count=5 TerminalServices-0=TerminalServices\TS_ePadUSB TerminalServices-1=TerminalServices\TS_ePadInk TerminalServices-2=TerminalServices\TS_ePadII TerminalServices-3=TerminalServices\TS_ePadLS TerminalServices-4=TerminalServices\TS_ePadVision Component-type=string Component-count=2 Component-0=Citrix Component-1=TerminalServices Result=1 [{85DCB570-3344-4820-8700-012BEDB0653D}-SdStartCopy2-0] Result=1 [{85DCB570-3344-4820-8700-012BEDB0653D}-SdFinish-0] Result=1 bOpt1=0 bOpt2=0

I'm not sure if there's actually something wrong with that response file or if the problem might be elsewhere.  I'm guessing that the issue is related to the context that the installer is running under, since I can manually execute the same command successfully, but I'm not sure how I can account for that difference.  

Has anyone else run into this issue?  Any suggestions on what I can do to get this installing properly via system center?

Answer Summary:
1 Comment   [ - ] Hide Comment


  • I am having similar problems, setup64.exe" -s -SMS -b%SYSTEMROOT%\TEMP\ -f2%SYSTEMROOT%\TEMP\ENVI51.log returns error code 255. Also noticed for a 64bit app the installer is 32bit, had to kill the operating system requirements. the software is excelis ENVI
Please log in to comment

Community Chosen Answer



Ahh, thanks for the reply!  I had to wait for my post to be approved, and in the meantime I found a solution for my issue.  Unfortunately, after a couple of days, the post was still pending, so I couldn't update it with the solution.  

First off, using the /sms parameter was also necessary, but that alone didn't fix the issue I described in the OP.  It seems that the setup.exe file was extracting it's contents to a temporary directory under the user's profile.  When running it manually, that works fine, but when system center was running the same command line, it ran into trouble with either extracting the file or being able to read the files after it was done.

I had to add another parameter "/b<tempdir>", where <tempdir> is a local path that setup will be able to write to and read from.  After adding this additional path, the install worked perfectly.


Answered 10/31/2013 by: aurock
Senior White Belt

  • superb..thanks for sharing this information.
Please log in to comment
Answer this question or Comment on this question for clarity



try -sms in command line after /s, it worked in my case.

Answered 10/30/2013 by: neelvij
White Belt

Please log in to comment