Ivanti Endpoint Manager increases user and IT productivity by helping IT administrators gather detailed device data, automate software and OS deployments, and quickly fix user issues.
N/A
Progress Chef
Score 6.5 out of 10
N/A
Chef IT infrastructure automation suites were developed by Chef Software in Seattle and acquired by Progress Software in September 2020. The Chef Enterprise Automation Stack is an integrated suite of automation technologies presented as a solution for delivering change quickly, repeatedly, and securely over every application's lifecycle. The Chef Effortless Infrastructure Suit is an integrated suite of automation technologies to codify infrastructure, security, and compliance, as well as…
There is no direct replacement for the on-prem Ivanti [Unified Endpoint Manager (formerly LANDESK Management Suite)] solution. Ivanti has a companion product called Neurons, but that is in additional cost, and requires configuration with your on-prem [Unified Endpoint Manager] instance to perform basic functions. If cloud-based is a requirement for your organization, this is likely a dealbreaker. You can implement [Unified Endpoint Manager] in a cloud instance such as AWS, but the support for this appears limited. If on-prem is not an issue for you, this is a great tool for device management. It has robust features, impressive inventory, massive customization options, and excellent vendor support. If Patch Management is a problem in your company right now, this is the first product I would evaluate.
Chef is a fantastic tool for automating software deployments that aren't able to be containerized. It's more developer-oriented than its other competitors and thus allows you to do more with it. The Chef Infra Server software is rock-solid and has been extremely stable in our experience. I would definitely recommend its use if you're looking for an automation framework. And it also offers InSpec which is a very good tool for testing your infrastructure to ensure it deployed as intended.
Patch(Security) is done really well. You can use roll out projects or built-in automation as well as the use of groups and scopes to design pilot and other use cases.
It takes a solid inventory of what you have of your endpoints and can do an agentless scan as well if you need to collect data that way as well.
Provisioning is rather simple and even allows you to use other products' software for the image or the built-in if you wish to do so.
Software distribution works well and has a lot flexibility built into the module.
Setup - Boy it is a pain to configure everything correctly. Be aware that you'll probably be giving an AD service account some God rights to get everything working....and security just loves that....
Cost - Boy you have to pay for everything. I suppose it lets you buy into just what you want but having repeated items go through procurement is a pain if your procurement branch is a pain.
Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.
We are happy with the product but the support and development process is far superior to any other company we have worked with. Having a good support structure is very important in today's marketplace of products that do so many things and have so many robust options and capabilities. We are very satisfied with our contract, pricing, support and product execution.
Items are logically laid out and most are easy to find. The more advanced stuff can be trickier, but it is still not hard to find. There are a lot of options though, so remembering where some settings are, especially if you do not alter them often, can take a minute, but you will get to them fairly qiickly.
The suite of tools is very powerful. The ability to create custom modules allows for unlimited potential for managing all aspects of a system. However, there is pretty significant learning curve with the toolset. It currently takes approx 3-4 months for new engineers to feel comfortable with our implementation
It loads quick enough for basically all our systems. Because we have this for local dev environments, speed isn't really a big issue here. Yes, depending on the system, sometimes it does take a relatively long time, but it's not an issue for me. One thing that is annoying is that if I want to make a small change to a cookbook and re-run the Chef client, I can't just make the change in the cache and run it. I have to do the whole process of updating the server.
TRM\TAM support has been generally very good. Getting reported bug fixes, design changes, UX problems resolved has been a pain. It is often difficult to get problems escalated beyond the TRM\TAM level. Support is fantastic when you can get it, getting it can often require more work than it should, and that is probably our biggest issue.
Support for Chef is easily available for fee or through the open source community as most the issues you will face will have been addressed through the Chef developer community forums. The documentation for Chef is moderate to great and easily readable.
It's been many years since I did a full evaluation of other products but at the time we purchased it, the main competitors were Microsoft's SMS and Alteris. SMS just looked horribly ugly and complicated (which fit in very well with Microsoft's other server tools) and Alteris looked okay but had a piecemeal approach where even a basic deployment meant purchasing a half dozen or more components. LANDesk had one bundle for all the tools we were looking for and had a great interface for presenting the data.
We considered the three leading competitors in the field: Chef, Puppet and Ansible. Ansible is a very strong competitor and has a nice degree of flexibility in that it does not require a client install. Instead the configuration is delivered by SSH which is very simple. Puppet seems like it has fallen off the pace of the competition and lacked the strong community offered by Chef. We chose Chef because of the strong support by the company and the dynamic and deep community support.
The entire professional services team was great to work with. The curriculum was tailored to our specific use cases. The group we worked with were very responsive, listened to our feedback, was very easy to schedule and accommodate. I cannot say enough good things about our professional services experience
Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.
