What We're Working On [WWWO] for Patch Manager beyond 2.0...

To receive updates on the Patch Manager roadmap, JOIN thwack and BOOKMARK this page.

We recently released Patch Manager 2.0, which included support for Windows Server 2012 R2 and Windows 8.1. We're now working on simplifying the interface and making the Patch Administrator's time more efficient. We're also working on other ease of use enhancements such as:

PLEASE NOTE: We are working on these items based on this priority order, but this is NOT a commitment that all of these enhancements will make the next release.  We are working on a number of other smaller features in parallel. If you have comments or questions on any of these items (e.g. how would it work?) or would like to be included in a preview demo, please let us know!

  • I would love to see an update task be able to patch + reboot a target until the Needed count was zero.  There's never a good way to know how many reboots a given approved patch list will take on each target, and the only way to do that now is to schedule a patch + reboot task against the target every hour for an estimated count of times.  It would be SO much nicer if the patch process did the "lather, rinse, repeat" actions for us!

  • I'm very interested in seeing an update to the UI. The existing interface is cluttered and inconsistent, with many strange quirks which are sometimes potentially disastrous, such as a right click menu that sometimes acts upon the item selected but sometimes upon the previously selected item or even all items in the container. I'd also love to see improvements to the behavior of groups and scheduled tasks. Many of the concerns I listed in List of bugs and feature requests for Patch Manager 1.72 are still applicable to version 2.0. It would be great if some of these issues could be addressed in future updates.

  • There is one major enhancement I would like to see.  When adding or removing a computer to a patch manager computer group, automatically update any attached jobs that use the updated pm group to reflect the change.  Currently its too dependent and requires you to update each setting from the computer group to the actual job itself before it recognizes that a computer was deleted or added to a pm group.

  • FormerMember
    FormerMember

    How about Linux patching?

Thwack - Symbolize TM, R, and C