Install and distribute application with setup.iss file

[AmrelMahdy]

Hi,

 

Im currently working on SCCM 2012 on Windows server 2008. Im facing issue when creating a program for a application package.

THe commandline install for the app is setup.exe /s /f1"<full absolute path to setup.iss file". PLease note Full path to iss file needs to be given here and will not work with any relative path.

the setup.exe , source files and setup.iss file are in the same source location

How do i give the commandline when i create a new program for this package in SCCM. I cannot give the UNC path or local path

[Peter33]

You could use a script wrapper.

Here is how you can do it in powershell.

 

 

$Path = Split-Path $script:MyInvocation.MyCommand.Path

Set-Location $Path

$ExitCode = 0

$myargs = "/s /f1""" + $Path + "\Setup.iss"""

$ExitCode = (Start-Process -FilePath "Setup.exe" -ArgumentList $myargs -Wait -Passthru -NoNewWindow -ErrorAction SilentlyContinue).ExitCode

[Environment]::Exit($ExitCode)

[Rocket Man]

setup.exe /s /f1"<full absolute path to setup.iss file".

 

 

the setup.exe , source files and setup.iss file are in the same source location

 

have yo tried simply just using setup.exe -s as the command line........considering all files are in the one package...then the setup.exe -s command will use the setup.iss by default without having to use any further parameters such as -f1C:\ etc........

[AmrelMahdy]

Yeah I tried so but it Didn't work

[Rocket Man]

Have you tried copying both the .iss file and executable to the root of the c drive through a batch file as part of a task sequence and then run a command line also as part of the same task sequence that will execute the executable in the c drive along with the parameters to run the iss file....this will work...you could also have 3rd part to this task sequence that will remove the files from the local pc once the other 2 parts have finished.

 

Rocket Man