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.11.1 available

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

Plugin data not obtained from the clients/agents

Hello to all,

I've installed latest version of OCS via GitHub on CentOS7. All works well. then I've installed some plugins (via GitHub Repo as well) like:

  • winupdate
  • officepack
  • Network Share

I've instelled they as descrived in the Wiki (upload zip and install). The GUI on the server shows me the new tabs. I.e. on a windows client, if I select "Miscellaneous" I can see "WINDOWS UPDATE STATE" and "NETWORK SHARE". Then under Plugins Menu there is a item: "Office Key Management".

All those tabs are empty.

I've of course copied the vbs scripts on the client and tested them manually. Executing this:

OCSInventory.exe /local="D:\test" /force /xml="D:\test"

I'm able to get an XLS file with proper data and in the XML there are informations like OFFICEPACK, NETWORKSHARE, WINUPDATESTATE, but seems those informations are not sent or parsed server-side.

Only the default data are sent to the server, but no plugin data.

How can I debug it?



in OCS Inventory NG server for Unix by (600 points)

6 Answers

0 votes
I've additional informations.

Even if the XML created on the client shows me office,winupdate,network-shares informations, those are not sent. Eenabling the query log on the MySQL server, the plugin tables are not touched. They exist, it means the plugin are installed correctly. Only no data is populated from the client.

Thanks, Simon
by (600 points)
0 votes

This morning I've got Office License informations, but still no informations for Widows Update or Network Shares.

Again, is there a way to debug the whole process and see what is parsed on the server?

by (600 points)
0 votes

I've some informations more. Seems related to scripts that are collecting informations from the local registry.

I've tried winupdate.vps to execute it manually and redirect the output to a file. The file is correctly generated. But if I execute it from the Agent Service, the file is created, but empty. How to grant the access to the local register from the VBS?


by (600 points)
+1 vote

Hello to all,

At the end I've solved myself at the end the issue with the winupdate plugin....

It's related to a 64bit system which is executing a 32bit script. This invokes a 32bit HKLM tree instead to the 64bit which contains the needed data.

If someone is interested in, I could share the modified script.

Bye, Simon

by (600 points)
+1 vote
Hi  @xefil,

I'm interested in the solution you found. I'm trying to identify the officepack space in the xml that generates the instruction you mention, but I do not identify it. Additionally, I do not see information sent to the server. could you help me?
by (680 points)
edited by
+1 vote


I found a similar issue using a custom powershell plugin and OCS Inventory Agent (the latest version

I build a powershell plugin to get version of Microsoft App Package.

The plugin is based on Get-AppxPackage powershell function (example (Get-AppxPackage -name "Microsoft.MSPaint").Version") to get the version and then extend the XML for software.

The final output is:

Write-Host '<SOFTWARES>'

Write-Host '<PUBLISHER>' $appeditor '</PUBLISHER>'

Write-Host '<VERSION>' $version '</VERSION>'

Write-Host '<NAME>' $appname '</NAME>'

Write-Host '</SOFTWARES>'

I've copied the .ps1 scripts on the client and tested it. Executing this:

OCSInventory.exe /local="D:\test" /force /xml="D:\test"

It works. I'm able to get an XLM file with proper data and in the XML there are informations with the software App version.

Using debug I also found this section;

AGENT =>  Communication Server ask for Registry Query

REGISTRY => Executing query asked by server

REGISTRY => 13 query successfully executed

EXECUTABLE PLUGIN => Searching for VBS script(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>

EXECUTABLE PLUGIN => Searching for PS1 script(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>

EXECUTABLE PLUGIN => Found executable plugin <plugin.ps1>

================= TRACE START ===============

================= TRACE STOP ===============

EXECUTABLE PLUGIN => Plugin <plugin.ps1> executed successfully

AGENT => Sending Inventory

But if I proceed with a standard installation I'm able to check that plugin is in the right place, BUT seems those informations are not sent or parsed server-side.

How can I debug it?


by (220 points)
Powered by Question2Answer