VMware Digital Workspace Newsletter - Week 25








Week 25 Software Releases


System

Component

Release

Announcement

Release Date

macOS

Workspace ONE Intelligent Hub for macOS

22.05.1

  • HUBM-5601: 22.05 and 22.04 are not updating after seeding

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/Workspace-ONE-Intelligent-Hub-for-macOS.html

23.06.22

Backend

WS1 Access SaaS

June 2022

https://docs.vmware.com/en/VMware-Workspace-ONE-Access/services/rn/vmware-workspace-one-access-release-notes/index.html

23.06.22

Backend

Hub Services SaaS

June 2022

https://docs.vmware.com/en/VMware-Workspace-ONE/services/rn/hub-services-release-notes/index.html

23.06.22


Workspace ONE Access Services update coming soon 

  • Continue-on-Failure Authentication Policy In this release, a new access policy configuration that offers flexibility to control how rule policy execution is introduced. You can now create an access policy with rules that let users progress to the next rule if the authentication fails on the present rule. In the Workspace ONE Access service, regular policy execution terminates when the conditions in the first matching rule are executed. The new rule progression option allows you to progress rule execution to the next matching rule in the policy if the authentication fails on the present rule. Common use cases of this configuration include password less authentication flows and flexible alternative authentication rules for different sets of users.

  • For more information, refer to this Release Notes. 

   

Workspace ONE Hub Services update June

  • Branding Background Image Support on Workspace ONE Intelligent Hub Web Background Image is back! Admins can upload a background image from Hub Services Branding Settings and have that image rendered on the Hub end user UI. This capability builds on our existing branding settings and enables customers to deliver a more modern and stylish Hub experience.
    Note: This is available only on Workspace ONE Intelligent Hub web with this release.  

  • Configure Due Dates for Actionable For You Notifications Admins can assign due dates to actionable notifications from the Hub Services admin console. Select the day, time, and time zone that a notification action should be due by. A due date icon displays on the notification card in For You so employees can easily see what notifications need their attention and when they are required to complete a notification action by.
    Note: This is available only on Workspace One Intelligent Hub web and Windows with this release. 

  • Users can Change Their Primary Device for Two-Factor Authentication from Workspace ONE Intelligent Hub When the Verify (Intelligent Hub) authentication method is enabled in Workspace ONE Access, users have the ability to select and change their primary device for two-factor authentication from the Support tab in the Workspace ONE Intelligent Hub app.
    Note: This is supported on Workspace One Intelligent Hub web and Windows. 

  • For more information, refer to this Release Notes. 

  

New permissions required for UsersBatches and ExportedReports APIs in Workspace ONE (WS1) UEM (88595)

  • Workspace ONE UEM admin role permissions have been added for some UserBatches and ExportedReports REST APIs in order to mitigate a security risk in which all APIs must have an authorization check.
    The following APIs will no longer be accessible without the appropriate admin role permissions:

    UsersBatchesV1
    [POST] /users/batches/report
    [POST] /users/batches/{userBatchUuid}/details/report

    ExportedReportsV1
    [POST] /groups/{organizationGroupUuid}/exported-reports

  • This change impacts Workspace ONE UEM versions 21.11 and above.

  • To grant access to these APIs, the following permissions must be added to an admin role. To add a permission to an existing role, navigate to Accounts > Administrators > Roles within the Workspace ONE UEM Console. Search for a role in the list and click on Edit (pencil icon). Search for and select the permissions you want to add to the role, then click Save.

  • More info in: https://kb.vmware.com/s/article/88595?lang=en_US&source=email


BitLocker and BitLocker to Go Best Practices and Considerations (88620)

  • BitLocker and BitLocker to Go (BL2Go) are technologies designed to encrypt data and provide recovery capabilities as needed in the UEM console. There are some situations where changing GPO settings might conflict with BitLocker settings, resulting in unexpected results. Other best practices can be followed to ensure the highest recovery capabilities for hardware issues or forgotten passwords.

  • This article is intended to track recent issues identified with BitLocker and BL2Go and help guide you on the best experience with these technologies.

  • Review KB https://kb.vmware.com/s/article/88620?lang=en_US&source=email for latest updates.


PPAT-11109 - Tunnel service on Unified Access Gateway 2111 causes error “AllowListManager Query returns Bad Response” (88753)

  • Tunnel service on Unified Access Gateway 2111 causes error “AllowListManager Query returns Bad Response”

  • In UAG 2111 we introduced API pagination improvements for how the Tunnel service interacts with UEM APIs to fetch the AllowList of devices that are trusted by Tunnel. An error was discovered that would cause only the first page to be returned, and the tunnel.log will log
    ERROR: API: Bad connection to API. Check connection to API service
    ERROR: API: AllowListManager Query returns Bad Response
    ERROR: AllowListManager AsyncAPIQuery: OnError

  • The Tunnel service will not be able to pull in the complete device allowlist, but will instead rely on individual queries to UEM for each device. Due to the individual queries, the impact should be minimal. However, there is a chance for delays under heavy load as well as increased traffic with UEM APIs.

  • UAG 2203.1 introduced a fix for this issue and is the recommended version of UAG for Tunnel customers to use. The Tunnel service will automatically create a new TLS connection for every page in the API response.

  • KB-Reference: https://kb.vmware.com/s/article/88753?lang=en_US&source=email


Horizon Agent installed on Windows 10 physical machine remains stuck during machine restart. (88126)

  • Physical PC machines with Horizon agent installed hang upon reboot/ restart. Once this issue occurs subsequent reboot attempts also fail.

  • This article provides workaround for the mentioned system hang issue on reboot issue.

  • The root cause for this issue is under joint investigation with Microsoft.

  • Customer need to manually power cycle the Physical PC machine.

  • Workaround:

    • There are two potential workarounds for this issue.

      •  Option 1 to set verbosestatus works under most circumstances and is the preferred method.  

      •  Option 2 to disable the IDD driver is limited to certain OS versions and may increase CPU consumption slightly.


1. Set Windows diagnostic key verbosestatus.  (requires reboot)

Set the following registry value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]

"verbosestatus "=dword:00000001




OR

2. - Disable the  IDD driver on the physical machine. (requires reboot)

Set The following registry value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations]

  • "LoadWddmIDDDriver"=dword:00000000

    Note: This method is limited to Windows 10 versions 1909 and older.  This method will not work for Windows 11.


Workspace ONE UEM Unique Identifier for Windows Feature Removal (88754)

  • A feature was added to Workspace ONE UEM 2109 for Windows systems which was designed to reuse device records for physical devices upon re-enroll of a device, rather than create a new device record. After the release of this feature, issues were identified with the implementation that rendered virtual systems susceptible to device records being inadvertently reused. Other situations occurred with physical devices that supposed to be unique were enrolled seen as the same device, thus reusing an existing device record. 

  • In order to correct the implementation of the feature, the Unique Identifier feature will be removed from Workspace ONE UEM 2206. A different approach to handling cleanup of device records, which was the intended purpose of the Unique Identifier feature will be designed and implemented in an upcoming release of Workspace ONE UEM.

  • Due to this change, devices which are reenrolled will return to the pre-2109 behavior of adding a new device record each time it enrolls. This is true of physical devices and virtual machines.

  • A future Workspace ONE UEM release will allow a different approach to device records cleanup.

  • KB-Reference: https://kb.vmware.com/s/article/88754?lang=en_US&source=email


CRSVC-29893 - Mobile Single Sign-On through Workspace ONE Access may fail when using Device Compliance or Device Trust (88741)

  • Single Sign-On (SSO) through Workspace ONE Access may fail when used in conjunction with the following authentication methods:

    • Device Compliance (with Workspace ONE UEM)

    • Device Trust with Okta

  • Single Sign-On can be included in the following authentication methods:

    • Certificate Cloud Deployment

    • Mobile SSO (for iOS)

    • Mobile SSO (for Android)

You may see the following error under the Workspace ONE Access > Dashboards > Reports when a device fails to authenticate.
[{\"reason\":\"AUTHENTICATION_FAILURE\",\"authMethod\":\"identityProvider.embedded.authMethod.airwatchCompliance\",\"failureMessage\":\"Invalid value provided for unique device id.\"}]",

"authMethods" : "identityProvider.embedded.authMethod.airwatchCompliance",


Highlighting High Priority KBs


Recently updated and added KBs


Digital Workspace Techzone, Blog and YouTube Updates


3rd Party Blogs and Industry Updates



June Software Releases

System

Component

Release

Announcement

Release Date

Backend

WS1 Access Connector

22.05

https://docs.vmware.com/en/VMware-Workspace-ONE-Access/services/rn/vmware-workspace-one-access-release-notes/index.html

09.06.22

Backend

WS1 Access SaaS

June 2022

https://docs.vmware.com/en/VMware-Workspace-ONE-Access/services/rn/vmware-workspace-one-access-release-notes/index.html

23.06.22

Backend

Hub Services SaaS

June 2022

https://docs.vmware.com/en/VMware-Workspace-ONE/services/rn/hub-services-release-notes/index.html

23.06.22

iOS

Content

22.06

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/VMware-Workspace-ONE-Content-for-iOS.html

15.06.22

Android

Hub

22.05

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/Introducing-VMware-Workspace-ONE-Intelligent-Hub-for-Android.html

09.06.22

Android

Tunnel

22.03.1

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/VMware-Workspace-ONE-Tunnel-for-Android-Release-Notes.html

16.06.22

Android

Launcher

22.05

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/Introducing-VMware-Workspace-ONE-Launcher-for-Android.html

06.06.22

Android

Relay

5.18

https://kb.vmware.com/s/article/81990?lang=en_US

10.06.22

Android

SDK

22.5

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/VMware-Workspace-ONE-SDK-for-Android.html

08.06.22

Windows

WinMo Agent

6.5.14

https://resources.workspaceone.com/view/zvh5p8knphvqxqrwy6rw/en

10.06.22

macOS

Workspace ONE Intelligent Hub for macOS

22.05.1

https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/services/rn/Workspace-ONE-Intelligent-Hub-for-macOS.html

23.06.22


Patch & Seed Script Updates Week25-2022







  • Workspace ONE UEM 22.03



Comments