mkarak ✭✭✭✭✭

Hi, we updated requirements on this page: Use gMSA accounts for Windows polling gMSA account needs to be member of LOCAL Administrators group on both sides (SolarWinds Platform polling engine and as well polled node). There is no requirement for it to be part of Active Directory “Domain Admins” group.

Unfortunately, we cannot commit to exact release date but we are aiming towards next major version with the fix right now.

Thanks for reporting this. It is indeed bug in username validation. We will fix it in future version and for now update the documentation to capture this. Sorry for inconvenience.

Hello, First of all Orion.Discovery 'ValidateCredentials' verb can be used to validate node IP Address against SNMPv2/v3 credentials specified directly within the script (and not against those that are already saved in DB). Here are the examples for SNMPv2 and SNMPv3: SNMPv2 SNMPv2_node_ip = "1.1.1.1" snmp_port = 161…

Hello @"crr" , the bug I mentioned in my previous comment only affects the (SAM) Application/Component monitoring, so it is not the root cause of the problems you described. Those issues seem to be related to native node polling (such as Uptime). However, there was another issue fixed in the 2025.1.1 released today: the…

Hi @"darrencook" , Thanks for reporting this issue. I can confirm that this is a bug in the current version (2025.1). The value of the Connection Mode dropdown from the Edit Node page (e.g., WMIOnly) is currently only respected for Node polling (e.g., CPU Load) but is ignored for polling of Applications/Components on the…

Please make sure you are using latest version of online installer (build 2023.1.0.196). You can download it here: https://downloads.solarwinds.com/solarwinds/Observability/RTM/Solarwinds.Installer.exe Error you mentioned can occur when older version of online installer is used as it is not compatible with change done in…

It is not possible to modify this resource to display requested data. However you can create a new report that will do it for you. Report can be then placed on any view using "Report from Orion Report Writer" resource. Milan

Hi Thomas, you can do this using following filter condition: Nodes.NodeID = X (where X is a NodeID of your node). If you are using the resource on Node Details page and you want to limit it to actually displayed node you can use following filter: Nodes.NodeID = ${NodeID} Hope this helps. Milan

This was actually a bug that was introduced in 10.0 fixed in 10.0 SP1. In 10.0 alert suppression query was executed only for particular node that triggered the alert. However the expected behavior is to execute the suppression query for all nodes in database and if any of them matches the query the alert will be…

Hi Russ, We haven't seen this problem so far and we are not able to reproduce it. Could you please check which program has locked the file? You can use Process Explorer from MS (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) to do this. Click the Find menu and select Find Handle or DLL... Type the file name…

Hi, there is a way how to achieve this using Orion but it's quite complicated. Let me try to explain. First of all, you will need to upgrade to Orion 10.0. This version brought some improvement to syslog processing that is necessary to make this work. To be more specific (from Release Notes of Orion 10.0): * Orion NPM node…

Hi there, I would suggest to create a new custom property for nodes (e.g. device_image) which will store name of the image for each particular device stored in inetpub folder. Then you can use Custom HTML resource and reference the image name by variable: <img src="http://server/Orion/images/${device_image}" /> Hope that…

You can create new Summary View (e.g. "Management Reports") and add multiple instances of 'Report From Orion Report Writer' resource. This will allow you to put several reports on one page and you can then create new Report Scheduler task to send this view to your management on regular basis or you can add this view to…

Try this one: Nodes.Caption LIKE '*RO_1' OR Nodes.Caption LIKE '*RO_2' "Caption" column is contained in both, Nodes and Interfaces tables so unless you specify which one to use SQL will complain about ambiguity. Hope that helps. Milan