Using that syntax, the application installed successfully from ConfigMgr. "setup.exe" /s /f1setup.iss /bc:\swsetup\ /v/qn The final command line used for the application in SCCM looked like this: I was able to work around this by adding a "/b" parameter, in which is the directory where I want the setup files extracted to. If I run it manually, those files are placed in c:\users\appdata\local\temp\ - but it can't use the same path when running in the system context. When the InstallShield package executes, the first thing it does is extract files into a temporary location. Configmgr was running the package as system, not as a user. Since the command works fine when I run it manually, I decided it had to be a problem of the different context in which configmgr was running the installer. When I tried deploying this as an application from system center, using the same command line and the same response file, the installation failed with a return code of "-3". As long as I was manually running the command in step3 from an administrative command prompt. In theory, this should silently run the installer, using the same responses provided when creating the response file in step 1. On the target computer, run "setup.exe /s /f1setup.iss /v/qn" Example: "setup.exe /r /f1c:\temp\setup.iss"Ĭopy the setup.exe and setup.iss files to the computer where the software needs to be installed.
Run the installer with additional parameters to record the install and create a response file. The instructions from the readme file for unattended installs matched the typical method for InstallShield packages: I recently ran into an issue installing the driver package for some new Interlink "Epad" signature pads we got in at work. If you have the response file ready to go, you might also want to try this suggestionĭeploying Installshield package via SCCM fails, Return Code -3
Just out of curiosity, did you follow the instructions on how to create a silent install from their website?
0 kommentar(er)
