Systems Management

You could set it to download and run, rather than running from the DP - I think I've seen that work in the past for a similar problem.

Hope it helps,

Dunnpy

Oops, sorry forgot that in my original post. It is set to download and run locally but the only way I've gotten it to find the setup.iss file is to hardcode the path back to the DP.

Try to add: /f2”c:\temp\my-log-file.iss”
The installer will try to create a log file on your SCCM share, and it don't have permission to do that.

The log file is getting created locally so that's not the problem.

i use a command file in sccm. the command file contains the following: setup.exe /s -f1"setup.iss" -f2"%SYSTEMROOT%\TEMP\setup.log"

start the command file with the following
echo off
cls

pushd %0\..\

bitofcopy, you mean you created a program (under Software Distribution->Packages) that points to a command file with the install commands in it or you did it as part of a task sequence?

I originally ran into the problem last summer but at the time the error message I was getting was something along the lines of the package not matching what was on the distro point so I just had it installing via a task sequence command line pointing right at the dp. I also used the same command line in a TS that installs multiple programs but it's not an ideal solution as there's no easy way of verifying that it was installed correctly. I discovered last week that the problem was because there was a hidden file in my original install (http://iboyd.net/index.php/2009/01/11/sccm-content-downloaded-to-the-client-does-not-match-the-content-specified-in-the-content-source/) which is why I'm now revisiting this.

I have a package for the application created under Software Distribution->Packages yes then i create a program (ex. Run) and point the command line to the command file i created in the source files location. distribute the package to the distribution points. I did not realize you are using Task Sequence. It looks like the programs i have used for Task Sequence the command line file called is a *.bat not *.cmd The source file still resides in the source location of the package file source. I have multiple secondary servers with dp's. I distribute my packages via SCCM to the dp's.

I was doing it in a TS last summer because of my initial error (hidden file). I think I tried what you've done and it didn't work at the time but now that I've got the hidden file causing the content to not match fixed I'll give it another go.

Thanks.

You shouldn't have to specify f1 if the the file is in the same directory as setup.exe and it's called setup.iss

If it doesn't meet the above I was able to get this working using the below command from and SCCM program.

setup.exe /s /sms /f1.\setup.iss

So that it works from any distribution point, the %~dp0 is the way to go.

However, this does not work from the SCCM Program command line. You will have to create a .cmd file to run your command - setup.exe /s /sms /f1%~dp0setup.iss - and call the .cmd file from the SCCM program.

Oops. Forgot to reply back here with what finally worked for me. I ended up with a .cmd file that contained the following.... setup.exe -s -sms -f2c:\setup.log. If I tried to use /f1 it would complain about not being able to find the file and .iss files are automatically called from the parent directory if you use -s anyways.

Thanks for the help everyone.

If you are still looking for a solution without batch file I use this with an iss file renamed to setup.iss. The -f1 isn't needed as it will look automatically for a setup.iss:

setup -s -SMS -f2C:\Windows\Temp\file.log

Hi All, 

Anyone solve this issue? I am using .cmd file with sccm and it is keep failing with error code on -3. If i run same package from ccmcache it works fine only issue is happening while deploying from sccm. I am using setup.exe /s /a /SMS /z /f1"%~dp0setup.iss" /f2"%~dp0install.log"