Ivanti Neurons Patch for Intune is an effective tool designed for seamless patch management, catering to systems without internet connectivity while offering application upgrades, device management, and compatibility with numerous third-party applications.
| Product | Mindshare (%) |
|---|---|
| Ivanti Neurons Patch for Intune | 2.4% |
| NinjaOne | 7.5% |
| Microsoft Configuration Manager | 7.0% |
| Other | 83.1% |
| Company Size | Count |
|---|---|
| Small Business | 2 |
| Midsize Enterprise | 4 |
| Large Enterprise | 5 |
| Company Size | Count |
|---|---|
| Small Business | 50 |
| Midsize Enterprise | 25 |
| Large Enterprise | 41 |
Ivanti Neurons Patch for Intune simplifies patch management with its user-friendly design, supporting devices and offering robust automation for software deployment. Users can manage patches for over 700 products, enhance security and system performance, and leverage peer-to-peer patching. It enables users to efficiently manage updates using maintenance windows and activation dates across diverse environments. Reporting capabilities and inventory listing facilitate improved oversight, while allowing collaboration with IT teams to optimize patching routines and device management. It's also used for tasks like application deployment, file management, and USB blocking. While improvements are needed in update stability, documentation, and integration with cloud services, its strengths lie in automated and comprehensive patch management.
What are the main features?In industries like IT, healthcare, and finance, Ivanti Neurons Patch for Intune is instrumental in managing monthly security updates and ensuring system compliance. Organizations rely on its automation and comprehensive patch management to conduct thorough testing and maintain security standards across server groups.
Ivanti Neurons Patch for Intune was previously known as Ivanti Patch for Windows, Patch for Windows, Shavlik Patch for Windows.
Presbyterian Church
| Author info | Rating | Review Summary |
|---|---|---|
| IT Administrator at FPT Software Strategic Unit no 17 | 3.5 | I used Ivanti Neurons Patch for Intune primarily to update servers, appreciating the inventory list feature for software checks. However, the documentation needs improvement, as it was confusing during patching issues, often requiring technical support for resolution. |
| Senior Technology Consultant at SoftwareONE | 3.5 | We use Ivanti Neurons Patch for Intune primarily for feature and quality updates, testing with pilot groups before wider deployment. The reporting feature is effective, though we have encountered issues with on-premises infrastructure. There's no ROI or cloud provider data shared. |
| Information Technology System Engineer at DRÄXLMAIER Group | 4.5 | I work in system engineering, managing monthly patches and security updates with Ivanti Neurons Patch for Intune on-premises. We find it valuable for setting maintenance windows, scripting, and deploying software, collaborating with over 700 products. Previously, I used SCCM. |
| Systems Engineering Manager at NEC Software Solutions | 4.0 | I use Ivanti Neurons Patch for Intune to handle the security patching of Windows devices. However, I've encountered stability issues during patching, which need improvement. I haven't used other solutions, so my experience is limited to this tool. |
| Technology Solution Consultant at DWP Technologies | 4.0 | I appreciate Ivanti Neurons Patch for Intune's Peer to Peer patching feature, but I find its support and configuration lacking. Additionally, the product needs better scalability. I haven't used or considered any other solutions, and no specific cloud provider is mentioned. |
| Sr. Administartor at a computer software company with 1,001-5,000 employees | 3.5 | I find Ivanti Patch useful for device management and application upgrades, and it's stable. However, the initial setup is complex, and reporting, especially for compliance, needs significant improvement. This critical gap in presentable compliance data is leading me to seek a replacement. |
| Sr. System Admin at a manufacturing company with 201-500 employees | 4.0 | I find Ivanti Patch's patch module and package distribution valuable. After six years, I rate this stable, scalable solution 8/10, though it could improve cloud integration. Setup was easy, and it's superior to others. |
| Sales Manager at Nextlevel IP | 4.0 | I use Ivanti Patch for Windows for server patching. It's a good product with a friendly interface, but I find its pricing quite high. Overall, I rate it an excellent eight out of ten. |
| Infrastructure Systems Engineer at a tech services company with 201-500 employees | 4.0 | I find this solution valuable for its easy interface and patching of VMs and Linux, even offline. Setup was easy, it's affordable, and support is good. My main concern is occasional update issues after release. |
| Group Chairman at Unixpac | 5.0 | As a reseller, I confidently recommend this robust, easy-to-use, and highly efficient automated patching solution. It's stable, scalable, and setup is straightforward, outperforming cumbersome alternatives, despite occasional requests for non-existent features. |
Positive
The solution is used for certain features or quality updates. Testing is conducted before deployment to the entire company pilot groups, encompassing different user profiles, work methodologies, and departments. Once the local IT team has approved the patching phase, we configure RINs to update other server groups on a service-by-service basis.
Reporting is good as we used to be on local SCCM. It provides sufficient information to know how the patches have been deployed.
There are some issues in the on-premises infrastructure of the clients.
When implementing the configuration, such as transitioning from SCCM to Microsoft Intune, you may encounter issues with SCCM clients accessing Windows update policies. You can choose to deploy updates from either assisted systems or Intune. The capability may not always function, prioritizing cloud-based updates over hybrid mode configurations.
I rate the solution’s stability an eight out of ten.
The Microsoft component’s detection of the program’s usage is not always accurate for our audio devices. We have to escalate the issue through multiple departments until the department resolves it. We have provided detailed information to support our claim, but it seems this information is not always effectively communicated between departments. Additionally, the department assigned to handle our case may not be fully aware of the information we have already gathered and may require us to repeat testing unnecessarily.
The initial setup timeline varies depending on the client's availability and cooperation.
I provide the customer with the steps to follow, and they follow their scheduling and procedures. I also provide the information to the people involved in the pilot. My role is solely to provide a technical approach. The client decides how to handle communications, reputation management, etc. I provide a technical perspective.
The solution’s effectiveness depends on the reliability of the computers and their agents. If the computers are not functioning properly, the agents may not receive policies from the cloud, and patches may not be deployed as expected. The time it takes for policies to reach computers and be executed can vary depending on the specific circumstances. While the cloud component of the solution is consistently reliable, the client-side components can be more unpredictable.
They can do their on-premises patching capabilities in Intune if they have a well-established and functioning IT infrastructure. Similarly, implementing a patching solution from Intune is very easy for new organizations starting from scratch.
Overall, I rate the solution a seven out of ten.
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.
We use the solution for security patching of Windows devices.
I have been using the solution for two years.
The tool is scalable.
The solution's deployment is straightforward and can be done in a week. We have a team of 10 engineers who work on the deployment.
A consultancy helped us with the solution's implementation.
The license can get expensive if you have a lot of nodes.
I rate Ivanti Neurons Patch for Intune an eight out of ten. You must be mindful of your infrastructure and ensure the tool meets your requirements.
I like the product's Peer to Peer patching feature.
The product's support and configuration need to improve. It needs to be more scalable.
The tool is stable.
The tool's setup is easy.
The solution is expensive compared to other products.
I would rate the product an eight out of ten.
This product has many use cases including device management, Windows patching, deploying applications, copying files to multiple systems, and USB blocking.
This product helps us to create a streamlined process and it is working as expected.
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.
The reporting is an area that can be improved, which is why we are looking for a replacement. The reports have to show the compliance level of the patching, which Ivanti does not provide.
We need reports that are both good and presentable.
This is a stable product.
Ivanti scales according to the number of licenses. We have not had an issue scaling.
We have more than 800 users who are supported by our IT team of approximately 10 people.
Technical support is through the vendor and it is fine. We have not faced any issues with them.
The initial setup is complex. If I want to send a report then it is very complex. The reports are not easy to understand and not presentable. There are many manual steps that are required.
I was not with the company when Ivanti was deployed. It was done with help through the OEM.
When a patch is released then we need to update it. Otherwise, there is no maintenance required.
We are looking for a product to replace Ivanti and are evaluating different solutions with similar functionality. Right now, I am in the process of evaluating ManageEngine to compare both of the products.
My advice for anybody who is considering this product is that it is good enough for many situations but if you require a dashboard or reports to show your compliance level, then it is not there. In that case, you have to think about other options.
I would rate this solution a seven out of ten.
Ivanti Patch's most valuable features are the patch module and the package distribution.
Ivanti Patch could be improved with better integration with other cloud solutions.
I've been using Ivanti Patch for over six years.
Ivanti Patch's stability is pretty good.
Ivanti Patch is pretty scalable.
The initial setup was straightforward.
Ivanti Patch is far better than other solutions, and I would give it a rating of eight out of ten.
We mainly use the solution for patching Windows servers.
The solution is a good product and I have heard that the interface is more friendly than that of Windows.
The pricing is a bit steep, although, as we can understand the features concerning the interface, it may be commensurate with the product's value.
The product is geared towards really large enterprises, such as those of our customers. We act as integrators, partners of Cisco, meaning we provide customer service. We are resellers, not end-users. We exclusively provide patches using the client's console. I tried to be a partner of Ivanti and, from this vantage point, the quotes are, perhaps, a bit high.
I believe Windows to be free, included in the server license. Regarding the price, I would consider the product to be very good. I see no issues with it and consider it to be excellent. Its features are very complete.
I have been using Ivanti Patch for Windows for around two years.
While the price is a bit high, it may be equitable with the features one gets with the product, such as that involving the interface.
I rate Ivanti Patch for Windows as an eight out of ten.
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.
There are times when there is an update that causes some issues. These issues should be sorted out before the release.
I have been using this solution for approximately one year.
The solution is stable.
The technical support has been good.
The initial setup is very easy.
The solution is affordable.
I have evaluated ManageEngine Patch.
I rate Ivanti Patch for Windows an eight out of ten.
We are a reseller of this technology and not end-users.
Our clients use it to for automatically patching their software.
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.
Customers sometimes ask about non-existent features, and we pass these requests on to Ivanti.
I have worked with Ivanti since 2004.
I have never had negative feedback from a customer about something that didn't work.
When there has been feedback, it is about the patches themselves. This is a patching product that grabs available patches for a given application. For example, if an application from Adobe has a problem in the patch then it might manifest itself. However, that is the result of the patch and not the patching solution that was at fault.
Scalability has not been an issue. We have clients with as few as five systems and clients with as many as 30,000.
Occasionally, we have to use technical support. We don't normally have problems but sometimes customers will ask about non-existing features and want to know if there is a workaround available. This is typically when we reach out to them. In our experience, they have been pretty good.
We have had experience with our clients using similar products like BigFix and the SolarWinds Patch Manager. We assisted them in switching to Ivanti because their previous solution was too cumbersome or too complicated.
There have been other solutions from vendors such as Kaspersky and IBM, as well. We stay focused on Ivanti because we are confident in the product.
The initial setup is very straightforward and it takes just minutes to deploy.
There are two versions of this product available. One of them is complete and standalone, which comes with its own patching engine and does the scanning from a selected workstation. The other version taps into Microsoft SCCM, so you have to have the SCCM process running, and then it will just augment it with third-party applications.
The one that works with SCCM takes perhaps 15 to 20 minutes to deploy, whereas the standalone product takes about ten minutes longer.
Most of our customers take this product "as is" and install it themselves. Our after-sales support is minimal because they usually know how to use it.
The price depends on which version is being licensed. For the one that works with SCCM, it is relatively inexpensive at $8 USD per node, yearly. The standalone product has two versions; the one that patches servers is about $45 USD annually and the version that patches workstations is about half that price at $22 USD.
There are no costs in addition to the standard licensing fees. It is a term-based license that includes support for one, two, or three years at a time.
This is a product that we have been selling for 16 years and I recommend it with no hesitation.
I would rate this solution a ten out of ten.
