hy , you could use ocslogon.exe in comination with the ocspackage.exe (ocspacke.exe can be uploaded to the ocs-inventory server).
Launcher “OcsLogon.exe” is a little tool able to run inside a login script or an ActiveDirectory GPO. His goal his to launch OCS Inventory NG Agent on computer, and if Agent isnot installed, to setup Agent on computer
ocslogon.exe /GPO /PACKAGER /NP /DEPLOY=220.127.116.11 /server:yourdomain.com
perhaps the ocslogon is only available in older agent packages-
But you can use the old ocslogon.exe with a new agent
or just use a script which checks if the client allready installed in combination with the normal installer
if exist "%programfiles%\OCS Inventory Agent\OCSInventory.exe" goto end
OCS-NG-Windows-Agent-Setup.exe /S /SERVER=yourserverdnsname /NO_SYSTRAY
There are many more command options to deploy the agent.
In the past you can use 1 ocpackage.exe which you upload to your ocs server.
The ocslogon.exe downloads it to the client and installs it.
But today there are many compatility problems (new agent is ony 64 bit compatible for example)
so you should use a script which runs and check if you have a 32 or 64 bit OS and Windows 7 or windows 10. Depending on that the script installs the correct Agent Version with the normal installer.
hewre are some ver very old scripts by Philippe BEAUMONT
here a complete manual
The systray icon is maybe no visible because reinstallation which ocurs when your computer restarts
in my tests an upgrade install (which you are doing without intention) often does work , becuase of services which aren't restart and files which are open. So for the client "upgrade" i uninstall the client completely and reinstall the new agent.
How to upgrade the agent normaly is described here