Product documentation
Citrix Provisioning
Current Release 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR 7.15
View PDF

Automating vDisk updates

December 28, 2018
Contributed by: 
C

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, causes errors to occur.

In the Console, the vDisk Update Management feature is used to configure the automation of vDisk updates using virtual machines (VMs). Automated vDisk updates can occur on a scheduled basis, or at any time that the administrator invokes the update directly from the Console. This feature supports updates detected and delivered from WSUS and SCCM Electronic Software Delivery (ESD) servers.

When the Site node is expanded in the Console tree, the vDisk Update Management feature appears. When expanded, the vDisk Update Management feature includes the following managed components:

  • Hosts
  • vDisks
  • Tasks

To configure a site for vDisk Update Management requires completing the following high-level tasks:

  1. Designate a Provisioning Server within the site to process updates. Refer to Enabling automatic vDisk updates.
  2. Configuring a Virtual Host Pool for Automated vDisk updates. Refer to Using the virtual host connection Wizard. Note: Supported hypervisor types include; Citrix XenServer, Microsoft SCVMM/Hyper-V, and VMWare vSphere/ESX.
  3. Create and configure an ESD VM that to update the vDisk. Refer to Creating and configuring ESD update VMs.
  4. Configuring vDisks for Automated updates.
  5. Creating and managing update tasks. Refer to Create and manage tasks. Note: The user that configures vDisk Update Management tasks must have permissions to create, modify, and delete Active Directory accounts.
  6. Run the update task by right-clicking on the task object in the Console, and then selecting the Run update now menu option. The Update VM boots, install updates, and reboot as necessary. After the update task successfully completes, the virtual machine is automatically shut down. The update status can be checked from the Console tree under vDisk **Update Management\ > vDisks>(**vDisk name)> Completed Update Status. The status can also be checked using the event viewer or in WSUS.

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 Create and manage tasks or Update task properties.
  • User Envoked – select a managed vDisk from the Consoles Run update now menu option. This option requires that the administrator manually start, then stop the Update Device after the update is complete.

The following illustrates the basic update process for both scheduled or user invoked update methods:

Update process

  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 version (VHDX) and places that version in Maintenance mode (read/write).
  3. The virtual machine boots the assigned vDisk:
    • Scheduled update – vDisk Update Management performs the boot automatically.
    • User invoked update – the administrator invokes the update.
  4. All updates are automatically made and captured in the new version of the VHDX file.
  5. After you update 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.
Automating vDisk updates
December 28, 2018
Contributed by: 
C
December 28, 2018
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.