Es.exe - Client Service

[Lyssa]

Hi All,

First time posting, but I have been using these boards as a great guide/knowledge base to everything search. I am a system admin for a company that currently uses SAN only snapshots and I am creating a way to index file changes so we know what is on each of our snapshots. So far the process has been easy enough, but I have run into an issue with everything that I am not sure can be dealt with in the current version.

I have everything running on our file server monitoring one drive (for now, it will ultimately monitor all of them). I created a powershell script that will use es.exe to export a snapshot of the recent changes every 5 minutes. This snapshot is dumped into a database for later use. The problem I am running into is that es.exe will not talk to the everything client service, making it impossible to run this whole process as a service. For now I am just using a service user account and having it automatically login when the file server starts, load up everything, and run my powershell script. This of course feels very janky and I would love to clean this up to act like a proper service.

Is this something that can/will be added in the next 3-6 months?

Thanks,
Melissa

[therube]

Are you using a named instance of the service?
(ES: Does Not Work in Sandboxie.)

[Lyssa]

Hi therube,

I have not used any named instances, will they work? Not really following your link as to how it relates to my issue (ES talking to the client-service).

Thanks,
Melissa

[void]

Are you using the Everything client service for an ETP server?

I'll look into adding ETP support to ES.

[Lyssa]

Hi void, thanks for popping by.

Ideally I would like to have everything running as a client service and have es run against that client service to create the export-csv change "snapshots". This works great with a logged in user, but I would like to move away from having a logged in user as that is far from best practice in a corporate environment.

Thanks,
Melissa

[void]

Please try enabling "Allow service to interact with desktop" for the Everything client service and running es as LOCAL SYSTEM in session 0:

• Open Services (Start -> Run -> Services.msc)
• Right click Everything Client and click Properties.
• Click the Log On tab.
• Check Allow service to interact with desktop.
• Click OK.
• Download PsExec.exe from SysInternals.
• Run the following command:
  psexec.exe -i 0 -s es.exe rc: -export-csv c:\pstest\out.csv

Running an application as LOCAL SYSTEM:
https://stackoverflow.com/questions/691 ... rk-service

Running an application in session 0 (the session for services):
https://serverfault.com/questions/35754 ... ith-psexec

[Lyssa]

Hi void,

I tried all the steps you mentioned, but I am still getting an error with es (produces error code 8 - Unable to find session). Is it possible to run the client-service as a named instance, or would that help at all.

Thanks,
Melissa

[void]

Please try restarting the Everything client service:

• Open Services (Start -> Run -> Services.msc)
• Right click Everything Client and click Properties.
• Click the Log On tab.
• Check Allow service to interact with desktop.
• Click OK.
• Right click Everything Client and click Stop.
• Right click Everything Client and click Start (It may take a few seconds for Everything to stop from above before you can restart the service).
• Download PsExec.exe from SysInternals.
• Run the following command:
  psexec.exe -i 0 -s es.exe rc: -export-csv c:\pstest\out.csv