Target devices

A device, such as desktop computer or server, that boots and gets software from a virtual disk on the network is considered a target device. A device that is used to create the virtual disk image is a considered amaster target device.

The lifecycle of a target device includes:

• Preparing
  • A Master target device used for creating a virtual disk image
  • A target device that boots from a virtual disk image
• Adding target devices to a collection in the farm
  • From the Console
  • Using Auto-Add
  • Importing
• 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 must be configured to allow it to boot from the network. Also, a virtual disk 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 virtual disk.

There are several types of target devices within a farm. For example, while a device is being used to create a virtual disk 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 virtual disk version that is in production, test, or maintenance.

The device Type is selected on theGeneraltab of theTarget Device Propertiesdialog, which includes the following options:

• 生产: Select this option to allow this target device to stream an assigned virtual disk that is currently in production, the default.
• Maintenance: Select this option to use this target device as a maintenance device. Only a maintenance device can access and alter a virtual disk version that is in 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 Citrix Provisioning database. Target device properties include information such as the device name and description, boot method, and virtual disk assignments (seeTarget devicepropertiesfor details).

Target devices are managed and monitored using theConsole and Virtual Disk Status Trayutilities.

In the Citrix Provisioning console, actions can be performed on:

• An individual target device
• All target devices within a collection
• All target devices within a view

Target device properties

When configuring a target device, consider the following:

• A reboot is required if a target device is active when modifications are made to any of the following device properties: Boot from, MAC, Port, vDisks for this device.
• BitLocker encryption is not supported on a provisioned target device virtual disk.

The following tables define the properties associated with a target device.

General tab

Virtual disk tab

Personality tab

Authentication tab

Password information entered in this dialog is for the initial target device login process only. It does not affect the Windows account login.

Status tab

Logging tab

Setting the target device as the template for this collection

A target device can be set as the template for new target devices that are added to a collection. A new target device inherits the properties from the template target device, which allows you to quickly add new devices to a collection.

Tip

Target devices using virtual disks are created and added to a collection when running the Citrix Virtual Apps and Desktops Setup Wizard. If a target device template exists, it is ignored when the target device using a virtual disk is added to the collection.

To set a target device as the template device for a collection, in the console, right-click on the target device, then select theSet device as templateoption.

Consider the following when using templates:

• Disable the target device that serves as the template. Disabling it adds all target devices using this template to the database, but does not permit the target device to boot.
• Target devices receive a message requesting that they first contact the administrator before being allowed to boot.
• Tappears in light blue on the device serving as the template. New target devices automatically have a name generated and all other properties are taken from the default template target device. No user interaction is required.

Creating a VM with nested virtualization

Sometimes, you want to create a nested virtualization paradigm for a VM. If your environment uses Device Guard and you want to create a template from the VM running it, consider that Citrix Provisioning is unaware that it was set up for that particular VM. To resolve this issue, manually enable Device Guard on the Hyper-V host using a PowerShell command. Perform this operation after the VM has been created using the Citrix Virtual Apps and Desktops Setup Wizard.

To configure a VM to use Device Guard:

1. Create the VM using the Citrix Virtual Apps and Desktops Setup Wizard.

2. After creating the VM, run the following command for each VM on the physical Hyper-V host to enable nested virtualization:

   Set-VMProcessor -VMName -ExposeVirtualizationExtensions $true

Tip:

See the Microsoft site for more information aboutnested virtualization.

复制和粘贴目标设备properties

To copy the properties of one target device, and paste those properties to other target device members:

Note:Target devices that use virtual disks can only inherit the properties of another target device that uses one.

1. In the Citrix Provisioning console’sDetailspane, right-click on the target device that you want to copy properties from, then selectCopy device properties. TheCopy Device Propertiesdialog appears.
2. Select the check box next to the properties that you want to copy, then clickCopy. The properties are copied to the clipboard and the dialog closes.
3. Right-click on one or more target devices that inherit the copied properties, then select the粘贴menu option. The粘贴Device Propertiesdialog appears.
4. ClickCloseto close the dialog.

Booting target devices

1. Right-click on a collection to boot all target devices in the collection. Or, highlight only those target devices that you want to boot within the collection tree, then select theBoot devicesmenu option. TheTarget Device Controldialog displays with the Boot devices menu option selected in theSettingsmenu.
2. Click the Boot devices button to boot target devices. TheStatuscolumn displays theBoot Signal状态,直到目标设备成功发射es the signal, then status changes to Success.

Checking a target device’s status from the console

The target device status indicates whether it is active or inactive on the network.

To check the status of a target device:

1. Double-click on the target device in the console window, then select thePropertiesmenu option. TheDevice Propertiestab appears.
2. Select theStatustab and review the following status information:
   • Status, active, or inactive
   • IP address
   • Current provisioning server
   • Current virtual disk name
   • Provisioning server cache file size in bytes If the target device is active in the console window, the target device icon appears as a green computer screen. If the target device is inactive, the icon appears as a black computer screen.

Sending messages to target devices

To send a message to target devices members:

1. Right-click on the collection to send a message to all members within the collection. Or, highlight only those target devices within the collection that receive the message, then select theSendmessage menu option. TheTarget Device Controldialog displays with the Message to devices menu option selected in theSettingsmenu. Target devices are displayed in theDevicetable.

2. Type a message to display on target devices in theMessagetext box.
3. Click the Send message button. TheStatuscolumn displays theMessage Signal statusuntil target devices successfully receives the message, the status changes toSuccess.

Shutting down target devices

To shut down target devices:

1. Right-click on the collection to shut down all target devices within the collection. Or, highlight only those target devices to shut down within a collection, then select theShutdown devicesmenu option. TheTarget Device Controldialog displays with the Shutdown devices menu option selected in theSettingsmenu. Target devices display in the Device table.
2. Type the number of seconds to wait before shutting down target devices in theDelaytext box.
3. Type a message to display on target devices in theMessagetext box.
4. Click theShutdown devicesbutton to shut down target devices. TheStatuscolumn displays the shutdown signal status until the target device shuts down. As each target device successfully shuts down, the status changes toSuccess.

Restarting target devices

To restart target devices:

1. Right-click on a collection in the console tree or highlight only those target devices you want to restart within the collection. Select theRestart devicesmenu option. TheTarget Device Controldialog displays with theRestart devices菜单选项中选择Settingsmenu. Target devices display in theDevicetable.
2. Type the number of seconds to wait before restarting target devices in theDelaytext box.
3. Type a message to display on target devices in theMessagetext box.
4. Click theRestart devicesbutton to restart target devices. TheStatuscolumn displays the重新启动信号状态,直到目标设备成功发射es the signal, then status changes toSuccess.

Moving target devices between collections

A target device can be moved from one collection to another collection within a site by dragging it into the console’sDetailspane. Drag the device from one collection, then drop the device into another collection. Alternatively, target devices can be moved using theMovemenu option.

To move a target device using theMovemenu option:

1. In the console, expand the collection, right-click on the target device in theDetailspane, then select theMovemenu option.
2. From the menu, select the collection to move this target device into. If necessary, apply the collection’s device template to the target device being moved by enabling the optionApply target collection’s template device properties.
3. ClickMove.

Tip:

There is a risk that moving target devices from site to site can cause them to be deleted in the future. This risk increases if the target device was created using the Streamed VM Setup Wizard. You can use the interface to move target devices from one site to another site, however, Citrix recommends that you avoid moving them from site to site using this method.

Managing target device personality

Normally, all target device’s sharing virtual disk must have identical configurations. TheTarget Device Personalityfeature allows you to define data for specific target devices and make it available to the target device at boot time. This data is used by your custom applications and scripts for various purposes.

For example, suppose you are using a provisioning server to support PCs in three classrooms. Each classroom has its own printer, and you want the PCs in each classroom to default to the correct printer. By using theTarget Device Personalityfeature, you can define a default printer field, and then enter a printer name value for each target device. You define the field and values underTarget Device Properties. This information is stored in the database. When the target device boots, the device-specific printer information is retrieved from the database and written to an .INI file on the virtual disk. Using a custom script or application that you develop, you can retrieve the printer value and write it to the registry. Using this method, each time a target device boots, it is set to use the correct default printer in its classroom.

The number of fields and amount of data that you can define for each target device is limited to 64 Kb or 65,536 bytes per target device. Each individual field contains up to 2,047 bytes.

Target device personality tasks

• Define personality data for a single target device using the console
• 人格定义为多个目标设备的数据s using the console
• Using target device personality data

Define personality data from a single target device using the console

To define personality data for a single target device:

1. In the Console, right-click on the target device that you want to define personality data for, then select thePropertiesmenu option.
2. Select thePersonalitytab.
3. Click theAddbutton. TheAdd/Edit Personality Stringdialog appears.Note:There is no fixed limit to the number of field names and associated strings you can add. However, the total amount of personality data assigned to a single string, names, and data, combined, is approximately 2,047 bytes. Also, the total amount of data contained in names, strings and delimiters is limited to approximately 64 Kb or 65,536 bytes per target device. This limit is checked when you attempt to add a string. If you exceed the limit, a warning message displays and you are prevented from creating an invalid configuration. Target device personality data is treated like all other properties. This data is inherited when new target devices are added automatically to the database. This inheritance occurs using theAdd New Target Device Silentlyoption, or with theAdd New Target Device with BIOS Promptsoption.
4. Enter a name and string value.Note:You can use any name for the field.Name, but you cannot repeat a field name in the same target device. Field names are not case sensitive. In other words, the system interpretsFIELDNAMEandfieldnameas the same name. Blank spaces entered before or after the field name are automatically removed. A personality name cannot start with a $. This symbol is used for reserved values such as $DiskName and $WriteCacheType.
5. ClickOK.

To add more fields and values, repeat Steps 5 and 6 as needed. When finished adding data, clickOKto exit theTarget Device Propertiesdialog.

人格定义为多个目标设备的数据s using the console

Define target device personality for multiple devices:

1. 在控制台中,右键单击目标设备that has the personality settings that you want to share with other device, then selectCopy. TheCopy device propertiesdialog appears.
2. Highlight the target devices in theDetailspane that you want to copy personality settings. Right-click and select the粘贴device propertiesmenu.
3. Click thePersonality stringsoption, or, alternately choose to copy other properties. Click粘贴.

Using target device personality data

Once the file system becomes available to the target device, the personality data is written to a standard Windows .ini text file calledPersonality.ini. The file is stored in the root directory of the virtual disk file system, your custom scripts or applications access this file.

The file is formatted as follows:

`[StringData] FieldName1=Field data for first field FieldName2=Field data for second field`

This file is accessible to any custom script or application and is queried by the standard Windows .INI API. Also, a command line application, calledGetPersonality.exe, permits easier batch file access to the personality settings.

A target device’s virtual disk name and mode can be retrieved using GetPersonality.exe. The following reserve values are included in the [StringData] section of the Personality.ini file:

$DiskName= $WriteCacheType=<0 (Private image) All other values are standard image; 1 (Server Disk), 2 (Server Disk Encrypted), 3 (RAM), 4 (Hard Disk), 5 (Hard Disk Encrypted), 6 (RAM Disk), or 7 (Difference Disk). Min=0, Max=7, Default=0>

The xx field is the name of the disk. A virtual disk name cannot start with a $. This symbol is used for reserved values such as $DiskName and $WriteCacheType. The following message displays if a name that starts with $ is entered:

A name cannot start with a $. This is used for reserve values like $DiskName and $WriteCacheType. The $DiskName and $WriteCacheType values can be retrieved on the target device using GetPersonality.exe.

GetPersonality.exe

The command line utilityGetPersonality.exeallows users to access theTarget Device Personalitysettings from a Windows batch file. The program queries the INI file for the user and places the personality strings in the locations chosen by the user. GetPersonality.exe supports the following command line options:

`GetPersonality FieldName /r=RegistryKeyPath <- Place field in registry GetPersonality FieldName /f=FileName <- Place field in file GetPersonality FieldName /o <- Output field to STDOUT GetPersonality /? or /help <- Display help`

Examples:

Setting a Registry Key Value:

The following example retrieves the Target Device Personality data value from theDefaultPrinterfield. It writes it to the target device registry to set the default printer for the device.

The Target Device Personality String Set inTarget DeviceProperties is:

`DefaultPrinter= \CHESBAY01\SAVIN 9935DPE/2035DPE PCL 5e,winspool,Ne03:`

A batch file run on the target device would include the following line:

`GetPersonality DefaultPrinter /r=HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Device`

Note:

The key name is the UNC name of the network printer, such as\dc1\Main. The value entered for the key would be similar towinspool,Ne01:whereNe01is a unique number for each installed printer.

Setting environment variables

Setting environment variables with personality data is a two-step process:

1. Use theGetPersonalitycommand with the /f option to insert the variable into a temporary file.

2. Use the set command to set the variable. For example, to set the environment variable Path statement for the target device a personality name, define the Pathname with the string value:

   `%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Microsoft Office\OFFICE11\;C:\Program Files\Microsoft SQL Server\80\Tolls\Binn`

   The/foption creates a temporary file, allowing for a name to be assigned, in this casetemp.txt. The following lines are included in the batch file:

   `GetPersonality Pathname /f=temp.txt set /p Path= 

   Note:

   If the file name specified with the/foption exists,Get Personalitydoes not append the line to the file. Instead, the existing line is overwritten in the file.