Getting Started
Search
K

Publisher Releases

You can find the production release history for the Patch My PC Publisher below.

2.1.19 - 2024-01-16

Features

  • Ability to create Custom App updates and base installs (Public preview)
    • The Publisher must have ‘Install preview builds‘ checked in the About tab.
    • Custom Applications are supported in the ConfigMgr apps, Intune apps, and Intune updates tabs.
    • A license with one of the below subscription levels is required.
      • Enterprise Plus
      • Enterprise Premium
      • MSP
  • Implement Publish Now for Custom Apps
  • Support detecting software that translates DisplayName
  • Add support for configuring Win32 application max runtime in minutes

Improvements

  • *** Report lines have been updated.
    • As the catalog grows and the number of syncing products increases, our *** report line has gotten too long! CMTrace does not parse the line, and it will not show it. To prevent this, we have split up the report line into one line per type. Below is an example.
    • Patch My PC log file with four separate report lines all prepended by ***
  • Implement certificate pinning. All requests to Patch My PC domains will have the certificate validated.
  • Implement a safety check prior to deleting a ConfigMgr application. In some instances, the SMS provider returns an empty list of apps instead of a connection exception. To account for this, we ensure at least one Site is returned by the SMS provider prior to application deletion.
  • ConfigMgr script size is reduced. No functional changes. This should help with metadata download issues over CMG.
  • Add support for the ? wildcard character in detection.
  • Improve some popup notifications to direct the user to the correct tab.
  • Improve cleanup during service shutdown.
  • Update the default login authority for Intune. It is now https://login.microsoftonline.com
    • This will not affect existing Intune configurations. It is only a change to the defaults for a new connection.
  • Implement an attempted reconnect when a WMI query fails against the SMS provider.
  • Improved scriptrunner logic for finding uninstall strings. DisplayVersion will now have any “-” or “_” replaced by a “.” when searching for uninstall strings. This matches the behavior of our script based detection.

Fixes

  • Fixed a dead ‘More Info’ link for WSUS certificate management.
  • Fixed a bug causing dependencies to be removed from an Intune Win32 application when republishing.
  • Fixed a bug where publish now and delayed ConfigMgr apps did not work as expected.
  • Fixed a bug that caused a new install of Patch My PC Publisher to be in ‘Intune Only Mode’ regardless of the checkbox state.
  • Servers are no longer included in Intune device counts.
  • Resolved a race condition which caused the additional webhook filtering options to be unavailable in some instances.
  • Improved download engine logging to include the URL when the download fails. This was a regression that is now resolved.
  • The logging path for Intune Manage Installation Logging incorrectly defaulted to the ConfigMgr path. It is now corrected to the Intune default path for logging.
  • For some sync schedules, the ‘Next Sync’ time displayed in the General tab was in UTC instead of local time. The correct time should now be displayed.
  • Fix logging during the creation of Intune products when local content lookup fails. The Publisher would incorrectly log that the existing application would be deleted.
  • Fixed a bug causing Enforced Uninstall Arguments to be ignored for ConfigMgr apps. This resulted in some ConfigMgr apps being created with an uninstall that may not work as expected. The next sync after the Publisher is updated will fix these products’ uninstall configuration.
  • The connection name is now required in the Cloud tab.
  • Fixed a bug that caused a Null Reference Exception when exiting the Manage Conflicting Processes configuration in the Intune apps or Intune updates tab.
    • This was a regression that only impacted preview builds
  • Fixed a bug that caused the custom naming convention for ConfigMgr applications to be overwritten during a sync in some cases.
  • Fixed a bug where the authorization token can expire when connecting to Custom Apps, requiring a service restart.
  • Fixed a bug where Right-Click selections for “All Products” on the “Intune Apps” tab would be lost when custom apps was enabled.
    • This was a regression that only impacted preview builds

2.1.18 - 2023-10-16

Features

  • Sync only selected apps/updates during a sync
  • Allow the management of Delivery Optimization configuration for Intune assignments.
    • Note: Existing DO configuration on an assignment will also carry forward now when a new version of the software is Published.
  • The Intune Application Manager Utility now has some multi-select bulk options.
A right-click menu in the Intune App manager tool, showing the options available. Manage DO priority. Manage ESP associations. Delete assignments. Delete applications. Extract content(s).

Improvements

  • Implement a new download engine across all components.
  • Detection method improvements.
    • Support parsing version numbers that use – or _ instead of .
  • Improved logging regarding installer downloads and sourcing.
  • Use CSV-based reporting endpoints for detected software per-computer.
    • This should prevent 429 responses when getting the list of devices with an application.
  • WMI connection test to SMS provider prior to deleting ConfigMgr content.
  • Improve cleanup of files during the synchronization of Intune.
  • Updated the “Enabled” header of CSV exports in scan wizards to be less specific.
  • OK button has been changed to ‘Save and Close’
    • Open to feedback on this change. We have received a fair number of reports that it is unclear the ‘OK’ button will close the UI.

Fixes

  • Fixed a bug where the wrong ID property was shown in the ‘Show Package Info‘ tool for the update ID.
  • Fixed a bug where Manage Conflicting Processes may be enabled if ‘Add the executable name in the deployment type’s install behavior’ is enabled. This is unexpected behavior that will no longer occur.
  • Fixed a bug where multiple threads could access some components of settings at the same time, causing a race condition.
  • Fixed a bug where the ‘Change Visibility’ option for WSUS updates would not work if the WSUS DB is called something other than SUSDB.
  • Fixed a bug that caused the right-click menu at the root to sometimes not display correctly.
  • On the ConfigMgr Apps tab, if the option «Add the executable name in the deployment type’s install behavior» is enabled, the Manage Conflicting Process is automatically enabled to kill processes.
  • Fix crash when sorting some columns in the Manage Assignments tool.
  • Fixed a bug that would cause a republished Intune product to have the content for the latest version and the metadata for version n-1.
    • This would occur if the republish flag is set and there is a new version of the application in the catalog.
  • The list of Intune assignment filters is now filtered to Windows.
  • Fixed a bug where in some scenarios, the republish flag would not be removed after a sync.
  • Fix a possible null reference exception when loading assignments for bulk delivery optimization edits.
  • Fixed a bug where the custom logging path may be reset to defaults instead of inheriting the expected value.

2.1.17 - 2023-09-08

Fixes

  • General security fixes and improvements

2.1.16 - 2023-07-06

Improvements

Fixes

2.1.15 - 2023-06-14

Features

Improvements

  • The Update ID is now an available column in the Show package info tool.
  • Updated some graph calls to use a smaller page size. This reduces the chance of receiving a 429 or 503 response from graph.
    • The page size is configurable from 20-999 in the Advanced tab of the Publisher.
  • The product treeviews are now sorted by Vendor and then Product Name automatically.

Fixes

  • Fixed a bug where a ConfigMgr application’s supersedence relationship was lost when the application was upgraded in place.
  • Fixed a bug where the sorting of products in the email report was in reverse alphabetical order.

2.1.14 - 2023-04-11

Improvements

  • Adjusted log levels of some lines to assist with troubleshooting.
  • Update context menu items to reflect new labels in ConfigMgr for featured apps.
  • Update several labels in the UI to be more clear on their functionality.
  • The ability to set ‘Prevent the end-user from opening an application while the application is updating’ is now only allowed at the per-product level. This setting is only needed in specific scenarios, and enabling it for all products can be problematic.

Fixes

  • Fixed a bug where Intune device counts are not reporting properly.

2.1.13 - 2023-03-27

Features

  • Email and Webhook notifications now include information about delayed ConfigMgr applications during each sync.
  • Add support for creating an Available assignment for All Devices. This was previously not supported by Intune. Support has been added, and the Patch My PC UI now allows it as well.

Improvements

  • Added the option to import CAB files when importing tenants.
  • Email and Webhook notifications are now sent when a delayed ConfigMgr application fails to download. Previously a notification would only happen if the Publishing failed after the delay.
  • Improved the cleanup of registry keys related to ‘Prevent the end-user from opening an application while the application is updating’ in Manage Conflicting Processes.

Fixes

  • Fixed a bug where PowerShell scripts for Intune were created with an encoding of UTF8 with BOM. They are now encoded as UTF8 without BOM, which is the recommended encoding based on Microsoft documentation.
  • Fixed a bug where a malformed ConfigMgr folder item (SMS_ObjectContainerItem) would be created the first time the Publisher moved a ConfigMgr application. The result was a folder that could never be deleted.
  • Fixed a bug where having a product marked with exclude from auto-publishing rules and a custom naming convention or pause set would cause invalid XML to be generated.
  • Fixed a bug where the Collect Logs feature would fail if a company name contained characters that are invalid for file names.
  • Fixed a bug where PatchMyPC Scriptrunner logging did not use an invariant datetime format. This could cause CMTrace to fail to parse the logs.
  • Fixed a bug where an exception may occur if deleting a large number of Intune Applications using the Intune Application Manager Utility
  • Fixed a bug where some data exports would result in malformed date time strings. This occurred if a culture used the same character for the number group separator and for time parts.
  • Fixed a bug where ConfigMgr detection script logging did not use an invariant date-time format. This could cause CMTrace to fail to parse the logs.
  • Fixed a bug where Manage Conflicting Process logging did not use an invariant date-time format. This could cause CMTrace to fail to parse the logs.
  • Fixed a bug where the option to abort an uninstall if the prescript failed caused an argument parsing exception.
  • Fixed a bug where the automatic backup of setting changes would fail in certain cultures due to a date-time parsing issue.
  • Fixed a bug where custom naming conventions were copied between tabs. We no longer copy naming conventions when copying products between tabs.

2.1.12 - 2023-01-20

Features

Improvements

  • If a PMPC-defined pre or post-script is missing from the content source for ConfigMgr applications, then the Publisher will redownload it during a sync or republish.
  • The expected and actual hash of files found in the local content repository is now added to the log in debug mode. This has always been the case for files downloaded from the internet.

Fixes

  • Fixed a bug where non-Windows devices may show up in the Intune scan wizard drill-in.
  • Fixed a bug where republishing an Intune product would cause the application to be deleted from Intune if retention was also enabled and set to zero.
  • Fixed a bug where the Publisher would not check the WSUS certificate validity unless at least one WSUS update was selected.
  • Fixed a bug where the requirements for Workstation or Server OS would not be set for postponed ConfigMgr applications.

2.1.11 - 2022-12-16

Improvements

  • Improved the content of alerts when additional files or folders are missing when Publishing a product
  • The ‘Configure SMS Provider connection’ button is no longer highlighted if unconfigured in WSUS Standalone Mode.
  • Improved the logging for SMTP initialization and error handling.
  • All titles in the email report now link to release notes if available.

Fixes

  • Fixed a bug where the Publisher would not add a PMPC-defined script to an existing product.
  • Fixed a bug where Scriptrunner did not append the provided Silent Uninstall Arguments to MSI uninstalls.
  • Fixed a bug where some UI listviews had a broken filter.
  • Fixed a bug where the Manage Conflicting Process window may be offset from the bottom right corner.
  • Fixed a bug where the Pause was never removed from Intune applications.
  • Fixed a bug where the Publisher would check for the WSUS code signing certificate even if updates were disabled in some scenarios.
  • Fixed a bug where the DateTime formats in the Usage Statistics section of the Publisher were inconsistent.
  • Fixed a bug where some temporary folders were not cleaned up by the Publisher. These will be retroactively cleaned up once this build is installed and running.

2.1.10 - 2022-11-17

Improvements

  • Added a filter for Superseded to the Modify Updates Wizard.
  • Adjusted some log levels and log text to be clearer.
  • Added additional logging when the proxy settings are loaded in the event of a failure.
  • Add the ability to limit the number of threads used during the upload of Intune packages.
  • Scriptrunner will now log out a comma-separated list of all public desktop shortcuts if the installing product is configured to delete desktop shortcuts.
    • This is to help troubleshoot when icons for applications are not deleted.
  • Improved how running processes are enumerated for Manage Conflicting Processes making the popup more responsive.
  • Implemented a ‘retry’ in the event of failure for many critical interactions with Azure via Microsoft Graph.
  • The Publisher will delete files from the download cache if there is a hash mismatch for the file. This makes the root cause of Publishing failure easier to identify.

Fixes

  • Fixed a bug where whitespace at the beginning or end of the Organization Name for Manage Conflicting Processes would cause the property to fail to parse correctly.
  • Fixed a bug where old setting backups would not rename properly, causing an error during settings backup in some cases.
  • Fixed a bug where some network operations would not use the configured proxy.
  • Fixed a bug where the code signing of ConfigMgr detection scripts may fail to validate the digital signature on the endpoint.
  • Fixed a bug where the UseGSInstalledSoftware registry option would cause the ConfigMgr database scan to never perform a query.
  • Fixed a bug where a failure to download an icon would cause a product to fail to publish.

2.1.9 - 2022-10-14

Fixes

  • Fixed a bug where selecting Intune Standalone Mode during the initial installation of the Publisher would not hide the Updates and ConfigMgr Apps tabs.
  • Fixed a bug that caused a failure to rename legacy settings backup CAB files.
  • Fixed a bug where Scriptrunner would fail to parse the registry when searching for Uninstall keys if there is an empty string in the SystemComponent property.
  • Fixed a bug where Intune Dynamic Assignments may unexpectedly match against all selected updates.
  • Fixed a bug where the ‘Republish…‘ option is not unchecked on Intune products if the UI is left open while the synchronization runs.

2.1.8 - 2022-10-10

Improvements

  • Improve speed of creating .intunewin files for Intune package creation

Fixes

  • Fixed a bug where ConfigMgr applications would fail to install with error code 0x80070057 or “The parameter is incorrect ” during the installation.
    • If an existing application has this problem in your environment you will need to republish the affected application.
    • The trigger for this bug is having the ConfigMgr option set to “Update existing application’s metadata…
    • This bug was introduced in preview version 2.1.6.35 and carried through to production version 2.1.7.0.

2.1.7 - 2022-10-06

This release contains a variety of features, improvements, and fixes, as noted below.
This will be made available via the self-update channel over the next 2 weeks. You can upgrade in place now by downloading the latest MSI installer.
Note: Starting with this production build, Patch My PC Publisher now requires a minimum of Microsoft .NET Framework 4.6.2.

Features -

  • ConfigMgr and Intune scan wizard allow drilling into list of devices where the software was detected.
  • Ability to enforce timestamping, making it a terminating error for the publishing of a product
  • Intune package extraction
    • It is now an option to store the encryption keys used to create the Intune package files (.intunewin). This is configurable in the Advanced tab of the Publisher.
    • With the keys stored, you can use the Intune Application Manager to download and extract the content of the Patch My PC published Intune applications and updates.
  • Webhooks can now be granularly scoped based on several criteria listed below. (Requires Enterprise+)
    • Webhook Provider:
      • Slack or Teams is now selectable per webhook allowing the customer to send notifications to both based on their needs.
    • Notification Level:
      • All
      • Error
      • Success
    • Notification type:
      • Update notifications
      • ConfigMgr app notifications
      • Intune app notifications
      • Intune updates notifications
      • Alert notifications
        • Low disk space, certificate expirations, license expirations etc.
    • Specific product
      • Scope a webhook to a specific product, such as notifying the network team of VPN application updates being published.
    • Specific tenants
      • If using multi-tenancy, you can specify the tenant a webhook is scoped to.
  • Allow variables to be used to customize the ConfigMgr application name and localized application name. This provides parity with the Intune feature for customized names. The variables available are below.
    • %VendorName%
    • %ProductName%
    • %Version%
    • %OriginalName%
  • ConfigMgr application retention now has the option to remove Administrative Categories from retained ConfigMgr applications.
  • ConfigMgr security scopes now have the option to enforce the selected scopes. The Publisher will remove all non-selected scopes from the application when Publisher.
  • Allow any product to have Manage Conflicting Processes configured
  • Allow the same Azure group to be assigned multiple times for Intune assignments. This allows a group to be used as both an include, and an exclude.
  • Pass variables into pre and post-scripts.
    • Note: the %ProductName% and %VendorName% variables are Base64 encoded when they are passed to the pre and post-scripts. It will need to be decoded. Patch My PC will provide a sample PowerShell snippet to decode the resulting parameter.
  • Extract content from ConfigMgr applications.
  • Extract content from WSUS updates.
  • Azure app registration secret or certificate expiration is now shown in the Intune Options form.
  • Alerts are now sent via email and webhook when secret or certificate expiration is near.

Improvements

  • When exceptions are thrown in the Manage Assignments form, they are now handled better by presenting a popup with the exception and a link to related documentation.
  • Main form accessibility has been improved.
    • Accessibility names are assigned to many controls to provide context
    • Alt-codes are added to most buttons that did not have them before
    • Right-click options are now accessible via the Apps keyboard button or shift-F10
  • When a default Patch My PC provided translation exists for a language selected in Manage Conflicting Processes it will now automatically populate the text upon adding the language.
  • Intune synchronizations will now happen in parallel for multi-tenancy. Up to 20 tenants synchronize at a time for this build.
  • Improve the speed of uploading packages to Intune.
  • Refactor email report template.
    • The background is now transparent so that it will match the theme of the email client it is opened in.
    • The code used to generate the template has been refactored to simplify future changes.
  • PatchMyPC-Scriptrunner will now factor in the major version filter when available when searching for uninstall strings. This improves the accuracy of uninstalls in some cases.
  • Added tooltips to some right-click options that describe why they are disabled in some cases.
  • Improved the error handling within the Intune Assignments forms regarding permissions for managing Assignment Filters.
  • Format the dates using ISO 8601 formatting when doing the Intune App export for PowerBI reporting. This improves international support.
  • Improved the accessibility of the WSUS Options form.
  • Improve error messaging and logging for unhandled exceptions.
  • Improved child-form handling in some cases, so they now open in the center of the parent form.
  • Multi-selection views, such as selecting application scopes or categories, now use a consistent form that allows filtering.

Fixes

  • Fixed a bug that caused the Paused products section in the email alert to be empty.
  • Fixed a bug where we would not put back the version on retained applications if the configuration was set to remove the version from application names and update existing application metadata.
  • Fixed a bug in the Intune application manager tool that caused an unhandled exception if you attempted to edit an assignment with a deadline in the past.
  • Fixed a bug where the settings backups were stored in a non-sortable format. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
  • Fixed a bug where the filters were not applied in the scan wizards when filtering the data. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
  • Fixed a bug where the ConfigMgr database scan may throw an exception due to a malformed query. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
  • Fixed a bug where the logging option to copy failed logs to a share was not retained. This bug was introduced in preview 2.1.6.1 and would only impact customers who opted into preview.
  • Fixed a bug where failing to copy additional files did not cause an Intune product to fail to publish.
  • Fixed a bug where localization files for Manage Conflicting Processes may not be copied correctly in some cases.
  • Fixed a bug where the WSUS Options window was not scrollable.
  • Fixed several UI navigation bugs on the main form.
  • Adjusted encoding of detection and requirement scripts to use UTF8. Some scripts were failing to sign with the previous encoding.
  • Fixed a bug where the Manage Conflicting Process Organization Name was not retained when republishing a ConfigMgr application.
  • Fixed a bug where the wrong URL was used for Microsoft Graph batch requests in some cases.
  • Fixed a bug where the buttons in Managed Conflicting Process may not fit the text in some translations.
  • Fixed a bug where the ConfigMgr app options window is not resizable.
  • Fixed a bug where the Manage Conflicting Process Organization Name would not be set when a ConfigMgr application was revised.
  • Fixed a bug where settings could not be saved if the internet was unreachable.
  • Fix some typos 🙂

2.1.6 - 2022-06-15

Improvements

  • Setting Delete Desktop Shortcut… or Disable Self-Updater at the vendor level will now display the list of affected products similar to when these selections are made at the All Products level.
  • Updated language in the Update Republish message box to reflect new UI changes for Advanced WSUS options.

Fixes

  • Fixed a bug where a sync may run multiple times back to back.
  • Fixed a bug where Intune authentication did not use the configured proxy.
  • Fixed a bug where republishing an Intune application or update would not update the code signing configuration of the detection script. Republishing an Intune application or update will now update the detection and requirement scripts and code signing configuration as needed.

2.1.5 - 2022-06-02

Features

  • Include server name in Publisher upgrade notification email and Teams/Slack notification.

Improvements

  • Adding German and Dutch translations to Manage Conflicting Processes
  • Intune Filter viewing and configuration is now available in all instances of managing Intune Win32 assignments in the Publisher.
  • All setting backups are now in a .CAB format. The import setting option now allows for .XML or .CAB import to ensure we support importing older setting files.
  • The Delete desktop shortcut… right-click option now removes shortcuts from the user desktop for user-based applications.
  • The SMS provider button is now highlighted in the WSUS options if the SMS provider is not configured.
  • Updated default Manage Conflicting Processes banner.
  • ConfigMgr operating system requirements are now recreated when an application is updated. This ensures new operating systems such as Windows 11 or Server 2022 are added as applications are updated in place.

Fixes

  • Fixed a bug where scriptrunner may fail to find the uninstall string in the registry for some products.
  • Fixed a bug where scriptrunner may fail to validate an installation after the installer completes causing a 3-minute delay after the installation completes.
  • Fixed a bug where Pause does not account for postponed binaries. If there is an existing postponed binary it will publish even if a pause is set.
  • Fixed a bug where some publishing summarization info was miscounted in the PatchMyPC.log file.
  • Fixed a bug where the Publisher would leave behind an empty folder when Publishing a ConfigMgr application and the download fails.
  • Fixed a bug where a version number would be appended to the current ConfigMgr application instead of the retaining application if the download fails. This bug affected customers who had the ‘Do not include version…’ option configured as well as the ‘Retain…’ option.
  • Fixed a bug where an empty Intune tenant is written to settings causing errors when the Publisher attempts to query the invalid tenant.
  • Fixed the layout of the Add MST transformation file form.
  • Fixed a bug where we may fail to query for Distribution Point groups if the name or description is DBNull instead of an empty string.
  • Fixed a bug where the ConfigMgr SUP sync would not start after a Patch My PC Sync if only updates using local content were published.
  • Fixed a bug where the Intune auto-publishing may fail in some cases when right-click options are configured.

2.1.4 - 2022-05-04

Features

  • Add Intune multi-tenant support
  • Dynamic Assignments for Intune
  • Allow Intune assignment and ESP options to be set per product to override global options.
  • Per product retention setting for Intune Apps and Updates
  • Validate the hash of pre/post scripts on sync as well as during a republish.
  • Collect Logs button now prepends the file name with the company name from the license.
  • The email report now converts size to a readable format such as MB or GB instead of bytes.
  • Support for Intune Filters
  • Certificate Authentication for Azure App Registration
  • Option to pause creation of updates or applications for specific products
  • Allow per-tenant branding for Manage Conflicting Process

Improvements

  • CSV files are now saved with UTF-8 formatting.
  • PatchMyPC.log file now includes the timestamp for the catalog that is processed.
  • When a download happens we now write the redirected URL to the PatchMyPC.log as well as in the PatchMyPC-DownloadHistory.csv.
  • The Publisher will now retry every 10 seconds up 12 times when saving Package.xml for ConfigMgr applications. This helps account for file locks caused by antivirus.
  • The email report has been updated (dark mode)
  • Add an operator dropdown in the filter options for Intune and ConfigMgr scan wizards
  • Improve Manage Conflicting Process configuration window to better support scaling

Fixes

  • Fixed a bug where Intune ADR would publish both an Application and an Update.
  • Fixed a bug where we might fail to match a running process with Manage Conflicting Processes if the case of the process name did not match.
  • Fixed a bug where illegal characters were allowed in file paths, such as a custom log path.
  • Fixed a bug where an application may report being automatically enabled during every sync in some scenarios.
  • Fixed a bug where the Manage Conflicting Process UI would not show up for a user-based application.
  • Fixed a bug where the Manage Conflicting Process UI would not show for an Intune application when the user is not an Administrator.
  • Fixed the Collect Logs button so it takes into account custom log paths as defined in the Publisher.
  • Fixed a bug causing enter to close the group search form for Manage Assignments when in the group input textbox.
  • Fixed a bug where PatchMyPC-Scriptrunner may throw an exception during log cleanup if the folder does not exist
  • Fixed a bug where the publishing summary in the PatchMyPC.log would not include products published from the local content repository
  • Fixed a bug where changes to Intune assignments are applied even if the assignment form is cancelled
  • Fixed a bug where the Manage Conflicting Process window would not show up when the product install is triggered via Company Portal as a non-admin user
  • Fixed a bug where ConfigMgr app retention setting right-click option is not checked when configured
  • Fixed a bug where the Updates (WSUS) tab could be used while on an Intune license

2.1.3 - 2022-02-04

Features

  • Support for maintaining application dependencies in Intune
    • Checkbox added to Intune Options window: “Update application dependencies from previously created applications when an updated application is created”

Improvements

  • When republishing an Intune application or update there is now a prompt asking if assignments should be recreated. The newly recreated assignments would have a deadline and available time relative to the sync when the republish happens.

Fixes

  • Fixed a bug where republishing a ConfigMgr application would remove existing application dependencies, supersedence, and requirements the customer may have added.
  • Fixed a bug where the Manage Conflicting Process option to use the ConfigMgr application max run time for the notification timeout would not work for a republished ConfigMgr application.
  • Fixed a bug where republishing an Intune application or update might remove existing assignments.
  • Fixed a bug where we may fail to put back the version on the name of retained ConfigMgr applications in some scenarios.
  • Fixed a bug where the Manage Conflicting Process UI may fail to identify conflicting processes causing it not to show.
  • Fixed a bug where the Manage Conflicting Process UI may default to a 5-hour timeout for ConfigMgr applications in some scenarios.
  • Fixed a bug where delayed ConfigMgr applications may publish one day early.
  • Fixed a bug where the IsFeatured flag would not be set for a republished Intune application.
  • Fixed a bug where the Publisher would fail to validate a ConfigMgr source path if there were Deployment Packages with an empty source path.
  • Fixed a bug where the Publisher may delete a content folder during republishing if the binary was missing from the local content repository.
  • Fixed a bug where the Manage Conflicting Process UI notification would fail to display if the user DateTime format and the system DateTime format were conflicting, causing DateTime parsing failures.
  • Fixed a bug where the Manage Conflicting Process notification timeout setting may not be read correctly from settings.xml.

2.1.2 - 2021-12-23

Features

  • Collect Logs button added to the Publisher. Will create a .zip file of files useful for troubleshooting.

Improvements

  • If the ConfigMgr applications are configured to remove the version from the name, and there is application retention configured we will now append the version to OLD versions of the app. This is to ensure that there is only one application with the same name.
  • Improved the initial configuration process for adding Patch My PC Software Updates to an environment. This involves attempting to restart the WCM component after an initial Patch My PC update is published. This expedites getting the Patch My PC category into ConfigMgr so it can be selected.
  • The Publisher will send an alert if the catalog failed to download.
  • The Publisher can now process FTP links for downloads.
  • Updated to the latest Patch My PC logo.

Fixes

  • Fixed a bug where the Republish feature may cause multiple republish actions to occur if the customer performs the operation on multiple tabs.
  • Fixed a bug where ‘disabling’ a tab with the checkbox at the top would cause the settings to be lost if the Publisher was closed.
  • Fixed a bug where the alert webhooks may be duplicated during a setting import.
  • Fixed a bug where some unsupported right-click options might be enabled by the auto-enable product’s rules.
  • Fixed a bug where conflicting process notification timeout setting was not being read properly from settings.xml causing the setting to not apply.
  • Fixed a bug where the /SyncNow switch for the Publisher would not work if an instance of the Publisher was already running.
  • Fixed a bug where multiple assignments for the same group may attempt to be created in Intune.
  • Fixed a bug where the Organization Name specified for the Manage Conflicting Process window would not be populated for ConfigMgr applications.
  • Fixed a bug where the icon would not be set for a republished Intune application.
  • Fixed a bug where the republish ConfigMgr application feature would not validate the hash of existing additional files which caused edited files to not be copied during a republish.
  • Fixed a bug where republish ConfigMgr application would not set the expected OS requirements.
  • Fixed a bug where ‘Override manual assignment changes’ is checked for an Intune product, and there is an ‘exclude’ assignment which would cause the Publisher to fail to process all assignments.

2.1.1 - 2021-11-02

Features

Improvements

  • It is now possible to ‘Manage ESP assignments’ from within the Intune Application Manager.
  • ConfigMgr database scan button is now available on the ConfigMgr apps tab as well as the Updates tab.
  • ScriptRunner will always use Intune-based folders when executing from an Intune app installation.
  • ScriptRunner will now monitor for child processes during the uninstall of software. This ensures that uninstalls which spawn child processes do not exit immediately and cause a detection error.
  • Prevent using a ConfigMgr source path that could cause paths to exceed the 256 windows path limit.
  • Fixed a bug where publishing would proceed even if a custom script failed to be processed.

Fixes

  • Fixed a bug where the Publisher would fail to parse a command line that had a parameter that occurred more than once. This would cause a content update every sync.
  • Fixed a bug where Recreate Detection Script option for ConfigMgr would cause the wrong ‘Installation Behavior’ to be set for user-based apps.
  • Fixed a bug where the Publisher and ScriptRunner would fail to parse a parameter with nested quotes and spaces.
  • Fixed a bug where PreventStart UI would fail to be bypassed when a SYSTEM launched a conflicting process potentially leaving behind Image File Execution Option registry keys.
  • Fixed a bug where retained applications may be updated unexpectedly when both postpone app and retain app are configured.
  • Fixed a bug where the Publisher would run a sync every time ‘Apply Changes’ is clicked and the schedule is set to hourly.

2.1.0 - 2021-09-16

Features

  • Improve conflicting process timeout options
    • ConfigMgr and Intune timeout increased to their respective maximums, minus a 15-minute buffer.
      • ConfigMgr App Max: 705 minutes
      • Intune Max: 45 minutes
    • New option to use ‘maximum run time’ from the respective update or app.
      • ConfigMgr Update Max: Will use configured update ‘max run time’ as configured in ConfigMgr for the update.
        • Note: Update max run time must be edited before the update is deployed for a client to recognize the change.
      • ConfigMgr App Max: Will use the configured deployment time ‘max run time.’
      • Intune App/Update Max: Will use the maximum run time of an Intune Win32 app (60 minutes minus the 15-minute buffer).
  • Send an alert if the Publisher failed to auto-update.
  • Send an alert when the Publisher is updated
  • Add time zone to Teams/Slack Webhook notification
  • Split out notification settings to allow Error notifications and Information notifications to go to different webhooks

Improvements

  • Text boxes within the UI now implement an autocomplete for file paths and URLs.
  • The Manage Conflicting Processes notification will now display ‘update’ based language for an Intune Update. For example, the button will say ‘Close and Update’ instead of ‘Close and Install.’

Fixes

  • Fixed a bug where the Publisher would throw an exception if a ConfigMgr scope is deleted, but still associated with a product in the Publisher.
  • Fixed a bug where Intune email reports would not include the warning regarding missing local content for applications
  • Fixed a bug where the ConfigMgr source folder validation would perform a partial match, such as \\server\source_apps being considered a conflict for \\server\source. We now append a trailing slash to the comparison.
  • Fixed a bug where the ‘Prevent Start…’ option for Manage Conflicting Process would throw an access denied error instead of the desired message box.
  • Fixed a bug where assignments would be copied from Intune app to Intune updates when the copy between tabs is used.
  • Fixed a bug where custom return codes set in the catalog were not processed for updates by the Publisher.
  • Fixed a bug where ConfigMgr applications would be revised every sync when the Manage Conflicting Process option is set to an option other than ‘Notify’

2.0.9 - 2021-08-09

Features

  • Double-clicking a product in the Publisher will now bring up the ‘Show Package Info…‘ tool.
  • The Publisher will now check the permissions associated with the token for the Azure App Registration and provide more specific errors and logging. Additionally, the ‘Test’ button now presents a more information UI for permission validation.
  • Log current working directory in PatchMyPC-ScriptRunner.log
  • Export the list of enabled products and their right-click configurations to a CSV. This option is available in the Advanced tab of the Publisher. Only enabled products are exportable.
  • Publisher will validate the ConfigMgr application source path. A path is considered invalid if it is not a UNC path, or if the path is in use by a Software Update Deployment Package. Existing invalid configurations will not be impacted, but there will be an alert via email or Teams if alerts are enabled.

Improvements