Getting Data In

CLI: Linux vs. Windows

NK_1
Path Finder

Using the CLI, if I do

splunk search hoursago=1

I see output under a Linux Splunk installation, but not under a Windows Splunk installation.

Where does the output from the Windows installation go?

Tags (4)
1 Solution

gekoner
Communicator

I assume you are running Splunk 4.2.2 or higher and this is on a Windows 2008 server. You will need to run the command prompt with elevated privileges (Run as administrator). Then it should echo out to the same command screen.
If you don't it opens a new window, and if the results return quickly you might not even see the new command window popup.

View solution in original post

gekoner
Communicator

I assume you are running Splunk 4.2.2 or higher and this is on a Windows 2008 server. You will need to run the command prompt with elevated privileges (Run as administrator). Then it should echo out to the same command screen.
If you don't it opens a new window, and if the results return quickly you might not even see the new command window popup.

echalex
Builder

Thank you for the answer, gekoner. I hade the same kind of problem under Windows 7. Any splunk command, such as splunk status would only quickly flicker another terminal window. Opening cmd with "run as administrator" solved this issue.

0 Karma

NK_1
Path Finder

splunk search "daysago=1 AccountName" > c:\accounts.log

Tried this on Splunk 4.2.3 under Windows 7 Enterprise, and that was it (i.e. need to run the command shell as Admin). Thanks!

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...