The modernized Omnissa Workspace ONE UEM helps you quickly deploy individual versions of internal applications and efficiently track deployment progress.
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 version when you deploy and install it on your end users' devices and take the necessary actions for devices that require immediate attention.
Assignment Preview
When assignments are saved for a specific version of an internal application, an assignment preview is presented before publishing the assignments. This preview serves as a snapshot, providing a quick overview of any changes made to assignments. Its purpose is to help you identify any significant deviations in assignments that might have occurred accidentally before publishing.
The following assignment statuses help you quickly identify any substantial changes in assignments:
- Assigned - This represents the overall number of devices targeted to receive the particular version of an application. It is calculated by subtracting the devices that are excluded from the assignments and those that are not eligible to receive the specific version due to applicability rules (for example, iOS devices assigned to receive an Android app) from the total number of devices assigned through smart groups.
- Newly Added - These devices are newly assigned to receive the specific version.
- Newly Removed - This includes devices that have lost their assignment to the particular version due to updates in existing assignments or the addition of an exclusion.
- Unchanged - These devices continue to retain their assignments even after any updates are made to the assignments.
Additionally, the preview includes an estimated time for devices to receive the install or uninstall instructions for the app version. The estimated time provided for assigned devices to receive the install or uninstall instructions reflects the percentage of devices expected to receive these instructions within the next four hours. This estimate is based on the devices' historical check-in frequency. Note that this estimate represents the best-case scenario, as devices may not receive assignment instructions if they fail to check in after the particular version of the application is published.
Also, the estimated time is only applicable when the deployment type is set to Auto. For On-demand deployments, devices receive instructions when a user chooses to install the particular version or when an admin force pushes it from the console.
Deployment Tracking Dashboard
The deployment tracking dashboard provides in-depth insights into the deployment progress of a particular version of an application. You can monitor installation progress in real-time 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 tracking dashboard for your internal app version:
-
Navigate to Resources > Apps > Native Apps > Internal.
-
Select the app version from the displayed app list. You can also use the search functionality to find the specific app version easily.
-
Click on the specific application version's hyperlink.
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 specific application version and presents various operations that can be performed on the specific app version such as editing or assigning the app.
-
Summary Stats: This section presents a high-level summary of deployment statistics, including the number of devices targeted for assignment, those with confirmed assignments, devices pending evaluation, those excluded from assignment, and devices where applications are installed but not officially assigned.
-
Charts and Device Grids: This section contains intuitive and interactive charts that provide a visual representation of the Internal 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 four tabs corresponding to the summary stats: Currently assigned, Pending, Excluded, and Installed but not assigned. Each tab offers comprehensive tracking information and lists devices based on their respective categories.
Target Assignments
Target Assignments count represents the total number of devices targeted to receive the application version based on Smart Group criteria.
It is calculated by subtracting the devices that are excluded from the assignments and those that are not eligible to receive the application version due to applicability rules (for example, iOS devices are assigned to receive an Android app) from the total number of devices assigned through smart groups.
Target Assignments = Devices assigned through Smart Groups - Excluded devices - Inapplicable devices.
For example, let’s say there are 500 devices assigned to receive the application version through smart groups. However, 50 of these devices are excluded from receiving the application version through exclusion, and an additional 20 devices are not able to install this application version (For example, iOS devices assigned to receive an Android app). In this case, the Target Assignments count is 500 (Devices assigned through smart groups) - 50 (Excluded devices) - 20 (Inapplicable devices) = 430 devices.
Currently Assigned
The Currently Assigned tab displays devices that have a confirmed assignment to the application version at any given time.
When a device targeted for assignment checks in, UEM assesses whether it is eligible to receive the application version. If the device is eligible, it receives a confirmed assignment. Offline devices can take up to 6 hours to receive a confirmed assignment based on a periodic offline assessment performed by UEM.
Charts
The Currently Assigned 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 specific application version is installed or not on devices. It gives you a clear view of how many devices have the application version 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 version. You can select the 'Not Installed' filter option to view devices in this category and get a more detailed breakdown with the 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. |
| Last Action | The 'Last Action' chart represents the various actions taken by the Workspace ONE UEM console on the device regarding the specific application version. Here are some of the last actions: Install - Indicates that the device received the command to install the specific application version. Remove - Indicates that the device received the command to uninstall the specific application version. Unknown - Indicates that UEM didn't issue any command to the device regarding the specific application version. |
| 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 particular application version 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 device having a confirmed assignment at that time, providing insight into deployment progress. Additionally, you can execute bulk device-level actions, such as forcing an installation or removing an 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 particular version of the application is installed or not installed on the end-user's device. Possible statuses include Installed and Not Installed. |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the specific application version. 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 specific application version to narrow down the failure on the devices. |
| Assignment Status | This is always ‘Assigned’. |
| Assignment Source | This indicates the source of the assignment - either a direct deployment or through a Freestyle Workflow. |
| Device Friendly Name | This is the friendly name assigned to the device. |
| User Name | This is the username associated with the device. |
| Organization Group | This is the organization group name into which the device is enrolled. |
| Peer Distribution | Displays the status of the peer distribution |
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 simultaneously apply actions to all the filtered devices.
| Action | Description |
|---|---|
| Install | Force installs the specific application version on the selected device. A maximum of 100 devices can be selected at once for this action. |
| Remove | Removes the specific application version if managed, from the selected device. A 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 specific application version. 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. |
| Force Check-in | Initiates a notification to prompt the device to check in. Upon check-in, the device undergoes evaluation, receives an assignment to this version (only if applicable), and then receives installation instructions. 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 that specific device by 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
You can refine deployment tracking data for currently assigned devices using interactive charts or the filter panel. This allows you to focus on specific 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. To return to the full device listing and clear all selected filters, you can either click the ‘Clear’ button in the filter panel or selectively remove filters by clicking the ‘X’ next to each filter.
| 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 currently assigned 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 after a specific application 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 self-explanatory Last Check-in chart to track offline devices, a detailed devices grid with device-specific attributes, and options to filter the devices.
Listed are the scenarios when the devices are considered pending.
- When a specific application version is newly published, and the devices are offline.
- When app assignments are updated for a specific application version, all devices targeted for that app version are marked as Pending evaluation until they check in, including devices that were evaluated and are displayed as currently assigned. This ensures that all targeted devices are re‑evaluated against the latest assignment updates.
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 specific application version is installed or not installed on the end-users device. Possible statuses include Installed, Not Installed, 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 specific application version 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. |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the specific application version. For scenarios where the actions are unsuccessful, you need to know what actions were last taken by the Workspace ONE UEM console on the specific application version 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 specific application version. 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. |
| 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 this version (only if applicable), 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 specific application version. 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 interactive Last Check-in chart or the filter panel.
| Filter | Description |
|---|---|
| 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. |
Excluded Devices
The Excluded tab contains devices that have been excluded from deployment through an exclusion smart group. This tab provides a devices grid with excluded devices (and their attributes), along with options to search.
Devices Grid
The devices grid provides detailed information about each device that is excluded, allowing you to search for specific excluded devices.
| Columns | 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 specific application version is installed or not installed on the end-user's device. Possible statuses include Installed, Not Installed, and Installed but not assigned. In the Excluded tab, the installation statuses 'Installed', and 'Installed but not assigned' are possible only when the device is added to an exclusion smart group after the specific application version was initially installed on the device using 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 instructions to uninstall the application will be provided. |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the specific application version. In the Excluded tab, the 'Last Action Taken' can occur only if the device is added to an exclusion smart group after it had received installation instructions from the previous assignment. However, the Last action will be updated to 'Unknown' eventually when the device checks in next and receives instructions to uninstall the specific application version. |
| Assignment Status | This indicates whether a particular device has a valid assignment to the specific application version. Possible statuses include 'Assigned' and 'Not assigned.' In the Excluded tab, the 'Assigned' status for a device is only possible if the device was previously assigned. However, the assignment status will be updated to 'Not Assigned' eventually when the device checks in next. |
| Assignment Source | This indicates the source of the assignment, which is a direct deployment or a Freestyle Workflow. In the Excluded tab, 'Assignment Source' for a device is only possible if the device was previously assigned. However, the assignment source will be updated to 'N.A' eventually when the device checks in next. |
| Device Friendly Name | This is the friendly name assigned to the device. |
| 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. |
Installed but not assigned Devices
The Installed but not assigned tab contains devices that have the app version installed but do not have an assignment for the app version.
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.
Note: To ensure accurate status reporting, please update your Windows and Mac Hub to version 24.04 or later.
Devices Grid
The devices grid provides detailed information about each device that has the app version 'Installed but not assigned', allowing you to search for specific devices.
| Columns | 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 is always ‘Installed but not assigned’ |
| Last Action Taken | This indicates the last action taken by the Workspace ONE UEM console on the device regarding the specific application version. In the Excluded tab, the 'Last Action Taken' can occur only if the device is added to an exclusion smart group after it has received installation instructions from the previous assignment. However, the Last action will be updated to 'Unknown' eventually when the device checks in next and receives instructions to uninstall the specific application version. |
| Assignment Status | This is always 'Not assigned' |
| Assignment Source | This indicates the source of assignment, whether it is a direct deployment or a Freestyle Workflow. In the Excluded 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. |
| 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. |
Installation Status in Applications List View
To align with the deployment tracking changes, we have updated the quick deployment summary view displayed for specific application versions in the application list view.
When you hover on 'view' in the 'Install Status' column of an application, it displays four key metrics.
| Metrics | Description |
|---|---|
| Not Installed | This refers to the total count of devices currently assigned to the application, but have not yet installed the specific application version. Clicking this count redirects you to the Deployment tracking page, with the view defaulted to the 'Currently Assigned' tab and a filter applied on 'Installation status' as 'Not Installed'. |
| Installed | This refers to the total count of devices currently assigned to the application version and have successfully installed the specific application version. Clicking this count redirects you to the Deployment tracking page, with the view defaulted to the 'Currently Assigned' tab and a filter applied on 'Installation status' as 'Installed'. |
| Directly assigned | This refers to the total count of devices that are currently assigned to the application and received the assignment only through a 'direct' assignment. Clicking this count redirects you to the Deployment tracking page, where the view defaults to the 'Currently Assigned' tab and applies filters on 'Assignment type' as 'Assigned' and 'Assignment source' as 'Direct'. |
| Workflow assigned | This refers to the total count of devices currently assigned to the application version that received the assignments through a 'Freestyle Workflow'. Clicking this count redirects you to the Deployment tracking page, where the view defaults to the 'Currently Assigned' tab and applies filters on 'Assignment type' as 'Assigned' and 'Assignment source' as 'Workflow'. |
Was this page helpful?