Software Deployment Question

Using SCCM how do you package and deploy a batch file?

02/13/2018 10129 views
Currently I'm trying to deploy a .xml file from a server to a folder on the C drive on users pc. I was using a match file to call the .xml and copy/paste it to the c drive. I'm able to manually run the batch file and it copies and paste to the location on the C drive but using sccm it is stuck in progress. Message ID is 10072 and description is 4.
1 Comment   [ + ] Show comment


  • Hi Dunnpy,

    So should i always run the package from the DP and not download and run locally?

Community Chosen Answer

The message is a retrying message, likely due to the failure to run the batch file.

I suspect that as you're running this from a server that isn't an SCCM DP share that it's falling foul of access permissions - unless you're copying from a null session share.

Add the file and script into a package so that it's available on the DP and it should run correctly. The alternative is to provide the SCCM service account access to the share that the file is being copied from and it should work.

Hope that helps,

Answered 02/14/2018 by: dunnpy
Red Belt

All Answers

I would create a package with .bat and .xml and use xcopy etc to put it in the right folders.

Using a share would need to change permissions on share. Keeping xml in package is simpler.

This is from one of my packages.

md "c:\program files\sigma6"

copy sigma6.exe "c:\program files\sigma6"

copy sigma6.lnk C:\Users\Public\Desktop

Answered 02/15/2018 by: nagendrasingh
Black Belt

I would create a package
No-one else would. They'd create an application.
Answered 02/16/2018 by: anonymous_9363
Red Belt

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