What is our primary use case?
Once the WSS has been set up, we have to create an additional third-party sign-in certificate using Ivanti. After the certificate is generated, we import it into our server, with the same being deployed to all of our clients. Once the patch is published, or the third-party update has been published in Ivanti, we have to publish the WSS features into the SCCM consoles.
Ivanti scans all the applications that we have running in our environment. Based on that, it will generate updates or upgrades for the set of applications that require it. Once we have that information, we can mitigate the thirty-day vulnerabilities.
What is most valuable?
The most valuable feature of Ivanti Patch for SCCM is the detection logic. Ivanti will detect which client will require a patch and show us how many clients will be recording the update. For example, if we deploy a simple application like an Adobe update, without Ivanti, we would have to customize the package in SCCM. With Ivanti, the patch and logic are available.
What needs improvement?
Ivanti Patch is missing some of the capabilities that SCCM has. Anytime we have upgrades, in-place upgrades, or any deployment through Ivanti, it is missing the full features that can be leveraged through SCCM.
In future releases, I would like to see improvements with the feature upgrade for the SCCM, which Microsoft has already integrated. Currently, Ivanti does not give us information about the enablement package.
For how long have I used the solution?
I have been using Ivanti Patch for SCCM for 10 years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Ivanti Patch for SCCM is a scalable product. We have approximately 150 technicians that plug into SCCM. The applications that are being deployed from Ivanti to SCCM would have close to 30,000 users. This includes applications like Mozilla Firefox and Adobe, for example. Everything is tested through Ivanti.
How are customer service and support?
I haven't had experience with customer service and support, however, we did have an advisory case with one of their technical support staff. We were publishing and getting the full metadata for the patch. We were getting the full updates for the patch release.
There was confusion as to why we were seeing that in the SCCM, instead of in the full metadata patch. The support person was able to help us in understanding what we were doing wrong, highlighting it could be a certificate issue. We generated a new certificate, and after they were applied, the issue was fixed.
Overall, I would rate their customer service and support a five out of five.
How would you rate customer service and support?
How was the initial setup?
The initial setup of Ivanti Patch for SCCM takes 20 minutes to import and integrate the plug-ins.
What's my experience with pricing, setup cost, and licensing?
We do not have a license with Ivanti, instead, we buy just the plugins for the consoles, making it a much less expensive option versus other solutions.
Which other solutions did I evaluate?
We evaluated both Patch My PC and SolarWinds. Both of these options required individual licenses, making them cost prohibitive.
When comparing Patch My PC with Ivanti, we found that Ivanti has many more features than Patch My PC.
What other advice do I have?
Before anyone considers implementing Ivanti Patch for SCCM, I recommend that they be aware of the certificate they should be buying with the SCCM console. This is the only thing that needs to be checked before you start working with this product.
Overall, I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
