The Limit delivery of these assignments to specific computers option option helps in determining the type of assignment scenario such as: an assignment is newly created, an existing assignment is updated, or a duplicate assignment is skipped. Some of the assignment scenarios are listed in this topic for a better understanding.
New Assignment
Scenario 1:
An administrator assigns Application 'X', package 1 to a non-computer entity 'user' on computer 'Dev'. The administrator can assign the same Application Package to 'user' on another computer, 'Test'.
Scenario 2:
An administrator assigns Application 'X' (Marker or Package) to a non-computer entity 'user' on computer 'Dev'. The administrator can assign Application 'Y' (Marker or Package) to the entity 'user' on 'Dev'.
Scenario 3:
An administrator assigns Application 'X', package 1 to a non-computer entity 'group' on computer 'Dev'. The administrator can assign package 2 of the same application (X) to 'group' on another computer 'Test'.
Scenario 4:
An administrator assigns Application 'Y', package 1 to a non-computer entity 'OU'. No computer prefix is specified. This results in the application being assigned to 'OU' on all computers. The administrator can assign Application 'Y', package 2 to OU on 'Dev'.
Update Assignment
Scenario 1:
An administrator assigns Application 'X', package 1 to a non-computer entity 'user' on computer 'Dev'. The administrator can assign Application 'X', package 2 to ‘user’ on ‘Dev’. As an entity can receive only one version of the Application Package at a time on a specific computer, the assignment to ‘user’ on ‘Dev’ is updated to package 2. The assignment occurs at the following login session.
Scenario 2:
An administrator assigns Application ‘Y’, package 1 to a non-computer entity ‘group’ on all computers. The administrator can assign Application ‘Y’, package 2 to ‘group’ on all computers. ‘group’ receives package 2 on all computers because an entity can be assigned only one package version of an Application at a time on a computer. As a result, ‘group’ receives the latest package version assignment.
Skip (Duplicate) Assignment
An administrator assigns Application ‘X’, package 1 to a non-computer entity ‘user’ on ‘Dev’. The administrator unintentionally selects the same entity to assign the same package version of the application on ‘Dev’. As the application package is a duplicate, the assignment to 'user' is skipped.
For more information about the Limit delivery of these assignments to specific computers option option, see Application Assignment to Specific Computers.
Was this page helpful?