G2

Gaurav B.

System Engineer

Computer Software

Enterprise (> 1000 emp.)

9/10/2026

Business partner of the seller or seller's competitor, not included in G2 scores.

"Reliable Batch Scheduling for Large Production Workloads"

5/5

What do you like best about Control-M?

What works best for us is having a single monitoring view for all our batch jobs. Setting up job chains with dependencies, prerequisites, and event triggers is straightforward once you get the hang of it. We run jobs across both Linux and Windows servers, and it handles cross-platform execution well without dropping triggers. The Batch Impact Manager is also helpful for tracking SLAs and flagging delayed jobs early before they affect downstream business processing. Review collected by and hosted on G2.com.

What do you dislike about Control-M?

The thick client GUI can feel heavy and slows down when you have thousands of active jobs running during peak hours. Also, the learning curve is pretty steep for new team members who aren't used to how Control-M handles conditions and quantitative resources. Upgrading agents across a large server fleet takes a lot of planning and coordination during maintenance windows, which can be time-consuming for the team. Review collected by and hosted on G2.com.

What problems is Control-M solving and how is that benefiting you?

Before using Control-M, we had scattered cron jobs and Windows Task Scheduler tasks running across different servers, which made tracking job failures difficult. Control-M centralized all our batch scheduling into one place, so we don't have to check servers individually. It has significantly cut down on manual job monitoring and helped us catch failed dependencies instantly before they derail morning batch processing. Review collected by and hosted on G2.com.