Use Workspace ONE UEM to manage the deployment and maintenance of your organization's internally developed mobile applications. Management of internal apps differs slightly between platforms, review the topics in this section for getting a better understanding of these differences and successfully deploy the internal apps to the platforms you support.
Basics of Internal Applications
Use Workspace ONE UEM to distribute, track, and manage your internal applications. See Supported File Types for Internal Applications for a list of supported file types that you can upload to the console.
You can use Workspace ONE UEM to manage your organization's internally developed mobile applications in two ways.
- Add and Deploy Internal Applications as a Local File
- Add and Deploy Internal Applications as a Link
Upload and Deploy Internal Applications as a Local File
Upload your application package as a Local File for Workspace ONE UEM to parse the application metadata and distribute it to your end-user devices.
For an explanation on how to add your internal applications to Workspace ONE UEM, see Add and Deploy Internal Applications as a Local File. After you upload internal applications, use the flexible deployment feature to schedule single or multiple deployments for internal applications. See Flexible Deployment to Assign Internal Applications for more information.
Upload and Deploy Internal Applications as a Link
Add a publicly accessible link or a link to a repository on your internal network that points to your application package location. In this case, Workspace ONE UEM does not have access to your application package. Hence, your application metadata will not be parsed and the same link will be distributed to your end-user devices to initiate the download.
Links to your internal network repository have to be routed through 'Content Gateway' for your end-user devices to successfully download and install them. For more details, see Add and Deploy Internal Applications as a Link.
Use the console to track the installation of internal applications. One benefit is to install applications on those devices that have yet to install the application. Benefits of Tracking Internal App Deployments༔ outline other reasons to track internal application installations.
The details view of the applications is where you install and remove applications from devices. Read about the features of this page in Track Internal Applications With Details View. See descriptions for reason codes so that you know what the system is doing at each stage of the installation in the topic Installation-Status Reason Code Descriptions.
Application Removal Protection and Application Removal Safeguard
Use the application removal protection feature to hold application removal commands and the removal of internal applications until an admin approves the removal. This feature protects against the unintended removal of critical internal applications. See Application Removal Protection for more information.
If you test seeded Workspace ONE UEM applications before you deploy them to production, follow a specific order of steps to prevent the accidental removal of the production version of the test application. See Application Removal Safeguard for more information.
iOS Provisioning Profiles
Internal iOS applications require a provisioning profile to enable deploy and successful use. See Provisioning Profiles for Enterprise Distribution for a brief description of provisioning profiles and where to get them.
Keep these files updated by renewing them with the steps in Renew Apple iOS Provisioning Profiles.
To mitigate issues in Workspace ONE UEM caused by the difference in time that provisioning profiles are valid and the time that development certificates are valid, you can renew the provisioning profiles . For more information, read Provisioning Profiles and Updates for information.
Distribute Win32 Packages as Internal Applications
Use the internal applications area to upload, configure, and deploy Win32 application packages to Windows 10+ devices from a local file storage. For more information, reference Distribution of Win32 Applications.
You can also use the peer distribution system to deliver Win32 packages from peer to peer. This method reduces the traffic on single communication channels with a file storage system or a content delivery network. To see if this method works for your environment, see Peer Distribution for Win32 Applications.