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
- 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).
- ConfigMgr Update Max: Will use configured update ‘max run time’ as configured in ConfigMgr for the update.
- Idea: PATCHMYPC-I-1516
- ConfigMgr and Intune timeout increased to their respective maximums, minus a 15-minute buffer.
- Send an alert if the Publisher failed to auto-update.
- Idea: PATCHMYPC-I-1254
- Send an alert when the Publisher is updated
- Idea: PATCHMYPC-I-791
- Add time zone to Teams/Slack Webhook notification
- Idea: PATCHMYPC-I-856
- Split out notification settings to allow Error notifications and Information notifications to go to different webhooks
- Idea: PATCHMYPC-I-1536
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’
Published On September 16, 2021