

However, on the following Monday (and going forward until the next version update), any devices where Workspace ONE UEM triggers an application install would install version 1.1. Any device where Workspace ONE UEM triggers an application install from Monday through Sunday would install version 1.0. Imagine the following scenario where the current App Store version of an application is 1.0 on Monday, but then becomes 1.1 on the following Monday. Volume-purchased applications (iOS, macOS, and tvOS) always install the current App Store version of the application at the time the install occurs. NSUserDefaults and CFPreferences Configuration via Custom Settings.Automatic or On-Demand (Catalog-Requested) Installation.Microsoft Office (Legacy Versions or Insiders).Installers Requiring Configuration Files.ChoiceChanges XML for Complex Installers.Common Non-Store App Deployment Use-Cases.Troubleshooting Non-Store App Installer Problems.Determining When to Install Non-Store Apps.Introduction to Troubleshooting Non-Store Apps.Troubleshooting Non-Store App Deployments.Troubleshooting Volume-Purchased App Installs.Assigning Volume-Purchased Apps to Devices.Adding Location Token to Workspace ONE UEM.(Optional) Configuring Additional Hub Services.

Configuring the Hub Services App Catalog.Deploying Store vs Non-Store macOS Apps.
