Ivanti Patch for Linux, UNIX, Mac, powered by Heat, swiftly detects vulnerabilities in today’s environment, from workstation to data center. And it deploys expertly pretested patches automatically, helping organizations to patch with more efficiency and efficacy.
Ivanti Patch for Linux, UNIX, Mac prices typically range from $24 to $30 per device annually, depending on the volume and specific requirements. Users frequently highlight the cost-effectiveness and comprehensive patch management capabilities it provides for enterprise environments, making it a competitive option for IT departments managing diverse operating systems.
We use Ivanti Patch to develop our website and post that website in the Linux OS, which is Ubuntu 20.04. With the software, we used to install Apache, MySQL, and other dependencies.
The website development section is the most valuable feature of the solution. We have clients in the United States and the United Kingdom. We used to develop products and program the solution for them.
The better way to improve the solution is by working on an area where it lacks, which includes the migration part. Currently, on Amazon AWS, we have hosted all the websites. It is fine to migrate from AWS to another platform, like Azure or Pantheon.
I feel there is room for improvement when it comes to the migration part and its integration with AWS.
I have been using Ivanti Patch for around six years. I work with Ivanti's Ubuntu 20.04.
It is a stable product.
There is no huge traffic for our websites, so we don't concentrate on scalability.
Including backend users, there will be around 25 to 40 users of the solution in my company.
The tool is used on a daily basis. One of our clients in one of the European countries has around 2,000 websites, so we migrate on a daily basis or at least once or twice a week.
As for technical support, we don't use it since we also provide technical support for the solution. Ivanti's technical support contacts us for any technical queries. We don't rely on technical support from Ivanti.
The initial setup is straightforward.
The time taken for deployment for the website depends on the website code files and database. It may take four hours to eight hours for a single site to migrate from another solution.
We used to do the migration from the cloud only and not on-premises.
For deployment, we used to compress the code files, and using SFTP, we used to transfer the files. We then configure the same with that, and after transferring the code files, we used to have the UAT, staging, and production URL. Once everything is fine, we will switch the DNS for the live website.
For the deployment and maintenance, we need support from the client's side and from the management side to make the DNS switch. We also need help from third-party vendors to provide access.
The solution is not expensive. It is cheaper than other solutions. The solution is open-source, so we do not need any licensing.
I would tell those planning to use the solution not to attach anything on the live production website since it may cause the website to go down. Whatever you do, you do on the UAT or the staging side. Once everything's fine, then test the production code file in the database. Take precautionary methods to test the live website.
Overall, I rate the solution a nine out of ten.
