aLTeReGo ✭✭✭✭✭

Nothing new on this front to report in SAM 5.5 but we haven't lost track of this request. Improving macro support in SAM is something we're definitely considering.

You will find component settings, like the URL configured for a specific component, in the APM_ComponentDefinitionSetting table. 

The following attributes are required. * In the Attribute Statements section, add following attribute statements: NameName formatValueEmailUnspecifieduser.emailFirstNameUnspecifieduser.firstNameLastNameUnspecifieduser.lastName * Add following to the Group Attributes Statements: NameName…

You are not missing anything. This is a limitation of SAM 5.0 and is something we're currently working on addressing, as you can see in my "What we're working on" post for SAM.

Have you tried troubleshooting using the 'test' button? I'm afraid I haven't used Idaptive before. You may want to contact their support for assistance in getting this working with Orion. 

You can upgrade directly from the product versions you're running on your current operating systems. The process should be fairly straightforward. Backup your database, take a snapshot of the VMs if you can, and run the upgrade on your main poller, followed by any scalability engines. 

How is this node managed in Orion? I.E. what is the polling method used for this node? This is found by editing the node properties or looking at the "Polling Method" value of the "Polling Details" resource on the "Node Details" view for that node.

Database maintenance occurs daily at 2:15 AM (configurable under [Settings - Polling Settings]. If there are other tasks occurring on either the Orion server or the SQL database server at this time such as nightly reboots, WindowsUpdates/Patching, backups, defrags, antivirus scans, etc. These can all influence the success…

Correct Vinay BY. Regular non-Orion specific database maintenance should be performed to keep the database and indexes up to date.

Case # 63255 Solarwinds Diagnostic uploaded via LeapFile

There is a known issue with the SSL Expiration Date Monitor used in AppInsight for IIS that is resolved with Hotfix 1. If that is the issue you are experiencing I recommend downloading and applying Hotfix 1 to see if it resolves the issue you are experiencing.

If you need to monitor each unique instance of w3wp.exe then you should create a process monitor for each, using the command line filter as pictured below.

Are all your monitors behind an hour or just some? It looks like it might be a timezone or daylight savings issue rather than the poller not being able to keep up. Can you please check the timezone settings and server time for the Orion Server and the SQL database server?

Seems you cross posted this question. This is Petr Vilem's response to your other thread. Petr Vilem wrote: Is not this particular database (ServiceBrokerMessages) configured for AutoClose? We have seen this behavior in such cases. Once database uses AutoClose, collecting its performance counters works only while there is…

Your best best bet would be to copy over the background images and re-add the appropriate items to the map. All items contained on the map are identified by their entity ID, which is unique per-instance. Be that a group, node, application, etc.. There's really no way of moving this map from one system to another intact…

This unfortunately is not currently something that is possible today, but is something we're thinking about for a future release.

Have you defined your website URL under [Settings > All Settings > Web Console Settings]? 

Your screenshots actually suggest that your RDP session is below the minimum resolution required for the installer

You would follow the steps outlined at the link below as if you were migrating the SQL database to a new server. https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Migrate_the_SolarWinds_Orion_SQL_database_to_a_new_server.htm

SAM supports the same 100 Additional Pollers as any other Orion Product module. This is a function of the Orion Platform. Now each module has its own maximum number monitored 'things' it supports irrespective of the number of APEs used. The documentation references usually the maximum number of fully loaded (maxed out)…

By not working fully, what exactly isn't working or what symptoms are you seeing?

This should get you started. Just replace the display names with the names of your servers and add whatever additional fields of information you're wanting to display. SELECT [data].[DisplayName] AS [DisplayName],[data].[InstanceSiteId] AS [InstanceSiteId] FROM orion.nodes AS data WHERE ((([data].[Caption]) =…

Orion's High Availability does not provide for zero-downtime upgrades of the Orion platform itself. It provides high availability from network, server, and application failures, as well as allows you the ability to patch or upgrade the operating system of another member of the pool without disrupting services. It can also…

What product modules and versions are you currently running? This issue should be resolved in the latest release. 

Out of curiosity, what web browser are you using? Also, have you been able to reproduce this issue using a different browser? 

DNS is used in HA solely as a convenience feature for those customers running HA in a multi-subnet failover configuration who need some mechanism for redirecting end-users to the active member hosting the Orion web interface but do not have a load balancer. DNS can also be used by some devices to send Syslog, SNMP Traps,…

Good suggestion @"jjroncag". For now, you can use floating-point percentage thresholds for instances where whole numbers are too larger for enormous volumes For example where 99% used on a terabyte drive would be 10GB, you could configure the threshold to be 99.9% free which give you 1GB. 

If you are running 2019 releases, then use Centralized Upgrade located under [Settings > My Orion Deployment > Updates and Evaluations]

Is it safe to assume you are hosting the banner image at the top on a web server and referencing it within the HTML of the message body?

@"roga", of course we did.