Managing target devices
A device, such as desktop computer or server, that boots and gets software from a vDisk on the network, is considered a target device. A device that is used to create the vDisk image is a considered a Master Target device.
The lifecycle of a target device includes:
- a Master target device used for creating a vDisk image
- a target device that boots from a vDisk image
- Adding target devices to a collection in the farm
- from the Console
- using Auto-Add
- Assigning the target device type
- Maintaining target devices in the farm
After a target device is created, the device must be configured to boot from the network, the device itself must be configured to allow it to boot from the network, a vDisk must be assigned to the device, and a bootstrap file must be configured to provide the information necessary for that device to boot from the assigned vDisk.
There are several types of target devices within a farm. For example, while a device is being used to create a vDisk image, it is considered a Master target device. All other devices are configured as a particular device type. The device Type determines a devices current purpose, and determines if that device can access a particular vDisk version that is in Production, Test, or Maintenance.
The device Type is selected on the General tab of the Target Device Properties dialog, which includes the following options:
- Production: select this option to allow this target device to stream an assigned vDisk that is currently in production (default).
- Maintenance: select this option to use this target device as a Maintenance device. Only a Maintenance device can access and make changes to a vDisk version that is Maintenance mode (only the first Maintenance device to boot the version while in Maintenance mode, is allowed to access that version).
- Test: select this option to use this target device to access and test differencing disk versions that are currently in Test mode.
A target device becomes a member of a device collection when it is added to the farm. The use of device collections simplifies the management of all target devices within that collection. A target device can only be a member in one device collection. However, a target device can exist in any number of views. If a target device is removed from the device collection, it is automatically removed from any associated views.
When target devices are added to a collection, that devices properties are stored in the Provisioning Services database. Target Device properties include information such as the device name and description, boot method, and vDisk assignments (refer to Target Device properties for details).
Target Devices are managed and monitored using the Console and Virtual Disk Status Tray utilities.
In the Console, actions can be performed on:
- An individual target device
- All target devices within a collection
- All target devices within a view
There is a risk that moving target devices from site to site could cause them to be deleted in the future. This risk increases if the target device was created using the Streamed VM Setup Wizard. While an administrator can use the interface to move target devices from site to site, Citrix recommends that you avoid moving them from site to site in this fashion.