I used Microsoft System Center Configuration Manager (SCCM) before this solution. I switched because of CPO detection in the said solution.

I have not worked with a similar solution previously. We purchased Tanium
two to three years ago. It is being used by a different team, but we are still using BigFix. We want to replace BigFix, but we are not able to because we are more comfortable with it. So, we are continuing with BigFix.

I did not previously use a different solution. The company's been around for a long time, and it seems like everybody's just known BigFix to be one we used. I'm a bit newer to the company.

We were using Microsoft SCCM prior to BigFix. We switched toBigFix because we wanted to have a complete solution. Microsoft SCCM was lacking features, such as managing the network endpoints, the discovery of the endpoints, VMware functionality, and Linux patching.

I have used ManageEngine previously.

In my usage, I have found BigFix is more professional than ManageEngine. The reason that I'm saying this is when you deploy an application, you are sure and you are guaranteed that all workstations will receive it. However, for the ManageEngine, for some reason, you will find it may fail for 13 workstations. You might have to redeploy again, otherwise, you have to do it manually.

One of the positives of ManageEngine is it can be easy for users to deploy an application compared to BigFix.

I used a few competitors a while back, but I don't know what LANDESK is up to these days. They were a big player in the market, but I don't know what other contenders are out there now.

I have used other similar solutions previously. The main difference between the other solutions and BigFix is you can do more for a lesser price with BigFix. You can do more with less effort to get it up and work properly. Its broader support for different OS systems.

We initially switched because we had different solutions for all different platforms. We had one for MAC OS, we had one for Windows, and we weren't really using them that much so we were able to use it to manage all of them with a single tool instead of a bunch of different ones.

I have not worked with any other similar product.

Like many other small IT-companies, I patch the clients manually or by Windows Update. When you get a lot of clients to be patched, it's impossible to do it manually. You need a tool to do the job and you need documentation what you have done and when. If patch goes wrong, you must be able to identify that one very wuick and removed before it do to much damage. With BigFix, you get control and you know excactly the status of patches. If you use tools like Microsoft InTune to do the patch job, it's like sending Voyager 2 to Pluto - It felles like the patch is lost in space and you never know if it will ever send information back home what happends. With BigFix, more than 90% of you patches will dsitrbuted at first try and report back home that they found a safe harbour.

Intune only supports Windows and does not support other platforms like Unix and Linux. On the other hand, BigFix supports all platforms.

I'm also familiar with ECCM. However, it only patches Microsoft products. We've also used BatchPatch, used for pushing scripts, among other solutions.

We've used BigFix in the past with other companies so we knew BigFix was a superior tool. Ten years prior, the current tool we were using had a lot of overhead, was time-consuming, used a lot of resources, and time spent on it. We knew there were better tools out there. 

It's far superior and there's no comparison to SCCM. It is so easy to navigate in the console. Everything's in a single view within a fixlet or a task. You can tell what actions are taking place versus having to go through separate menus in your console to figure it out. Just that alone and knowing instantly what your environment looks like based off of content makes BigFix superior. 

We were using an old IBM solution framework solution and some custom scripts that we had built around the framework solution to do our software distribution. When BigFix came along, we went right into the BigFix framework.

When choosing a vendor, one thing that is always critical is, how much does it cost? It needs to be cost effective. Support is also one of the things that we look for. We have a small team so when we are looking at vendors, we want to know if they provide any training. Also, can any kind of training dollars be rolled into the product or can experts come on site to train? We also want to hear customer feedback about how the company or the product are doing at another company's site that is similar to ours.

We previously used Microsoft Windows Server Update Services, but we switched because we could not have a complete schedule for a server to receive updates. We have a few other features in BigFix, such as managing network endpoints, discovering endpoints, and a scanner. All of these features are not available with Microsoft and Linux patching.

Previously we were using the Microsoft solution, Windows Software Update Services. That's a very all or none solution which is not as granular. Regarding BigFix, I like that I can push out updates to systems within their patch window and make sure that they're complete and done within that patch window.

Our previous tool was the predecessor to BigFix, Tivoli Configuration Manager. We were entitled to migrate from TCM to BigFix, so it was kind of a no-brainer.

I previously used Symantec Altiris v6.5. We stopped using this product because the maintenance cost of the hardware infrastructure was too high. This solution requires high numbers of servers, as opposed to IBM BigFix.

We were using a different solution before this and we outgrew it. My company has gone through a period of hypergrowth and we went from handling just a few years ago 60 stores with maybe 500 endpoints in them, to 1600 stores now with tens of thousands of endpoints. So we knew we needed a new solution because the one we had just kept breaking, over and over.

I know how to use them all. I have used Asterisk and other solutions, but I got used to BigFix. BigFix is pretty straightforward.

I haven't messed with SCCM too much. There's a lot of things that are desirable in SCCM regarding scalability. There are lots of workflows that exist that SCCM is pretty universally used and can make things happen instantly. It can also help with a lot of the zero configuration, zero-touch computerization things but we get to get a little more specific with BigFix. We can employ a lot of things from all kinds of different sources to help tailor our solutions and we have better functionality with Mac and Lenox.

Our previous solution was extremely unstable. We had a lot of downtime and the inability to reach clients. We ended up choosing BigFix because it was already in an aspect of our organization, and so it was easy to adopt for our endpoints.

At the current site, they were using WSUS to patch the Windows servers and native tools for the AIX, Red Hat, and Solaris environments. Although these tools were “doing the job”, there was no easy reporting capabilities out of any of them. SCCM was also used in the Windows server environment at one point, but due to a major issue that was caused, it was removed from the servers.

For the extra data that IBM BigFix collects, there are other tools that provide the information, but required logging into the different tool consoles to gather and then manual consolidation.

Currently, we have our solution and we put in the BigFix solution. It was all because of the PCI compliance. We got a new security team in and they were completely focused on PCI. The previous solution didn't quite meet the requirements that made it easy. Now with BigFix, it's a lot more straightforward.

We switched to BigFix mainly because of scalability and for centralizing the work that we did, rather than being distributed. From what I know of SCCM, and the little that I've used it, the granularity that relevance an ActionScript allows you over the endpoint, and the information coming back from the endpoint is fairly significant compared to the work that you would have to do to script all that out in SCCM to get that information back.

We're always looking for innovation and the most efficient and effective way to serve our client base. BigFix came up on our radar as part of that continual enhancement search.

No other tools were used.

I came into the company and it was already there. So, I'm not sure about previous solutions.

Actually, we had all the tools and we pulled them out, after which we went to BigFix. The reason why we chose this solution is because the government paid for it.

I haven't used a previous solution as such. I worked at a previous company, moved to the current company I am employed at now, and saw the process and how different it was.

Coming from a company that utilized BigFix, I knew that there was a better way here, and I pushed hard to get BigFix implemented. They went on my recommendation, spent the money, and we have it in place. It's been in place for almost two years now.

We weren't previously using a solution, so we knew we had to invest in one. We brought in a bunch of different solutions and BigFix was the one that won out. 

It goes back to reliability. I was in this company before they started using BigFix. We broke it over and over on our old endpoint system and it was just getting to the point where it wasn't even saving us time anymore. That's how we knew we had to invest in a new solution.

We were using HPE Server Automation, which we were formerly using to automate most of the Linux patching. We were using HPE SA for our automation. It automates but it doesn't have the feature as to where we can back out the patches that were pushed and BigFix offers that to us.

In my opinion, trust and reputation are the most important criteria when selecting a vendor. IBM is known for that.

We did a proof of concept, looked at the other competitors and after scaling all of them on a matrix, IBM ended up being the best option for us.

The most important criteria while selecting a vendor are the product's stability, relationship with the support team, salesperson and technicians.

We did an audit. A PCI audit. We were looking for reliability. Also cost and support were considerations.

We started with SCCM and decided to switch because of inaccurate reporting, limited OS support, and we were unable to patch remote endpoints.

Not really, I have been using multiple tools like BigFix/SCCM/Tanium for vulnerability remediation/inventory management. I never really switched from any other tool, but used them in parallel for different projects.

We switched to BigFix because of the scalability and because it can be used across multiple platforms.

I initially onboarded with Microsoft SCCM. The user interface leaves a lot to be desired, performance impact as you go above 10,000 endpoints and also maintenance tasks like setting up of distribution points are not available at the click of a button.

The most important factor while choosing a vendor is how much profit we can make after selling the solution. Secondly, how successful could I make the solution in the marketplace. The third factor would be the level of support from the provider.

Yes, Itelligence Germany uses HP automation and we had a pilot implementation.

When considering a solution the criteria we consider are the features, whether the specific tool provided by that vendor will cater to our services or our requirements. Second, we look into the credibility of the OEM. Third, is the cost.

In my previous profession, we used SCCM from Microsoft, and I am familiar with NetApp Storage and Windows.