aLTeReGo ✭✭✭✭✭

The Collector and Information Service, as well as others are already 64bit. Are there 32bit services you're finding in your environment are nearing or approaching the 2GB limit?

The information you're attempting to collect is already available to via Asset Inventory.

RDP to your main Orion server. Navigate to the 'C:\Program Files (x86)\SolarWinds\Orion' directory and launch the 'PollerCheckerTool.exe' tool. You may have installed Orion into a different directory. If so, you may need to first locate which drive and directory Orion was installed to on your system.

Yes, PowerShell could be executed locally on the server where the agent is installed without the need to configure WinRM for remote PowerShell execution.

Have you tried using the Custom Object Resource?

This is already possible today using TreeSize Pro with SAM. I have this setup in my lab to run on-demand and email me a report when a volume has less than 1GB free. Below is an example of what that looks like. It does require blat for the email send action, but the alert trigger action is a simple batch file shown below…

Almost. Keep in mind this is a beta, so it's still a work in progress.

To handle this situation, I would recommend not defining a warning or critical threshold in SAM at all. Instead, I would suggest using the exit code of the script to determine the components status, as outlined in the Administrators Guide. This allows the script to have the intelligence of determining what's good or bad.…

For those who vote this idea up, please provide us examples of the devices you'd like to see supported and the operating system w/version those devices are running.

SAM's SNMP Component Monitors have no Credential fields. There is nowhere to either select existing credentials nor enter new ones.

It would also be nice with the agents to run scripts on a node without having to download source to run every time...actually that should be an option within the current SAM environment. It is inefficient having to push any source even if it is to run a script on the monitored node....especially with SSH capability on…

SAM 6.3 would be the minimum version required to complete the steps outlined above. Really any Orion Platform 2016.2 module or later would work. Orion Platform 2016.2 compatible products - SolarWinds Worldwide, LLC. Help and Support

petermanns, you should have received an email from me yesterday with a link to download beta 4. Let me know if you haven't yet received it.

This is being tracked internally under FB171256

At best you will likely need to recreate this property after upgrading or the Configuration Wizard is run and schema is updated. At worst, you may encounter erroneous errors when upgrading, requiring you to drop your computed field from the table before proceeding with the upgrade. I'd recommend testing on lab/test machine…

This already exists in SAM today

The unusual text wrapping that you're seeing should be resolved when you upgrade to SAM 6.2.4.

The "XXX" at the end of the Macro are a variable to be defined by the user based on which warning or critical threshold value you would like populated within a multivalue script. Normally this is ".1", ".2". etc. but could also be a string, depending on your script output results.

I would recommend allocating at least two CPU cores and four gigabytes of memory for a small'ish test environment that includes the SQL express database installed on the same machine as the SAM 6.0 beta.

Agreed. Excellent catch. Post updated accordingly. Thank you!

rcbarr​, the case you make reference to above, CORE-12365, is specific to some erroneous and benign errors in the error log files related to a legacy dependency that is no longer included in 2018.4 or later. Going through your case history the tracking number for the real issue you encountered appears to be 'PRO-765',…

What seems to be the issue?

The totality of inventory data collected per-node comprises less than 100k of database space. For a somewhat large environment consisting of 1000 servers the asset inventory data should total less than 100MB. Please note that inventory collection is optional can can be enabled/disabled on a per-node basis.

YOu would need to apply this template to the servers where that storage is being presented from the NetApp, rather than the NetApp itself.

Is there information in any of the other resources? What kind of device are you monitoring (OS, version, etc.). How is that node managed in Orion (WMI, SNMP, ICMP, Agent)?

Correct, with one notable exception. Both TLS 1.0 and 1.1 must be re-enabled when performing upgrades. Once the upgrade is complete however, you can once again disable those ciphers.

You have the ability to control which events are generated. If they are disabled they will not write to the event log. There is no way for these events, or any other for that matter, to write to the event log depending upon certain conditions. E.G. If the node reboots there's a sequence of events that must occur in a…

NPM v11 includes 10 free Server Packet Analysis Sensors (SPAS) and one free Network Packet Analysis Sensor (NPAS), not one of each as you describe above.

NodeIDs are unique per-instance, so you will likely have a NodeID of "1" on both Orion instances managed by EOC. EOC does not require object IDs to be unique across all managed instances.

Out of curiosity, what information would you expect to see from something like this?