ElisabethZakes

Vic, if you can send me your case number, I'll get you an update on its progress.

Great! Glad it's working for you now.

For example, see Config Change Report - Compare Startup to Running Configs.

Replied offline.

For how to unmanage a node, see page 35 of the Administrator Guide: To unmanage nodes: Select the nodes you want to unmanage in the nodes list, and then click Nodes > Unmanage Selected Nodes. That section of the guide also explains what unmanaging a node does.

I'll contact you privately and get you to a sales engineer.

Not at present, but I've entered this as a feature request (and a good one!).

I'm sorry you didn't have a good experience with support on this issue. We do try to respond as quickly as possible and to look at all factors that may be contributing to the problem in an attempt to find the best solution for you. I'm glad Zeid was able to get you fixed up!

Just click on the link in my reply (the underlined words) and it'll take you to the post in question.

In the Report Writer, there are several historical reports. "Historical - Availability Details" might suit your purpose. There are variables for Average Response Time, Availability, and many others.

Matt, is that stored procedure anything you'd be willing to share in our Content Exchange area? Others might be able to benefit from your expertise.

We are considering translation of documentation. Timeline and specific languages will be based on demand.

Did you try Denny's suggestion above?

Sounds like you're in good shape, then. Just to clarify, Customer Service assists customers with licensing issues, while Support deals with any product-specific issues (installation, something not working quite right, etc.). Good luck with your adoption! :)

It's definitely in 2.5; see page 33 of the Administrator Guide, in the section on Templates: File Size Monitor This template measures the size of a file at the given file path. The statistic is the file size in bytes. Prerequisites: None. Credentials: Windows credential with read access to the network share.

Yes, please.

Did you use the search tool above the node list? If the resource is in a group, did you make sure you were looking in the appropriate group? (If you haven't already, check page 62 of the Administrator Guide for instructions on viewing node resources.)

Excellent workaround, and thanks for posting it so others can benefit from it!

Can you do an incremental upgrade to SQL 2005 first? That will be common ground between the Orion versions.

Since this is still an issue, you should probably open a support ticket to have a technician help you with your alerts directly.

Not directly, as you can from the Report Writer. In the web console, schedule the report to be sent by e-mail, and then you can copy/paste from the e-mail into Excel.

If you haven't already, do look over the requirements (page 8) and server sizing (page 9) in the Orion NPM Administrator Guide. For large installations, we highly recommend putting your SQL on a separate box from NPM, and possibly even dedicated just to the Orion DB.

I think a support ticket is in order so we can help you track this down directly.

Warbird, remember Denny's post here on using a SAN. The major issues are configuration and write speed. But you can run Orion with a SAN. Also see here for use of AWE.

A support representative will be calling you on Tuesday.

jjohnson, e-mails were sent. Please check your spam or junk folders for e-mail from SolarWinds. I've alerted the technician on the case.

The Help with regular expressions and config change reports thread has some insight on the Running vs Startup issue.

How can I put in a feature request for this. Post in the product-specific board under the Product Feature Requests heading (Forums » SolarWinds » Product Feature Requests); in this case, the Cirrus board.

If no one in the community has come up with an answer yet, you should probably open a support ticket.

mcampbell, Please upload your log file to Leapfile, and include the case number (97793). I'll make sure it gets looked at promptly.