Better protect against threats that stem from vulnerabilities in third-party applications.
Improve protection against threats that stem from vulnerabilities in third-party applications by extending Intune with risk-based third-party patch publishing – without any additional infrastructure.
Ivanti Neurons Patch for Intune was previously known as Ivanti Patch for Windows, Patch for Windows, Shavlik Patch for Windows.
Presbyterian Church
We deliver a patch each month, a security update, and we can supersede and remove patches.
I'm in system engineering. The solution is deployed on-premises.
There are six people in our team who are working with the DSM servers. We also have first-level support. They have access to the web application of DSM, and they only have limited access to that.
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.
I have used this solution for a year and a half.
It's stable.
It's scalable between servers.
You can set the number of admins in the DSM console and give them other rights.
It's a difficult configuration because you need to install many servers in a location, and you have to install the primary server in the main location. You have to set a secure network between servers, and there are many products to define the application at the end.
You can make the script in one day, test it, and then distribute it in the location. You need to wait one hour for it to be distributed in the whole location, and then you can test it. After you test it locally in a test machine, you can test it in some groups globally.
You can ask the customer, and when you need to roll out the application, you will be agreed about one week later. You set the rollout at that date. Then, you follow the distribution and compliance policy for the devices. After that, you can close your request.
Preparing the script, testing, and distribution is affected by the policy, and you have to follow compliance. We have four or five main staff members for deployment.
I previously worked with SCCM. Ivanti offers good configuration for patches.
I would rate this solution as nine out of ten.
I would recommend this solution to those who want to start using it.
