Earlier last week, we released Snow Inventory Oracle Scanner 5.0.1. Since this release has been developed for over a year and contains several enhancements and important bug fixes, we recommend to upgrade to this version.
With Inventory 5 it's actually really easy to upgrade SIOS, and in this blog post we will show you how.
This post is not a replacement for our user guides. The current user guide for the admin console describes how to perform an agent upgrade in general, but it does not have a specific example for SIOS.
If you agree, we will incorporate some of the content into the user guide.
- All agents (Windows, Linux, macOS, Unix and SIOS) are updated on the Inventory Server using Snow Update Service (SUS). There are some limitations in the SUS User Interface, so when an agent update is published, you cannot see which files are getting downloaded. By default all these agent files are stored in the folder: C:\ProgramData\SnowSoftware\Inventory\Resources\Agent
- SIOS behaves a bit different from the other agents. SIOS requires that one of the other agents (Windows, Linux or Unix, since Oracle Database cannot be installed on macOS) is installed along with it. Technically, we say that the sios.jar-file is a "support file" that needs to be put in the same folder as the snowagent.exe-file.
Step 1, verify that the latest sios.jar-file has been downloaded with SUS.
For this specific version (5.0.1) verify that a sios.jar-file exist in the path C:\ProgramData\SnowSoftware\Inventory\Resources\Agent\sios\5.0.1
If there is no such file or directory, make sure to run Snow Update Service (SUS) to download the latest Inventory agents.
Step 2, Create a new agent update
In The Inventory Admin Console, navigate to Agent Updates and click "Create new". Give the update an appropriate name and chose the target operating system, then click "Next".
Step 3, Add the sios.jar-file as a support file
Add the sios.jar file from Step 1 as a Support file, by clicking "Add" as in the image below. Then click "next".
Step 4, Choose the target computers for the update
You can specify which devices that should get the update by using either sitename, configurations, specific devices or a custom built view. Click "next" when the target has been specified.
Step 5 (optional), Schedule the update for the future
If you don't want to run the update immediately, you can select a future time and even a service window to perform the update. If you want to publish the update immediately, just click "Next".
Step 6, Publish the update
Verify that the summary looks correct and click "Publish". (In my environment I did not have any Linux computers so no devices are affected. Not an ideal example, but at least you see how it works)
That's it, the update is now published, and the targeted agents will automatically upgrade themselves the next time they connect to the Server. You can follow the update progress in the Admin Console in the "Agent updates"-section.
As always, let us know if you have any feedback!