aLTeReGo ✭✭✭✭✭

This change affects only Custom HTML widgets. The setting is binary. Either 'on' or 'off' for all Custom HTML resources. 

The notes are in the AlertStatus table which only shows active alerts. Notes don't make it into the AlertLog table where the historical alert data is kept.

So if you move the nodes to another polling engine, does the issue follow the node(s) or do the jobs execute fine when the node is moved to a different polling engine? 

An error 503 does not mean that the Orion server was able to contact the server, but that the remote server could not process the request. Usually this is because the information sent was improperly formatted. www.itpro.com/.../what-is-http-error-503-and-how-do-you-fix-it

The following thread discusses this error, as well as provides some recommended remediation steps. https://thwack.solarwinds.com/product-forums/user-device-tracker-udt/f/forum/26725/error-in-udt

If the alert triggered, which should be easily confirmable by reviewing the Orion event log, then the Agent, and the poller its associated with did their job. The fact that the alert triggered, also means that the alerting service on the main poller completed its job of triggering on the alert. Where the breakdown appears…

There is really no such thing as a 'full list' as it's heavily dependent upon which modules and module versions you are running. You can do a search on your Orion server for the file extension .apkg which should return all agent plugins relevant for your specific deployment. 

We have attempted to confirm your findings comparing 2020.2.5 to 2020.2.6 but our results differ from yours above. The "Dynamic IP.." checkbox only appears when selecting nodes where this setting is enabled. Hence, it can only be used to disable Dynamic IPs, not enable existing nodes in bulk to use a dynamic IP address. 

The Agent should never initiate a reboot. Rather, it should appear in the Agent Management as awaiting a reboot. The next time a reboot occurs for that machine, the Agent upgrade process should complete. The Agent should only require a reboot if an Agent binary or associated dependency (usually .NET) is locked or in use by…

Unfortunately, these are considered different accounts in Orion, and are therefore treated as such with no native ability to merge or migrate settings from one to the other. In theory it should be possible to read the settings out fo the database for the old account and update the record for the new account with these same…

No, this would not be considered normal operating procedure to restart Agents after an upgrade. However, Agents and/or their plugins are often upgraded also as part of the normal Orion upgrade process. I cannot imagine what would cause what you observed above to occur, but it definitely appears to be related to the upgrade…

The only time the Orion Platform will show is when there is a hotfix that is only applicable to the Orion Platform. Since the product module versions mirror that of the Orion Platform they're certified to run on, by downloading and installing SRM (for example) 2020.2.6, you are by proxy also getting the Orion Platform…

Agent plugins are deployed dynamically, only as needed. If you'd like to seed the plugins as part of your deployment, you would simply copy the plugins folder from an Agent that has all the plugins you wish to use elsewhere. Then using chef, puppet, etc. you can have those plugins copied to the plugin folder of each agent…

Instructions for adding MIBs to the database can be found a the link below. https://support.solarwinds.com/SuccessCenter/s/article/Add-MIBs-to-the-SolarWinds-MIB-database?language=en_US

Logs for WPM Recorder should be found here: C:\ProgramData\SolarWinds\Logs\SEUM\WPMRecorder.log If the log file is not present or new logs doesn't appear in the WPMRecorder.log file - this usually means that the user account used for running the WPM Recorder doesn't have access to this log directory:…

This definitely does sound like it's security/permissions related. My advice would be to use Procmon and look for any access denied messages when launching the Recorder application within the virtual desktop. It could be either File Permissions or Registry related. Another, simpler way of diagnosing if it's permissions…

Apologies..I meant 'Recorder'. I've updated my response accordingly. That's what I get for multi-tasking.

I'm not aware of any internal testing done to certify the WPM Recorder for use within a VDI environment. Nor am I aware of a customer I've spoken with that is using the WPM PlayerRecorder in a virtual desktop. I cannot think of any reason why it would not work, I would also not consider myself an authority in all things…

Correct. There is no additional detail beyond what the audit event states. If you'd like to see additional detail included like 'changed value X to Y' or something to that effect, I would suggest opening a feature request. 

Something like... SELECT [N].[Caption] AS Caption , ISNULL([PortsTotal].[PortCount], 0) AS PortCount , ISNULL([PortsActive].[PortCount], 0) AS ActivePortCount , (ISNULL([PortsTotal].[PortCount], 0) - ISNULL([PortsActive].[PortCount],0)) AS UnusedPorts , CASE WHEN ((ISNULL([PortsTotal].[PortCount], 0) = 0) OR…

The ActionTypeID is the unique internal numeric value assigned to each audit event type. 60 Orion.SSH.ConnectionSuccess SSH connection successful. 61 Orion.SSH.ConnectionFailed SSH connection failed. 30 Orion.NodeChanged In the examples above, 60, 61, and 30 are the ActionTypeIDs for the audit event, followed by the…

Looking at the release notes, it appears this option was added in the 2020.2.6 release 

In you rule have you selected both 'Use the original sender's address as the source address' as well as 'Use the original sender's address for the HOSTNAME field' as described here > documentation.solarwinds.com/.../lm-log-forwarding.htm

Is this issue occurring with the new Chromium based WPM Recorder, or with the older Internet Explorer based recorder? 

Sounds like that resolved the issue? 

1. All scalability engines must match the version of the Main Poller. 2. You can either run the installer on the APE or depending upon what version you were running prior to the upgrade to 20202.2, you can use the web based Centralized Upgrade. A detailed walkthrough of Centralized Upgrades can be found here…

Follow the steps outlined in the following KB article. https://support.solarwinds.com/SuccessCenter/s/article/Delete-Polling-Engines?language=en_US

If the issue is not occurring when in incognito mode, then the problem is with your browser cookies. To flush the cookies in your browser. In Chrome * On your computer, open Chrome. * At the top right, click More . * Click More tools Clear browsing data. * At the top, choose a time range. To delete everything, select All…

While you are selecting a product to download, all Orion product installers are identical and contain all the necessary bits required to upgrade any/all modules that are installed on the server.

Apologies, I meant installer. Note that this issue is documented in the following KB article. The easiest way to resolve the issue if to apply all available Windows Updates to the Orion server prior to running the installer.…