aLTeReGo ✭✭✭✭✭

How were these accounts added from Active Directory? Were they added via a group or individual user accounts? You will need to update either the group or the individual user accounts to properly reflect the permissions they should have. By default, all new users created in Orion are non-admin until otherwise specified.

Have you tried creating a 'Group Member' report?

What version of SAM are you running? There was at least one bug fixed in SAM 6.1 related to the information displayed in this resource that may be related to the issue you are seeing. If you're already on SAM 6.1 please open a case with support so we can gather diagnostics to determine the root cause of the issue.

I think you need to look at defining a custom property for the device using the custom property editor.

Unfortunately this is not a configurable option and is how the chart is designed, such that it handles ridiculously large integers (think trillions and up) while maintaining the maximum amount of horizontal space for the actual line chart itself.

What kind of active/passive cluster are you trying to monitor? Is it a Windows Failover cluster?

Sounds like the WSMAN Listener needs to be recreated as outlined in the following KB Article. * SolarWinds Knowledge Base :: "Unable to create WSMan listener" or "An HTTPS listener currently exists on port 5986" Simply delete the the listener on the server you are trying to monitor "winrm delete…

On the standby/secondary server there are zero cluster resources because it is not active. This is normal expected behavior for a standby/secondary cluster member. As such you should remove the threshold for this component monitor. This particular component monitors threshold is really only valuable when assigned to the…

The information contained within this error is too vague to properly diagnose via Thwack. I think you're on the right track opening a case with support. Please post back the resulting findings of your case here once your case is closed. Thanks!

All Application Templates are listed under [Settings -> SAM Settings -> Manage Templates] under the "All" Tag To add tags to your own templates, simply edit the template and add your own tags separated by a comma to the "Tags" filed in the Template Editor. These Tags will then appear in the left navigation above under…

The only advantages the Service Status - SNMP component monitor has over the Windows Service Monitor - WMI is that it uses less bandwidth, is high latency friendly, and requires no administrative privileges on the remote host in order to monitor the state of the service. Latency and bandwidth concerns are typically only a…

A simpler solution may be to look at SolarWinds Storage Manager. It has native support for monitor NetApp storage and integrates directly into the Orion web console.

Altering the Nodes status via an alert action can only be performed by Node related triggers conditions. E.G. "I want to alert on" must be configured for "Node", not "Application". Standardizing as well as adding additional flexibility for how object status is calculated is however something we are considering for a future…

Hmm... Agreed. Here's mine just for good measure.. An error has occurred with the Orion website. Additional Information System.Exception: Unable to create TopApplicationsReport. ---> System.Data.SqlClient.SqlException: Invalid object name 'NetflowDetail_163'. at System.Data.SqlClient.SqlConnection.OnError(SqlException…

If you're looking to monitor File Existence, File Change, File/Directory Size, File Share accessibility, etc. then this is very easily accomplished using Server & Application Monitor. If you're looking to audit users accessing files/shares, this is a task better suited for Log & Event Manager.

Is it possible that you aren't monitoring the volumes where those databases reside or that you are monitoring the node via SNMP? I recommend changing the node polling method to WMI and ensure that you monitor all volumes displayed under "List Resources" to see if this resolves the issue.

Orion uses the reported "uptime" as returned by SNMP or WMI to determine if the machine was rebooted. If the node is managed via SNMP, simply restarting the SNMP daemon alone on the host will cause this alert to trigger. As such there's really no way to differentiate between a purposeful or unintentional reboot of a node…

Thanks grahampriley for your contribution to the community. You may want to add this script to an APM template and share it in the Content Exchange Zone of Thwack where it will receive greater community visibility through in-product integration with Thwack. You can even upload an existing template you already have created…

The ESX hosts themselves must also be managed by Orion for these resources to populate with information.

This information comes from > http://www.net-snmp.org/docs/mibs/host.html#hrStorageTable

Click the title "Verify the AP/AW modules (Additional Poller/Additional Website)" which will provide a more detailed explanation of the error, as well as remediation actions.

The following additional macros are now available in the SAM 6.0 RC (available now) * ${USER} * ${PASSWORD} * ${PORT} * ${Node.SysName} * ${Node.Caption} * ${Node.DNS} * ${Node.ID} * ${Component.ID} * ${Component.Name} * ${Application.Id} * ${Application.Name} * ${Application.TemplateId * ${Threshold.Warning} *…

It sounds like the HP Insight Agent may have corrupted the MIB database on the server, or caused SNMP to crash. I would recommend re-installing the latest version of the HP Insight Manager agent software and managing the node(s) via WMI rather than SNMP.

The WPM Recorder connects only to the main Orion server's web interface port (normally Port 80 or 8787) and TCP Port 17777. The WPM Player connects either to the main Orion server, or any additional poller over TCP Port 17777 when in Agent Initiated Mode (AKA Active Mode). If the Agent is in Server Initiated Mode (AKA…

It's hard to say for certain without additional information. I would recommend opening a case with support so we can look through your diagnostics, but I would also suggest editing the component settings and double check the URL, Proxy Settings, credentials, etc. to ensure they are correct.

Have you ensured that you enabled impersonation for this PowerShell Component Monitor and that the account specified has adequate permissions to both run the script, as well as access that share remotely?

The new installer ensures that only module combinations which are compatible with each other can be installed together. You are being forced to upgrade other modules because the version of the module you are seeking to upgrade is incompatible with the other module versions currently installed.

You can view the SMTP logs on the server itself that's being used to send the email. Below is an IIS example. Alternatively you can enable debug logging on the application itself which will then log verbose debug messages to a file in the SAM log directory. The default location is C:\programdata\Solarwinds\Logs\APM

Have you tried changing the bitness from 32bit to 64bit? This can occur when/if you are calling 64bit PowerShell snapins.

Translated from Portuguese Ewerton Rabello wrote: I'm trying to add a monitoring of a JBoss server by SAM and is the error below : Testing on node 10.10.100.35: failed with 'Unknown' status Cannot connect to JMX server SolarWinds server connection towards the JBoss server is normal. I wonder if there is some kind of…