What is wrong with this command line in a batch file?

setup.exe /s /f1.\pacs.iss
xcopy "drsys.ini" "c:\drs\sys\data" /y /c /i

I ran this batch file locally and the app installed fine, but when I push it via SCCM, it fails to install and give me a timeout error on clients.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Have you got the Xcopy.exe in the same place you are running the commandline?

Put a 'Pause' at the end of the batch file and see what it is saying
Answered 08/11/2008 by: Thegunner
Second Degree Green Belt

Please log in to comment
Hi darklord,
most likely its the path of the *.iss file.
Let the batch write a log. Use output redirection to do it.
Something like this:
setup.exe /s /f1c:\<yourpathgoeshere>\pacs.iss > yourlog.txt
xcopy "drsys.ini" "c:\drs\sys\data" /y /c /i >> yourlog.txt
Regards, Nick
Answered 08/12/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
Thanks for the tip. When I run the batch file I mention above, this time from the server that contain the package, I get this error message on the command line:

\\sccmServer\pkgsource$\software distribution\PACS'
CMD.exe was started with the above path as the current directory.
UNC paths are nots supported. Defaulting to Windows directory.

How can I change the command lines so that SCCM knows that the .iss file and .ini files are in the current directory? In other words, what is an alternate way to point to the source package on the server without using UNC path? pkgsource is the name of the drive letter 'Z' on sccmServer.
Answered 08/12/2008 by: darklord12
Senior Yellow Belt

Please log in to comment
take a look @ the contents of this .CMD file... the msi & transforms will be pathed from the location of the .CMD file:

%windir%\system32\msiexec /i "%~dp0MyMsiInstall.msi" TRANSFORMS="%~dp0MyTransform.mst" /qb!- /l*v "C:\MyLogDir\MyLog.log
Answered 08/12/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
setup.exe /s /f1c:\\pacs.iss > yourlog.txt

You might want to try that line like this.

setup.exe /s /f1"c:\<yourpathgoeshere>\pacs.iss" /f2"c:\temp\logfile.log"

The quotes " " are needed right after the f1 with no spaces
Same with the f2
f2 will generate your log file.
Answered 08/20/2008 by: Foleymon
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity