OCS Inventory AG Agent dumping inventary-informations through command line

Question

Hello,

if I click the tray icon and click show inventory-information that works and that's good so far. I'd like however a commannd line / parameter switch to write these informations into a file but can't find anything. How to do this?

Edit: Ok, OCSInventory.exe /local="C:\" works but it creates a .ocs file. If I try OCSInventory.exe /xml="C:\" no file is generated. What am I doing wrong?

Answer 1

When I use

/XML /LOCAL=.

only .ocs file is created

when I use /XML=.

after approx. 1-2 minutes an .xml file is created

when I use

/XML=. /LOCAL=.

both .ocs and .xml files are created

OCS Windows Agent version 2.3.0.0

Answer 2

Hello,

use the command line parameter  /local.

http://wiki.ocsinventory-ng.org/index.php?title=Documentation:WindowsAgent#OCS_Inventory_NG_Agent_for_Windows_command_line_options.

Answer 3

Ok, OCSInventory.exe /local="C:\" works but it creates a .ocs file. If I try OCSInventory.exe /xml="C:\" no file is generated. What am I doing wrong?

Answer 4

Use : OCSInventory.exe /xml="C:\" /force

Answer 5

Unfortunately still no file generated.

Answer 6

It works fine on my workstation, but the xml file is generated after 2 or 3 minutes.

Answer 7

Yes, I noticed it takes approx. 10 seconds for the .ocs file so I waited for the .xml but unfortunately no .xml file is generated :\

The setup I downloaded is "OCSNG-Windows-Agent-2.3.0.0.zip" and after setup I'm executing like this after:

cd "C:\Program Files (x86)\OCS Inventory Agent"

C:\Program Files (x86)\OCS Inventory Agent>OCSInventory.exe /xml="C:\" /force

So, maybe there is something wrong? Otherwise realy weird because a .ocs is generated. Maybe there's a way to convert the .ocs into .xml?

Answer 8

Hi,

Use ocsinventory.exe /xml /local=c:\

Regards

Frank

Answer 9

Hello Frank,

I tried your command but it creates the same binary .ocs file :\ (no .xml file even after 1 hour btw)

Answer 10

Hi,

I have tested on may Workstation. The /XML option works fine in the 2.1.1.1 agent version, but it doesn't work in 2.3.0.

It seems to me that it is a bug in the Windows agent version 2.3.0.

Regards,
Bexounet.