Ivanti Autonomous Endpoint Management Reviews

We are working with MDM requirements for major purposes alongside other products including mobile application management and content management on mobile phones.

Our market in the Philippines in terms of MDM is evolving with AI as clients are trying to manage their devices, especially since many of our clients have been working remotely since the pandemic.

We have experience with app distribution, as some of our clients develop their internal applications and they are using Ivanti Neurons for MDM to distribute those applications.

The security features in Ivanti Neurons for MDM are very effective, which is why we have been distributing it for the past 15 years.

The positive impacts from the product are that it is easier for our clients to manage their endpoints, especially for those BYOD scenarios. It also helps to implement policies with criteria for BYODs and company-owned or employee-owned devices. Additionally, it protects corporate information when it comes to the devices of end users.

Ivanti Neurons for MDM provides very good visibility into mobile device inventory, especially through the dashboard.

The automation aspect has an impact on operational efficiency, as the rolling out of mobile devices is very easy with the help of Ivanti Neurons for MDM.

Ivanti Neurons for MDM is easy to install, and the creation of policies is easier as well, except when clients have complex requirements.

Windows devices could be improved, as we are more familiar with client-managed devices where we install the application or the client of Ivanti Neurons for MDM or MobileIron in those devices. We are familiarizing more with the Mac and Windows side.

The disadvantage in connection with Windows devices is that the pushing of policies takes some time.

We have been distributing Ivanti Neurons for MDM since 2010.

Considering all its agents and connectivity, the stability rating would be an eight out of ten.

There is no limitation in scalability; Ivanti Neurons for MDM is very scalable. The scalability rating would be nine points out of ten.

The technical support rating is eight points.

We have been working with MobileIron as well, and we have not worked with other products for MDM apart from Ivanti Neurons for MDM.

I cannot say if Ivanti Neurons for MDM is expensive on the market or quite affordable because I am not familiar with the pricing of other products. However, we have received feedback from clients that Ivanti Neurons for MDM costs more than other products. The overall review rating for Ivanti Neurons for MDM is nine out of ten.

Private Cloud

My main use case for Ivanti Autonomous Endpoint Management is security management. A specific example of how I use Ivanti Autonomous Endpoint Management for security management is agent-based security communications and security purposes.

Ivanti Autonomous Endpoint Management offers features that make it more secure and useful for security purposes. The security is enhanced because it is easy to deploy, and we can use it through the SCCM agent. All the agents can be deployed through SCCM as well.

Ivanti Autonomous Endpoint Management has positively impacted my organization because I used this tool in my previous project, and it is useful for security purposes. The positive impacts include reduced incidents, saved time, and easier compliance. It is more secure, which is why we have reduced incidents and are more compliant. Vulnerability is also less because of that.

There is no improvement I can suggest at this time; it is a good tool from my perspective. If I had to think of one thing that could be better, I would say the support is also good, but we should get senior support expert people when using P1 tickets.

I have been using Ivanti Autonomous Endpoint Management for two or more years.

Ivanti Autonomous Endpoint Management is stable in my experience.

From a scalability point of view, we have not experienced any scalability issues.

The customer support is good.

I did not previously use a different solution before Ivanti Autonomous Endpoint Management. Before choosing Ivanti Autonomous Endpoint Management, we were using Symantec and also explored it.

There is a return on good investment.

My experience with pricing, setup cost, and licensing was handled by my procurement team; I was not part of that.

I have not used the Ivanti Autonomous Endpoint Management patching features. I do not recall specific scenarios where Ivanti's unified platform for IT and security operations helped streamline processes. I would assess the trust-building process of Ivanti's AI, from assist to advise to full automation in my organization, as we have not used Ivanti AI yet. My overall rating for this product is 8.5 out of 10.

Private Cloud

Other

The primary use case for Ivanti Neurons for Patch Management is patching both servers and computers. I am using it for security control and batch management.

The most effective feature of Ivanti Neurons for Patch Management is its reactivity when a patch is released before its due date. Additionally, everything is automated for both computers and servers, which results in significant time savings.

Reporting needs improvement. It is not very useful and lacks depth. Another area that needs enhancement is the integration with proxies, as better integration would be beneficial. Also, the history of patching is missing from the solution, making it a challenge.

I have been using Ivanti Neurons for Patch Management since 2018.

Deployment was straightforward and took approximately half a day.

I have not faced any issues regarding the stability of the solution.

The solution is scalable for my environment. I would rate the scalability as nine out of ten.

Technical support provides feedback, but it sometimes takes a long time to answer questions. They should provide a faster response. I would rate the support as six out of ten.

Neutral

Before using Ivanti Neurons for Patch Management, I only used Microsoft solution.

The initial setup is relatively easy, though there were some difficulties with the last version.

I have seen a lot of gains in terms of time savings.

The price for this solution seems to be reasonable for my company.

Apart from Ivanti, I have evaluated other solutions, but no specifics are mentioned.

I recommend using Ivanti Neurons for Patch Management as it is easy to put in place and use. I would give the overall solution an eight out of ten.

On-premises

We have around 1,500 endpoints within our business internationally, and we need to make provisioning for this application, deploy applications, and maintain patch management. We use Ivanti Neurons for MDM for these purposes.

The zero-touch capability where you can install all the business applications and deliver the laptop to the user, who just needs to log on to complete everything without any human intervention, are the best features in Ivanti Neurons for MDM.

We have security features, patch management, compliance reports, and dashboards integrated within Ivanti.

The MDM, asset management, and software spend management are areas that could have more improvement in Ivanti Neurons for MDM.

I have three years of experience with Ivanti Neurons for MDM.

It is a stable solution.

Ivanti Neurons for MDM is a scalable solution.

I would rate Ivanti technical support as seven out of ten.

Positive

The implementation began three years ago and is a continual process. It involves constantly adding features, adding modules, and configuration. It is a non-stop process.

The implementation process sometimes requires a third party, sometimes depends on the Ivanti support team, and sometimes can be handled by our internal team. It depends on the complexity of the module.

The software spend module allows us to predict usage and license requirements. We can remove or add licenses according to business requirements, and it is all controlled within the application.

The pricing is comparable to Microsoft Intune, but Ivanti Neurons for MDM offers many features and innovation.

I am a customer of Ivanti Neurons for MDM working as Manager, Information Technology Support at Fee Fund Info. My overall rating for this solution is 7 out of 10.

Public Cloud

Other

The primary use case of Ivanti Neurons Patch for Intune was primarily for updating all servers, ensuring that both main servers and production servers are updated to the latest patch.

I quite like the inventory list feature. Any time I needed to check a machine for any software, I could see the list of software directly from the Ivanti console. It was a helpful feature that I quite liked.

In terms of improvement, I would recommend better documentation. During the time I used it, there were issues with up-to-date patching, and the documentation around those specific errors was quite confusing. Sometimes I had to uninstall, reinstall, or engage technical support, which took a lot of time. It would be helpful if the documentation could easily help us fix bugs on our own.

I worked with Ivanti Neurons Patch for Intune for about two years.

The technical support from Ivanti is good. I would rate them an eight or nine. They are responsive, stick to time, and are enthusiastic about helping. The only downside is the time zone difference, as we are two hours behind their support team, meaning we sometimes have to wait until the next morning for support.

Positive

The only downside I found regarding technical support was the time zone difference. Since we are two hours behind, we occasionally had to wait until the next morning for assistance. I would rate the Ivanti Patch Management solution a seven out of ten.

The products are quite good when they are operational. They offer good solutions, technology, and user experience. Everything is satisfactory.

The release of new versions often goes in the wrong direction with Ivanti. The test team or the testing procedures are flawed because they release new versions with numerous basic issues. There are significant problems which are unacceptable for me.

I have used the solution for approximately five or six years.

Currently, there is no significant problem in scaling. Everything is good except for the testing of new release versions.

My last communication with technical support involved an R1T engineer. He gathered a lot of information from the environment, like special web files. He is now checking the log files and packages. Although they usually solve the problem, I am concerned about consistently needing to call support for installing brand new solutions. This is not typical for standard installations like Windows Server.

I have experience with the Juniper SRXX firewall, and the need for MobileIron, as well as the secure pool VPN, is essential.

The initial setup for MobileIron is difficult and very complex. This is a complex system, but the issue is not with the initial setup itself; rather, it is with the poor releases.

Typically, I act as a subcontractor for larger companies, providing solutions for them. Our team are Ivanti Partners.

This is not a cheap solution. I do not have exact pricing information as I am not responsible for this aspect.

I am interested in the mobile add-on. There are three different types of products in this category: VMware, Microsoft, and MobileIron. They top the list. I have no experience with others, only with MobileIron.

My rating for the overall solution is six out of ten.

On-premises

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.

On-premises

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.

Hybrid Cloud

MobileIron UEM will be used to manage mobile devices. We will be able to manage a wide range of endpoints from the MobileIron console, similar to VMware Workspace ONE.

The user interface is user-friendly.

I don't believe I have, given the scope of this, because I haven't explored them thoroughly. So I don't think I have a problem with them right now.

For a new user, the initial setup could be simplified.

We had an issue with the integration of an add-on, but it has been resolved.

They are using a MobileIron as the base mobile device management solution, and we have added some additional solutions to that, such as Advanced Neurons. The integration between the MobileIron and Advanced Neurons isn't completely in sync, and we're still working on that.

I have been testing MobileIron UEM for two to three weeks.

We are working with the latest version.

MobileIron is still with Ivanti. We are still working on the proof of concept with them, and I believe the tenant is still with them. I'm not sure who the host is.

MobileIron UEM is a stable solution.

MobileIron UEM is a scalable solution.

We are only going to deploy it to 200 plus, users at first. That will increase in the future, depending on how our business grows.

When it comes to technical support, the person who is fixing it is the one who leads the POC. The same engineer who is assisting us with the proof of concept is also the one who is repairing it. I believe technical support is quite responsive because he is the one who is resolving the issues.

We are working on the proof of concept for both MobileIron and Workspace ONE.

We are only testing MobileIron and Workspace ONE. After that, we will decide which device to use.

Workspace ONE by VMware Similarly, we will use MobileIron as a mobile device management tool, allowing us to manage our endpoints remotely. So far, we have not had any issues with VMware, and we have resolved some, if not all, of the issues.

I have been testing with VMware Workspace ONE for the same amount of time as MobileIron UEM, three weeks.  We are using the latest version, and it is deployed on a public cloud. The cloud provider is VMware.

I have also been working with Google Chrome. Google Workspace is an email production tool provided by Google.

We don't have a firewall because we're in the cloud right now. We have no on-premises network and all of our systems are hosted in the cloud.

Perhaps because it is my first time, it is quite complex, but there are engineers guiding us, but it is quite complex on my end.

We had assistance from a MobileIron team member. We will investigate their features and see what capabilities they have while conducting a proof of concept. That is our proof of concept's goal.

We don't have the cost until we have completed the proof of concept.

They need to research other platforms or solutions to determine which solution best meets their needs. In particular, I don't think I have any recommendations for MobileIron because my experience with it has been limited. I lack extensive experience with MobileIron.

I'm a potential customer.

I would rate MobileIron UEM an eight out of ten.

Public Cloud

Other

I use this solution in order to manage mobile devices.

The solution is good. It's effective in what it is able to achieve and it's easy to use.

The control on offer is the most valuable aspect of the solution. 

The product is stable. 

We've found the scalability to be good.

We haven't really found anything lacking in terms of features.

The support on offer could be better. 

We would like the initial setup to be simpler. 

I've been using the solution for at least the past 12 months or so.

The solution is pretty stable. We haven't had issues with bugs or glitches. It doesn't crash or freeze. 

The solution can scale well. If a company needs to expand, it's not a problem. We have a lot of people using the solution currently. Likely there are hundreds of users on it. 

We'd like for the product to offer better support so that if we need help we can feel confident we'd get it. They are just not as efficient or effective as we would like them to be.

We did not previously use a different solution. 

It was not an easy initial setup for us. It was a bit difficult and not really straightforward. 

I don't deal with the costs of the pricing. I'm not sure how much it is for the company. 

I'm not sure which version of the solution we're using. 

I'd rate the solution a seven out of ten. It's okay. There are a few areas where it could improve. 

On-premises