February 12, 2020
Score 10 out of 10
Read Adam Friedli's full review
Pros and Cons
- Automated patching. The patch management is very robust and doesn't let us down. We can rely on it to do its job.
- Scripting. The scripting engine and layout is excellent. It's very easy to work with and adapt Powershell scripts and other script to the native format with its functions. It also gives detailed logs to help determine why something went wrong if there's issues.
- They have conflicting scheduling paradigms. When scheduling patching for clients, the 1st Friday is interpreted as the very first Friday of the month, even if this is the 1st of the month. For scripting, the 1st Friday of the month is interpreted as the 1st Friday of the 1st FULL WEEK of the month. This makes no sense to have two different interpretations, and makes it unreliable to schedule recurring scripts to fall when recurring maintenance does. The scripts need to be done manually because of this.
- There is no way to dictate reboot orders for patch policies. This tied directly in with my first point. We have some clients that require reboot orders. This is not possible without having different patch policies for each server and specifying a time this way. But, there aren't small enough increments of time to make this reliable, plus patching duration might vary. Excluding reboots with patching and scheduling reboot scripts fixes this. However, this can't be done once on a recurring schedule due to the different scheduling paradigms already discussed. We have to schedule these manually each month.