SolarWinds offers strong stability capabilities. The majority of stability issues typically arise from the underlying operating system rather than SolarWinds itself. I would rate it eight out of ten.

I would rate the stability of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best.

SolarWinds is stable. I would rate it as ten out of ten.

The solutions’ stability is good.

When you first deploy a solution there will be problems from time to time. You will have to address the issues as they arise.

I rate the stability of SolarWinds Network Configuration Manager a six out of ten.

The stability of the solution is good. However, it was not always the best. There was an issue where the National Security of the USA was hacked through the solution.

Initially, we encountered sluggish performance, prompting us to reassess our system specifications. We realized that operating with only 8GB of RAM and a quad-core CPU wasn't sufficient for our needs. Consequently, we upgraded the RAM to 42GB and boosted the CPU performance. With these enhancements, we've achieved satisfactory performance.

It's stable. I've had an issue once or twice, but it's more related to Microsoft updates than anything else. I've had it happen once or twice over a period of a year or two, where one of my jobs got stuck.

So I back up my configs most every night and split my backups into multiple sessions so that I don't back up all the devices at once. I back up the core, or back up the edge, or back up the age, all different stations at different times. And then I found one of the jobs got stuck, which I'm not sure why, but I never did it before. So I suspect it's either another .NET update or a Windows security patch. And it's very inconsistent. As I said, it's so small and insignificant that I haven't worried about it because it doesn't present itself often.

It is a stable solution.

Platform stability is extremely good. A few areas of improvements required - better handling of NCM jobs failing - for example if an NCM job has multiple devices to be backed up, a detailed report/log of the success or failed status is required.

We have been using NCM for a long time, and many of the clients are using it. It's been stable for us. If my client is happy, I'm all happy.

The solution is stable.

I rate the stability of SolarWinds Network Configuration Manager a seven out of ten.

I think so far stability is going great.

SolarWinds Network Configuration Manager is very stable for now.

This solution is very stable. I have never had any real issues with stability.

When you deploy it with an external SQL server database that is properly managed and properly tuned, you won't experience any issues.

The solution is stable.

The stability of the solution is good. We haven't faced any issues.

It is stable. 

We do health checkups for the network devices. However, compared to NetBrain, the NCM health checkup is getting very bad.