Deployment Problems with SCCM

[LiquidTension]

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).

What I am seeing is if I run the installation manually from a server directly with

msiexec.exe /q ALLUSERS=2 /m MSIASQSH /i "splunkforwarder-5.0.2-149561-x64-release.msi" DEPLOYMENT_SERVER="Myserver:8089" AGREETOLICENSE=Yes

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.

Has anybody else experienced this? I would prefer not to have to push a bat file containing switches.

[LiquidTension · Accepted solution]

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.