No more typing reviews! Try our Samantha, our new voice AI agent.

AutoSys Workload Automation vs BigFix comparison

Why PeerSpot?
Sponsored
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JAMS Scheduler
Sponsored
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
57
Ranking in other categories
Workload Automation (2nd)
AutoSys Workload Automation
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
Workload Automation (5th)
BigFix
Average Rating
8.6
Reviews Sentiment
6.4
Number of Reviews
100
Ranking in other categories
Configuration Management (9th), Endpoint Protection Platform (EPP) (21st), Patch Management (7th), Unified Endpoint Management (UEM) (10th), Autonomous Endpoint Management (7th)
 

Mindshare comparison

Workload Automation Mindshare Distribution
ProductMindshare (%)
AutoSys Workload Automation6.4%
Control-M10.1%
Automic Automation4.5%
Other79.0%
Workload Automation
Endpoint Protection Platform (EPP) Mindshare Distribution
ProductMindshare (%)
BigFix2.0%
Microsoft Defender for Endpoint6.4%
CrowdStrike Falcon5.5%
Other86.1%
Endpoint Protection Platform (EPP)
 

Featured Reviews

SP
Developer at a consultancy with 1,001-5,000 employees
Centralized scheduling has improved automation and reduces manual monitoring for complex workflows
The best features JAMS Scheduler offers are centralized job scheduling, dependency management, and monitoring. I also appreciate the alerts and retry options because they help us handle failures without constantly checking jobs manually. Centralized scheduling makes it easier to manage all our jobs from one place instead of maintaining multiple schedulers or scripts. Dependency management is especially useful for chaining workflows because JAMS Scheduler can automatically trigger the next job only when the required previous step completes successfully. Another useful feature is the monitoring and alerting. If a scheduled job fails or runs longer than expected, we can quickly identify it and take action, which is particularly helpful for production support and reducing manual monitoring. JAMS Scheduler has helped quite a bit with identifying common job failures, missed schedules, dependency issues, and execution errors. The alerts and job history make it easier to identify the failure point and take corrective action without manually checking every workflow. JAMS Scheduler's code-driven automation has been useful for handling more complex scheduling logic and workflows that go beyond simple time-based triggers. It is important for us because we can combine scripts, dependencies, conditions, and parameters to support different production scenarios without creating too much manual intervention.
PK
Assistant VP at a financial services firm with 10,001+ employees
Experience significant automation with robust integration and user-friendly interfaces
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancements in the R24 release. The web UI needs some improvement. Cloud integrations are limited to 25 or 30 configurable plugins and integrations to the cloud. They can improve in that area. They have separate tools, not AutoSys Workload Automation, such as Atomic and other SaaS-based solutions that can run inside the cloud. AutoSys Workload Automation can be configured in the cloud, but it requires a substantial number of VMs depending on the load. For on-premises deployment, it is a very good solution. They need to increase their footprint in the cloud and improve the web UI. They are making excellent progress in the R24 release.
InderjeetSingh4 - PeerSpot reviewer
Administrator at a tech vendor with 10,001+ employees
End-to-end automation has simplified patching and software deployment across thousands of servers
There is one feature in BigFix called the automation patch policy that requires enhancement. When an action is initiated through the patch policy, it appears on the console but arrives in chunks. When targeting hundreds of servers from the patch policy, the actions come in chunks such as ten out of six, ten out of nine, or ten out of fifteen. This fragmented approach creates a significant challenge for the patching team to monitor the action status. I would recommend that the development team provide a single action or one to two actions instead of multiple actions requiring individual monitoring. A broad status update could be provided to the client indicating the overall progress of the patch policy implementation rather than requiring monitoring of every individual action. This would reduce the bandwidth required by the team to track multiple actions on the console.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I didn't know about JAMS because I don't have a person with any challenges with the purchase administration. The feature or the user interface is user-friendly because of the readable icons or very descriptive icons. Though I'm a beginning user of JAMS, I had no issues using it."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."
"I appreciate JAMS for its readily available templates that allow me to create and deliver stand-up presentations within minutes quickly."
"This feature helps my team day-to-day by running hundreds and hundreds of jobs on JAMS in a timely fashion, which is extremely important and sensitive, providing a lot of reporting to the entire firm and beyond."
"JAMS positively impacts my organization because it helps make it easier to manage JD Edwards scheduled jobs and fills the gap that the JD Edwards application has with scheduling, resolving a lot of those issues."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"The planning capabilities are most valuable."
"We definitely can count on it being up all the time."
"We need to have things run in a very sequential order, so it is very useful that we can schedule the work flows."
"The CA workload agent has gotten much better. For our organization it's important for us to communicate in a secure fashion between the host and the other platforms, and we are able to do that with our CA product"
"We use it for a number of our clients, and so far, we have had great success with it because it works constantly and is pretty seamless, so you do not have to open up many support tickets."
"The most valuable feature of AutoSys Workload Automation is batch processing."
"The stability has been good in my experience."
"It has been my go-to tool for 28 something years, and it has not failed me yet."
"Running anything in crontab, you need to put a lot of logic into it to make it work. With this product, you don't have to worry about it. You have the schedule object where you put all the dates or holidays in it, and it does it for you."
"If you are using BigFix and you have the client installed on every machine, you are nearly always audit-safe from out of the box."
"Due to the automation, we've been able to prevent a lot of human errors with BigFix so it's reduced our help desk calls by 50%."
"This solution is giving us the results that it's meant for."
"I like the inventory and life cycle management feature."
"BigFix provides tremendous benefits to users and clients and provides a comprehensive view and broad features for users."
"The most valuable and essential features of BigFix are all of them, they are needed when serving the purpose of the desktop operation framework. We cannot run operations without patching or without having an appropriate mechanism for deploying software, et cetera. The features all serve their purpose for our use case."
"Once you get over the learning curve, it is pretty easy to use."
"The product is less costly when compared to other solutions, and this is a good solid solution for what we have paid."
 

Cons

"They recently switched to subscription-based pricing, which increased."
"I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
"JAMS doesn't allow us to implement SOC controls. We are a company that trades stocks on the New York Stock Exchange, so all our transactions are audited. It has a feature that saves the file for only a month but doesn't segregate the data between finance and SOC-related compliance."
"The cost has definitely gone up tremendously. That is where I do know, as much as the feature sets are there, and if the newly acquired company is going to be doing a pushback, they might just say, 'Do we still need to pay this much? Or at that point, should we look into an alternative?'"
"The JAMS automation code isn't so clean."
"For the most part, JAMS is very stable. Occasionally, if you leave multiple windows open over a period of time, it is necessary to end that task and restart."
"I want JAMS to implement a global search function."
"Once we realized how much we were leveraging this feature on the mainframe version, and that we wouldn’t have it on ESP-DE, we were a little disappointed."
"SQL server clustering is not supported."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"It needs more complex scheduling capabilities on the end points."
"However, when compared to other products in the market, it is still behind other solutions."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"AutoSys Workload Automation could improve the integration."
"The way that it was brought to us, in our initial setup, we had a lot of initial questions and they replied, "Well, set it up the way you want it." It was kind of confusing from an end-user support aspect, asking them what are the best practices."
"It can be improved speed-wise. They can make it a little bit light. If you do any query for servers in bulk, it can take some time. Similarly, creating a job can take some time."
"Still, you have to dance around and probably do some voodoo in order to get that data back."
"The product is quite buggy and complicated to use."
"I would like to see different types of reporting and the ability to integrate closer with the cloud."
"I'd like to see better API integration with BigFix. We have some tremendous API capability inside of CyFIR and the ability to take textual search results, for example, and bring that back into the BigFix dashboard. This would be of extreme interest to us and our customers."
"License management isn't quite as easy as it should be to deal with the licensing. You need to take the server down to import the new licenses which I find to be annoying."
"The self-service application seems to need some work to replace the client UI. There are a lot of pop-ups if you use a baseline as the object that you're setting to a workstation. Unless you're using web UI, the message is not customizable in the user notification."
"Relay selection and availability needs improvement as an incorrect relay selected can cause network chokes."
 

Pricing and Cost Advice

"For what it does, the product is priced very well."
"The product is reasonably priced, and we don't have any add-ons."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"Definitely check how many single processes you want to run and count them as jobs. That is how you would work out your pricing on JAMS. For example, if you're running a number of commands and you can put them all into one script and run that script, you can count that as one job."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"The pricing is reasonable."
"We paid to use the solution monthly."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"There is an annual license to use AutoSys Workload Automation."
"It is overpriced."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The price of this solution is reasonable and there is an annual license required."
"Validate how many agents you need beforehand."
"The tool's price continues to go up. The cost per endpoint can vary, ranging from approximately 30 to 80 dollars per year. Compared to other products, pricing is in the middle. You need to buy an additional database license, but most users already have it."
"There's not much big cost. We only have to pay the agents' cost for the server, and for the systems."
"The price of BigFix is better than the solutions. You are able to pay monthly or annually. There are not any hidden costs with BigFix. There is an additional cost for the SQL database."
"So, the pricing is slightly more expensive than the others. I have to keep buying licenses every time I add a new device."
"It might be about $23 a client."
"The price is very fair."
"We have a subscription-based contract with BigFix."
"The price of BigFix could be lower. However, I am always seeking a lower price."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
921,840 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Comms Service Provider
10%
Construction Company
9%
Manufacturing Company
9%
Financial Services Firm
30%
Outsourcing Company
9%
Manufacturing Company
7%
Retailer
5%
Financial Services Firm
13%
Manufacturing Company
10%
Outsourcing Company
10%
Comms Service Provider
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise18
Large Enterprise30
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise12
Large Enterprise68
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
My experience with pricing for JAMS Scheduler was good. The pricing was reasonable, and the vendor only charged us fo...
What needs improvement with JAMS?
JAMS Scheduler can be improved by sectioning off credentials and also the web functionality and setting that up.
What is your primary use case for JAMS?
My main use case for JAMS Scheduler is to trigger integrations as well as send out alerts and reports. For sending al...
How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful b...
What needs improvement with AutoSys Workload Automation?
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancement...
What is your experience regarding pricing and costs for BigFix?
I rate the price for BigFix as medium, neither low nor high.
What needs improvement with BigFix?
There is one feature in BigFix called the automation patch policy that requires enhancement. When an action is initia...
What is your primary use case for BigFix?
My current use case involves being one of the products and one of the clients implementing this tool.
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
Tivoli Endpoint Manager
 

Interactive Demo

 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
US Foods, Penn State, St Vincent's Health US Foods, Sabadell Bank, SunTrust, Australia Sydney, Stemac, Capgemini, WNS Global Services, Jebsen & Jessen, CenterBeam, Strauss, Christian Hospital Centre, Brit Insurance, Career Education Corporation
Find out what your peers are saying about BMC, JAMS Software, Broadcom and others in Workload Automation. Updated: November 2026.
921,840 professionals have used our research since 2012.