Overview
On October 17, 2019, VMware will no longer support the Standalone Content Gateway (additional details here), and in turn VMware will not support hosting internal applications on internal networks with connections facilitated by the Content Gateway (when an Internal App is added as link).
Customer Impact
If you are using a repository on your internal network to distribute internal applications, the Windows version of the Content Gateway was able to facilitate the connection for the device to get the application from this repository when the Workspace ONE UEM console initiates app deployment.
The Windows Content Gateway will not be supported after October 17th, 2019. This means customers who are hosting internal applications on an internal network and leveraging the Content Gateway to retrieve that application will need to consider one of the alternative strategies listed below.
Alternative Strategies
Host and distribute applications from cloud storage
If you are using cloud storage to host an internal application, Workspace ONE UEM facilitates the connection for the device to get the application package from the cloud storage system when the deployment is initiated. Workspace ONE UEM currently does not support cloud storage system links that require authentication.
Download and distribute with Workspace ONE UEM
Select to have Workspace ONE UEM retrieve the package file from a link and store it rather than distributing the link directly to end-users. This functionality is particularly useful for customers who use Workspace ONE UEM for continuous integration between systems to distribute applications. Go to the API help in the console to find the API value.
Support Contact Information
To receive support, either submit a ticket via the My Workspace ONE portal or call your local support line.
Best Regards,
The VMware Workspace ONE Team
Other Languages: 日本語
0 Comments