Ivanti Patch for Endpoint Manager Reviews

It's been doing a lot for us, especially with third-party software patching and scheduling. We create multiple projects for monthly patch distribution and manage it all well. 

We face some challenges, particularly with non-domain-joined macOS devices. Patching, updating, and syncing with the server can be tricky for them.

So, the major challenges are macOS updates, patching, and backups.

And for drawbacks, I wish Patch management was cloud-based instead of hosted on our own server.

If Ivanti Patch had a cloud-based option instead of requiring an on-premises server and software. Hosting it in the cloud would simplify management, eliminating dependence on VPNs or other connectivity issues.

Similar to Microsoft's EMS licensing, offering a cloud-based solution like Azure Active Directory or Endpoint Management Suite (EMS) would be ideal. EMS allows us to manage policies, batching, and software distribution entirely through the cloud, minimizing server downloads. 

If Ivanti considered a cloud-based approach, it would be hugely beneficial in today's hybrid work environment, where employees use desktops, laptops, and various locations. It's not just about patching office PCs anymore; mobile workers and backups need seamless access as well.

Cloud-based patching would be much easier in a hybrid environment. Imagine updates coming directly from the cloud instead of relying on individual VPN connections. It would streamline the entire process.

We use the solution to patch Windows and Linux machines. We download the patches and implement them. We get vulnerability reports after patching.

Earlier, we faced some challenges while installing patches. Maybe there were agent compatibility issues. Now, Ivanti helps install patches easily.

I'm primarily focused on patch management. Ivanti is a comprehensive solution, but my expertise lies in the patch management aspect for our customers. Specifically, I handle Windows patching and similar guest services.

When it comes to Ivanti Patch for endpoints, I find peer-to-peer patching valuable. Having a peer-to-peer patching capability is highly beneficial for us.

In terms of endpoint devices, enhancing network bandwidth is crucial. Additionally, if we consider third-party tools like VLC or other software, Ivanti can patch them and even enhance network bandwidth. 

However, when comparing it with SCCM and similar tools, they will consume more bandwidth, which negatively affects network performance. So, by using Ivanti, I can effectively improve our network bandwidth as well.

When dealing with SCCM, it tends to use more bandwidth in comparison to Ivanti. Therefore, I can secure better network bandwidth utilization by utilizing Ivanti.

We were looking for a central console to manage our endpoint, especially for patch management and the service after deployment. We already had security so overall our challenge was that the initial patch management interval deployment was a manual process and that was a struggle. I was employed to execute and implement the solution for the entire organization which has around 1,300 people. We are customers of Ivanti and I'm an information technology consultant.

Because of the internet gateway, we were able to get clear visibility regarding the status of the endpoint which we needed to do recently when everyone was working from home. Reporting and management is via the central console which gets its information from the cloud gateway.