How to update OCS-NG Inventory agent for Windows to

For quite a long time now the ocs-ng agent version is production running. We encountered a few problems with it (for example not displaying notification message text to user when installing software) and decided to upgrade our agents to new version numbered New version apparently have this fixed, since on multiple test computers the message text was displayed properly. Thus, we have decided to upgrade.

In order to upgrade the agent, you need to:

  • create a new package for deployment
  • download latest version of ocs-ng agent
  • fine tune command to install agent

Assuming you already now how to deploy software using OCS and know what is the difference between “LAUNCH” and “EXECUTE” actions I will just provide essential information.

First, download new version of agent from and extract OCS-NG-Windows-Agent-Setup.exe file from the archive. Then, zip it again but double check if it is zipped in root of archive, not in directory inside it.

Then fine-tune your install command for upgrade.

Mine is :

Switches are:

/S – silent

/UPGRADE – tells the installer that it is an upgrade, so stop OCS service and store success code

/NOSPLASH – do not display OCS splash message

/NO_SYSTRAY – keep OCS hidden from system tray

/NOW – run inventory after installation (sometimes it doesn’t work)

/SSL=1 – Keep SSL turned on

/SERVER – fully qualifed domain name of server with HTTPS prefix

Select Execute action

This should look like:

Click Send button, activate the package and affect computers.

Keep in mind, that this package WILL update the agent upon next inventory cycle (in our environment it is 1 hour) and will report back on NEXT cycle. So be patient. After upgrading, agent will not contact server before on it’s own.

You could of course build a small .bat file, that executes upgrade, then run inventory but this is a bit overkill for such a small change.

Ok, that’s all, pretty easy, huh?

By |2016-12-22T21:35:09+00:00May 18th, 2016|OCS Inventory NG|5 Comments

About the Author:

I am passionate about Systems Administration. I like to face new challenges and test new environments.Windows and Linux Debian boxes (both physical and virtual) are my favourites. I like solving problems related to Windows Server roles and services as well as Linux but some distributions in particular. I'm not considering myself as Linux master but surely, I always do my best to fit the needs. On the other hand I consider myself as a Windows Server Professional and in terms of WS and Windows Desktops I always follow best practices, good advices and opinions from other admins.


  1. Emeline July 12, 2016 at 08:28 - Reply

    What a pleasure to find someone who idenitfies the issues so clearly

  2. Matthias July 12, 2017 at 10:27 - Reply

    i think the difference between launch and execute is that execute starts a command which is allready on the client

    for example “dir”
    Why exactly do you choose execute ?

  3. teamboss August 4, 2018 at 22:57 - Reply

    but i allways use the launch commands with parameters …it works flawless … tested with agent 2.05

    • Miłosz Engel August 14, 2018 at 08:50 - Reply

      me too, to be honest I do not remember why I chose execute. Thanks for marking this up!

Leave A Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.