Collections

Device collections allow you to create and manage logical groups of target devices. Creating device collections simplifies device management by performing actions at the collection level rather than at the target-device level.

Note:

A target device can only be a member of one device collection.

A device collection represents a physical location, a subnet range, or a logical grouping of target devices. For example, a collection consists of all target devices that use a particular virtual disk image, and the collection might consist of maintenance, test, and production devices.

Alternatively, three device collections can exist for a particular virtual disk; one consisting of production devices, one consisting of test machines, and another consisting of maintenance machines. In the proceeding examples, all devices in a given collection are assigned to the same virtual disk.

Depending on a sites preference, another collection use case might include the consolidation of test and maintenance devices into a single device collection. This use case manages virtual disk assignments on a per device basis rather than a per collection basis. For example, create a device collection labeled Development consisting of five target devices, each one assigned to a particular virtual disk. Farm administrators create and manage device collections for sites they have security privileges to configure.

Expanding a Device Collections folder in the Console’s tree allows you to view members of a device collection. To display or edit a device collection’s properties, right-click on an existing device collection in the Console, then select the Properties menu option. The Device Collection Properties dialog displays. Use it to view or modify that collection.

You can perform actions on members of a device collection, such as rebooting all target devices members in this collection.

Collections