rterakedis
VMware Employee
VMware Employee
‎01-28-2021 07:16 AM

ICYMI: Multiple Workspace ONE UEM application pools and services do not start once stopped

In Case You Missed This KB:   https://kb.vmware.com/s/article/82369

Symptoms
Multiple Workspace ONE UEM application pools and services may not start once stopped after Jan 27th, 2021. Event logs display an error loading certain DLLs due to a code signing validation error. This affects SaaS as well as On-premise customers. Affected version

The following versions are potentially impacted:

  • Workspace ONE UEM 19.7.0.5, 19.7.0.16, 19.7.0.38, 19.7.0.39
  • Workspace ONE UEM 19.9.0.2, 19.9.0.11, 19.9.0.34 
  • Workspace ONE UEM 20.1.0.9, 20.1.0.26, 20.1.0.27
  • Workspace ONE UEM 20.3.0.1, 20.3.0.6
  • Workspace ONE UEM 20.4.0.16
  • Workspace ONE UEM 20.5.0.17, 20.5.0.24, 20.5.0.33, 20.5.0.34, 20.5.0.35
  • Workspace ONE UEM 20.6.0.14
  • Workspace ONE UEM 20.7.0.0 GA, 20.7.0.2 GA, 20.7.0.10
This list will be updated as we continue validation.
 
Resolution
Our Product team is engaged and actively working to provide a resolution for each of the affected versions in the form of a patch. The affected version list (above) will also be updated as we continue to validate each supported release. Fix Version(s):
  • Workspace ONE UEM 1907 - Addressed in 19.7.0.60 (Available for download at UEM Console 1907 Patch)
  • Workspace ONE UEM 1909 - Addressed in 19.9.0.45 (Available for download at UEM Console 1909 Patch)
  • Workspace ONE UEM 2001 - Addressed in 20.1.0.28 (Available for download at UEM Console 2001 Patch)
  • Workspace ONE UEM 2003 - Addressed in 20.3.0.20 (SaaS Only)
  • Workspace ONE UEM 2004 - Addressed in 20.4.0.17 (SaaS Only)
  • Workspace ONE UEM 2005 - Addressed in 20.5.0.36 (Available for download at UEM Console 2005 Patch)
  • Workspace ONE UEM 2006 - Addressed in 20.6.0.15 (SaaS Only)
  • Workspace ONE UEM 2007 - Addressed in 20.7.0.11 (SaaS Only)
Action Required:
  • Customers with SaaS environments - None. VMware Cloud Operations is working round the clock to patch all impacted environments.
  • Customers with On-Premise environments - Please follow this article for updates regarding the fix for each version. It is highly recommended that you deploy the relevant patch once as it is made available.
 
More details (Cause, Impact/Risks) can be found at the KB:      https://kb.vmware.com/s/article/82369
Labels (1)
Labels
Reply