13.2 User Assignment Status

This dashlet displays the assignment status of an individual bundle assigned to users. Along with the assignment status, the dashlet chart also displays the total number of users to whom the bundle is assigned and the number of unique devices into which the users are logged-in.

For example:

Scenario 1: A bundle is assigned to 2 users who have logged-into to the same device, Device 1. The dashlet chart will display the Assigned Users count as 2 and the Logged-in Devices count as 1. The number of records displayed in the Status Details panel will be 2.

Scenario 2: A bundle is assigned to 2 users, User A and User B. User A has logged-into Device 1 and Device 2. User B has logged-into Device 2. The dashlet chart will display the Assigned Users count as 2 and the Logged-in Devices count as 2. The number of records displayed in the Status Details panel will be 3.

The user assignment status is processed only when the user logs-in to a device. If you are accessing the bundle dashlets for the first time, then the User Assignment Status dashlet will load after a few minutes. For more information, see Reduce High CPU Utilization while Computing User Assignment Dashlet Data.

The assignment status information of a bundle is categorized as:

  • Effective: Indicates that the system requirements have met on a user-assigned bundle for a given device. This is determined only when the user logs-in to the device.

  • Not Effective: Indicates that the system requirements have not met on a user-assigned bundle for a given device. This is determined only when the user logs-in to the device.

  • Blocked: Indicates that the bundle assignment has been blocked for a specific user.

  • Unknown: Indicates that the bundle assignment for a user exists but the server is unable to determine the status of the bundle as the user might not have logged into the device or the bundle has not been used on the device.

To determine how best to configure the dashlet for your organization’s needs, you can ask questions such as:

  • How many devices to which the user is logged-in, do not the meet the system requirements of the bundle?

  • How many users are yet to log-in to their devices and install the bundle?

Filter the data displayed: To filter the data that the dashlet displays, expand and modify any of the sections in the Filter panel. The filters include Device Folders, Device Groups, Operating System, Device Type, and Agent Version. Additionally, the following filters are also available based on which the displayed data can be modified:

Filter

Description

Device Folders

View users based on the device folder to which their logged-in devices belong.

Device Groups

View users based on the device group to which their logged-in devices belong.

Operating System

View users based on the operating system version on their logged-in device.

Device Type

View users based on whether the logged-in device is a server, workstation or a mobile device.

Agent Version

View users based on the agent version installed on the logged-in device.

Status Processed Time

View users based on the time at which the status of the bundle, such as the assignment status or the deployment status, was last updated or modified.

Bundle Assignment

View users based on the manner in which the bundle was assigned, that is, whether a bundle was assigned directly or through a bundle group. On selecting the bundle name, only those users to whom the bundle was directly assigned, are displayed.

On selecting the bundle group (if any) then all users to whom the bundle was assigned through a group are displayed.

Also, based on your selection, the number of users displayed in the dashlet chart will also be updated.

Bundle Version

View users based on the version of the bundle assigned:

  • Published version

  • Sandbox version

Show Logged-in Users Only

Select Yes if you want to view only those users who are either currently logged-in or had logged-in to their devices at some point in time. By default, all the users to whom the bundle is assigned, are displayed.

Assignment Status

The assignment status of the bundle:

  • Effective

  • Not Effective

  • Blocked

  • Unknown

The User Assignment Status panel: displays the devices that meet the criteria defined in the Filter panel. This panel also displays the reason for a bundle to be not effective on the device. You can also filter the list by searching for a user name.

Column Name

Description

User

The name of the user to whom the bundle is assigned.

Device

The name of the device. This is displayed only if the user has logged-in to the device.

Status Processed Time

The time at which the status of the bundle, such as the assignment status or the deployment status, was last updated or modified.

Bundle Version

The version of the bundle for which the record is displayed. By default the latest published version is displayed. The bundle version might be displayed as Unknown, if the bundle is yet to be processed on the device.

Assignment Status

The status of the assignment based on the selected bundle version assigned to the device is displayed. The statuses are:

  • Unknown

  • Effective

  • Not Effective

  • Blocked

Not Effective Reason

The reason for the bundle to be not effective for a user logged-into a given device.

Blocked Time

The time at which the bundle was blocked from executing on the device.

Bundle Assignment

The manner in which the bundle is assigned. If the individual bundle is directly assigned to the user and a bundle group, to which the bundle belongs, is assigned to the user then the value 2 is displayed.

It determines the different ways in which the bundle is assigned to the device and helps in identifying duplicate assignments made for the device.

Execute action from the User Assignment Status panel: The actions that you can execute from this panel are:

Task

Description

Block Bundle

To block the bundle for the selected user. This would block the execution of the bundle on all devices to which the user logs in. If the blocked bundle uninstalls from the device to which the user logs-in, the assignment status of the bundle changes to Pending after the server side computation.

Unblock Bundle

To unblock an already blocked bundle for selected users.

Refresh Device

To refresh the device so that any pending actions can immediately be initiated on the device. This quick task updates all information (bundle, policy, configuration settings, registration, and so forth) on the selected devices.

Retrieve Bundle Status

Obtains the latest bundle status from the selected devices and rolls up this information to the server. You can select from one of the following options:

  • Differential scan: obtains the change in status of all the bundles in the selected device since the last complete scan.

  • Complete scan: runs a full scan to obtain the current status of all the bundles in the selected device.