aLTeReGo ✭✭✭✭✭

I'd recommend you look at this application template as well But to be perfectly honest I'm not aware of a method of determining the age of the oldest message in the queue. This may be possible via PowerShell but honestly I'm not sure. This would require some research.

The timezone on all Additional Polling Engines should be identical and consistent with the SQL server, regardless of which region of the world they reside.

This might be a good Template Feature Request.

These Performance Counters are still available in Windows 2012 as seen below on my server running Exchange 2013.

Not currently, but at some point in the future we may consider doing this automagically when/if we deprecate the legacy charts.

And while I am on a beef, where does the User Notes field populate when filled with information? It's not showing up on any details screen. Currently these fields are only viewable/accessible when editing the application or template, and can be optionally passed in an alert as an alert variable through the Advanced Alert…

A similar question to the developers. Why provide a field in the Component details screen called 'Message' and not make it available to the Administrator to populate with anything? The message field is used predominantly in script monitors as an optional message field for returning debug, diagnostic or message strings…

Since you won't be migrating your pollers, but rather installing new ones and assigning nodes to them you will not need to export any certificate information from any of your polling engines.

It sounds like in the Advanced Alert you have a "Trigger Action" defined to write to the Event Log, but no text has been defined.

Case # 10645 if anyone is interested.

It's on our road map, but not something we're currently working on immediately following the 5.5 release.

The metrics you seem to be trying to monitor are included in one or both of the following templates Exchange 2013 Mailbox Role Counters (Advanced)‌ Transport SMTP Receive: Average bytes/message This monitor shows the average number of message bytes per inbound message received. This determines sizes of messages being…

This is theoretically something that could be done using PowerShell as a Script Monitor.

I would recommend changing the polling method for this server to WMI to see if that resolves the issue. If that's not an possible for some reason I suggest opening a case with support so we can troubleshoot where/why this phantom CPU is appearing.

Do you have SP4 for Windows 2000 installed? Is all other information available to you via WMI beyond volumes? Have you tried enabling SNMP on that node and managing it that way instead?

Correct. You only need to alert on Application or Component monitor. Not both. Which you choose is dependant upon the level of specificity you require.

Thank you for bringing that to my attention. That statement was unfortunately incorrect. I have re-opened the feature request.

These queues are for temporary storage in the event the Orion server is unable to communicate with the SQL server. These queues should be low or empty at all times, but should not be deleted.

As suggested I would clear the browser cache and see if that resolves the issue. Also try another browser (FireFox/Chrome) to see if this is reproducible outside of IE. If it is, please try re-running the Web Site portion of the Configuration Wizard to see if that resolves the issue. If none of those steps help please open…

Have you run netstat on the Orion server and validated TCP Port 17777 is bound to 0.0.0.0? Have you tried using the IP address instead of the hostname to connect to the server? Lastly, are there any firewalls, or access control lists between your client and the Orion server that could be blocking TCP port 17777?

WPM 2.2, which is currently available as Release Candidate.

If you'd like to be alerted when the server is rebooted, open the Advanced Alert Manager on the Orion server and enable the out of the box alert labeled "Alert me when a node reboots"

My apologies, I misread that as 'Export', not 'Data Explorer'. The Data Explorer is not available for regular metrics. It's only available for items which have additional data behind them, such as Alerts, Syslog, SNMP Traps, Configuration Changes, etc..

Ensure you've upgrade to Orion 10.0 before upgrading to APM 3.5. The upgrade matrix below should help. If you continue to run into upgrade issues I would recommend opening a support ticket online and working through the issue with one of our Support Engineers.…

What kind of filters are you trying to configure? Are you talking about SNMP trap filters in Orion? If it's failing can you explain how? Do you get an error message? Can you post a screenshot?

Based on the screenshot provided it looks like you're unable to connect either WMI or RPC. Have you verified there is no firewall or router access control lists between the Orion server and the monitored server that could be blocking communications? Also, how is the WPSANSQL01 node managed in Orion? Is this node being…

The Unmanage Scheduling Utility allows you to unmanage nodes, interfaces, applications, etc on the regularly scheduled reoccurring basis. 

In the latest SAM 5.5 beta we've added Hardware Health Monitoring support for the Dell M1000e and HP BladeSystem Chassis. If you'd like to participate in the latest SAM beta you can sign-up here to download to give it a try.

Did you uninstall the previous version before you upgraded? HP's SIM Agent upgrade is a simple file replacement. You will need to uninstall then upgrade to repair any issues related to the agent software.

This is not an out-of-the-box application template that's included with SAM (any version). This script was uploaded by a customer to the SAM Content Exchange but is not in template format. This is the raw script itself that needs to be opened in notepad, then copied/pasted into SAM's Windows Script Monitor to run. The fact…