Production Releases
You can find the production release history for the Patch My PC Publisher below.
- Intune option added to ‘Copy requirements’ for Intune products. This can be configured globally, per vendor, or per product.
- 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.
- 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.
- 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.
- 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 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.
- 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.
- 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.
- 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 the ‘Republish…‘ option is not unchecked on Intune products if the UI is left open while the synchronization runs.
- Improve speed of creating .intunewin files for Intune package creation
- 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.
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.
- 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.
- 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.
- 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 🙂
- 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.
- 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.
- Include server name in Publisher upgrade notification email and Teams/Slack notification.
- 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.
- 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.
- 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 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.
- Add Intune multi-tenant support
- Requires MSP license
- Dynamic Assignments for Intune
- Requires Enterprise Plus
- 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
- Requires Enterprise Plus
- Certificate Authentication for Azure App Registration
- Option to pause creation of updates or applications for specific products
- Requires Enterprise Plus
- Allow per-tenant branding for Manage Conflicting Process
- 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
- 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
- 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”
- 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.
- 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.
- Collect Logs button added to the Publisher. Will create a .zip file of files useful for troubleshooting.
- 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.
- 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.
- Allow customized Managed Conflicting Process popup notifications, including support for localization.
- Option to “Republish” ConfigMgr and Intune Applications
- 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.
- 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.
- 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
- 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.’
- 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’
- 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.
- Added tooltips to fields in the scan wizards to improve accessibility.
- The Publisher will not delete the local content for a product if the publishing of the product failed.
- The Publisher will automatically revise an update if the applicability rules or description is updated in the catalog.
- The Publisher now supports log rollover of up to 10 log files. Previously we would only retain one rollover log. This is configurable in the General tab of the Publisher above the max log size.
- Fixed a bug where the Manage Conflicting Process window may not show the proper process name in the list of conflicting applications.
- Fixed a bug where the Publisher did not respect the ConfigMgr app retention settings when the delay in-place upgrade feature was also in use.
- Fixed a bug where Intune apps and updates would not use the temp content download directory specified in the advanced tab.
- Fixed a bug where the Publisher would revise ConfigMgr apps every sync in certain cultures (The known issue was with Russian, but could impact others).
- Fixed a bug where the alert webhook configured for Slack may revert to a Teams webhook causing malformed messages.
- Fixed a bug where the Manage Conflicting Process UI may continue to append text instead of having a countdown when it is set to ‘Do not allow user deferral…’
- Fixed a bug where pre/post uninstall scripts would only copy into the ConfigMgr source during a new application publisher. Scripts will now be copied into the source during the sync after the configuration change.
- Fixed a bug where the Intune Assignment UI would allow an invalid grace period/restart/snooze configuration.
- Fixed a bug where PatchMyPC-ScriptRunner would create an invalid command line for an MSI uninstall in some cases.
- Fixed a bug where the Manage Conflicting Process UI would fail to enumerate some properties of the blocked processes causing it to close the blocking process before the user can interact.
- Manage Conflicting Process ‘Close and Update’ button will now call the CloseMainWindow first. If the conflicting application is still running after 20 seconds we fall back to the Kill method.
- This gives the user 20 seconds to respond to any ‘save’ prompts or other app-closing windows.
- Pre/Post scripts for uninstall
- Manage Conflicting Process settings also apply to uninstall. This ensures that a user will be prompted to close software for the uninstall as well.
- Allow multiple webhooks so alerts are posted to multiple endpoints.
- MSI uninstall performed by Scriptrunner will append REBOOT=ReallySuppress to the uninstall command.
- MSI uninstall performed by Scriptrunner will generate an MSI log file if logging is configured for the application in the Publisher.
- If publishing an update fails with timestamping then we will attempt to publish again without timestamping.
- Improved connection testing to patchmypc.com:443 during publisher sync.
- During Publisher sync the WSUS cleanup for ‘Unneeded update files’ will now run.
- Manage Conflicting Process UI should now scale better vertically.
- Fix user validation of the input fields for pre/post script when the file does not exist.
- Fixed Intune detection script which was looking for a non-existent ‘dn’ property.
- Fixed Intune detection script so that it will parse invalid version parts that exceed a 32-bit signed integer.
- Fixed ConfigMgr detection script so that the RegKeyDetection work as expected for enhanced detection based on additional registry key values.
- Script Version: 3.1
- Fixed a bug where double-clicking an item in the Intune App Manager would cause an ‘Index out of Range’ unhandled exception. This now opens the Manage Assignment wizard as expected.
- Fixed a bug where ConfigMgr applications with only user-based deployment types would have the checkbox set to allow installation during a task sequence, which is not allowed.
- Fixed a bug where the UI notification log file may not be created if the folder does not exist.
- Fixed a bug where user-based ConfigMgr applications may not have the Application Experience configuration properly configured.
- Fill out ‘Disk Space Required’ for Intune apps.
- Intune app manager will filter by PMPC published apps by default, providing a drop-down to select non-PMPC or all apps.
- Within the ‘Show Package Info‘ window, you can now right-click on any cell to copy the cell data or the row data to your clipboard.
- Further improvements to CM log format for culture compatibility.
- Add support to re-sign updates.
- Use windows native methods for signing PowerShell scripts.
- PowerShell detection scripts will use regex to extract the version from the displayVersion field to account for vendors that put more than the version in the field.
- Set ErrorAction to SilentlyContinue for extra regkey validation checks to suppress errors in the event the key does not exist.
- Add a delay in Scriptrunner if the main installer exits in less than 2 seconds. This is to account for installers that spawn child processes.
- Fixed a bug where a ‘Security Error’ may occur when signing PowerShell scripts and a PowerShell Execution Policy is set via GPO.
- Add option to update Intune assignments on sync.
- New checkbox at the bottom of the Manage Assignments wizard to ‘Override manual assignment changes…’
- Add the title of the application or update to the Manage Assignments wizard.
- Notifications are presentation mode aware
- View and customize Conflicting Processes list
- The UI notification for Conflict Processes now lists all processes which are conflicting in a dropdown. This is to make it more clear what software will be closed.
- Send alerts to Slack
- Note: Slack notifications are a work in progress.
- Reverted a Scriptrunner change which flagged the exe to always run as Administrator. This is in preparation for supporting user-based applications in Intune and ConfigMgr.
- When a product is double-clicked in the show package info tool the applicability rule will be shown.
- Improve the message which displays when an incorrect configuration is saved.
- Code changes in preparation for user-based applications.
- Publisher SMTP alerts for the creation of ConfigMgr apps, Intune apps, and Intune updates will all now show the CVE information. Previously only the WSUS updates would show this information.
- Added notes to the pre/post script window to help clarify the feature functionality.
- Fixed a bug where the Manage Conflicting Process window would not appear when a ConfigMgr application was deployed as required and the checkbox for ‘Allow user interaction…’ was not checked.
- Fixed a bug where Intune role scope tags would not be updated on sync for Intune Updates.
- Fixed a bug where the configured proxy may not be used for the Intune connection during publisher sync.
- Fixed a bug where software may be marked for revision during every sync of the Publisher. This would occur when PreventConflictingProcessRestart was in use and the KillProcess was set instead of Notify.
- Fixed a bug where the 'Exclude from Auto-Publishing' option for Intune apps and Intune updates may not work as expected causing excluding software to still be published if found.
- When a user or admin category was selected on a ConfigMgr application the Publisher would create a revision of the application every synchronization. Now a revision will only be created if a user or admin category needs to be added.
- Improved logging when checking access to timestamp.digicert.com if a proxy is defined
- Adding a right-click context menu to the Intune App Manager allowing you to navigate to the MEM portal to view some application information.
- Fixed a bug where ConfigMgr applications would not populate in the Publisher if a scope was set at the All Vendors or the Vendor level.
- Added the Usage Statistics group in the General tab that will show usage statistics
- Changed the license input to display only the 20 character license id and not the full license URL
- Define ConfigMgr scopes inside the Publisher service