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.
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.
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 textProduct: Workspace ONE UEM Database -- Installation operation completed successfullyat the end.
[Action Required] Android Intelligent Hub 18.104.22.1681 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 22.214.171.1241 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 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).