Carl Stalhood

Monday, 13 March 2017

Wednesday, 26 October 2016

XenDesktop Master Class: Live Install of XenDesktop/XenApp 7.6

Please share your suggestion so that i can improve this blog

https://www.youtube.com/watch?v=Fv-XEsniMu8

Citrix Provisioning server - pdating vDisks



Updating vDisks
update an existing vDisk is required so that the image contains the most current software and patches. Each time the vDisk is to be updated, a new version of that vDisk is created (VHD file) to capture the changes without changing the base vDisk image.
Updating a vDisk involves the following:
  • Create a new version of the vDisk, manually or automatically.
  • Boot the newly created version from a device (Maintenance device or Update device), make and save any changes to the vDisk, then shut-down the device.
  • Promote the new version to Production. 
The availability of the updated version depends on the current promotion of that version (Maintenance, Test, or Production), and the type of device attempting to access it (Maintenance Device, Update Device, Test Device, or Production Device).
Note: Updating images for devices that use a personal vDisk, must be done on a virtual machine that does not have a personal vDisk attached. Otherwise, updates are saved to the personal vDisk image rather than the virtual machine image.
  1. Create a new maintenance version of the vDisk.
  2. Make any necessary updates to the maintenance version.
  3. Promote the new maintenance version to test.
  4. Boot the PvD test device, and then verify updates were made.
  5. Promote the test version to production.
Update Scenarios
The following vDisk update scenarios are supported:
  • Manual Update – An administrator may choose to update a vDisk manually by creating a new version of that vDisk, and then using a Maintenance device to capture updates to that version. Manual updates are initiated by selecting the New button on the vDisk Versions dialog. The Access column on the vDisk Versioning dialog displays that the newly created version is currently under maintenance. While under maintenance, this version can only be accessed and updated by a single Maintenance device. Multiple Maintenance devices can be assigned to a vDisk. However, only one device can boot and access that version of the vDisk at any given time. During that time that Maintenance device will have exclusive read/write access.
  • Automated Update – Creating automated updates saves administration time and physical resources. Updates are initiated on-demand or from a schedule and are configured using vDisk Update Management. If updating automatically, the Access column on the vDisk Versioning dialog displays that the newly created version is currently under maintenance. While under maintenance, this version can only be accessed and updated by the one Update device to which it is assigned (only one Update Device exists per vDisk).
Note: vDisk Update Management is intended for use with Standard Image Mode vDisks only. Private Image Mode vDisks can be updated using normal software distribution tool procedures. Attempting to register a Private Image Mode vDisk for vDisk Update Management, or switching a vdisk that is already registered, will cause errors to occur.
  • Merge – Merging VHD differencing disk files can save disk space and increase performance, depending on the merge option selected. A merge update is initiated manually by selecting the Merge button on the vDisk Versions dialog, or automatically when the maximum vDisk versions count is reached.

Manually Updating a vDisk Image

This procedure requires that:
  • A Maintenance device has been assigned to the vDisk being updated.
  • No version of this vDisk is currently under maintenance.
Note: Updating images for devices that use a personal vDisk, must be done on a virtual machine that does not have a personal vDisk attached. Otherwise, updates are saved to the personal vDisk image rather than the virtual machine image.
To create a new version:
  1. In the Console, right-click on a vDisk to version within a device collection or vDisk pool, then select Versions... from the context menu. The vDisk Versions dialog appears.
Note: Verify that the vDisk is currently not in Private Image mode.
  1. Click New. The new version displays in the dialog with Access set to Maintenance and the update Type method set to Manual.
  2. Boot the vDisk from a Maintenance device, install or remove applications, add patches, and complete any other necessary updates, then shutdown the Maintenance device. Optionally, test that changes were made successfully.
Note: If booting a Test or Maintenance device, a boot menu displays that allows the user to select from which vDisk, or version of that vDisk, to boot from unless the device is a PvD Test device.
  1. Right-click on the vDisk, then select the Promote... menu option from the context menu that appears (for more details on promoting versions refer to Promoting Updated Versions).
  2. Select to promote this maintenance version into test or directly into production. If Production is selected, set the availability of this version in production to be either immediate or scheduled.
  3. Click OK to promote this version and end maintenance.
Automating vDisk Updates
After the site is configured to use vDisk Update Management, managed vDisks can be updated using the following methods:
  • Scheduled – the Image Update Service automatically updates a vDisk, on a scheduled basis as defined in the Update Task. For more details, refer to Using the Update Task Wizard or Update Task Properties.
  • User Envoked – an administrator selects a managed vDisk to be updated from the Consoles Run update now menu option (requires that the administrator also manually start, then stop the Update Device after the update is complete).
The following illustrates the basic update process for both scheduled or user envoked update methods:


  1. The vDisk update process starts either automatically (scheduled), or when an administrator right-clicks on a managed vDisk, then selects the Run update now menu option.
  2. Provisioning Services creates a new version (VHD) and places that version in Maintenance mode (read/write).
  3. The virtual machine boots the assigned vDisk. If this is a:
    • Scheduled update – vDisk Update Management performs the boot automatically.
    • User envoked update – the administrator envokes the update.
  4. All updates are automatically made and captured in the new version of the VHD file.
  5. After updating the vDisk, the virtual machine is shut down automatically.
  6. The vDisk is promoted from Maintenance to either Test or Production. The availability of the new vDisk version depends on the Access mode that was selected when the Update Task Wizard was run, or the mode that is currently selected on the Update Task Properties' Finish tab (Maintenance, Test, or Production). After this version is made available in production, target devices will be able to access it the next time they boot that vDisk.