Install old setup with .iss in task sequence sccm
Hello,
I have a problem for install a package in task sequence sccm.
My package running correctly with system account (Psexec -s, sccm deployment) and admin account.
But in my task séquence, i have exit code -3 in package log, and exit code 2147753984 in appenforce.log.
have you a solution for this problème?
Thx
Answers (2)
Whats the command line your using? I know InstallShield response files need to reference the full path.
They are a problem to implement in SCCM sometimes too.
You should be able to setup your application in SCCM with similar to the following commandline:
Setup.exe /s /f1"%~dp0setup.iss" /f2"c:\windows\logs\TextMap 6.00.126.01 Install.log"
The %~dp0 (that’s a zero) variable - when referenced within a Windows batch file or SCCM commandline - will expand to the drive letter and path of that batch file.
Comments:
-
Thx, I execute my command line in vbs :
"setup.exe -s -f1" & chr(34) & GetCurrentPath() & "\Bin\" & LCase(Action) & ".iss" & chr(34) & _
" -f2" & chr(34) & GetEnvironmentString("%Windir%") & "\Temp\" & Action & "-" & AppStamp & ".log" & chr(34) - AGRILLON 5 years ago-
I Test installation by command line Setup.exe /s /f1"%~dp0setup.iss" /f2"c:\windows\logs\TextMap 6.00.126.01 Install.log" in sccm deployment, but it's not good. exit code -3 - AGRILLON 5 years ago
