Getting Data In

Windows msiexec install is failing...why?

phongshader1
New Member
This is the command run as  a ps1 script pushed out by Airwatch: msiexec.exe /i C:\Windows\Temp\splunk\splunkforwarder-8.0.6-152fb4b2bb96-x64-release.msi RECEIVING_INDEXER="<indexer>" WINEVENTLOG_SEC_ENABLE=1 WINEVENTLOG_SYS_ENABLE=1 MONITOR_PATH=“C:\Program Files\osquery\logs\osqueryd.results.log” MONITOR_PATH=“C:\ProgramData\Airwatch\UnifiedAgent\logs\” AGREETOLICENSE=Yes /quiet. It fails but Airwatch gives no clue as to why.  The script can be run from cmd prompt as admin and it executes as expected. When run from powershell cmd locally or through Airwatch this pops up on the remote endpoint.splunkmsiexec.PNG
Has something changed in the last few days to make this happen? This install has been working for quite a while. Some windows updates?
Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...