Weekly highlight: ENRL-3362 - Enrollment Blocked if the device that was Registered Earlier is now added to “Allow Device” (87921) - Device registration records already consumed by enrolling devices can later be updated to Allow/Deny records via UI or via batch import. When such a change is made, re-enrollment of the device is blocked even if an Allow record was created for it.
- Workspace ONE UEM 2105
- Unenroll the device which is registered and add the record to "Allow Device" list and try enrolling the device. Enrollment gets blocked for those devices.
- This issue has no affect on fresh device enrollment and it will only affect device re-enrollment.
- Our product team has been notified and is working to address this issue in a timely manner. Please subscribe to this article to receive updates when they are available.
- Workaround: Before creating Allow/Deny records, you must search if the records for those attributes exist. If present, those records must be deleted before adding the Allow/Deny records.
- KB-Reference: https://kb.vmware.com/s/article/87921?lang=en_US
Release Updates Week 12 Failed to connect to RDSH server over Blast or PCOIP when upgrading from Horizon 8.0 and Horizon 7.13 to newer releases (87968) - After upgrading to a newer Horizon Agent connection to an RDSH desktop or application fails.
- Access via RDP protocol remains working.
- As an example , when upgrading from Horizon 8.0 to newer Horizon 8.1, 8.2, 8.3, 8.4 or Horizon 7.13 or 7.13.1 to Horizon 7.13.2.
- Log Lines will tend to include lines like the below in the agent log sets (log location )
- To highlight an additional requirement to reboot the guest o/s twice to ensure the correct display driver is initiated.
- The O/S will only update the RDSH display driver after a reboot with the newer updated binary.
- However before the O/S has a chance to update the RDS display driver, the older RDS display driver is already loaded at startup.
- This causes a version mismatch of RDS display driver and Horizon causing connections to fail.
- This can impact application and desktop sessions.
- Please perform an additional second reboot after upgrade.
- The RDS display driver is updated after the first reboot and a second reboot will ensure the new updated RDS display driver is loaded.
- Failed to connect to RDSH desktop when upgrading from Horizon 8.0 and Horizon 7.13 to newer releases (87968)
How to collect thread dumps on Workspace ONE Access Connector (87840) - This article will explain how to collect a thread dump if you are requested to provide one in order to troubleshoot a Workspace ONE Access Connector issue.
- A version of JDK must to be running on the Workspace ONE Access Connector machine. JDK is not installed by default on Workspace ONE Access Connector systems and must be installed separately. Most installations of JDK, like Open JDK for example, can be used to collect thread dumps.
- The following steps can be used to collect thread dumps on a Workspace ONE Access Connector:
- Go to the Windows Connection machine.
- Download and Extract the JDK to any location.
- Open command terminal as Administrator.
- cd to the extracted folder’s bin. bin will have jstack file.
- Please take note of the process ID (PID) of connector from Task Manager > Services.
- For example, let’s say 5836 is the PID. Run the command “jstack 5836 >threadDump.txt” from the JDK bin folder. Replace the number in the command with the actual process ID found in Task Manager. It will generate a threadDump.txt file in bin.
- Collect the threadDump.txt file and share
- KB-Reference: https://kb.vmware.com/s/article/87840?lang=en_US
RUGG-10680 - Deprecation of Offline Provisioning in Products (QNX, Win Rugged Platforms) (87922) - Offline Provisioning is a feature applicable only for QNX/Windows Rugged Platforms and requires a custom client build. Starting Workspace ONE UEM 2204, this feature will not be available.
- Due to its custom nature and dependency on a legacy platform, this feature is being deprecated.
- The feature will be deprecated and no longer available as of Workspace ONE UEM 2204
- KB-Reference: https://kb.vmware.com/s/article/87922?lang=en_US
Error messages seen in database install log after successful upgrade of Workspace ONE UEM Database (87988) - Upon a successful installation of Workspace ONE UEM database, if we inspect the install log we see errors printed out similar to: “ERROR: Failed to drop data type provisioningPolicy.DevicePolicyJob_DataType_V4: Cannot drop type 'provisioningPolicy.DevicePolicyJob_DataType_V4' because it is being referenced by object 'DevicePolicyJob_Add_V12'. There may be other objects that reference this type.”
- UEM Version: 2005 and above
- This note is for Engineering teams to take note of deprecated SQL Datatypes which may still have references from other procedures. Owing to the point of error being common to other more fatal deprecation errors, the verbiage cannot be changed to Warning.
- This will be taken note by the engineering teams, if any references are missed while deprecating the datatypes and can accommodate them in the upcoming release. This is not an installation failure and hence can be ignored as long as the log contains the text Product: Workspace ONE UEM Database -- Installation operation completed successfully at the end.
- KB-Reference: https://kb.vmware.com/s/article/87988?lang=en_US
Highlighting High Priority KBs - Announcing end of support for device administrator (Android Legacy) in Workspace ONE UEM (80971)
To align with Google’s strategy and ensure VMware’s investment in the right long-term solution for Android, as of March 31st, 2022, VMware will no longer support device administrator-based management on Android (referred to as Android (Legacy) in the Workspace ONE UEM console). - [Action Required] Android Intelligent Hub 9.0.0.391 Cannot Check In (86083)
VMware will start requiring SNI in Workspace ONE UEM Dedicated SaaS environments starting January 16th, 2022. After this date, Android devices running Intelligent Hub 9.0.0.391 or lower may no longer communicate with Workspace ONE UEM. Affected devices may have to be re-enrolled with a supported version of Intelligent Hub. - VMware Tunnel Proxy End of Support Life Announcement (87345)
VMware is announcing End of Support Life for the Tunnel Proxy component of the VMware Tunnel solution. This will be effective January 30, 2023. - VMware Workspace ONE UEM New Control Plane SaaS Deployment Schedule (86243)
Workspace ONE UEM has undergone a complete re-architecture to modernize the platform using microservices and containers to enable increased scalability and performance and increase the rate of innovation. Now after having conducted significant and careful testing, these architecture updates, including a new control plane, will be deployed to UEM SaaS environments over the next several weeks, with options available to on-premise customers after this roll-out (Later in 2022). - [Resolved] CRSVC-25521 - Workspace ONE UEM - Guidance for addressing CVE-2021-22054 (87167)
The Workspace ONE team has investigated CVE-2021-22054 and has determined that the possibility of exploitation can be removed by performing the steps detailed in the Workaround section of this article. This workaround is meant to be a temporary solution until updates documented in VMSA-2021-0029 can be deployed.
Recently updated KBs Digital Workspace Techzone, Blog and YouTube Updates 3rd Party Blogs and Industry News
March Software Releases Patch & Seed Script Updates Week12-2022 - OS Updates Seed Script
- Seed Script for latest Device Model Information
- Custom Script to Allow Android 12 enrollments into Workspace ONE UEM Console
|
Comments
Post a Comment