Unassignable Packages

If a package is not complete, for example it does not contain all of the necessary files it needs, then the package cannot be assigned to computers.  You must resolve the incompleteness in order to make it assignable.  The packages that cannot be assigned to computers are displayed under Packages in the Scope pane as Unassignable Packages.

To detect the reason why a package is not assignable

  1. In the Scope pane expand the server name > Packages.

  2. Click Unassignable Packages to display the packages in the Result pane.

The Reason(s) for Unassignability column displays why the package cannot be assigned.

Reason(s) for Unassignability

Description

Missing Vendor Files

The vendor files for the package are not in the Package Depot.

DEPOTDIR

The vendor files for this package are used by another package and the vendor files are not in the Package Depot.

Vendor Files and DepotDir package are missing

The vendor files for this package are used by another package and both the vendor files and other package are missing from the Package Depot.

Unresolved dependency

A dependent package does not exist in the Package Depot.

To resolve package assignability

  1. In the Scope pane expand the server name > Packages > Unassignable Packages.

  2. Select and right-click a package and choose Resolve Assignability.

  3. Follow the instructions on each dialog box to resolve the assignability of the package.