The stability on this solution is rock solid. I will put money up against it. BigFix is absolutely unbelievably stable. We never had any data corruption of any kind while using it.

Regarding stability, I rate the solution a seven on ten. The solution requires a lot of customization. So, if you’re making a small change, you’ll need to ensure that everything is aligned with the change. 

If you make a small mistake, then it's gonna be a problem.

The product is stable.

It is very stable. You can trust and rely on an automated job. It will definitely work. You get a proper message if it is not working for any particular reason. It gives you a complete picture.

I give the stability of BigFix a nine out of ten. The solution is very stable.

It is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze.

It's been around for a while, according to what I've seen. It used to be an IBM product before the move to an HTC, so I'm pretty sure it doesn't have a lot of complications. It'll still be a pretty stable product moving on into the future.

For now, it seems like BigFix has been the most popular for server management.

I rate the solution a nine out of ten for stability.

BigFix is stable overall. However, like any software, you may encounter occasional issues, but they are manageable.

BigFix is reliable and stable, it is perfect.

Performance-wise is the best. When you have to do deployments you are sure that all the workstations will receive it, even though that there is sometimes a delay in reporting back to the server. The only time the deployment would not work is if the computer is decommissioned or not available.

The stability has been solid when I've used BigFix with customers in the past. In that space, I don't think everybody is doing as much innovation as in other areas in the endpoint management or security market. 

I delineate between those two because endpoint management is a different use case. I think it's probably become a lot more important since the pandemic started.

BigFix is stable. However, there have been a few minor issues, such as the relay's not reporting.

The solution is stable. The primary role of the solution is to patch the systems to the latest released security updates. We have not had any issues once we had deployed the solution correctly.

During our exploration of available solutions, we found that very few in the market offer comprehensive security features. In our evaluation of BigFix, we were particularly impressed with its VMware functionality, which far exceeded that of other solutions we considered. Rather than having to configure multiple solutions, BigFix provided us with basic security information and VMware management detection and response all in one. While the effectiveness of BigFix is certainly a key consideration, its ability to consolidate security features was a major factor in our decision to choose it.

I rate the stability of BigFix an eight out of ten.

BigFix is extremely stable.

I've been admining the system for two and a half years now and other than server side issues we have never had stability problems. My core system is four servers and they're not maxed out. We've never had any performance issues.

The solution is stable. 

Its stability is very good. It is a standard tool, and it is also one of the leading tools in the market.

Stability is incredible. A lot of times people will let it run forever without touching it because it just keeps going. Once you stand up the solution, there's very little that you have to do. Just the occasional update and that's it.

It is pretty stable and reliable. That's not a problem at all. 

This is a stable solution. The only issues that we have had in the past with BigFix is with the sizing. If you don't perform the right sizing of the BigFix server, you may have performance issues. We have had no major issues with the performance itself.

The stability is great! We have not experienced any issues. 

The solution is stable. I'd rate it eight out of ten. We've had no issues with stability. Performance-wise, it has been fine. 

One of the issues that my guys come across is it can take up to 48 hours before the Microsoft patches are available in BigFix since we are a day ahead in New Zealand. 

It's very stable.

It's extremely stable. 

The core capability is very strong and hasn't changed a lot. Sometimes it is harder than others to get to some of the newer features, mostly just because we have a very large install base, and so having the time to roll out new capabilities is hard. Overall the stability and the upper trend of the capability is very good.

The stability is excellent. I haven't had issues with BigFix crashing unexpectedly or anything like that.

It is very stable. We haven't had any issues on any downtime that inhibits our ability to get things out, so it's been pretty stable.

I give the stability an eight out of ten.

I have experienced good stability while using BigFix in Windows. However, it is not good with Linux.

It's very stable. We haven't had any major issues from it. Most times, we have false positives. Our people tell us that BigFix is doing something and we go back and look and it doesn't.

We've had no problems, it's a very stable solution. It's very well supported and has a big forum of users. So you always have a resource to reach out to.

We've actually fixed the patching by improving our patch application by almost 60%. We went from applying 6,000 patches manually to 34,000 on average a month.

It's been stable. I've used the product for seven years and I haven't had an issue that has brought things down. So it's been very stable.

Until our most recent information security system that we stood up, which is unrelated to BigFix, BigFix was our most solid system, in terms of how much engineering effort it requires to keep up and running, relative to the number of servers involved. It's a pretty solid system. We do run into bugs and interesting functional quirks, usually around how the endpoint agent reports into the relays. It mostly just takes care of itself, for the most part. We do have to do a little care and feeding, but it's mostly self-sufficient.

The stability is paramount. It has definitely reduced the need for multiple products down at the endpoint, it's reduced the number of agents needed at the endpoint, and overall because the product was created so many years ago when networks were not nearly as robust as they are now, the improvement of the product over time along with the improvement of the stability of large networks, has coincided. It is as stable today as when you could only transfer 15 bits across the line.

The solution is extremely stable and it communicates very well.

I think the current tool is fairly robust. We have ways of breaking it, though.

Overall it's a very stable solution.

We had problems with stability from the first use. There was network bandwidth outage when we deployed a huge application or a lot of security patches. This problem was solved by specific client settings and their management, and some changes to the architecture of the product.

Stability is excellent. It doesn't crash, it can handle whatever we throw at it. It does a good job with that. Other solutions that we've had haven't panned out that way.

Even at a very large number of endpoints, it's very stable.

The stability is generally pretty good. The one thing that we came across is the battle between load on endpoints and load on our servers and relays versus how quickly, effectively and reliably actions can be taken. I'd like to not have to take an action on a system while I'm working with someone and then have to say whether something will happen between five seconds or thirty minutes from that point. 

Stability is totally safe. We've been using it for years and years and it hasn't done us wrong.

It's stable. We occasionally run into hic-ups here and there. We've been working with BigFix for eight-plus years and occasionally things happen. 

It's very stable.

The stability is good overall. 

I have not had any issues that were due to the product itself. I have had issues that are user related, such as admins using incorrect installer in DMZ, and other external issues that impacted IBM BigFix, but not the product itself.

The installer for the BigFix agent is comprised of an MSI and a file called masthead.afxm, which is the file that contains configuration information such as the BigFix Server host name and a key. With only these two files, the agent has to be able to communicate with the BigFix Server on port 52311. If the agent cannot communicate over this port, it will fail to register and will never connect to the BigFix Server. In order to get around this, a file called clientsettings.cfg is included to configure the agent to talk to a different BigFix server called a relay. This relay would have the ports open to allow communication between the agent and the BigFix server. This is a very standard practice for devices in secured networks. So even though I have provided this install method and the users have been provided documentation, it still seems to get missed once in a while. Here is an article on this http://www-01.ibm.com/support/docview.wss?uid=swg21505838

At a site I worked at a while back, the user insisted that every support tech, help desk person and server admin be allowed to have console access to the BigFix infrastructure. This ended up being about 350 users which is way more than they had in other tools and it was strongly recommended that they do not do this and we only give it to people who were trained and would actually use it. This leads to issues with people not using the tool correctly (lack of training) and not understanding the tool. As part of the administrators for the tool, there was no way for us to provide training to the 350 users. This again is not a tool issue, but a process issue.

Couple other external issues we have seen that impacted BigFix

- Proxy issues stopped content from being downloaded to BigFix server

- SAN issues caused performance problems. BigFix can be very I/O intensive, so degradation in I/O can really bottleneck transactions and console performance.

I am sure I could think of a couple more, but usually these are not tool issues, just user/process problems.

The stability is great. Any product that can basically run itself, requires minimal intervention, and is self-healing is a great tool.

It's very stable. There's minimal maintenance on the server infrastructure itself.

The solution is generally stable although sometimes our customers will report some issues and it's not always easy to find the source. 

It's very stable. 

I believe the solution is very stable and we have never had an outage of the solution. Communication with our agents is always well-synchronized. Stability is very nice.

Stability is very good. We have no issues with it.

It is very stable.

It is a pretty stable product. There are problems only if you mess up during the installation. If you do it right, then everything is fine.

It's very stable.

Stability is solid. Very, very solid. We rarely have issues and if there are, it was usually due to old architecture issues, but we've taken care of that and since then, we really haven't had any.

Usually after upgrades, you have some hiccups but they're manageable. It's kind of common between products, after upgrades; either it is a learning curve or it could be a bug and then it's fixed in subsequent patches. So, nothing out of the ordinary, but it scales well.

We haven't encountered any issues with stability.

BigFix is a stable solution. We have not had any issues with it. 

Stability is good. It works well. When it works, it works great. It's pretty quick to respond.

It's stable. I've been running it for more than ten years and it's generally pretty good. 

We just ran into something, during the last update of version 9.5.3. We're still trying to figure out, if it was the update or not. But, we've had a couple of issues recently with some different things and as to how it's running, as far as the permissions go. Other than that, it has been great.

The stability is good.

Stability is good.

The stability of BigFix isn't bad.

Stability is great.

The stability is great.

It is very stable. Streaming, of course, will do it.

No stability issues. If relays are not configured correctly, then this can cause a performance issue. An occasional health check is needed to ensure the solution is running at peak performance.

I never had problems, so I think it's highly stable.

Stability is very good. We've had very little downtime.

The tool has been quite stable. It has improvements within each version, which have made it become better and more powerful.

Yes, occasionally we did.

Stability has not been an issue at all.

BigFix is a stable solution. You can deploy it and forget about it. 

No issues.

When it comes to stability, it is very stable and it has a robust infrastructure.

It's a stable solution. We have not had any issues.