Patch for MEM Version 2021.1 Release Notes

1. Important Note

These release notes support the current General Availability (GA) version of Matrix42 Patch for MEM 2021.1

New and existing customers should download and install Patch for MEM 2021.1 If you are currently running Patch for SCCM 2020.1, 2019.2 or 2019.1, you should upgrade to Patch for MEM 2021.1 using the full installer.

2. System Requirements

Matrix42 Patch for MEM installs as a plug-in to an existing Configuration Manager 1906 or later console with a minimum of 4 GB or RAM. The Configuration Manager console must be installed on a 64-bit version of one of these Windows operating systems (excludes Server Core and Nano Server):

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows 10, Pro or Enterprise Edition
  • Windows 8.1
  • .NET Framework 4.8 or later
    If you are missing this requirement, .NET Framework 4.8 will be installed for you during the installation of Matrix42 Patch for MEM.
  • Microsoft Visual C++ 2015-2019 Redistributable (x86 and x64)
    If you are missing these requirements, they will be installed for you during the installation of Matrix42 Patch for MEM.
  • Windows Server Update Services (WSUS) requirements:
    • If Matrix42 Patch is installed on the primary WSUS server and you are using Windows Server 2016, Windows Server 2012 or Windows 8.1, then the WSUS API and the PowerShell cmdlets features must be enabled.
    • If Matrix42 Patch for MEM is on a remote Windows 8.1 machine, then the remote admin tools feature must be installed on that machine.
  • SQL Server requirements:
    • As of Patch for SCCM 2020.1, a SQL Server database is now mandatory, every user must have access to a SQL Server database and must have read/write permission to the database. You can use any version of SQL Server that is supported by Microsoft's System Center Configuration Manager.
    • The user who installs the database must have db_create permissions.
  • If you intend to automatically publish updates using a recurring scheduled task, then the Microsoft Task Scheduler service must be enabled and you must have the rights necessary to create scheduled tasks.
  • If you intend to receive alert notifications via email, then MEM must be configured to allow email notifications.
  • The user running Matrix42 Patch must have Log on as a batch job rights and must be a member of the WSUS Administrators group on the WSUS server. In addition, the
  • user must be assigned to the All instances of the objects that are related to the assigned security roles security scope. Finally, if the WSUS Server is remote, the user must be a member of the local administrators group on the WSUS Server.
  • You must add a number of web URLs to your firewall, proxy and web filter exception lists. The URLs are used by Matrix42 Patch for MEM to download updates from third-party vendors.
    For the complete list of URLs that you should add, see the URL exception list.
  • Federal Information Processing Standard (FIPS) environments
  • When operating in a FIPS environment, the console must be configured as a FIPS-compliant machine before you install Matrix42 Patch. If FIPS is enabled after the installation, you must reinstall Matrix42 Patch.
  • Client machine requirements:
    Each of your client machines must meet the following requirements in order to deploy non-Microsoft updates distributed by a WSUS server:
    • Must contain a copy of the code signing certificate in the appropriate certificate stores
    • Must have enabled the Allow signed updates from an intranet Microsoft update service location policy setting
    • The following languages are supported for use within the Patch for MEM interface: Chinese (Simplified and Traditional), English, French, German, Italian, Japanese, Portuguese (Brazil), Russian, Spanish.

3. New Features

Patch for MEM Version 2021.1 provides the following new features.

History View for Scheduled Task

Within Automation Scheduler, you can view the history of any of your automated tasks. You can access the history from the Automation Scheduler calendar or while editing a scheduled task.

For details, see: Viewing History of Scheduled Tasks

Microsoft Intune Integration Enhancements

The Synchronizing Third-Party Applications functionality has moved from the Application Management workspace to the Automation Scheduler. The ability to specify which applications to import and the cadence at which the applications are checked for updates is now all contained within the same scheduled task. This enhancement will greatly streamline and automate your workflow. In addition, the ability to sideload applications is also new.

For details, see: Synchronizing Third-Party Applications with Configuration Manager and Intune

Streamlined Deployment Enhancements

The synchronizing third-party applications functionality has moved from the Application Management workspace to the Automation Scheduler. The ability to specify which applications to import and the cadence at which the applications are checked for updates is now all contained within the same scheduled task. This enhancement will greatly streamline and automate your workflow. In addition, the ability to sideload applications is also new.

For details, see: Viewing and Managing Scheduled Tasks

Automated Scheduled Task Delay

You are now able to delay a scheduled task by a specified number of days. This enables you to schedule a task to run a few days after a regular monthly event, such as Microsoft's Patch Tuesday.

For details, see: Scheduling Automatic Publications and Downloads

Support for Additional Third-Party Applications

The Application catalog now contains additional third-party applications that are available for import to Microsoft Endpoint Configuration Manager and/or Microsoft Intune.

For details, see: Synchronizing Third-Party Applications with Configuration Manager and Intune

User Experience Improvements

The Application Management functionality has moved to the Synchronize Applications button in the Automation Scheduler workspace.

  • The Settings dialog has been simplified:
    • Proxy information is now configured on the new General tab.
    • The Configuration Checker has been relocated to the new General tab.
    • Metadata options are now configured on the new General tab.
    • Information about the number of endpoints that Patch for MEM has published updates to in the last three months is displayed on the About tab.
    • The ability to choose which catalogs to use has moved to the Catalogs button, consolidating all catalog-related information in one area.
    • You can now import multiple catalogs at the same time.
  • Three new columns have been added to the Alert History grid: Related CVEs, Task ID and Task Type. In addition, it is now possible to change the number of days that alerts are stored in the database.
  • The ability to individually select CVEs during the import process.
  • The option to automatically subscribe to WSUS categories during the publication process.
  • The maximum length of the custom command-line has increased from 200 characters to 32,768.

4. Resolved Issues

The following customer support issues have been resolved in this release:

  • Resolved an issue where column layout changes were not retained after navigating to other locations within the product.
  • Resolved an issue where upgrading to Patch for MEM 2020.2 failed to properly upgrade the database due to a transaction timeout in the Data Migration Tool