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 coming days. You can upgrade in place now by downloading the latest MSI installer.
Features
- Migration from ConfigMgr to Patch My PC Cloud (Private Preview)
- Read only for Enterprise+ customers
- Read/Write for Enterprise Premium customers
- Add support for ECDSA code signing certificates
- Add a progress bar to the Publisher UI – displays the current application or update being processed
- Add a filter button to only show products that are selected in the Publishers UI
Improvements
- Enabling publisher to allow users to override win32 app options for custom Intune apps and Intune updates
- Updated the process for saving logs to use a SaveAs to allow users to customize the location and filename of the saved logs
- Enhanced the notifications to include included/excluded status
- Added a notification to the ConfigMgr scan wizard to notify users when there are SQL errors
- Improved how Publisher displays information around misconfigured items and items that require manual content to ensure the warning does not consume the entire screen
- Trigger search in Entra ID Group Search window when pressing Enter key
- Present a warning when importing a code signing certificate if ConfigMgr is set to automatically manage your code signing certificate
- Add additional fields, related to user install statistics, to the Intune Application Manager
- Modernised the icons in the Publishers UI
- Ensure the scrollbar on the Intune application scan wizard only shows when needed
- Improve the logging of PowerShell-based detection and requirement script signing
- On new installs the PatchMyPC.log file is stored in the Logs subfolder of the installation directory
- Write the name of the account used to run PatchMyPCService to the publishers log file
- Amended the rolled over log file extension from
.lo_
to.log
- Log username of active user when using Manage Conflicting Processes to kill processes
- Improved logging when ScriptRunner calls PowerShell scripts
- Add an IntuneReportsRequestTimeout registry option to set the timeout for Intune reports (default: five minutes)
- Update tooltips in the Publisher UI for Manage Conflicting Process timeouts to reflect Intune changes
- If the code signing certificate is not found, then WSUS updates will not process
- If the code signing certificate is not found and ConfigMgr detection script code signing is enabled, then ConfigMgr apps will not process
- Improve the handling of UINotificationSettings.xml for Manage Conflicting Processes – now generated per session to prevent access denied errors
Bug Fixes
- Fixed a bug where additional files, folders, and Patch My PC defined pre/post-scripts were not processed when updating existing ConfigMgr applications
- Fixed an issue where Selective Sync (Publish Now) would not take into account postponed ConfigMgr app updates, causing all postponed app updates to be processed regardless of Selective Sync enablement
- Fixed a bug where Publisher would leave behind files from older versions of an application
- Fixed a bug that caused Manage Conflicting Processes to fail to close running applications in some scenarios
- Fixed the URL for the Patch My PC logo in webhook alerts
- Fixed a bug that would allow a configuration of maximum application runtime that conflicted with the Manage Conflicting Process notification runtime
- Fixed a bug that caused the filtering of Intune groups to hang the UI
- Fixed a bug where rolled over log files were not cleaned up according to retention settings
- Fixed a bug where the Publisher may select the incorrect SMS_Content instance in some cases when searching for a previous ConfigMgr application
- This fix addresses the alert “Unable to process <Application Name>. PackageId… does not find an application with a matching content source path…”
- Fixed a bug that caused customers to see an error message if ScriptRunner tries to display a notification while Focus Assist is enabled
- Fixed a bug that caused Postponed binaries to fail to process when custom applications are enabled and the PostponedBinaries folder does not exist.