<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Deployment Problems with SCCM in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-Problems-with-SCCM/m-p/55681#M10885</link>
    <description>&lt;P&gt;I am currently testing deployment of the universal forwarder.  The end goal is to have it on all windows computers so they are ready to pull data from a deployment server when I enable them to (we are taking a phased approach to rollout).&lt;/P&gt;

&lt;P&gt;What I am seeing is if I run the installation manually from a server directly with &lt;/P&gt;

&lt;P&gt;msiexec.exe /q ALLUSERS=2 /m MSIASQSH /i "splunkforwarder-5.0.2-149561-x64-release.msi" DEPLOYMENT_SERVER="Myserver:8089" AGREETOLICENSE=Yes&lt;/P&gt;

&lt;P&gt;everything works fine and the deploymentclient.conf file appears.  If I use those switches with the MSI through an SCCM deployment everything installs but it does not create the deploymentclient.conf file.&lt;/P&gt;

&lt;P&gt;Has anybody else experienced this?  I would prefer not to have to push a bat file containing switches.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jun 2013 13:05:17 GMT</pubDate>
    <dc:creator>LiquidTension</dc:creator>
    <dc:date>2013-06-05T13:05:17Z</dc:date>
    <item>
      <title>Deployment Problems with SCCM</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-Problems-with-SCCM/m-p/55681#M10885</link>
      <description>&lt;P&gt;I am currently testing deployment of the universal forwarder.  The end goal is to have it on all windows computers so they are ready to pull data from a deployment server when I enable them to (we are taking a phased approach to rollout).&lt;/P&gt;

&lt;P&gt;What I am seeing is if I run the installation manually from a server directly with &lt;/P&gt;

&lt;P&gt;msiexec.exe /q ALLUSERS=2 /m MSIASQSH /i "splunkforwarder-5.0.2-149561-x64-release.msi" DEPLOYMENT_SERVER="Myserver:8089" AGREETOLICENSE=Yes&lt;/P&gt;

&lt;P&gt;everything works fine and the deploymentclient.conf file appears.  If I use those switches with the MSI through an SCCM deployment everything installs but it does not create the deploymentclient.conf file.&lt;/P&gt;

&lt;P&gt;Has anybody else experienced this?  I would prefer not to have to push a bat file containing switches.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2013 13:05:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-Problems-with-SCCM/m-p/55681#M10885</guid>
      <dc:creator>LiquidTension</dc:creator>
      <dc:date>2013-06-05T13:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment Problems with SCCM</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Deployment-Problems-with-SCCM/m-p/55682#M10886</link>
      <description>&lt;P&gt;I dug deeper and discovered that the server that was being used for testing already had a universal forwarder on it...Doh!  Package does exactly what it is supposed to in that case.  When pushed to a Windows server that did not already have the Universal forwarder, everything worked.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2013 19:04:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Deployment-Problems-with-SCCM/m-p/55682#M10886</guid>
      <dc:creator>LiquidTension</dc:creator>
      <dc:date>2013-06-12T19:04:48Z</dc:date>
    </item>
  </channel>
</rss>

