We performed a comparison between Chef and OpenText Operations Orchestration based on real PeerSpot user reviews.
Find out what your peers are saying about Red Hat, Microsoft, HCLTech and others in Configuration Management."It has helped with compliance. It has helped to ensure that devices comply with the organization's policy. If they are not compliant and secure, they cannot access the resources."
"The ability to push applications on devices is valuable. You do not have to manually install applications one by one. If you like to use ten different applications, you do not have to manually go and download them one by one. Intune can compile a package for you, and then you can just push them from the admin center."
"The reporting and analytics features in Microsoft Intune have been a lifesaver."
"It is a very stable and scalable cloud-only solution."
"The most valuable features in Microsoft Intune for me are application deployment, Defender deployment, and asset management."
"The Microsoft Windows Autopilot and Defender policies are the most valuable features of this solution."
"The most valuable feature for us is the security, including risk analysis and patch management."
"It is a very helpful solution."
"The most valuable feature is the language that it uses: Ruby."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"The most valuable feature is automation."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"Manual deployments came to a halt completely. Server provisioning became lightning fast. Chef-docker enabled us to have fewer sets of source code for different purposes. Configuration management was a breeze and all the servers were as good as immutable servers."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"It has reduced the time taken to go to market. In the past, we were struggling with building these integrations, but now the process has sped up and there is an added advantage of quick delivery. In addition, it is an agent-less solution, which provides more flexibility in terms of multiple options."
"It's very stable. If you ask me for the success rate metrics, it's more than 90% for both."
"The product is good functionality-wise. I am impressed with the tool's flexibility in customization."
"When Microsoft Intune is used with different android devices it does not always work as it is supposed to."
"It would be helpful if there was proactive remediation."
"Onboarding of endpoint devices is not straightforward. The onboarding process was a little heavier than I thought it would be. That's the key improvement area. Obviously, the more control you have over the devices, the better it is."
"The reports that are generated aren't so great. They don't give a lot of meaning so far, but that could be down to user knowledge than the actual reporting side of things. I'm not a big user of it, but I was a bigger user of MaaS360, and we used to be able to run weekly and monthly reports. In the case of any deviations. we'd get a warning immediately. That's not so easy to do or to get in place for Intune. This could be just a user issue, but when I compare both, that's the only thing that's lacking for me."
"An area for improvement is the absence of seamless integration, particularly with external dashboards."
"In an upcoming release, I would like to see some kind of analytics report."
"The scalability could be improved, and like most other MDM products, Intune is good but not 100% there yet."
"It needs incorporation of Knox, ZeroTouch, etc."
"It is an old technology."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"The agent on the server sometimes acts finicky."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"There were a lot of scalability issues that we initially faced. Whenever I tried to deploy 100-200 endpoints, it became a huge challenge. We had to actually start using other tools like Tivoli Endpoint Management in order to patch the issues."
"The tool's UI needs to be improved. It needs to have better administration features in future releases."
"The price is an area that should be addressed because the price is high."
More OpenText Operations Orchestration Pricing and Cost Advice →
Chef is ranked 16th in Configuration Management with 18 reviews while OpenText Operations Orchestration is ranked 19th in Process Automation with 24 reviews. Chef is rated 8.0, while OpenText Operations Orchestration is rated 7.8. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of OpenText Operations Orchestration writes "HP OO blows away the competition, but has its fair share of flaws". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and SaltStack, whereas OpenText Operations Orchestration is most compared with Red Hat Ansible Automation Platform, Control-M, Camunda, Microsoft System Center Orchestrator and BigFix.
We monitor all Configuration Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
