We performed a comparison between Chef and OpenText ZENworks Configuration Management based on real PeerSpot user reviews.
Find out what your peers are saying about Red Hat, Microsoft, HCLTech and others in Configuration Management."One of the most valuable aspects of Microsoft Intune is its seamless integration with Azure Active Directory, offering capabilities akin to Group Policy Objects."
"Stable solution at a good price."
"Compliance and the policies that can be set are the most valuable features."
"I like that we can implement conditional access."
"Intune's unified endpoint management platform is invaluable."
"One of the best features is Windows Autopilot because if you change any of your devices, whatever security policies and compliance policies that applied can be easily migrated to the new devices. Windows Autopilot gives you that flexibility."
"One of the biggest advantages of Microsoft Intune is that it brings the management of Windows, macOS, iOS, Android, and even Linux under a single pane of glass."
"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."
"Chef recipes are easy to write and move across different servers and environments."
"Deployment has become quick and orchestration is now easy."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"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."
"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."
"The most valuable feature is the impact analysis."
"Helps me perform changes in connected infrastructure thanks to the discovery features."
"In terms of what can be improved, I am looking for better enhancements regarding Apple management, not only on the mobile device, but also on the laptop."
"The reporting could be improved, as it's pretty poor compared to other products of this type."
"One area for improvement is app deployment. Another is the Windows update rollout. If you're rolling out an object to a device that's offline, Intune stops trying to reach this device after it sits idle for a bit. We are forced to find a workaround that could help manage that."
"Intune's third-party patch management could be better. It should be easier for the average system admin to keep non-Microsoft applications updated."
"There can be delays in the deployment of new policies."
"The reporting needs to be a bit more interactive."
"The technical support could be improved."
"They need to integrate more with security options."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"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."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"Support and pricing for Chef could be improved."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"It is an old technology."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The native UI should be simplified because it is outdated and a little bit over-complicated."
More OpenText ZENworks Configuration Management Pricing and Cost Advice →
Earn 20 points
Chef is ranked 16th in Configuration Management with 18 reviews while OpenText ZENworks Configuration Management is ranked 20th in Configuration Management. Chef is rated 8.0, while OpenText ZENworks Configuration Management is rated 8.0. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of OpenText ZENworks Configuration Management writes "It allows us to deploy applications and primitive desktops globally. The upgrade cycle is very long". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and SaltStack, whereas OpenText ZENworks Configuration Management is most compared with Microsoft Configuration Manager and Quest KACE Systems Management.
See our list of best Configuration Management vendors.
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.
