Variable for Splunk install directory in deployed scripts

[rtadams89]

I need to run a vbs script on some of my Windows Forwarders. To do so, I have deployed a batch script that calls the vbs script with the following code:

@echo off
cscript //nologo "C:\Program Files\SplunkUniversalForwarder\etc\apps\my-test-app\bin\script.vbs"

The problem is that the Splunk Universal Forwarder may be running from a location other than c:\program files.

Is there any way to get the directory Splunk is running from within the bat wrapper script and use that to provide the correct path to the vbs script file?

PS: I am aware of the environmental variables for "Program Files", but I would like to cover the cases where Splunk is installed to an arbitrary directory, perhaps not even in the Program Files folder.

[rtadams89 · Accepted solution]

Figured it out. I ended up using the variable "%~dp0" inside the patch script. This will return the path to the directory the batch script is located in. By appending the name of my vbs file to that, I end up with the full path to the vbs file.

[rtadams89]

Because inputs.conf supports the $SPLUNK_HOME variable.

[linu1988]

Then how are you going to configure the scripts in inputs.conf? If you are just looking for the directory, a simple vb script to check on the splunk registry to get the installed path.

[rtadams89]

I don't know where Splunk is installed on each host.

[linu1988]

Why not declare a environment variable as you know where the splunk forwarder installed. and replace them until \etc. Any reason why it can't happen?