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
- Email and Webhook notifications now include information about delayed ConfigMgr applications during each sync.
- Idea: PATCHMYPC-I-1862
- 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.
Published On March 27, 2023