Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.10.0 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

Agent failed to get executable plugin PsExec.exe output

In OCSInventory.log I find this error:

EXECUTABLE PLUGIN => Searching for VBS script(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
EXECUTABLE PLUGIN => Searching for executable(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
EXECUTABLE PLUGIN => Found executable plugin <PsExec.exe>
ERROR *** EXECUTABLE PLUGIN => Failed to get executable plugin <C:\Program Files (x86)\OCS Inventory Agent\plugins\PsExec.exe> output

Could this be related to my already posted issue with PsExec account problem (see http://ask.ocsinventory-ng.org/2748/ocs-agent-service-and-deploy-account) ?

Or is something else going on here ?

in OCS Inventory NG agent for Windows by (840 points)

1 Answer

0 votes

After lot of testing, I found the solution: after deleting the psexec.exe from folder

C:\Program Files (x86)\OCS Inventory Agent\Plugins the problem was solved !!

In addition, deployments were no longer staying in status NOTIFIED.


I was confused with the documentation on http://wiki.ocsinventory-ng.org/index.php/Documentation:WindowsAgent

Basically to deploy the OCS Inventory Windows Agents, in the SERVICE version ! , using a startup script inside a GPO, there are 2 methods:

1) using launcher OcsLogon.exe together with the agent deploy package OcsPackage.exe, that was created using tool OcsPackager.exe. This is done in the Computer Configuration section of the GPO : as a startup script.

Note: a special case is the section "Deploying or running Agent through login script", where OcsLogon is used from a shared folder, to launch the standalone agent (not as a service). This is basically a login script, and has to run as a user with administrator rights. We are not considering this further.

2) using the PSEXEC or "OCS Inventory NG Agent Deployment Tool" to push the OCS Inventory NG Agent.
(the word "or" could be misleading; better would be "scripts using PSEXEC" )
Using PSEXEC is the simplest form : using command PSEXEC in a script, to directly launch OCS-NG-Windows-Agent-Setup.exe , with the necessary options.  PSEXEC being used to allow running the setup using an account with the proper permissions.

Note: a variant on (2) is by using "OCS Inventory Agent Deployment Tool", which is a GUI to install at an administator's workstation, and which is used to push the clients to a selected group of hosts or hosts on a given IP address range (still using PSEXEC.EXE).

Additional info on method (1) :
When launching the OcsPackager.exe, while PsExec.exe is NOT present in the same folder, a warning message is popping up "Using alternate account to launch setup requires Microsoft SysInternals <PsExec.exe> tool." --> Click [No] to accept (!) disable installing under alternate account.

In fact the installation is running with the GPO startup script account "Local System". No need for PsExec.exe.

After the installation, the service OCS Inventory Service is running with this account.
I use a separate script to change this to a specific domain "DeployServiceAccount" , which has the User Rights Assignment :

  • Act as part of the operating system
  • Log on as a batch job
  • Log on as a service

These are set from the Default Domain Policy > Computer Configuration > Policies> Windows Settings > Security Settings > Local Policies > User Rights Assignment


by (840 points)
Powered by Question2Answer