neomatrix1217 ✭✭✭✭✭

There are a couple of ways to do this the easiest would be the following using the service control manager on that node and selecting those specific services. Use the Service Control Manager in SAM (solarwinds.com) or Create a Windows Service Monitor in SAM (solarwinds.com)

Take a look at a log file called c:\programdata\solarwinds\logs\orion\orionweb.log it should show your attempt to log in to the web console.

Well you get 30 days free with ARM or you can use the free tool SolarWinds has FREE Access Rights Auditor | SolarWinds

Are using the legacy or OLV?

Not sure about AD Tidy but you can do this with Access Right Manager Identify inactive accounts (web client) (solarwinds.com)

Did you go through this documentation How the API Poller feature in SAM works (solarwinds.com)

So probably the only way to do that would be through the Orion API and I'm not smart enough to guide you through that one. The reason the nodes are skipped is that as stated they are already in the Orion DB.

I would look at the config wizard logs for completion located in the same directory as above.

I would look into using user-defined groups to reduce the alerting noise. Configure user-defined groups in SEM (solarwinds.com)

This is how the variables need to be structured. Log Analyzer alert variables for syslogs and traps (solarwinds.com)

Have you tried monitoring the node using the Orion agent instead of SNMP? also I would do an SNMP walk and see what the device is sending us. List of NPM, NTA, UDT, and VNQM MIBs and OIDs used for polling (solarwinds.com)

No need to be sorry I know it is not the best solution but unfortunately the only way to solve it.

Hello, First off I think you meant to post this in NPM but as far as the issue that you are having the only way to correct this will be to delete and re-add the node making sure not to select those volumes when you re-add it.

Since this seems to only be at start-up and not causing any issues have you tried putting the trap service in a delayed start?

So on your screenshot, the current count is 2 and the component is showing as up and in your alert, if you have it set to critical but I don't see that you put in a threshold value for critical.

are you using the legacy trap and syslog?

Hello, make sure that you have all of the following requirements. AppInsight for Exchange Requirements and Permissions (solarwinds.com)

Hello, I would open a support ticket for this one if not there are other actions you can use the 2nd like is to an older post where they use growl. Alert actions available in the Orion Platform (solarwinds.com) Desktop Notifications for Orion - Forum - Network Performance Monitor (NPM) - THWACK (solarwinds.com)

Yes, you are correct meaning that you would need to install the agent on the file server you want to monitor for activity.

Please take a look at this KB article to accomplish what @"npatterson" was referring to in his reply below. Configure FIM connectors to monitor Windows files, directories, and registry settings (solarwinds.com)

You can add it via SNMP and see what we can monitor but more than likely you will need to use a universal device poller.

In the string just type in Action and a list will appear that you can select.

Select a node and on the inspector, panel select text and click on the (+) to add variables to the node Here is how you add it to a view or SolarWinds Orion Add Orion Maps to views as a widget (solarwinds.com)

Look for a rule called "Continuous Excessive Logon Failures" you can edit this rule and use it as a template for what you are trying to accomplish.

Component status value definitions (solarwinds.com)

If this is for NTA I would take a look at this KB Flow environment best practices (solarwinds.com)

You can remove the disks from monitoring in manage nodes so that you don't get those alerts

@"vandu" Have you opened a support ticket for this issue?

Got it sorry did not reply sooner but glad you got it working.

Usually, that is an indication of a licensing issue with LA do you own LA or use OLV? WARN SolarWinds.Orion.LogMgmt.Common.Licensing.LicenseValidator - Unable to load licensed nodes, retrying #10 SolarWinds.ApiProxyFactory.ApiProxyException: Exception while acquiring API channel