The modernized Omnissa Workspace ONE UEM helps you quickly deploy internal applications and efficiently track the summary of different versions together.
Note: This topic applies to organizations transitioning to the modernized Workspace ONE UEM. If you are on a traditional Workspace ONE UEM version, you may notice that the features and functionalities described in this topic differ from those available in your current product version. For information relevant to the traditional Workspace ONE UEM version, see Tracking and Monitoring Application Deployment (Legacy).
Using the tracking features and in-depth statistics that the Workspace ONE UEM console offers, you can easily track and monitor the deployment progress of a specific internal application across versions, when you deploy and install it on your end users’ devices and take the necessary actions for devices that require immediate attention.
Deployment Tracking Dashboard
The deployment tracking dashboard provides in-depth insights into the deployment progress of an internal application at the bundle level, summarizing all versions. You can monitor installation progress through intuitive and interactive charts, apply filters, view device-level installation statuses, and perform bulk operations on devices. This functionality empowers you to quickly identify and address any issue, resulting in successful deployments.
To access the summary of all the versions of your internal application:
-
Navigate to Resources > Apps > Native Apps > Internal.
-
Click the app bundle hyperlink from the displayed app list.
The deployment tracking dashboard has various elements that help you access app data and monitor the deployment progress effectively.
-
Header: This section offers metadata about the application such as Operating System, Bundle ID, and so on.
-
Summary Stats: This section provides high-level summary stats for the deployment such as total assigned devices, the number of evaluated devices, devices pending evaluation, devices excluded from assignment, and devices having applications installed but not assigned.
-
Charts and Device Grids: This section contains intuitive and interactive charts that provide a visual representation of the app deployment progress and filters to view the individual device installation statuses, along with the ability to perform bulk device actions. This section is divided into three tabs corresponding to the summary stats; Evaluated, Pending, and Installed but not assigned. Each tab offers comprehensive tracking information and lists devices based on their categories.
Total Assigned Devices
The total Assigned count represents the overall number of devices entitled to receive at least one of the versions of the application. It is calculated by subtracting the devices that are excluded from the assignments and those that are not eligible to receive the application due to applicability rules (for example, deploy only to devices with specific processor architecture, with minimum OS version) from the total number of devices assigned through smart groups.
Total Assigned = Devices assigned through Smart Groups - Excluded devices - Inapplicable devices.
For example, let’s say there are 500 devices assigned to receive the application through smart groups. However, 50 of these devices are excluded from receiving the application through exclusion, and an additional 20 devices are not able to install it (for example, deploy only to devices with specific processor architecture, with minimum OS version.) In this case, the Total Assigned count is Total Assigned = 500 (Devices assigned through smart groups) - 50 (Excluded devices) - 20 (Inapplicable devices) = 430 devices.
Evaluated Devices
The Evaluated tab contains devices that have a confirmed assignment to at least one of the versions of the application.
For devices that are online and communicating with the server to receive commands: They undergo evaluation on check-in, receive an assignment to the highest applicable version of the application, and then receive installation instructions either automatically in the case of auto-deployment or wait for admin initiation for on-demand deployments.
For devices that are offline and not communicating with the server to receive commands: Periodic offline evaluations are performed, typically every four hours, comparing the device’s last known state with its desired state. The device is then assigned to the highest applicable version of the application, but installation instructions cannot be provided until the device is online and communicating with the server.
Charts
The Evaluated tab provides self-explanatory charts to track the progress of deployment, a detailed devices grid showcasing installation-specific attributes, and options to filter the devices.
| Charts | Description |
|---|---|
| Installation Status | The Installation Status chart shows whether the application is installed or not on devices. It gives you a clear view of how many devices have the application installed and how many don’t, helping you track deployment progress and adoption rates. The different installation statuses are: Installed - Displays the counts of devices that have successfully installed the application. Not Installed - Displays the count of devices that are yet to install the application. You can select the 'Not Installed' filter option to view devices in this category and get a more detailed breakdown with installation status details(For example, 'Downloading', 'Prompting') and Last action status. Together they provide insights into whether an install instruction is issued to the device, why certain apps have not been installed and the underlying factors contributing to their non-installation. Out of Date - Displays the count of devices with the older version of the application installed, awaiting installation of a newer version that has been deployed. This status represents an interim state until the device receives and installs the newer app version. |
| Installation Status Details | The Installation Status Details chart provides detailed information about the installation state of the application. This information complements the corresponding installation status.  Here are some of the detailed statuses: Prompting: Indicates that a prompt is being displayed on the device, awaiting user action to either accept or cancel the application installation. You can determine the number of devices where the installation prompt is pending by selecting the ‘Prompting’ option from the chart. This allows you to precisely identify how many users have not yet accepted the prompt to install the application. Download in Progress: Indicates that the application is currently being downloaded onto the device. Installing: Indicates that the application has been downloaded and the installation process is in progress. Managed: Indicates that the application is installed and managed by the Workspace ONE UEM Console. This is the final state for Installation status detail. Unknown: Indicates that either the installation has not commenced on the application, or the device might not have yet sent management information to UEM. |
| Last Action | The 'Last Action' chart represents the various actions taken by the Workspace ONE UEM console on the device regarding the application. Here are some of the last actions: Install: Indicates that the device received the command to install the application. Remove: Indicates that the device received the command to uninstall the application. Unknown: Indicates that UEM didn't issue any command to the device regarding the application. |
| Versions | Displays the count of devices with specific versions of an internal application installed.  |
| Peer Distribution Details (Applicable only for Windows internal applications) | Displays the number of devices that have downloaded the particular version using peer distribution, the amount of data downloaded, and the source of the downloaded data.  Total devices - This indicates the overall count of devices with the peer distribution profile installed. It presents a pie chart illustrating the devices that have the application installed and used peers for downloading against those that didn’t. Total bytes saved - This indicates the aggregate amount of data saved through Peer Distribution. It includes a percentage reflecting the portion of saved bytes obtained from peer downloads in comparison to the total bytes downloaded from the server or peers combined. Total utilized server bytes - This indicates the total bytes downloaded by all devices directly from the CDN or Device Services server. Total utilized cache bytes - This indicates the total bytes downloaded by all devices from their peers, leveraging the peer distribution. |
Devices Grid
The devices grid provides detailed information about each evaluated device, providing insight into the deployment progress. Additionally, you can execute bulk device-level actions, such as forcing an installation or removing the application, by selecting multiple devices simultaneously.
| Column | Description |
|---|---|
| Last Check-in | This indicates the timestamp when the device last checked in. |
| Last Sample Collected | This indicates the timestamp when the device last reported the sample. |
| Installation Status | This indicates whether the application is installed or not installed on the end-user device. Possible statuses include Installed, Not Installed, and Out of Date. |
| Installation Status Details | This provides detailed information about the installation state of the application, which should be reviewed alongside the corresponding installation status. |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the application. For scenarios where the actions are unsuccessful, it is important to know what actions were last taken by the Workspace ONE UEM console on the application to narrow down the failure on the devices. Possible values are Install, Remove, and Unknown. |
| Assignment Status | In the Evaluated tab, this is always ‘Assigned’. |
| Assignment Source | This indicates the source of assignment - either a direct deployment or through a Freestyle Workflow. |
| Device Friendly Name | This is the friendly name assigned to the device. |
| Assigned Version | This indicates the specific version of the application assigned to the device. |
| User Name | This is the username associated with the device. |
| Organization Group | This is the organization group into which the device is enrolled. |
| Peer Distribution | Displays whether the peer distribution has been turned on or not for the device. |
Device Level Management Actions
You can perform management actions such as forcing application installation directly from the Devices grid. By filtering devices based on specific criteria, you can apply actions to all the filtered devices.
| Action | Description |
|---|---|
| Install | Force installs the highest applicable version on the selected device. A maximum of 100 devices can be selected at once for this action. |
| Remove | Removes the installed application version if managed, from the selected device. A maximum of 100 devices can be selected at once for this action. |
You can use the search functionality in the device grid to quickly locate a specific device by using a friendly name or the associated username.
To initiate a search:
- Navigate to the devices grid and select the search icon on the device grid header.
- Enter the username or device-friendly name in the search bar and select Enter to execute the search.
Filters
Filters
You can refine deployment tracking data for evaluated devices using interactive charts or the filter panel. This allows you to focus on specific evaluated device subsets. Filters can be applied directly on the charts or through the filter panel. When filters are applied, both the charts and the device grid are updated accordingly. Multiple filters can be applied simultaneously as needed.
| Filter | Description |
|---|---|
| Installation Status | Filter for devices with installation status such as Installed, Not Installed, and Out of Date. You can select one or more installation statuses simultaneously. |
| Installation Status Details | Filter for devices with installation status details such as Managed, Prompting, Download in progress, Installing, etc. You can filter one or more installation status details simultaneously. |
| Assignment Status | This indicates whether a particular device has a valid assignment to the application. Under the ‘Evaluated’ tab this will always be 'Assigned'. |
| Assignment Source | Filter for devices that are assigned directly or through a workflow. You can select only one of these options at a time for filtering. |
| Installed Version | Filter devices based on the version installed. |
| Last Action Taken | Filter for devices with last action such as Install and Remove. |
| Peer Distribution | Filter for devices with peer distribution status such as On/Utilized, On/Not Utilized, and Off. You can select one or more peer distribution statuses simultaneously. |
| Assigned Version | Filter devices based on the version assigned to the device using the UEM console. |
To return to the full device listing and clear all selected filters, you can either click the ‘Clear’ button in the filter panel to remove all applied filters at once or selectively remove filters by clicking the ‘X’ next to each filter.
Pending Devices
The Pending tab contains devices that are yet to be evaluated for the highest applicable version after the assignment of that version is published. It’s critical to monitor these pending devices since a device can only be assigned to the application and receive installation instructions on evaluation.
The Pending tab provides a detailed devices grid with device-specific attributes and options to filter the devices.
Listed are the scenarios when a device is considered pending.
- When a specific application is newly published, and the devices are yet to check in.
- When assignments are updated for any version of the application, all devices assigned to that version are marked as pending until they check in again, including devices that have already been evaluated.
Devices Grid
The devices grid provides detailed information about each device that is Pending, allowing you to perform bulk device-level actions.
| Column | Description |
|---|---|
| Last Check In | This indicates the timestamp when the device last checked in. |
| Last Sample Collected | This indicates the timestamp when the device last reported the sample. |
| Installation Status | This indicates whether the application is installed or not installed on the end-users device. Possible statuses include Installed, Not Installed, Out of Date, and Installed but not assigned. In the Pending tab, the installation statuses 'Installed', and 'Installed but not assigned' are possible when assignments are updated(and re-published) after the application was initially installed on the device due to a previous assignment. However, it's important to note that this installation status is transitional and lasts only for a brief period until the device re-checks in. Upon re-check-in, the device's assignments are re-evaluated, and the application may continue to be installed or uninstalled based on the updated assignments. |
| Installation Status Details | This provides detailed information about the installation state of the application, which should be reviewed alongside the corresponding installation status. In the Pending tab, the 'Installation status details' can occur only if assignments are updated(and re-published) after the device has received installation instructions from the previous assignments. |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the application. For scenarios where the actions are unsuccessful, you need to know what actions were last taken by the Workspace ONE UEM console on the application to narrow down the failure that occurred on the devices. In the Pending tab, the 'Last Action Taken' can occur only if assignments are updated(and re-published) after the device has received installation instructions from the previous assignments. |
| Assignment Status | This indicates whether a particular device has a valid assignment to the application. Possible statuses include 'Assigned' and 'Not assigned.' In the Pending tab, the 'Assigned' status for a device is only possible if the device was previously assigned(and re-published) and is awaiting re-evaluation. |
| Assignment Source | This indicates the source of assignment - either a direct deployment or through a Freestyle Workflow. In the Pending tab, 'Assignment Source' for a device is only possible if the device was previously assigned(and re-published) and is awaiting re-evaluation. |
| Device Friendly Name | This is the friendly name assigned to the device. |
| Assigned Version | This indicates the app version assigned to the device. A version can be present against a device under the ‘Pending’ tab only if it was previously assigned. |
| User Name | This is the name of the user associated with the device. |
| Organization Group | This is the name of the organization group into which the device is enrolled. |
Device Level Management Actions
You can perform management actions such as forcing the device to check in for evaluation directly from the devices grid.
| Action | Description |
|---|---|
| Force Check-in | Initiates a notification to prompt the device to check in. Upon check-in, the device undergoes evaluation, receives an assignment to the highest applicable version assigned, and then receives installation instructions. Maximum of 100 devices can be selected at once for this action. |
| Query | Sends a request to the device to retrieve the latest samples regarding the state of the application. The maximum number of devices that can be selected at once for this action is determined by the bulk settings configured in the console for this specific action. |
| Send | Send a notification such as an email, push, or SMS to the selected devices. The maximum number of devices that can be selected at once for this action is determined by the bulk settings configured in the console for this specific action. |
Filters
You can refine Pending device data using the filter panel.
| Filter | Description |
|---|---|
| Installed Version | Filter for devices having one or more versions installed. |
| Last Check In | Filter for devices that have last checked in during this time interval. You can select one or more last check-in times simultaneously. |
| Assigned Version | Filter for devices based on version(s) assigned to them. |
Installed but not assigned Devices
The Installed but not assigned tab contains devices that have the application installed but do not have a valid assignment to any specific version of the application.
A device belongs to this state when:
- An application is side-loaded to a device and is not assigned by an admin.
- An application is installed on a device through a previous assignment, but is no longer assigned.
- An application is seeded to the device by Workspace ONE UEM.
- An application is pushed by the device manufacturer (OEM app) and is pre-installed on the device.
- A system application, such as 'Camera' and 'Contacts', is pushed by the platform and is pre-installed on the device.
For more information about the Installed but not assigned status, see the knowledge base article at https://kb.omnissa.com/s/article/6000807.
Devices Grid
The devices grid provides detailed information about each device that has the app “Installed but not assigned”, allowing you to search for specific devices.
| Column | Description |
|---|---|
| Last Check In | This indicates the timestamp when the device last checked in. |
| Last Sample Collected | This indicates the timestamp when the device last reported the sample. |
| Installation Status | The installation status will always be ‘Installed but not assigned’. |
| Installation Status Details | This provides information about the installation state of the application, which should be reviewed alongside the corresponding installation status. Possible statuses are ‘Unknown' and ‘Managed’. In the ‘Installed but not assigned’ tab, the ‘Unknown’ status is displayed for the devices that have side-loaded the app. ‘Managed’ status is displayed for the devices that have the app installed from a previous assignment. |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the application. |
| Assignment Status | This will always be ‘Not Assigned’. |
| Assignment Source | This indicates the source of assignment which is a direct deployment or a Freestyle Workflow. In the Installed but not assigned tab, ‘Assignment Source’ for a device is only possible if the device was previously assigned. |
| Device Friendly Name | This is the friendly name assigned to the device. |
| Assigned Version | This indicates the specific version of the application assigned to the device. |
| User Name | This is the name of the user associated with the device. |
| Organization Group | This is the organization group into which the device is enrolled. |
App Status in Device Details Apps List view
The app status column on the Device details > Apps List View page has been updated to align with the deployment tracking changes.
In addition to the existing ‘App Status’ like ‘Installed’ and ‘Not Installed,’ two new statuses are available; ‘Installed but not assigned’ and ‘Out of date.’
The ‘Installed but not assigned’ status applies to any application installed on the device that wasn’t assigned through the Workspace ONE UEM console. This includes system apps, personally installed apps, or side-loaded apps. Some internal apps may also fall under this status if they were previously installed but have lost assignments. These apps will eventually be uninstalled from the device, but until then, they will be categorized as ‘Installed but not assigned.’
Additionally, internal apps may now display an additional status called 'Out of Date.' This status indicates that an application's lower version is installed on the device, while a higher version has been assigned but not installed. This can occur if the installation fails or if the device has not received the instruction to update the application version. It serves as an interim state until the device successfully installs the higher version of the application.
Was this page helpful?