You can use Omnissa Workspace ONE UEM to distribute, track, and manage your internal applications. These are applications built in-house and not hosted on Public App Stores. You can upload the application files directly to the Workspace ONE UEM console for deployment. However, if you use an external repository to host your internal applications, then you can easily integrate that host with Workspace ONE UEM, instead of migrating the entire catalog to Workspace ONE UEM.
Workspace ONE UEM supports specific file types for internal applications. For some file types, you upload more than one file so that the application works across devices. Find out what file type the system supports and which file types require you to upload multiple files.
Supported File Types for Internal Applications
Note: Ensure that the auxiliary files packaged with the Apple iOS or macOS applications do not have spaces in the names. Spaces can cause issues when you load the application to the console.
| Platform | File Type |
|---|---|
| Android | APK. For more information, see Deploying Internal Application on Android Devices. |
| Apple (iOS, iPadOS, tvOS, visionOS) | IPA |
| macOS | DMG MPKG PKG Note: You can also use the product provisioning feature to deploy macOS internal applications as DMG, PKG, and APP files. |
| Windows Desktop and Windows Server | EXE: Upload an EXE package of Win32 applications for Windows Desktop and Windows Server. MSI: The MSI file, also called a Windows Installer, is a package that contains everything to install, maintain, and remove the software. ZIP: Upload a ZIP package of Win32 applications for Windows Desktop and Windows Server. |
| Linux | DEB: For Debian-based distributions, including Ubuntu RPM: For RedHat-based distributions |
Was this page helpful?