aLTeReGo ✭✭✭✭✭

I'm glad we would help. We've made improvements to some of SAM's email monitoring capabilities in the latest beta so you're no longer required to use the same credentials for both sending and receiving the email. You can sing-up here to download the latest SAM beta and try it out for yourself. We'd love your feedback.

.regarding NCM, for example binary config backup, i will have to define the IP address of config storage device. since its a single IP address, i cant use HA and will have to point it to a single server. There are a variety of different high availability options available for making NCM's binary storage redundant. The most…

The items you reference in your screenshot above fall under the Property Type "APM: Component", which should be covered out-of-the-box by the "Alert me when a component goes into warning or critical state" or "Alert me when an application goes into warning or critical state" alerts. There is no need to create separate…

I apologize to the community but I had to delete SKerley's posting as it violated the Thwack terms of agreement. The buddy drop that was provided to SKerley is not an officially supported fix, and as such cannot be publicly distributed. If other members of the community are experiencing the same issue as described above I…

Documentation error that will be corrected by Bronx‌. This should read that this component was removed, not that it was added. Thank you for bringing this to our attention Manilyn Ramos‌.

The problem is most likely an issue with credentials/permissions or firewall policy/access control lists. I recommend you open a case with support so we can get a look at the diagnostics to determine what exactly the problem is.

Good to hear. If you continuing to have a problem restarting the service as the trigger action of the Advanced Alert Manager I recommend opening a case with support.

utildayael in another thread was able to solve similar issues he was having by increasing the number of concurrent users, max shells per-user, and memory per-shell utildayael wrote: So in short, adjust your WINRM settings to have 20 MaxConcurrentUsers, 20 MaxShellsPerUser, and 512MB for MaxMemoryPerShellMB. This completely…

Ahh, that's much better! Registering "NetflowCOMInterop.dll" solved the problem. You guys are really on top of it. Thanks again for all your help.

Yes, though step #4 is not necessary.

@"hebron1212" wrote:@"aLTeReGo" This link requires a login. My support login doesn't work. Any way to make it public? Steve I'm working now with InfoDev to determine where this KB was moved. 

Strorage servers rule... Yeah, I noticed that right after posting and changed it, but thanks for pointing it out to everyone. JK

PowerShell scripts are not inherently universal between local and remote execution. The component you are referencing is specifically calling the remote invoke command in the following code block. This script would need to be significantly altered to collect information locally, rather than rely on Exchange's PowerShell…

It may be that your maintenance has expired, or is due to expire very soon. If neither of these are the case you can direct message me here on Thwack with your SWID and I'll dig into why 6.0.1 is not appearing in your Customer Portal.

In Perfmon on target cluster node you should be able to see exactly which resource is failing. If your environment is working fine with these occasional errors you can disable thresholds for this component monitor or increase current critical threshold (greater than 3).

Yes. This can be done using the Multiple Object Chart.

Damn straight! English teacher, look at me now!

ariabell, if looks like you've been working with Cooper. I'll have someone from sales reach out to you shortly to schedule some time for you to work through this issue with an SE. 

It sounds like what you're seeing is normal behavior. The Windows Event Log Monitor as configured is telling you there are Errors in the Application Event Log. This is why it's "Red". The Messages you're seeing are the message details of those events. E.G. * LDAP authentication on interface is Event ID 4343. * "Unable to…

I you can, I would recommend truncating the SNMP Traps from SQL Management Studio or Database Manager then manually re-running database maintenance again. Truncate Table TrapsTruncate Table TrapVarBinds

Yes. That is correct.

Sure. The following blog posting includes a screenshot and a brief description.

If RPC is working then would I suggest using that instead.

For others who might be following this thread, we're tracking this bug internally as FB88947

That would be correct, yet you continue to receive incorrect hardware information for the server that is in distress? If that's the case please open a case with support as this is not normal behavior. We will need to look through your diagnostics to determine the cause of the issue. When opening your case please reference…

So as not to overwhelm WAN links, the agent upgrade process limits itself to 10 Agents at a time, meaning that only 10 Agents will be upgraded in parallel while the remaining agents sit in a queue until one or more agents have been successfully upgraded or timed out, freeing up one of the 10 slots. While on a good local…

Only warning and critical thresholds are related to sustained threshold conditions. Most every SAM component monitor type already has retry mechanisms built-in to reduce potential false positive "down" status alerts from occurring.

From the SAM Administrators Guide -> http://www.solarwinds.com/documentation/en/flarehelp/SAM/default.htm#SAM Template Reference/OrionAPMAGTemplateApache.htm Configuring Apache to allow access to the server-status page: * Log on to your Apache server using an SSH or telnet client. * Grant yourself root permissions (su…

The script would be a simple batch file comprised of the following command del c:\windows\temp\jet*.tmp /Q /S

Have you tried using the following Macros as part of the alert notification? They should tell which group member that's down. ${GroupMemberDisplayName} ${GroupMemberDisplayNamePlural} ${GroupMemberFullName} ${GroupMemberName} ${GroupMemberStatusName}