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

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

OCS client requires Administrator privileges?


I'm trying to deploy a more recent version of the OCS client in Windows PC in our network (see also: http://ask.ocsinventory-ng.org/7647/ocs-inventory-migration-and-upgrade)

The client version is (the last one supporting Windows XP). When a non-admin user logs on Windows, the OCS installer starts, but tries to install the service version despite I specified the /NO_SERVICE flag.

An error message is shown to the user, and this file (named OCS-NG-Windows-Agent-Setup.log) was created in %TEMP%:

Starting OCS Inventory NG Agent setup on 18/09/2017 at 11:26:49
Checking if setup not already running...OK.
Checking Operating System...OK, Windows 2000 or higher.
Command line is: C:\DOCUME~1\PERONC~1\IMPOST~1\Temp\OCS-NG_Agent_Setup.exe /S /NO_SERVICE /S /DEPLOY= /SERVER= /DEBUG /EDITLOG
Parsing command line arguments...OK.
Checking for silent mode...Enabled.
Checking for splash screen...Enabled.
Checking if logged in user has Administrator privileges...NO.
ABORT: unable to install Agent as a service without Administrator privileges !

Is there something we have to set to have the PC correctly inventoried, even by non-admin users?

asked in OCS Inventory NG agent for Windows by (260 points)
edited by

2 Answers

0 votes
It's not possible to install OCS agent without admin priviledges. It is necessary to access all windows componant for inventory and teledeploy.

If you install from an active directory, simply put your rules on Computer login script instead of User login script.
answered by (18.2k points)
0 votes
So the agent needs to be installed anyway, even if not used in Service mode?

We use a Samba-LDAP server to authenticate users, so I can't set computer login scripts.
I could wrap the installer execution in a sort of "run as" an Administrator account, but then I think the PC would be inventoried as the Administrator user, and not the user who actually logged on.

How can I perform the installation as Admin, and then run the inventory as normal user?
answered by (260 points)
Powered by Question2Answer