
Albert_M asked a question.
Windows Agent Oracle/Non-Oracle
Hello,
Could you please advice what could go wrong if we install on all Windows Servers Inventory Agent with SIOS?
Does SIOS somehow hard affect performance and Inventory duration?

Albert_M asked a question.
Hello,
Could you please advice what could go wrong if we install on all Windows Servers Inventory Agent with SIOS?
Does SIOS somehow hard affect performance and Inventory duration?
→ Flexera One
→ Snow Atlas
→ FlexNet Manager
→ App Broker
Need help finding an answer?
Are you targeting the servers for the Agent with SIOS install where you suspect Oracle or are you planning on installing this agent on every device?
Ideally you would target the installation as you need Java installed as a pre-requisite for the SIOS enabled agent to work.
The SIOS scan adds little overhead to the scan itself but with the many options on how to enable SIOS in the agents config this can increase though still unnoticeable in real world operations. We are talking seconds and not minutes over a normal scan duration.
Hi Joe,
We want to include Inventory Agent in Deployment Image for Windows Server and so I can't manage Agent Installation if there is Oracle installed.
What could possibly goes wrong if we include Agent with SIOS for all Servers? Even if Java is not installed.
If SIOS can not be started so no affect for Endpoint?
Nothing should go "wrong" but you will see errors in the logs stating the Oracle scan failed etc and Java was missing.
Also as you probably already know, to include and Agent in an image ensure you anonymise the agent by deleting the C:\Program Files\Snow Software\Inventory\Agent\data directory before you sysprep/seal the image.
If your system is on premise and not hosted by a Snow partner you could install the non-SIOS enabled agent via your image and then use the SMACC on Inventory server to deploy an updated configuration to only the servers where Snow shows possible Oracle installations.
Joe,
Thank you for your help and advices! :)
Hi Albert,
In order to minimise the number of agent/configurations, I like to keep things simple.
I've always deployed an "Oracle aware" agent on sites where we suspect Oracle.
If the machine has java then the SIOS scan will run,
If it doesn't have java, it will error out and this adds minimal delay to the scan time.
In this fashion I have deployed SIOS enabled agents to tens of thousands of machines with no noticeable impact.
I also have the reassurance that there should be no surprises, i.e. if Oracle and Java are present on any machines then we have a very good chance of detecting it (assuming my other agent config parameters are correct).
Tom
Hi Tom,
Thank you for sharing your experience. We have a common thoughts :)
We did it that way too ;)
you could always use a different config file which disables the oracle scan option on the devices that won't have oracle installed on them