This article contains information about how to use the Provisioning Services Automatic vDisk Update process.

Background

The vDisks assigned to the clients during the Automatic vDisk Update process are new versions of the vDisks currently assigned to the clients; allowing for the automatic distribution of the updated vDisk images to one or more clients. The vDisks can be marked for update at a specific time; allowing the clients to receive the new vDisk image upon boot after the specified time.

---

Instructions

Complete the following steps to automatically update a vDisk:

Important: The following steps must be used for PVS version earlier than 6.0. For later versions of PVS (6.x and above), refer to eDocs - Updating vDisks on Physical Devices.

1. Open Farm/Servers.

2. Right-click on the Provisioning Services (PVS) server.

3. Select Properties.

4. In the Option tab, select Check for new versions of a vDisk or Check for incremental updates for a vDisk. Depending on what is required to be updated, select both or either one.

   

5. Copy the original XP01 vDisk and rename it to different name XP01update. Copy both the .vhd and .pvp files.

   

6. Add the copy of existing vDisk to the store.

   

7. Change the XP01update vDisk to Private Image access mode.

8. Assign the XP01update vDisk to a separate target device and start the target device to apply the changes.

9. After updating the XP01Update vDisk with the required software or file changes, shut down the target device.

10. Change the XP01update vDisk properties to match the original XP01 vDisk.

11. Change the access mode to match the XP01 vDisk (Standard Image).

    

    Note: There is an option to schedule updates on a particular date.

12. Ensure that the Class and Type is the same on both XP01 and XP01update vDisk.

    

13. Increment the version number on the XP01update vDisk. Particularly, the Build number.

    The following screen shot shows the version number for the XP01 vDisk:

    

    The following screen shot shows the version number for the XP01update vDisk:

    

14. Enable automatic updates in the vDisk File Properties of both the XP01 and XP01update vDisks.

    

15. The Target Class has to match the vDisk Class on both the XP01 and XP01update vDisks.

    

    Note: You can use Copy Target Device Properties to copy the Class to multiple targets.

    

16. Verify the vDisk name assigned to the Target before you start the update.

    

17. Start Check for Updates (select the required update).

    

18. Validate the target device vDisk was updated.

    

The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the sample code may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the sample code fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the sample code. In no event should the code be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SAMPLE CODE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the code belongs to Citrix, any distribution of the sample code should include only your own standard copyright attribution, and not that of Citrix. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the sample code.

This article explains how to configure automatic virtual disk updates.

For additional information on Provisioning Services 7.0, refer to Automating vDisk Updates.

In Provisioning Services 5.6, DEBUG or TRACE level logging is configured in the Server properties and the Stream log processes information on the Automating vDisk Update.

Log Location:  C:\Documents and Settings\All Users\Application Data\Citrix\Provisioning Services\Log

Example log: The following entries indicate the four targets that were updated from vDisk XP01 to XP01update:

2010-12-22 13:29:46,673      [0x00000a24]      TRACE      CSSServerCache::DispatchAutoUpdateRequest  Recv: LS_AUTO_UPDATE_REQUEST from device at IP:AC102865
2010-12-22 13:29:46,673      [0x00000a24]      DEBUG      CSSServerCache::DispatchAutoUpdateRequest  autoupdate request function = 1
2010-12-22 13:29:46,673      [0x00000a24]      TRACE      CSSAutoUpdate::TriggerImmediateAutoUpdate  AutoUpdate:  TriggerImmediateAutoUpdate called
2010-12-22 13:29:46,673      [0x00000a24]      TRACE      CSSServerCache::DispatchAutoUpdateRequest  Send: LS_AUTO_UPDATE_REPLY
2010-12-22 13:29:46,673      [0x0000078c]      DEBUG      In DoServerGetAllDiskPaths, for serverId = xxxxxxxx-eeee-aaaa-wwww-zzzzzzzzzzzzzz
2010-12-22 13:29:46,673      [0x0000078c]      TRACE      handing out connection = 0
2010-12-22 13:29:46,673      [0x0000078c]      DEBUG      In CServerDbAccess::DoGetAllDiskPaths
2010-12-22 13:29:46,689      [0x0000078c]      DEBUG      harvested storePathPair, storeId = 1dedd544-a53b-4c21-a057-dcc2b73d6600, path = <F:\IMGStore>
2010-12-22 13:29:46,689      [0x0000078c]      INFO       CSSAutoUpdate::PerformImmediateAutoUpdate  Immediate Auto Update process started.
2010-12-22 13:29:46,689      [0x0000078c]      DEBUG      In DoServerGetAllDiskLocators, for serverId = xxxxxxxx-eeee-aaaa-wwww-zzzzzzzzzzzzzz
2010-12-22 13:29:46,689      [0x0000078c]      TRACE      handing out connection = 0
2010-12-22 13:29:46,689      [0x0000078c]      DEBUG      In CServerDbAccess::DoGetAllDiskLocators
2010-12-22 13:29:46,705      [0x0000078c]      DEBUG      harvested DiskLocatorListItem, storeId = 1dedd544-a53b-4c21-a057-dcc2b73d6600, diskLocatorName = <XP01update>, diskLocatorId = 0ab9a18b-5c87-4182-b782-59ce5a1d67b6
2010-12-22 13:29:46,705      [0x0000078c]      DEBUG      harvested DiskLocatorListItem, storeId = 1dedd544-a53b-4c21-a057-dcc2b73d6600, diskLocatorName = <XP01>, diskLocatorId = 3065b3bc-b496-4f63-b887-d956286b274e
2010-12-22 13:29:46,705      [0x0000078c]      DEBUG      In DoDeviceDiskLocatorUpdateDiskLocatorId
2010-12-22 13:29:46,705      [0x0000078c]      TRACE      handing out connection = 0
2010-12-22 13:29:46,736      [0x0000078c]      DEBUG      CSSProtocolModule::DoTraceEvent  Auto Update: scheduled update of 4 devices from disk 'XP01' to disk 'XP01update'.
2010-12-22 13:29:46,736      [0x0000078c]      DEBUG      In DoUserGroupDiskLocatorUpdateDiskLocatorId
2010-12-22 13:29:46,736      [0x0000078c]      TRACE      handing out connection = 0
2010-12-22 13:29:46,767      [0x0000078c]      INFO       CSSAutoUpdate::PerformImmediateAutoUpdate Immediate Auto Update process finished.