VMware Tunnel Proxy End of Support Life Announcement (87345)
VMware is announcing End of Support Life for the Tunnel Proxy component. This will be effective January 30, 2023.
All customers should plan to migrate to the modern VMware Per-App Tunnel component, also available as part of VMware’s Unified Access Gateway platform. The VMware Tunnel Per-app component, hereafter known as VMware Tunnel, supports all the same use-cases as the Tunnel Proxy component.
Now through January 30, 2023, VMware Tunnel Proxy remains supported so you can migrate to the VMware Tunnel.
The Support period will end on January 30, 2023, and the product will reach End of Support Life. Following this date, the Workspace ONE product team will not be servicing this product in any fashion.
A Tunnel SDK module was introduced as part of VMware’s Workspace ONE SDK in UEM 1905. This module enables native mobile apps to perform app tunnelling on unmanaged iOS and Android devices. This eliminates the need for Tunnel Proxy and the Tunnel SDK will now leverage VMware Tunnel. Administrators now have the option to either use the Tunnel SDK or the VMware Tunnel application for secure access to internal resources.
New App Store option to distribute Apps via the Apple App Store:
Release your apps that aren’t suited for public distribution as unlisted on the App Store, discoverable only with a direct link. Unlisted apps don’t appear in any App Store categories, recommendations, charts, search results, or other listings. They can also be accessed through Apple Business Manager and Apple School Manager. Apps for specific organizations, special events, or research studies, or apps used as employee resources or sales tools are good candidates for unlisted distribution.
Distribute your app to:
Limited audiences (such as part-time employees, franchisees, partners, business affiliates, higher-education students, or conference attendees) through a standard link that’s usable on the App Store and Apple School Manager or Apple Business Manager.
Employee-owned devices that aren't eligible to be managed through Apple School Manager or Apple Business Manager.
Custom Settings profiles alone will not be processed during OOBE on Windows systems (87559)
Windows systems where the OOBE Status tracking page has been enabled allows for profiles to be delivered to the system during OOBE, ensuring the settings in those profiles are deployed before finishing OOBE. In the case of Custom Settings profiles, they will not be delivered to the system during the process.
This is particularly important in the case of preventing the Windows Hello PIN prompt from appearing. This can be disabled in an image through Group Policy, or through device management with the PassportForWork CSP. If using the CSP, and creating a sync-ml payload through custom settings, it will not apply if that payload is the only one in the profile and thus the PIN prompt will continue to appear.
This is expected behavior for a custom settings profile and OOBE status screen. See the Workaround section for a method to address this limitation.
In order to deploy a custom settings payload during OOBE, it is possible to configure a profile which includes one of the UI based payloads as well as a custom settings payload. Doing so will cause both payloads to be deployed during the OOBE setup phase. For example, a Web Clip payload and a properly configured custom settings payload will both apply at OOBE if configured in the same profile and required during OOBE status screen processing.
In summary, except for seeing multiple harmless warning events during the “Initial Deployment Phase” and a single harmless error event during the “Enforcement Phase” for each Horizon component, there is no impact on Horizon functionality.
[Action Required] Android Intelligent Hub 220.127.116.111 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 18.104.22.1681 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.