vDisks 编辑

vDisks are managed throughout their lifecycle. Full image lifecycle takes a vDisk from creation, through deployment and subsequent updates, and finally to retirement. The lifecycle of a vDisk consists of four stages:

1. Creating
2. Deploying
3. Updating
4. Retiring

When provisioning target devices, consider the following:

• To have a single vDisk, all target devices must have certain similarities to ensure that the OS has necessary drivers required to run properly. The three key components are the motherboard, network card, or video card.

• Install and configure OEM NIC teaming software before you install the target device software.

• Identify target devices by the operating system running on the device.

• Dual boot vDisk images are not supported.

• BitLocker encryption is not supported on a provisioned target device vDisk.

See System requirements for more information.

Creating a vDisk

Creating a vDisk includes:

• preparing the master target device for imaging
• creating and configuring a vDisk file where the vDisk resides
• imaging the master target device to that file

These steps result in a new base vDisk image. This process can be performed automatically, using the Imaging Wizard, or manually. You can also create a common image for use with a single target platform or for use with multiple targets. For details, see Creating vDisks.

Deploying a vDisk

After a vDisk base image is created, it is deployed by assigning it to one or more devices. A device can have multiple vDisk assignments. When the device starts, it boots from an assigned vDisk. There are two boot mode options; Private Image mode (single device access, read/write), and standard image mode (multiple devices, write cache options). For more details, see Prerequisites for deploying vDisks later in this article.

Updating a vDisk

It is often necessary to update an existing vDisk so that the image contains the most current software and patches. Updates can be made manually, or the update process can be automated using vDisk Update Management features. Each time a vDisk is updated a new version is created. Different devices can access different versions based on the type of target device and version classification. A maintenance device can have exclusive read/write access to the newest maintenance version. Test devices can have shared read-only access to versions classified as test versions. Production devices can have shared read-only access to production versions. Versions are created and managed from the vDisk Versioning Dialog. An update can also be the result of merging versions. For more details on updating vDisks, see Updating vDisks.

Retiring a vDisk

Retiring a vDisk is the same as deleting. The entire VHDX chain including differencing and base image files, properties files, and lock files, are deleted. For details, see Retiring or deleting virtual disks.

Note:

In addition to those vDisk tasks performed within a disk’s lifecycle, there are also other vDisk maintenance tasks that can be performed. These include importing or exporting the vDisk, backing-up vDisks, replicating, and load balancing.

Prerequisites for deploying vDisks

vDisks are configured before being deployed. Configuration tasks include:

• Selecting the vDisk access mode and if applicable, the write cache mode. See Selecting the write cache destination for standard vDisk images.
• Configuring the vDisk for Microsoft Volume Licensing. For details, see Configuring a vDisk for Microsoft Volume Licensing.
• Enabling Active Directory machine account password management, if applicable.

Selecting the write cache destination for standard vDisk images

Citrix Provisioning supports several write cache destination options. The write cache destination for a vDisk is selected on the General tab, which is available from the vDisk File Properties dialog.

Considerations and requirements

• Consider the impact of using the server-side persistent write cache. Persistent cache is only used where unauthorized users have access to a machine. Ensure that machines are not shared among users.
• When selecting cache on local hard drive, ensure that the hard-disk drive is formatted with NTFS for Window devices, with a minimum of 500 MB.
• When selecting cache on the target device RAM and standard image mode, the registry setting WcMaxRamCacheMB (a DWORD) in the BNIStack Parameters determines the max size of the RAM write cache. If the registry entry does not exist, then the default value used is 3584 MB.
• Citrix Provisioning version 7.7 only supports the use of Microsoft System Center Configuration Manager (ConfigMgr) Client as follows:

The following sections describe all valid write cache destination options.

Note:

Provisioning Services version 7.12 introduced Linux streaming. When using this feature, consider that caching options on a Linux target device are the same on a Windows device. For more information about Linux streaming, see Installation.

Cache on device hard drive

Write cache can exist as a file in NTFS format, or on the target-device’s hard drive. This option frees up the server. It does not process write requests because it does not have the finite limitation of RAM.

The hard drive does not require any additional software to enable this feature.

Note:

The write cache file is temporary unless the vDisk mode is set to Private Image mode.

Important:

The vDisk cache type field Cache on device hard drive is deprecated and will be removed in a future release. Citrix recommends using one of the other available cache types. For more information, see the Deprecation article.

Cache on device hard drive persisted (experimental phase only)

The same as Cache on device hard drive, except cache persists. This write cache method is an experimental feature and is supported only for NT6.1 or later. This method also requires a different bootstrap. To click the correct bootstrap from the console, right-click on the provisioning server, select Configure Bootstrap. On the General tab, click the Bootstrap file option, then choose CTXBP.BIN. Citrix recommends that the local HDD (client side) drive has enough free space to store the entire vDisk.

Important:

The vDisk cache type field Cache on hard drive persisted is deprecated and will be removed in a future release. Citrix recommends using one of the other available cache types. For more information, see the Deprecation article.

Cache in device RAM

Write cache can exist as a temporary file in the target device’s RAM. It provides the fastest method of disk access since memory access is always faster than disk access.

Cache in device RAM with overflow on hard disk

Write cache uses the VHDX differencing format:

• When RAM is zero, the target device write cache is only written to the local disk.
• When RAM is not zero, the target device write cache is written to RAM first. When RAM is full, the least recently used block of data is written to the local differencing disk to accommodate newer data on RAM. The amount of RAM specified is the non-paged kernel memory that the target device consumes.

Compared to “Cache on device hard drive” cache mode, the VHDX block format has a faster file expansion rate. The local disk free space is reconsidered to accommodate the streaming workload. To ensure target device reliability in a high demand workload, Citrix recommends that local disk free space is larger than vDisk capacity size.

When the local disk is out of space, the target device vDisk I/O goes in to a pause state. It waits for more local disk free space to become available. This condition has a negative impact on the workload continuity. Citrix recommends allocating enough local disk free space.

The amount of RAM specified does not change the local disk free space requirement. The more RAM assigned, the more vDisk I/Os temporarily saved in RAM cache before all data gets flushed back to the VHDX file. The RAM reduces the initial VHDX expansion rate.

Cache on a server

Write cache can exist as a temporary file on a provisioning server. The Provisioning server handles all writes, which can increase disk I/O and network traffic.

For extra security, the server can be configured to encrypt write cache files. Since the write-cache file does exist on the hard drive between reboots, the data is encrypted in the event a hard drive is stolen.

Cache on server persistent

This cache option allows for the saving of changes between reboots. Using this option, after rebooting, a target device is able to retrieve changes made from previous sessions that differ from the read only vDisk image. If a vDisk is set to Cache on server persistent, each target device that accesses the vDisk automatically has a device-specific, writable disk file created. Any changes made to the vDisk image are written to that file, which is not automatically deleted upon shutdown.

The file name uniquely identifies the target device by including the target device’s MAC address and disk identifier. A target device can be assigned to multiple vDisks and therefore have multiple cache files associated to it.

To restore a vDisk that uses Cache Persistent on Server, be sure to back up all vDisk files and associated user cache files before making changes.

The benefits of using this cache option include:

• Saves target device specific changes that are made to the vDisk image.
• Same benefits as standard image mode.

The drawbacks of using this cache option include:

• The cache file is available so long as the file remains valid. Any changes made to the vDisk force the cache file to be marked invalid. For example, if the vDisk is set to Private Image Mode, all associated cache files are marked invalid.

Note:

Cache files that are marked as invalid are not deleted. Periodically, these files are manually deleted.

Invalidating changes include:

• Placing a vDisk in maintenance
• vDisk is placed in private image mode
• Mapping the drive from the Citrix Provisioning console
• Changing the location of the write cache file
• Using the automatic update

Tip:

Consider the impact of using a server-side persistent write cache. Persistent cache is only used where unauthorized users have access to a machine. Ensure that machines are not shared among users.