aLTeReGo ✭✭✭✭✭

The certificate must be in PEM format to be imported into SAM. The Certificate will look similar to the following. In fact you can import the one below if you like, there's no password encrypting this example. -----BEGIN RSA PRIVATE KEY----- MIICWQIBAAKBgHsSuRPLMDrxcwMB9P6ubGFGmlSvHvSXq2kfwycrcEKf/TCctShz…

David Ibrahim wrote: how can one create alerts to capture hardware sensors like Power Supply, Temperature, and Fan? The default out-of-the-box "Alert me when any hardware component goes into a warning or critical state" should already be pre-configured to trigger when a hardware component fails.

Just out of general curiosity, why do you prefer to migrate these from Universal Device Pollers to SAM application templates?

If the performance counters work remotely using perfmon.exe and the problem only started cropping up after upgrading to SAM 5.0 then I'd recommend you open a support case so we can look through your diagnostics to determine the cause of the issue.

Correct. The new Web Based Alert Manager uses a new macro expression format from the legacy Win32 Advanced Alert Manager. You should use this new format when recreating your alerts in the new Web Based Alert Manager.

What is it that you're seeing in the Orion web interface that tells you the reason why the component is in a given status that you are trying to include as part of the alert email notification?

Currently there are no custom macros available for use in Network Atlas Maps.

At a minimum It doesn't appear you are returning a statistic, which is required. It looks like you're only returning an exit code.

Sorry about that. I've updated the link above. It's also here. http://dug.servebeer.com/drop/badgraph.jpg

A Script Monitor in SAM would likely be your best option barring Syslog or SNMP Traps.

SAM simply reports the hardware health status as provided by the device through the vendor supplied software. I'd recommend clearing the alert on the server using the vendor supplied software. Only then will the error state in SAM clear.

If the server is simply bound to port 80 and not using host headers, then there's no need to specify anything in the host header field. Simply using the IP address of the actual server in the URL field instead of the FQDN of the cluster VIP should be sufficient.

susan chopra‌ is heading up this research effort but it out of the office this week. She will likely follow-up with dennes.bocado early/mid next week to schedule a time to discuss.

The Advanced Alert Manager pictured above is included with all products that integrate with Orion (Excluding the Enterprise Operations Control). You will find it on the Orion server itself under [Start - Programs - SolarWinds Orion - Alerting, Reporting, and Mapping - Advanced Alert Manager]

We've seen a similar situation once before where the entry URL is dynamic. For example, when you type in https://www.someurl.ext the page appends a unique identifier onto the end of the URL string. So your entry URL looks like https://www.someurl.ext/8765435678987. The problem is, because this is the entry URL it's the…

You may also want to try changing the Fetching Method from WMI to RPC for those Event Log Monitors assigned to nodes that don't appear to be working. This may change the behavior of those component monitors if for some reason WMI is not working properly.

My question is how are you "forcing" these gigabit interfaces to run at 10Mbit? Are these 10/100/1000 TX interfaces? Are you using the "speed 10" command to set these interfaces to 10Mbps? Or are these fiber links that you're using QoS or some other method to limit the bandwidth consumption to 10Mbps?

I have nothing of value to add to the conversation, but like so many other customers I just wanted to say "Me too".

Below is a link to an application template I uploaded that will return the total number of processes running on either Windows or *nix machines.

You are correct, the backup information shown in AppInsight for Exchange is not available in the Custom Table resource. I have logged this issue internally under SAM-3833.

You would not use groups, but rather Custom Properties to categorize and classify these devices for filtering within the report.

Your alert as written will never fire as you can't have a component that is both in a warning and a critical status simultaneously. Your operator in this trigger condition is "All" which is another work for "and". All items listed must be true before the alert will fire, which as defined is not possible. You'll want to add…

Correct. The template has not yet been assigned to a node so no credentials are required at this level. When you attempt to assign the template to the node you will be prompted to provide valid credentials. These credentials will then be stored in the Credential Library and added to the quick pick list so they can be…

That is not an application that is in an unknown state. In fact, based on this screenshot it appears there are no application templates assigned to this node. It's very likely that it's a volume that is in an unknown state on this node. I recommend looking at the "Disk Volumes" resource and hovering over the volumes…

I wasn't able to find the MIBs for this device anywhere. I would recommend obtaining them from the vendor directly and submitting them through support so they can be included in our MIB database. I can make some wild assumptions that the following OIDs are Temperature values. .1.3.6.1.4.1.534.6.7.1.1.4.4.3.1.0 = String:…

The information is stored in the APM_ApplicationTemplateSetting table or the APM_ApplicationSetting if overridden.It’s stored in a format of key/value pairs. 

Does this not work properly for any of your monitored servers or just one in particular. You may be experiancing this issue referenced here -> http://thwack.solarwinds.com/thread/33124

If the SQL Server is a named instance, then the instance name will need to be specified explicitly in each SQL User Experience component monitor settings. If it is not, then this could be the cause of the issue. Also, I notice that most (if not all) of the things you are monitoring are included in AppInsight for SQL. A new…

This should not take longer than a few minutes at most to complete. On the Exchange Server itself you will find a "RunWinRMConfigurator.log" file under "C:\ProgramData\Solarwinds\Logs\APM\". The log file contains all information and errors related to the WinRM configuration process. Either something obvious will stand out…

Exchange 2007 SP3 includes support for Server 2008 R2. As a general rule we recommend running SAM on Server 2008 R2. I'm also currently monitoring Exchange 2007 using this application template from my SAM 5.0 server running on Windows Server 2008 R2 in my lab without issue.…