<div>
Assuming that the batch works when you execute it manually, the issue is probably the path to the config file, which seems to be a UNC.<br />
The SCCM client runs as Local System, so the <b>AD computer account</b> needs permission for the share. You can use the group &quot;Domain Computers&quot; to grant read permissions.
</div>


Assuming that the batch works when you execute it manually, the issue is probably the path to the config file, which seems to be a UNC.
The SCCM client runs as Local System, so the AD computer account needs permission for the share. You can use the group "Domain Computers" to grant read permissions.

<div>
<div class="content wysiwyg-content">
I have a working batch file/config xml to do a silent uninstall of the Lync client (hopefully all existing 2013 and 2010), but when I create an deploy it as a package in SCCM it fails. <br />
<br />
batch:<br />

<pre><code id="code-10-28675983-1">echo off
taskkill.exe /F /IM iexplore.exe /T
taskkill.exe /F /IM outlook.exe /T
taskkill.exe /F /IM lync.exe /T

&quot;C:\Program Files\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\setup.exe&quot; /UNINSTALL LyncEntry /config  \\path\to\xml_file\SilentLyncUninstall.xml</code></pre>
<br />
XML:<br />

<pre><code id="code-10-28675983-2">&lt;Configuration Product=&quot;LyncBasic&quot;&gt;
&lt;Display Level=&quot;none&quot; CompletionNotice=&quot;no&quot; SuppressModal=&quot;yes&quot; AcceptEula=&quot;yes&quot; /&gt;
&lt;Setting Id=&quot;SETUP_REBOOT&quot; Value=&quot;Never&quot; /&gt;
&lt;/Configuration&gt;</code></pre>
<br />
Has anyone out there dealt with doing this?
</div>
</div>


I have a working batch file/config xml to do a silent uninstall of the Lync client (hopefully all existing 2013 and 2010), but when I create an deploy it as a package in SCCM it fails. 

batch:
(CODE)

XML:
(CODE)

Has anyone out there dealt with doing this?

Creating applications in SCCM using a batch file

Batch files are text files containing a script of commands that are executed by the command interpreter on DOS, OS/2 and Windows systems. Most commonly, they are used to perform a series of functions that are repeated -- copying a set of files created daily with one step, for example.