We can set a maintenance window and push the patch.

I prefer writing scripts, doing software deployment, pushing it, and distributing applications in servers for the corner of the whole location. We download patches from Ivanti, and it collaborates with more than 700 products.

For third-party applications, we download the patches, set a role in our environment, and push it using the maintenance window time and activation date. For software deployment, we receive the service request to install and prepare scripts and then push it in many locations according and relevant to the service request for each location. The group or collection devices are affected by the policy.

Reporting is good as we used to be on local SCCM. It provides sufficient information to know how the patches have been deployed.

I like the product's Peer to Peer patching feature. 

The most valuable features are device management and support for upgrading applications. If I want to upgrade a version of an application, for example, Google Chrome, then I can create a task and push a Google Chrome update.

Ivanti Patch's most valuable features are the patch module and the package distribution.

This is an extremely robust product. It now has almost 20 years of history.

It is very easy to use, as well as extremely efficient and accurate. Most of our customers just set it and forget it. They install it, and it does all of the automatic patching, month after month.

The solution is a good product and I have heard that the interface is more friendly than that of Windows.

I have found the interface and ease of use valuable features. Additionally, it is very easy to patch VMs and other systems, such a Linux. We are able to do patches even without the internet manually.