RN200944: Release Notes:Raynet One Unified Endpoint Manager 3.2.4220.788 [U1]

Feature Highlights:

• Security assessment reporting. [RDEP-257]
• Reports of user-based deployments. [RDEP-205]
• Historical data is now available for third party patching. [RDEP-184]

Improvements:
 

• Improved device matching for the relation "Owner equals" in the dynamic groups editor. [RDEP-454] [RDEP-458] [RDEP-457]
• Improved the performance of the edit group dialog for complex groups. [RDEP-397]
• Added search function to the IT visibility, Hardware overview and Operating System tab. [RDEP-357]
• Enlarged the comment box in the "Edit Package" dialog. [RDEP-422]
• Pending scheduled tasks queued without a start date now are added at the top of the list. [RDEP-398]

Resolved Issue:

• Resolved an issue, where the deployment state was not properly updated for all child groups when the force installs option is changed. [RDEP-451]
• Resolved inconsistencies between group and owner-based assignments. [RDEP-353]
• Resolved an issue, where it was possible to use the uploaded package file as both the installer and a stand-alone file. [RDEP-354]
• Resolved issues with failing dynamic group matching. [RDEP-443]
• Resolved an issue where Third-Party Patching was failing on updating assignments due to deadlocks. [RDEP-437]
• Resolved issues with the installation state being not updated for imported packages after changing force install option from optional to mandatory. [RDEP-405]
• Resolved issues with incorrect target deployment, resulting in packages being installed for not qualifying devices. [RDEP-440]
• Resolved issues with the creation of EXE packages if a file was added and then removed from the package. [RDEP-433]
• Resolved an issue, where it was possible to define device settings, device schedules, and agent update packages as dependencies. [RDEP-401]
• Resolved issues with validation of PackageStore macOS packages in DMG/PKG format. [RDEP-375]
• Resolved an issue where Raynet One UEM could be blocked by RayVentory Server Integration in case of inaccessible or invalid connection. [RDEP-340]
• Resolved an issue where postponable notification and options to install were missing for mandatory configured packages that were previously manually uninstalled by the user. [RDEP-319]
• Resolved an issue with Azure scheduled task where its execution did not contain imported and updated device owners. [RDEP-303]
• Enforced folder names rules for automatic generation of folder structure to prevent duplicated folders. [RDEP-282]
• Resolved issues with automation assistant causing an error when adding a package to a group by ID due to large JSON parsing failure. [RDEP-424]
• Resolved a visual glitch where the GUID was presented as a blank field in the Group without OS preferences until clicked. [RDEP-421]
• Resolved an issue where assigning devices to users or groups was showing no device name for devices with only GUID and no inventory. [RDEP-418]
• Resolved issue with the Group membership counters not refreshing after assignments were made in another tab. [RDEP-399]
• Resolved issues with package status not updating to the packed state after being added. [RDEP-368] [RDEP-279]
• Resolved issues with empty or misaligned titles in exported reports. [RDEP-363]
• Optimized clean-up of resource of third-party patches. [RDEP-332]
• Resolved an issue with invalid targets after importing of packages. [RDEP-277]
• Resolved an issue, where the label on the login page was incorrectly suggesting, that the username was wrong, instead of the e-mail. [RDEP-439]
• Resolved an issue where merging of devices resulted in an empty value shown in the domain dropdown when either of devices had no domain. [RDEP-436]
• Resolved issues with Install states count in the Users page not updating to 0 after removing a device. [RDEP-419]
• Resolved an issue with device schedule and device settings packages sharing the same creation constraints, preventing creation even if they are not linked. [RDEP-412]
• Resolved a small delay with the display of previously configured dependency settings for PackageStore managed packages in the 'Edit dependency' dialog. [RDEP-343]
• Resolved an issue where products tab in security assessment devices has bad vulnerability count [RDEP-304]
• Resolved an issue where the shared report “UEM device security summary” does support drill down, instead the report component becomes unresponsive [RDEP-360]
• Resolved an issue on package edit dialog, when a custom property is deleted the ‘Save changes' button is not activated [RDEP-358]

Migration

• The application database migration is handled automatically during the initial launch of the UEM console.
• Raynet One UEM 3.2 Update 1 introduces new environment properties that require your attention. Please use the provided
  templates to update your existing Docker Compose configuration accordingly.

Installation

Instructions:

Detailed installation instructions and further documentation can be found here:

RayManageSoft Unified Endpoint Manager