aLTeReGo ✭✭✭✭✭

each condition group represents an "AND" condition to the alert, so as I recommended the without 3 tier nesting the alert should now read "in plain English": Trigger Alert when Node Name is equal to LDNJIRA01 OR LDNJENKIS01, AND when the application name is equal to "Linux Process Check - LDNJENKIS01" OR "Linux Process…

Alerting functions independently of polling so alerting when polling is has not occurred in "X" number of minutes. Below is such an example.

I honestly can't imagine what would be causing these events to occur as SAM isn't backing anything up. The closest thing I can think of that would relate to file access would be the File Size/Existence/Change/etc. Monitors. What version of SAM are you running, and what application templates are assigned to the node?

If MSSQL is installed on the Orion server itself, you cannot perform a zero downtime migration.

If the account is being locked then the credentials are likely incorrect. This can be the more obvious typo of the password, or the sneaky and more likely culprit of not specifying the domain name in the username field of the credential. E.G. "Domain\username", "username@domain.ext", or ".\username".

This is the behavior of all Orion managed elements. Anything that triggers a negative (Down/Warning/Critical) status event also triggers a positive (Up/Ok) status so when auditing events you can easily see for instance when a device was exhibiting problems, and when it was resolved. Starting with SAM 5.0 we added the…

If you're using Windows Certificate Services the root CA certificate I believe is used on the Certificate Services web interface. Have you tried monitoring that with SAM's SSL Certificate Expiration Date Monitor?

The simple fix would be to delete the assigned applications and reapply AppInsight for Exchange to those nodes. The "right" fix would be to open a case with support so we can determine why this occurred in the first place and possibly even provide a fix.

You cannot eliminate particular scan types from being performed during the Network Sonar Discovery. There are however some fairly significant discovery improvements included in the SAM 6.3 release (currently in beta), which should address your concerns.

SAM is written in compiled C# code, so there are no scripts.

There is no way to save the historical data in the process of deleting and recreating the component monitors at the template level. You can however export the raw data through the web interface to Excel format, or even export chart data by clicking on "Export to PDF". More advanced data export options are available through…

Let's try this link instead. https://support.solarwinds.com/SuccessCenter/s/article/Unable-to-retrieve-the-URL-for-scheduled-PDF-report

Have you tried changing the fetching method for these services to use RPC instead of WMI for the assigned application instance that isn't working?

I believe the articles below are what you are looking for. * Enable SSL or https for the Orion Web Console - SolarWinds Worldwide, LLC. Help and Support * Alerts still shows HTTP and using port 80 even Orion is already using HTTPS - SolarWinds Worldwide, LLC. Help and Suppor…

I would recommend upgrading to SAM 5.5 as that's not the expected behavior. This was how the HTTP User Experience Monitor worked previously under APM, but relatively recent changes in SAM allow for the inclusion of the host header as part of the HTTP request. We're also working on some additional improvements to the host…

Have you followed the steps outlined in the following KB article? https://support.solarwinds.com/SuccessCenter/s/article/Corrupted-license-store 

The alerts macro can only populate one URL. If you have multiple additional web servers, these are typically front ended by a load balancer. In such a scenario the IP, hostname, or FQDN of the VIP is what would be populated into the ServerName field of the database.

Do you have a case open with support? If so, what is your case number?

To enable FIPS Mode in Orion follow the steps outlined in the KB article below Enable FIPS for compliance - SolarWinds Worldwide, LLC. Help and Support

Another option is to apply a group policy to the machine which will ensure that FIPS mode is always applied to the machine, even if it's reset by another application.

Forms that utilize JavaScript need a full fledged browser with a JavaScript engine. For this purpose (and much more) Web Performance Monitor was born. I recommend you give that a shot.

Edit your user account settings under [Settings -> Manage Accounts]

I would recommend opening a case with support. This is definitely unusual behavior and something that will require a look through your database and diagnostics to resolve.

Case number?

This information is aggregated across DAGs using the out-of-the-box reports "User by Mailbox Size" and "Users by Mailbox Quota". You can also create your own custom reports which aggregate data across Exchange instances. This same method can be used in dashboards using the Custom Table resource.

This is where you would use condition groups, where you define what the alert applies to and what it doesn't apply to.

The Gold Master image is laid down and ready to be provisioned by the Orion server when the server reboots. E.G. when it's been cloned and starts for the first time. If you plan to continue to make changes to the master image that require you to reboot once the agent has been installed, you should disable the Orion Agent…

You could invoke Internet Explorer through a PowerShell script like we've done for the Exchange 2010 OWA Form Login (PowerShell) template.

That is correct. With the 2.0 release, Synthetic End User Monitor was renamed Web Performance Monitor.

Got it. Tracking internally as FB78184.