Showing results for 
Search instead for 
Did you mean: 
Create Post

Patch Manager 2.1.6 is Now Generally Available

I'm happy to announce that Patch Manager 2.1.6 is now available. This release marks the addition of PowerShell® script support and other improvements. You can view the Release Notes here.

PowerShell Scripting: Windows PowerShell scripts can be now be executed as part of an Update Task, both before and after the task completes. This new functionality provides additional flexibility to your Update Tasks to perform tasks such as snapshotting a VM prior to an update task and reverting to the snapshot if an issue occurs, stopping services in a particular order, failing over machines and muting alerts from Orion nodes during an update tasks. For a great example on how to leverage PowerShell scripts to mute an Orion node during a patching window, please see a great blog post from KMSigma: Patching Machines (or Shut-Up Alerts!).

Screen Shot 2018-12-06 at 10.39.08.png

Updated OS Support: Patch Manager 2.1.6 includes support for deployment on Windows Server 2019.

TLS:  TLS 1.2 is now fully supported to ensure Patch Manager no longer requires TLS 1.0/1.1 to be enabled on the Patch Manager server.

The team is already hard at work on the next version of SPM, as you can see covered here in the What We're Working On post. Also, please keep the feedback coming on what you think and what you would like to see in the product in the Feature Requests section of the forum.


Great addition!

I guess the PoSH scripts run under the specific service account which is defined in the credentials ring ?

Glad you like the PoSH addition!

Currently, there is not an option within the Credential Ring to specify an account for executing PowerShell scripts. Local scripts run under the account which starts Patch Manager. Remote scripts use the credentials specified within the Credential Ring for the particular client machine (if none assigned, then the default credential is used).

Hey Jaime

the 2.1.6 download is 1.67 GB but the display shows 1.27 GB


Also, im sure you know but its still unable to be downloaded via Chrome, it just spins when you select finish download.  It does download fine with IE.

Also the default download when going to the portal is still 2.1.5.  You need to expand all downloads to get to 2.1.6

Hey Sean - apologies for the delayed response. Thanks for flagging the issue with the download size, I'm looking into it now. I've been unable to reproduce the issue with Chrome and the default download going to 2.1.5. Can you trying clearing the cache in Chrome and trying the download again? I'm going to do some further investigation into your portal issue and report back to you ASAP.

I cleared the cache and tried again and got the same thing in Chrome

The circle just spins.  I only left it for 1 minute.  My version of Chrome is

Google Chrome is up to date

Version 71.0.3578.98 (Official Build) (64-bit)

2019-01-04 07_37_06-Downloads _ SolarWinds Customer Portal.png


I would just like to warn anyone from upgrading to 2.1.6.  There is a bug we have encountered where all of our batch tasks (all 198 of them!!) no longer run when we upgraded from 2.1.5 to 2.1.6.  This has been documented in the release notes for 2.1.7 RC1 upgrade (see below).  We have a support ticket open for this, which has not progressed since it was created almost a week ago.

00217203 / Scheduled tasks fail to run

Issue: After you upgrade Patch Manager to the latest release, one or more scheduled tasks fail to run.

Resolution/Work-around: Recreate the scheduled tasks after the upgrade.

This error appears when we edit the old batch tasks.  It seems like a fairly easy fix as it refers to a missing field value...


Support offered a workaround for the above issue with existing tasks failing to run.

Edit task.xml files found under C:\Program Files\SolarWinds\Patch Manager\Server\scheduled\taskid

The taskid is a unique folder for each task, the task id can be found on each task in scheduled tasks

Edit the .xml file and replace the text, lastNMonthUnit="month" with lastNMonthUnit="months".

Then edit the task from scheduled tasks and re-save it.

Version history
Revision #:
1 of 1
Last update:
‎12-04-2018 03:17 AM
Updated by: