MECM Current Branch 2006 batch .cmd or .bat not working if called from package inside tasks sequence

Krelll 1 Reputation point
2020-10-20T07:55:56.1+00:00

Hi,
I've got a couple of packages (not applications) in 10 1909 OSD tasks sequence running .bat or .cmd batch for example running Symantec smc.exe to add or change firewall rules not working in task sequence but running fine if called manually (I copy package content onto the administrator desktop and manually run .bat or .cmd file : it's ok).
Have you by any chance met this issue in MECM deployments ?
I tried to disable UAC without luck.
Thanks for your help,
Krelll

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
930 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jason Sandys 31,186 Reputation points Microsoft Employee
    2020-10-20T13:25:57.21+00:00

    Without knowing anything about these scripts or their results, no one can say anything of value here.

    Have you reviewed smsts.log for these tasks and their results?

    0 comments
  2. Gary Blok 1,736 Reputation points
    2020-10-20T13:55:37.95+00:00

    Can you paste an example of the batch file?
    I'd recommend also testing just pulling one command out of your batch file and running it as a command line step, and checking the results.

    I have command line steps that rely on SMC, but I've only ever used the Run Command Line step, and I've never had issues.

    You might have to also account for different exit codes
    https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/appendices/windows-commands-for-the-endpoint-protection-clien-v9567615-d19e6200.html