Production Releases 1.x
Production Releases for version 1.0.0 - 1.9.9
- Improved the updating of supported products metadata during Publisher synchronization.
- Adjust certificate signing validation for Patch My PC signed files.
- Fixed an issue where Recreate Detection for MSI-based applications would not populate some variables in the script.
- Manage categories for Configuration Manager applications
- User Categories: Viewable to users in Software Center
- Admin Categories: Viewable to administrators in the Configuration Manager Console
- ScriptRunner now has a new custom variable, %CurrentDir%
- This variable may need to be put in double-quotes or the entire parameter may need to be in double quotes depending on the application. Examples of this are below.
- Config=”%CurrentDir%\Config.ini”
- “Config=%CurrentDir%\Config.ini”
- During a Publisher sync, the Settings.xml will be automatically updated according to SupportProducts. This improves the experiences when Patch My PC makes metadata changes that impact some of the application configurations such as detection.
- The Intune Application Manager now has a button for ‘Manage Assignments’
- Improve how ScriptRunner handles version parts that exceed the 32 bit signed integer max.
- Improve logging associated with delayed application publishing
- Manage Intune categories for created and updated Intune applications and updates.
- Note: Currently, existing applications/updates in Intune will not have their categories removed but new categories will be added for existing Win32 applications.
- Clicking a ‘digest’ in the Modify Published Updates Wizard, or the Package Details wizard will now open the respective VirusTotal page.
- Sorting by ‘Selected’ in Modify Published Updates Wizard now sorts by the checked state.
- The Configuration Manager detection script now handles invalid version parts better. Some vendors use DateTime stamps in their version. This can end up being a value larger than a 32-bit integer causing the version cast to fail.
- Fixed an issue where copied Intune Assignments for newly published Intune software would not have their custom available time, and deadline time adjusted relative to the new publish date.
- Fixed an issue where Intune Assignments would be created without a deadline or available time if the ‘copy assignment’ option was not configured.
- Fixed an issue where the maximum value for restart notification would not allow a value greater than 201.
- Fixed a bug where the console version check for UninstallContent setting was incorrect.
- Improved catalog parsing when there are a large number of CPU cores on the machine running the publisher.
- The below information can be viewed for the currently synchronized catalog.
- Title (Including version)
- File Name
- Command-line
- Download URL
- Digest
- Improved the speed at which the catalog is processed. This will improve the loading speed of the CVE Import Wizard, the new Package Details Feature, and the Modify Updates Wizard.
- Improved the speed at which the catalog is extracted for the CVE Import Wizard.
- Win32 Intune applications will no longer be created as featured by default.
- Existing Intune applications will not have their ‘featured’ state changed. The Publisher will retain the currently configured ‘featured’ setting for any given application.
- Fixed a bug where new Intune assignments may not be created.
- The first release of our CVE import/matching features based on UserVoice Feature Request for CVE Import automation
- You can launch the CVE import feature in the Updates tab by clicking the new document lock icon
- If you have any feedback on the first release, leave a comment at https://ideas.patchmypc.com/ideas/PATCHMYPC-I-916
- Updates published via the CVE Import Wizard will have a Teams and Email alert if enabled.
- Scan Configuration Manager Database wizard updated.
- Supports Filtering
- Can optionally show, and export, applications whose count is zero.
- General UI improvements such as tooltips, alt-shortcuts, empty field validation.
- Certificate selection for Intune code signing will now additionally search the WSUS store if it is found.
- The Product Name has been added to the PatchMyPC-DownloadHistory.csv generated in the installation directory of the publisher.
- Improved the method used to gather PackageID from newly published Applications.
- Fixed a bug where an application may fail to publish on versions of Configuration Manager older than 1706.
- Fixed a bug where the publisher would fail to find applications published to a folder containing square brackets
- For Example: \\server\sources\[PMPC]Applications
- Fixed a bug where the TLS port for SMTP alerts may show as 587 in the UI, even when a custom port is set. The port in the UI will now accurately reflect the saved settings.
- Fixed an issue where Intune assignments may not set the correct delayed deadline
- Fixed an issue where older versions of the ConfigMgr console may receive error: Method not found: ‘Void Microsoft.ConfigurationManagement.ApplicationManagement.MsiInstaller.set_UninstallSetting(Microsoft.ConfigurationManagement.ApplicationManagement.UninstallContentSetting)’.
- Application update in-place vs. create new application configurable at the individual product level.
- Support for user-based installations for Configuration Manager applications, as well as Intune Applications and Intune Updates.
- Note: We still need to add user-based software to the catalog, but the publisher now has support for this so that we can begin adding some user-based software.
- Option to not append the republished date tag to republished updates.
- This is now a configurable checkbox in the advanced tab.
- Update the PatchMyPC-ScriptRunner.exe to use the CCM client log directory defined in the registry by default
- Check“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global”> LogDirectory, and fallback to “%windir%\ccm\logs”
- Log out the in-progress count of updates and applications as they are processed.
- Previously the in-progress count was only logged if the log level was set to debug. It is now logged with informational level logging.
- Improve the PatchMyPC-ScriptRunner.exe to have better logic when searching the registry for uninstall strings
- The PatchMyPC-ScriptRunner.exe will retry MSI based operations if a 1618 exit code is returned by the installer. The result is a reduction in failed installs due to Windows Installer being unavailable.
- Maximum three retries, with 1 minute in between.
- Updated the PowerShell script for Intune applications and updates to improve compatibility with constrained language mode.
- Optimized icon resizing for ConfigMgr applications.
- MSI based ConfigMgr applications will now have 'No uninstall content' set for the uninstaller, as we directly call msiexec, no content is needed.
- Configuration Manager application detection script fixed to supported PowerShell 2.0.
- Fixed an issue where republishing a WSUS update would also cause the equivalent Intune Update to republish as well.
- Fixed an issue where the Intune Application Manager Utility would throw a terminating error if Intune applications were found with an empty ‘Notes’ field.
- Added an option to disable WSUS publishing using a checkbox at the top of the 'Updates' tab. This allows the Update publishing feature to be disabled while still retaining all products and settings. This can be helpful if you need to sync only Applications, Intune Applications, or Intune Updates, but don't want to lose your selected Updates and configurations.
- Added a right-click option to open the help page that details the right-click options.
- During synchronization, the Publisher will check if the WSUS code signing certificate is expired or near expiration and add a message in the email report.
- During synchronization, the Publisher will check if the WSUS code signing certificate is in the required Windows Cert stores and add it if needed.
- SMTP port automatically set to 587 when 'Use TLS' is selected, and to 25 when 'Use TLS' is unselected. The port can still be manually edited to account for any port, but the common port for the protocol is set by default.
- Add additional known errors in the log, providing a link to a KB article that may assist with solving the known error.
- Display additional info in the Certificate information wizard on whether the certificate is found in the expected Windows Cert stores.
- SMTP port default to 25 instead of 587 when the feature is in a non-configured state.
- The Publisher will retry several times when the rename of a folder during an SCCM application upgrade fails. This should help prevent'Access Denied' errors that are caused by file locks.
- Fixed an issue where, sometimes, the SupportedProducts.xml file cannot be read during a synchronization.
- Fixed an issue where a machine with a large number of CPU cores may experience high CPU load when running the Intune Scan Wizard.
- Fixed a bug where if the application delay option is enabled and an update contains spaces in the file name such as Firefox, it may download with an incorrect file name.
- This would cause the following error in appenforce.log:
- **fails to install error code Looking for exit code-2147467259 in exit codes table**
- Unmatched exit code (2147500037) is considered an execution failure.
-
- The Publisher now has a 'Recreate Detection Script' right-click option. When this is selected, the specified products will have their Detection Scripts recreated during the next Publisher synchronization.
- The Modify Updates Wizard now has a checkbox to 'Show Only Updates for Not Enabled Products'
- This is helpful in identifying updates you may want to decline for products you no longer publish updates for
- Intune Application and Update detection script now has improved version string parsing
- Intune Application and Update detection script will only parse DisplayName for a version if the DisplayVersion is empty
- SCCM Application detection script will only parse DisplayName for a version if the DisplayVersion is empty
- VLC is now split into an EXE and an MSI
- The existing selection of VLC will be converted to the EXE version of the application. The MSI can now also be selected and published.
- Pre/Post Script form now validates that Pre-Update Script and Post-Update Script exists before allowing you to press OK.
- Fixed an issue where the Publisher was unable to get the list of published Intune applications.
- Fixed an issue where a republished WSUS update may be republished multiple times if the Publisher was left open during synchronization and settings were changed after the initial republish completes.
- Fixed a bug where certain detection scripts generated for Intune Applications and Intune Updates would not detect as expected.
- Improved the copying of right-click options from the Updates tab, to the ConfigMgr Apps tab, or the Intune Apps tab.
- Fixed an issue where the Publisher would falsely report that it was not installed on a Software Update Point in some scenarios.
- Fixed an issue where the Intune Updates product list was not reloaded during publisher sync in some scenarios.
- Fixed an issue where Intune Applications would not detect appropriately for certain applications. OneDrive was a known affected product, but others may have been included.
- Fixed an issue where the Intune Connection Options would log out an error state 'Invalid Uri.'
- Fixed an issue where ConfigMgr Base Applications were created with a detection script that did not specify a version to search for. All base applications created with **Publisher Version 1.8.4 or newer(released 2020-07-22)** would always show as detected if any version was installed on the endpoint. The version was not being validated.
- The affected detection method would show version 2.2 in the logs, and in the script itself.
- Applications created after 2020-07-22 by the Publisher should be deleted and recreated to ensure the proper detection method script is used.
- Fixed a bug where the publisher would report ‘Cannot get available disk space’ when validating there is enough free disk space for deferred application publishing.
- Fixed a bug where the publisher would fail to parse the Proxy URL, reporting the following error.
- An error occurred while converting the provided Proxy URL to a URI for use by the Web Client…
- You can now automatically create the security role for allowing the publishing to create Configuration Manager applications.
- Within the ‘Manage Assignments’ page for Intune Applications and Updates the cells now have a clickable link to open up the form for managing available dates, deadlines, and restart behavior. Previously this link was only on the application name.
- Fixed an issue where SMTP settings were not properly translated when the new Anonymous authentication option was added.
- Fixed an issue where right-click settings from the “All Products” level may not be applied when copied to another tab.
- Support for Intune Updates
- Add Anonymous authentication method to send emails.
- Intune updates use the description in the SDP for the title.
- Split the «Delete Intune Application when a new release is published» option to allow to choose the behavior for Apps and Updates independently.
- Add a button to export data in the Intune Apps Manager.
- Add a column to show Classification in the Intune Apps Manager.
- Allow to show «Applications only», «Updates only» are «All» in the Intune App Manager.
- Display the Publisher service's status on the 'About' tab.
- Download timeout is now logged out in minutes and seconds, instead of milliseconds.
- Implement log rollover for Intune detection and requirement scripts.
- Send an MS Teams message and add a line in the Email report if the server runs low on disk space on the PMPC installation or the Wsus Content drive.
- Support for the Contains string operator when searching for an AAD Group.
- The Publisher will notify the user if the installation drive is running low on disk space.
- The Publisher will notify the user if the Publisher is installed on the Site Server, and the server is not also a Software Update Point.
- Tooltips added to buttons on Intune Apps and Intune Updates tabs.
- When several files with the same name are found in the Local Content repo, and subdirectories, we try to identify the right one with the expected digest before falling back to downloading.
- Fixed an issue where custom options are not correctly copied between two tabs when copying enabled products from one tab to another.
- Fixed an issue where reserved characters were not working as expected when searching for Azure AD Groups
- Fixed an issue where the Publisher may display a warning that the certificate is incorrect or missing when it's within 30 days of the expiration date.
- Changed how Unreferenced Package Folders are found. If third party updates are set to display in WSUS, then they might show up as 'Unreferenced' by the WSUS content cleanup tool. The publisher now correctly display the list of unreferenced contents.
- Available date and deadline date for Intune assignments are not properly displayed in the assignment setting wizard
- The Publisher may crash when trying to check for a new release on Intune only installation where only RSAT:Windows Service Update Services is being used. If you are affected by this issue, please perform an in-place upgrade of the publisher using
- Add an Intune Scan Wizard allowing you to auto-enroll applications based on Intune App scanning.
- Add all options available in the 'User Experience' for Applications to a new context menu option for base installs.Improvement
- Add more logging to the application update and creation processes to assist with troubleshooting.
- Code optimization and cleanup for applications.
- Detection script now accounts for user-based installs when needed.
- Detection script checks if running as SYSTEM using the SID instead of the username.
- Add a new known error to assist with identifying and resolving TooManyCategories for WSUS.
- Enabled CTRL+F functionality in the Intune tab.
- Product download will fallback to the Internet in case of a digest mismatch in the local content repository.
- Display third party vendor/product count in the Update Modification Wizard.
- Deprecate WSUS v3
- We now use a FIPS compliant algorithm when creating Intune applicationsFixes
- Fixed a bug where the Publisher service would never timeout during content downloads in some scenarios, causing the service to hang.
- See the HTTP Download Timeout section for more information regarding the timeout. The default value is a 15-minute download timeout.
- Fixed a bug where some system cultures would result in incorrect command-line parsing.
- Fixed a bug where an application's content would not be updated when a right-click option was selected in some scenarios.
- Fixed a bug where the 'exclude from autoenrollment' option was unable to be changed on a product when the setting was configured at the vendor level.
- Fixed a bug where the publishing service could not publish a postponed application if it contained an HTML escaped character.
- Fixed a bug where the Intune Scan Wizard was overwriting the Intune Authentication URL
- Fixed an issue where the checkbox in the MSI installer to enable Intune only mode may not be applied after the installation
- Fixed an issue where the republish option no longer showed for"All Products" and Vendor nodes
- Fixed an issue where incorrect workstation counts were shown on certain SSRS reports
- Fixed an issue where the admin comment field of a dependent application would be updated to say the application was created by Patch My PC
- Fixed an issue where the republish updates right-click menu may exist in the ConfigMgr Apps and Intune Apps tab
- Settings tool can crash when copying enabled products from the WSUS tab to another tab if the «All Products» node is not displayed
- Teams notifications are malformed if they contain a file path.
- Add button to restart the service
- Cache binary for postponed updates allows postponed updates to be published after the download link has changed.
- Custom right-click options applied at the All Products level are now retained when the UI is closed, and future products are enabled. UserVoice Idea: Retain the Logging Options in View when Saved at the All Products Level
- SCCM Database Scan now has an option to "Auto-enable products as 'Metadata Only' if found, but threshold is not met"Fixes
- Fixed bug where some SSRS report links did not function as expected
- Fixed an issue where a customer with an expired Intune only license could get stuck in a message box loop.Improvements
- Enhances the display in the Update modification wizard when there is a lot of updates.
- Sort SCCM folders when choosing a folder to move new newly created applications to. UserVoice Idea: Fix sorting in Console Folder Browser
- Allows creating a self-signed certificate with the private key marked as non-exportable.
- Added new subscription state reporting using Teams or SMTP emails
- Added 'Like,' 'Dislike', and 'Feedback' button in the title bar of the settings tool.Fixes
- List unreferenced package folders did not list any folders in some WSUS configurations
- Added a workaround to handle SCCM apps published with an unsupported language
- Resolved incorrect summarization within the SCCM Scan Database toolImprovements
- Web domains of downloaded icons are listed in the DownloadHistory.csv file.
- Added several help links in the UI.
- Improved logging for known errors linking to KB articlesChanges
- The option to fallback to ConfigMgr package publishing when an application can't be published as an SCCM application has been removed in the UI due to not being needed.
- SQL query default timeout is now 90 seconds from 30 seconds.
- Removed from the UI the option to generate a CSV file with publishing info. The option is always enabled, and the file path can be configured with the registry setting : HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:PublishingHistoryCSVFolder
- Intune assignments created during an application creation or update are now reported in Teams notifications and email alerts(Idea:
- Adds a line in the log to specify Intune AppIDs (old and new release) during an application updating (Idea:
- Improves how Azure AD groups are retrieved (Set page limit to 999). We will also now display O365 groups. Adds the ability to search a group based on the group name starts with (Idea:
- Adds a new column, UpdateEnabled, to the resulting CSV from the SCCM Scan Database Wizard -
- UI improvements to the Base Install options
- Generates a CSV file (PatchMyPC-DownloadHistory.csv) that includes the vendor name, protocol, web domains, and download status for downloaded binaries. (Idea:Fixes
- Fixed an issue where the WSUS Maintenance for unreferenced updates would not return folders when the name is longer than 80 characters
- Fixed an issue where file coping during publishing would fail when a file is referenced more than once (e.g., in additional files and pre-command script)
- Fixed an issue where adding multiple Intune assignments with customer deployment deadlines may cause the publisher UI to crash
- Fixed an issue where double quotes in the command line argument for software updates would not be retained.Improvements
- Adds logging for a new known error when access is denied to the application source.
- Improved documentation for different areas of the Publisher UI.
- An error message is logged out if a device collection attribute is not configured in the SCCM application scan feature
- Intune assignments referring to another a customer Azure AD group may be lost from the settings. Previous Intune assignments could be restored by importing a settings backup from the\\backup folder in the advanced tab.
- Mistakenly notify a success when a hash validation failed during an SCCM application in-place upgrade
- Added the ability to edit assignments for already published Intune applications using the Intune application manager
- Added a right-click option to open Local Content Repository
- You can now limit the SCCM application database scan to a specific collection based on UserVoice 475Improvements
- When a TRANSFORMS command is added in the additional arguments, we will automatically add the full relative path at execution based on UserVoice 668
- Install times are now expressed as time offset starting from the publishing date when an application is published for the first time
- When an Intune application is updated, if assignments are not copied from a previous version, new assignment(s) are created based on the right-click assignment options
- Displays a warning message if the Local Content repository path is empty, and the option to look into this directory first is enabled
- We made significant performance improvements for our SCCM database scanning for application detection
- Fixed an issue introduced in build 1.7.3 where assignments for Microsoft Intune applications created directly within Microsoft Intune may be removed if they are not assigned within the Patch My PC Publisher.
- We will now create assignments in Intune even if the Intune application was already created before adding the assignmentFixes
- Snooze duration in Intune assignments can be set to an invalid value when the restart grace period and restart countdown are also enabled
- SCCM Applications may fail to be created on older SCCM builds with error "An error occurred while creating an application in SCCM: Could not load type'Microsoft.ConfigurationManagement.ApplicationManagement.ProcessDisplayName' from assembly'Microsoft.ConfigurationManagement.ApplicationManagement, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'."
- Microsoft Intune application may fail to be created with error"An error occurred while processing an Intune application: Unrecognized Guid format."
- Log the ApplicationID of the Intune app that is updated instead of the Intune App ID (reported by Jan Ketil Skanke)
- Retain Deployment type dependencies during application in-place updateChanges
- Changed the behavior of the Scan SCCM Database wizard, add an Ok button, and rename the Close button to Cancel.
- Remove «Full Content» mention on Intune and SCCM TreeViewsFixes
- We would always log 0 requirements carried from the previous version even if more than 0 requirements have been carried over
- PowerShell detection method script wouldn't be signed if the filename contained a single quote
- Intune assignments are not always carried during an upgrade
- Advanced
- Add the ability to parse the catalog using a sequential method instead of parallel (UseSequentialMethod = 1)
- Fix an issue where if there's a WIn32 application larger than 1.95gb, you would receive the following error:
- An error occurred while connecting to Intune: JSON integer 2242219440 is too large or small for an Int32. Path'value[75].size', line 1, position 118932.
- Microsoft Intune production release.
- This update contains backend changes to prepare for production support for Microsoft Intune in an upcoming release.
- Fixed an issue where the code-signing certificate may not save correctly in the Microsoft Intune options.
- Improved the Microsoft Intune options. The options are now available in the Intune Apps tab and not the Advanced tab.
- Improved the installation options for enabling Microsoft Intune only publishing.Features
- Display application dependencies in the SCCM application manager.
- Enhancements to prepare for Microsoft Intune support
- Adds a new application management tool for SCCM in the application options menu. You can now bulk delete applications created from Patch My PC or bulk delete deployments for applications
- Changed title format for republished updates to be more granular
- Included updated DLLs for Compression.cab from Wix
- When an update is republished, all previous republished updates can be superseded by the new update that is republished
- Add email, teams, and logging notifications when an update cannot be revised
- Added a more details button in the modify published update wizard that will show important details about updates published to WSUS
- Improved success and failed icons for Microsoft Teams alertsFixes
- Fixed an issue where the right-click option for manage logging may display the correct information
- Fixed an issue where updating MSI based applications may result in an error: An error occurred while updating a package in SCCM: Access to the path \ is denied.
- Added the Intune bulk editor in the Advanced tabFixes
- Fixed an issue where custom files and folders defined, may not be included in a software update cab file
- Added a new right-click option in the Applications tab to display an application as featured in company portal.
- Fixed an issue where you may receive an error: An error occurred while signing the PowerShell detection script, but there is no error message to display.
- Applications will no longer be duplicated in the event the deployment type's source folder was deleted.
- You can now trigger a full and delta software update point synchronization from the advanced tab
- Microsoft Intune (Release Candidate)\
- You can now automate Win32 application management in Microsoft Intune
- You can now create assignments for Win32 applications in Microsoft Intune
- The authority URL for Microsoft Intune will be prepopulated
- You can now select a custom code-signing certificate from the computer's personal certificate store. A full WSUS installation is no longer required for code-signing the detection method script used for Intune.
- The publishing service can now be installed on Windows 10 (x64) for a Microsoft Intune only setup.Improvements
- Use env variables instead of hard-coded path in PowerShell detection script.
- No longer perform WSUS service checks when the WSUS publishing is disabled for Intune only scenarios.
- You can now test the SMS Provider connection under SYSTEM-level context
- Other fixes and improvements.Fixes
- Bug fixes and other improvements
- Fixed an issue where you may receive an error: An error occurred while updating a package in SCCM: OpenDatabase,DatabasePath,OpenModeChanges
- Rename Intune preview to Intune Release Candidate.
- You can now trigger a full and delta software update point synchronization from the advanced tab
- You can now set a custom folder for temporary downloads of the software update and application content
- You can now set a custom folder for the log save location
- You can now browse to UNC paths when adding a custom folder in scripts dialog
- You can now change the folder location for the generated CSV fileImprovements
- You can now test the SMS Provider connection under SYSTEM-level context
- Fixed an issue in version 1.5.7 where youo may receive the following error when an application is updated in-place
- An error occurred while updating a package in SCCM: Invalid property: object Application(ScopeId_*) property DisplayInfo.DisplayInfo.DefaultLanguage: Language En does not match any data in the set
- You can now right-click an individual product in the application tab and choose to move it to a custom folder in the console
- You can now create new folders in the applications node of the console directly from the folder browse dialog
- You can now refresh folders in the applications node directly from the folder browse dialogImprovements
- Files downloaded for publishing updates are now cached and reused for applications within the same sync cycle
- Support to publish applications in other languages than en-US
- You can now send Microsoft Teams publishing alerts using a webhookImprovements
- The software update point synchronization will be triggered after the update synchronization task rather than waiting for the updates and applications sync.
- Improved the accuracy of the SCCM application scan feature to better differentiate between x86 and x64 products based on UserVoice Improve accuracy of 32/64-bit count results of SCCM Database scanFixes
- Minor bugs fixes
- Add support to auto-popular the uninstall command line for 50+ applications in SCCM
- Allow searching backward for products and vendors when clicking(Shift+F3)
- Preserve User Categories when updating Apps in SCCM
- Preserve Admin Categories when updating an SCCM application
- You can now configure a custom application name, localized application name, localized application description, and icon
- You can now enable your software update point to sync when updates are published when your software update point is on a remote site system.
- You can now exclude products at the vendor level from being enabled in automatic scanning
- You can now press F4/Shift+F4 keys to go to the next/previous when searching products or vendors
- When disabling updates, we will now create a RegKey is it doesn't exist to disable self-updates
- Set default download timeout to 100 seconds from 30 seconds.Fixes
- Fixed an issue where a custom command line may not be processed if it contained double quotes and a space
- Fixed an issue where the UI may crash when enabling a large number of products
- Improved logging for varias actions including download percentages
- Improved logging
- Remove leading and trailing spaces in catalog URL, sms provider server name, application source folder path, and timestamp server URL
- Create a CSV file at the end of each synchronization with a summary of what was published, revised, created
- You can now set the max log size between 1-10 MB
- Added an option to show and delete unreferenced WSUS folders in the UpdateServicesPackages folder
- Added an option to show/hide already enabled products in the SCCM scan
- Added the ability to start a sync by running the PatchMyPC-Settings.exe with argument /SyncNow (the UI is not displayed)
- Log events in the Windows event log (Starting/ending sync, success/fail publishing updates)Improvements
- Add several log entries when sync fails
- Improve the version comparison in the PowerShell detection method scriptFixes
- Distribution point groups containing apostrophe were ignored during distribution
- Improved the PowerShell detection method scripts to handle invalid DWORD entries better fixing a "Specified cast is not valid." error message
- Various bug fixes