This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

What We're Working On For Patch Manager (Updated August 14, 2020)

Solarwinds Patch Manager 2020.2 has shipped and we are already busy working on the next release. Here's what we're working on:

  • Web Console: updates to the Orion web console, adding new reports/views:
    • Last Patching Date.
    • Computer and Update views.
 
  • LDAPS support for encrypted domain controller communication.
 
  • Add capability to execute remote PowerShell scripts on agents.

As always, if there are features that you'd like to see implemented in Patch Manager, please submit your ideas here.

  • 2.0 was released over a year ago (11/26/2013), I think you meant to post 2.1 RC? The truth is not much as changed since the 1.x days aside from branding, os support, and Orion integration... Earlier this year andrewm. created a post asking Is Patch Manager dead?  The fact is development on PM has slowed greatly... GREAT questions like List systems without a specific application installed are not even being answered... It feels like PM is not getting the internal support it needs... I have not heard much chatter on the 2.1 RC other than the beta announcement post Patch Manager 2.1 Beta 1... what would be nice to know is when this will be out of beta, if the laundry list of bugs will be addressed, the clunky and slow UI/X will be improved...

  • FormerMember
    0 FormerMember

    Hey Mark, a couple things.

    Before I get started, the only reason this was re-posted was to move to a new Roadmap/What We're Working On system we're implementing on Thwack. This isn't actually new content, it's the same thing Kevin posted on the Product Blog... yes, we're talking 2013/2014. emoticons_plain.png These posts generally get updated as we're releasing and planning new releases, so there will be a new one sometime after the release of 2.1. When that happens, I'll update this post so if you get subscribed (which by commenting you do by default) you'll see the new content.

    Now that that's out of the way, the first thing I wanted to say was the release of Patch Manager 2.1 is imminent - you'll see an announcement about availability soon. It has been in RC for quite a while since that beta post (and on the customer portal available for download), but I don't know if the announcement made it very widely. Most of the things that are in this list today are covered in that release (publishing third party patches, new reports, better grouping, for example, the beta post you referenced covers it pretty well).

    Secondly, we've actually taken some initiative to give Patch Manager more love. We've moved it over to the Security product team (together with Log & Event Manager and Firewall Security Manager) and as a part of a smaller scoped team we'll be able to dedicate more resources to content, feedback, and a long-term roadmap that doesn't make you wonder if Patch Manager is dead. We're not abandoning the server operations (non-security) audience (similar to how Log & Event Manager also plays in multiple audiences), but we're taking a fresh look at what we want to do in the long term.

  • I appreciate your response.  I would respectfully ask going forward such information be shared before it is asked for.

  • I agree, I've only been using PM since 6/2013 after coming from an SCCM background while working at another company and it seems like major development on the product has stalled. And after the great loss of Lawrence Garvin even tech support has dried up now in the support forums. Even the release of 2.1 left me underwhelmed and when 2.1.1 was released the release notes weren't even updated so we have no idea what changes were made in that (bugfix I guess). Eventually I'll get around to installing the upgrade but there's really no "must have" feature in it that I need.

  • FormerMember
    0 FormerMember

    Just a comment on the 2.1 vs. 2.1.1 issue - there was a problem in the files uploaded initially and we had to quickly correct them. We decided to increment the version in case someone had inadvertently downloaded 2.1.0 in the small window before we found the issue.

  • FormerMember
    0 FormerMember

    All three items you listed would be a huge benefit.    I recently joined a company and  I was tasked with implementing patch management in our Data Center and remote sites and these three items are the great features that the product needs.

    I have been patching servers that have been in the field for 3+ years that have never been patched at all.     The ability to keep on patching until complete would be a HUGE feature and would take a lot of pain from having to constantly

    having to resubmit jobs and babysit a system until it is fully patched. 

    I will be impatiently waiting for these new features!   emoticons_happy.png

  • is there any plan to include cluster aware?

    Currently Patch manager is not cluster aware.

  • Is this is a dead product?  Supported products seems very small to the competition.  I believe I might have been sold a bit much by the sales people on it's real potential here. 

  • I think we are in the same boat as you.

  • I'm still not seeing it. You claim that you've got folks working on this product, but the 2.1 update included only minor changes and, other than Windows 2012 R2 support, added no major features and addressed no significant long-standing bugs or UI issues. I have seen no updates on the progress of the new automation features listed above in the seven months since this post and no indication that there is really much interest from Solarwinds in improving the product at all, aside from what appears to be the bare minimum necessary.

    This software has much potential and has already saved us hundreds of hours in admin time, but it needs developer attention to keep up with competition in terms of functionality and usability. I have been using Patch Manager for over 4 years now, and as a customer every year my maintenance renewal date rolls around, I ask myself what I am paying for and whether it's worth it; and every year I feel a bit more hesitant.