This release contains a variety of features, improvements, and fixes, as noted below.
Improvements
- Add an IntuneReportsRequestTimeout registry option to set the timeout for Intune reports. The default value is 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. They are now generated per session.
- XML per session prevents access denied errors that can occur when one user creates a file and another non-admin user later attempts to edit it.
Fixes
- 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…”
- Refer to this KB article for more information.
- 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.