Command Line error
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.
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
Answers (5)
Please log in to answer
Posted by:
Thegunner
15 years ago
Posted by:
nheim
15 years ago
Posted by:
darklord12
15 years ago
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.
\\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.
Posted by:
kiptek
15 years ago
Posted by:
Foleymon
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.