/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Install old setup with .iss in task sequence sccm

02/13/2019 1026 views

  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

0 Comments   [ + ] Show comments

Comments


All Answers

0

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.

Answered 02/13/2019 by: rileyz
Red Belt

0

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.

Answered 02/13/2019 by: vjaneczko
9th Degree Black Belt

  • 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)
    • 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
    • This content is currently hidden from public view.
      Reason: Removed by member request For more information, visit our FAQ's.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ