627: Simplify lifecycle management of desktop images with latest version of provisioning services

Transcription

1 627: Simplify lifecycle management of desktop images with latest version of provisioning services Hands-on lab exercise guide Exercise 1: Integrated vdisk Versioning Page 1

2 Table of Contents Overview... 3 Exercise 1: Integrated vdisk Versioning... 5 Exercise 2: Merging vdisks Exercise 3: vdisk Replication Exercise 1: Integrated vdisk Versioning Page 2

3 Overview Hands-on Training Module This training module has the following details: Objective Provide hands-on experience with image management features of Provisioning Services Provide hands-on experience with the capabilities for vdisks Audience Citrix Partners; Provisioning Services, XenDesktop and XenApp administrators, engineers and architects. Lab Environment Details This section is used to describe the lab environment and the virtual machines that are used. VM Name IP Address Description AD.training.lab Windows Server 2008 R2. Domain controller for training.lab, DNS, and DHCP services SQLServer Windows Server 2008 R2. SQL Server 2008 R2 hosting the Provisioning Services database PVS Windows Server 2008 R2. Provisioning Services (Excalibur) PVS Windows Server 2008 R2. Provisioning Services (Excalibur) Win7Target DHCP Windows 7 Target Device Win7-P001 DHCP Windows 7 diskless virtual machine Win7-P002 DHCP Windows 7 diskless virtual machine Win7-P003 DHCP Windows 7 diskless virtual machine NOTE: This is a shared lab environment image and not all virtual machines will be used. NOTE: If prompted with a dialog to restart on any virtual machine, always select Restart Later. Required Lab Credentials Below you can find the login credentials required to connect to the workshop system and complete the lab exercises. Domain/Machine Username Password Description Training.lab Administrator Citrix123 Domain Administrator Training.lab User1 Citrix123 Domain User Exercise 1: Integrated vdisk Versioning Page 3

4 Scenario The Provisioning Services infrastructure is based on software-streaming technology. This technology allows computers to be provisioned and re-provisioned in real-time from a single shared-disk image. In doing so, administrators can completely eliminate the need to manage and patch individual systems. Instead, all image management is done on the master image called a vdisk. The local hard-disk drive of each system may be used for runtime data caching or, in some scenarios, removed from the system entirely, which reduces power usage, system failure rates, and security risks. In this lab, you will learn about the various image management features provided by provisioning services. You will learn about vdisk versioning, merging vdisks, and vdisk replication. Exercise 1: Integrated vdisk Versioning Page 4

5 Exercise 1: Integrated vdisk Versioning Overview In this exercise you will promote target devices to various types and verify the behavior using different vdisk versions associated with them. Step-by-step guidance Estimated time to complete this lab: 25 minutes. Step Action 1. From within XenCenter, make sure AD and SQLServer virtual machines are powered on. Then power on PVS1 virtual machine. Note: DO NOT power on PVS2. 2. Log on to PVS1 as training\administrator with password Citrix Launch the Provisioning Services Console (icon located on the Desktop). 4. Click Connect to connect to the farm. NOTE: If having issues connecting to the PVS farm, verify the Citrix PVS Stream Service and Citrix PVS SOAP Service services are started. Start the Stream service before the SOAP service. Exercise 1: Integrated vdisk Versioning Page 5

6 5. In the Console tree pane, expand PVS, then Sites then expand LA, and click the Servers node. 6. On the right panel, ensure that PVS1 is available. Note: You might need to press F5 to refresh the view. 7. Expand the Device Collection node and click Desktops. Verify that only one desktop has a vdisk assigned. Note: The target devices were pre-added to the PVS Console and correspondent machine accounts created on Active Directory to save time for this lab. 8. Click vdisk Pool node and select the Win7 vdisk on the right panel. 9. Drag and drop the Win7 vdisk from vdisk Pool to Desktops under Device Collections. 10. Select Yes to Replace vdisk assignments. Exercise 1: Integrated vdisk Versioning Page 6

7 11. From XenCenter right-click Win7Target and select Start. 12. Login to Win7Target as training\administrator with password Citrix123. From the system tray, right-click the flashing Virtual Disk icon and select Virtual Disk Status to verify the Virtual Disk Information: Virtual Disk: Win7.vhd Mode: vdisk: Read Only, Cache Type: local hard drive 13. Close the Virtual Disk Status dialog. 14. Switch back to PVS1. In the console tree select the vdisk Pool and then right-click the Win7 vdisk and select Versions Exercise 1: Integrated vdisk Versioning Page 7

8 15. Click the New button on the top right and verify that a new version with Access type of Maintenance is created. Click Done. 16. In the console tree, expand the Device Collections folder then click the Desktops node. The target devices display in the details pane. Right-click the Win7-P001 target device then select Properties. Change the Type under the general tab to Maintenance. Click OK. 17. In XenCenter, right-click Win7-P001 and select Start. Exercise 1: Integrated vdisk Versioning Page 8

9 18. Verify a Boot Menu shows up with a maintenance option. Choose option 1) Win7.1 [maint]. You might need to hit enter to see the Boot Menu. Note: A boot menu always shows up if the vdisk has a maintenance version. If the menu is not shown and the virtual machine does not boot, try pressing Enter as the menu portion of the window may not be immediately visible. 19. Login to Win7-P001 as training\administrator with password Citrix123. From the system tray, right-click the flashing Virtual Disk icon and select Virtual Disk Status to verify the Virtual Disk Information: Virtual Disk: Win7.1.avhd Mode: vdisk: Read/Write 20. Close the Virtual Disk Status dialog. 21. Open Windows Explorer and navigate to \\AD\software. Run the Firefox Setup executable. 22. Click Next on the Welcome Screen. 23. Leave Standard selected and click Next. 24. Uncheck Use Firefox as my default web browser and click Install. 25. Uncheck Launch Firefox now and click Finish. 26. Verify a Firefox icon is placed on the Desktop. 27. From XenCenter, Shutdown target device Win7-P001. Exercise 1: Integrated vdisk Versioning Page 9

10 28. Switch back to PVS1. In the console tree select the vdisk Pool and then right-click the Win7 vdisk, select Versions select the Maintenance version and click Promote Set version access to Test and click OK. 29. Select the Test version you just promoted and click Properties. Type Version with Firefox for the description and click OK. Exercise 1: Integrated vdisk Versioning Page 10

11 30. Still under vdisk Versions, select the Test version and click New. Verify a Maintenance version was created. Click Done. 31. Expand the Device Collections node then click the Desktops node. The target devices displays in the details pane. Right-click the Win7-P002 target device then select Properties. 32. Change the Type under the general tab to Test. Click OK. Exercise 1: Integrated vdisk Versioning Page 11

12 33. From XenCenter, right-click Win7-P002 and select Start. Choose option 1) Win7.1 [test] from the Boot Menu. 34. Login as training\administrator with password Citrix123 and verify under Virtual Disk Status in the system tray the name for the Virtual Disk: Win7.1.avhd. NOTE: The Firefox shortcut should be visible on the Desktop. 35. In XenCenter, right-click Win7-P001 and select Start. 36. Verify the following versions show on the Boot Menu. Select version 1) Win 7.2 [maint]. Exercise 1: Integrated vdisk Versioning Page 12

13 37. Login to Win7-P001 as training\administrator with password Citrix123 and verify the virtual disk changed to Win7.2.avhd displaying Mode Read/Write. 38. Switch to PVS1 and open Windows Explorer to verify the vdisks created under vdisks(e:): vdisk Version Target Device Type Win7.1.avhd Win7-P002 Test Win7.2.avhd Win7-P001 Maintenance Win7.vhd Win7Target Base (Production) 39. From the PVS Console tree select the vdisk Pool and then right-click the Win7 vdisk and select Show Usage Exercise 1: Integrated vdisk Versioning Page 13

14 40. Verify 1 target device is running the vdisk Access Production, 1 target device is running the vdisk Access Test and 1 target device vdisk Access Maintenance. Click Close. 41. In the console tree select the vdisk Pool in the tree and right-click the Win7 vdisk then select Versions Select the Test version and click Promote Leave Availability as Immediate then click OK. 42. An error message will show up since Win7-P002 is using the Test version. Click OK. 43. Shutdown the Win7-P002 target device from XenCenter. Exercise 1: Integrated vdisk Versioning Page 14

15 44. Switch to PVS1 and within the PVS Console, click Refresh on the bottom right. The Test version will show 0 Devices connected. 45. Select the Test version and click Promote again. Leave Availability as Immediate, click OK and click Done. Exercise 1: Integrated vdisk Versioning Page 15

16 46. Expand the Device Collections node then click the Desktops node. The target devices display in the details pane. Verify the Type for Win7-P003 target device is set to Production. 47. From XenCenter, right-click Win7-P003 and select Start. 48. Login to Win7-P003 as training\administrator with password Citrix123 and verify on the Virtual Disk Status that you are using Virtual Disk: Win7.1.avhd. 49. From XenCenter, right-click Win7-P001 and select Shut Down. Exercise 1: Integrated vdisk Versioning Page 16

17 50. Switch back to PVS1. In the console tree select the vdisk Pool and then right-click the Win7 vdisk, select Versions Select the Maintenance version and click Promote. Set version access to: Test and click OK. 51. Select the newly created Test version and click New. A vdisk with Access Maintenance will show as Version 3. Click Done. 52. From XenCenter, right-click Win7-P002 and select Start. Choose option 1) Win7.2 [test] from the Boot Menu. Exercise 1: Integrated vdisk Versioning Page 17

18 53. From XenCenter, right-click Win7-P001 and select Start. Choose option 1) Win7.3 [maint] from the Boot Menu. Note If the VM stops at the screen below, press enter. Note: This is a pre-release build and this problem will be fixed by final release. 54. Switch to PVS1 and in the console tree select the vdisk Pool. Right-click the Win7 vdisk and, select Show Usage 55. Verify 2 target devices are running the vdisk Access Production, 1 target device is running the vdisk Access Test and 1 target device vdisk Access Maintenance. Click Close. NOTE: If the 4 target devices are not displayed click Refresh. 56. From XenCenter, right-click Win7-P001 and select Shutdown. END OF EXERCISE Exercise 1: Integrated vdisk Versioning Page 18

19 Summary Key Takeaways The key takeaways for this exercise are: vdisk Versioning : o Image updating & rollback without ever having to copy a VHD. o Image lifecycle management of create/update, test and production. o Ability to stream a disk in multiple modes simultaneously. 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. If Access displays as blank, this version is considered released to production but is not the version currently selected from which devices should boot. Maintenance is a new read/write difference disk version that is only available to the first Maintenance device that selects to boot from it to make updates. Exercise 1: Integrated vdisk Versioning Page 19

20 Exercise 2: Merging vdisks Overview In this exercise you will merge VHD differencing disk files to a partial merge combining a chain of VHD differencing disks and also to a new base image. Step-by-step guidance Estimated time to complete this lab: 25 minutes. Step Action 1. Switch back to PVS1. 2. In the console tree select the vdisk Pool and then right-click the Win7 vdisk, select Versions Verify the Merge option on the right is grayed out. NOTE: A merge can only occur when no Maintenance version exists for this vdisk or when the vdisk is in Private Image mode. Exercise 2: Merging vdisks Page 20

21 3. Promote the Maintenance version to Production with Immediate availability. You will receive a warning about existing test versions. Click OK. 4. Click Merge. Select Merged Updates All updates from last base. Set merge version access to: Test. Click OK. Exercise 2: Merging vdisks Page 21

22 5. Click OK. 6. A new version will show the Access as Merging 100%. Click Refresh. Exercise 2: Merging vdisks Page 22

23 7. Version 4 now will show Type Merged Updates and Access Test. Click Done. 8. From XenCenter, shutdown target devices: Win7-P002 and Win7Target. 9. Switch back to PVS1. In the PVS Console tree select the vdisk Pool and then right-click the Win7 vdisk, select Versions Select version 4 and click Promote. Leave Availability as Immediate then click OK. Exercise 2: Merging vdisks Page 23

24 10. Verify only versions 3 and 2 became obsolete since Win7-P003 is still using version Start the Win7Target virtual machine. 12. Switch back to PVS1. Click Refresh and for the Boot production devices from version: select 0. Exercise 2: Merging vdisks Page 24

25 13. Verify you have Version 0 as the production listed with Access Override. Click Done. 14. Expand the Device Collections node then click the Desktops node. The target devices displays in the details pane. Right-click the Win7-P002 target device and select Properties. Change the Type from Test to Production. Click OK. 15. Start target device Win7-P002. Exercise 2: Merging vdisks Page 25

26 16. Switch back to PVS1. In the PVS Console tree select the vdisk Pool, right-click the Win7 vdisk, and select Show Usage 17. Verify Win7-P002 is using version 0 (Access Override), since it was the version set to be the new production on the previous step 12. Click Close. Note: You might need to click Refresh. Exercise 2: Merging vdisks Page 26

27 18. Right-click Win7 vdisk, and select Versions Select version 4 and click New. A new version 5 will show as Maintenance. Select Version 2 and click Delete Click Yes. 19. Verify that both versions 2 and 3 were deleted. Exercise 2: Merging vdisks Page 27

28 20. Promote version 5 to Test and click OK. 21. Click Merge and select Merged Base - Last base + all updates from that base. Set merge version access to: Test. Click OK. Exercise 2: Merging vdisks Page 28

29 22. Click OK on the message and then click Refresh. Wait a few minutes for the merge to complete before clicking Refresh again. Verify target devices are still using Versions 0, 1 and 4 while the merge is being performed. Note: It might take a few minutes for the Merge to complete. 23. When the merge is complete and the version 6 is showing Access Test from XenCenter, shutdown the Win7-P002 target device. Exercise 2: Merging vdisks Page 29

30 24. Switch back to PVS1. In the PVS Console click Refresh on the Win7 vdisk Versions screen. Verify you still cannot delete Version 0 since it s the Production version. 25. Change the Boot production devices from version to Newest released. Select version 6 and click Promote. Set Availability to Immediate and click OK. Click OK for the warning for pending versions. Exercise 2: Merging vdisks Page 30

31 Note Version 6 should now show as Production. 26. From XenCenter, shutdown Win7Target and Win7-P003 target devices since they are using versions 4 and 1. Exercise 2: Merging vdisks Page 31

32 27. Switch back to PVS1 and click Refresh. Now you will be able to delete all previous versions prior to 6. Delete versions 5, 4, 1 and 0. Click Done. Tip: If you delete version 0 first, it will delete all the obsolete ones above. 28. Open Windows Explorer and navigate to vdisks (E:). Verify you only have version 6 for the Win7 vdisk. Exercise 2: Merging vdisks Page 32

33 29. Switch back to PVS1 and open the PVS console. Right-click the PVS node and select Properties. 30. Navigate to the vdisk Version tab and change the Alert if number of versions from base image exceeds to 3. Click OK. 31. Select the vdisk Pool and right-click the Win7 vdisk, and select Versions. Exercise 2: Merging vdisks Page 33

34 32. Click New and select the newly created version 7 and then click Promote Select Production and leave the Availability to Immediate, then click OK. 33. Select the Version 7 and click New. Click Promote on the newly created version 8 to Production with Availability as Immediate. Click OK. Exercise 2: Merging vdisks Page 34

35 34. Click New again and then Promote the newly created version 9 to Production with Availability as Immediate. Click OK. 35. Click New again and then Promote the newly created version 10 to Production with Availability as Immediate. Notice when you click OK a message will show up about the number of versions from last base exceeding your Farm Properties specified maximum (Step 30). Select No. Note: We won t be merging the versions on this step to save time. Exercise 2: Merging vdisks Page 35

36 36. Delete the new versions created: 10, 9, 8 and 7. You should only have version 6 to start the next exercise. Click Done. END OF EXERCISE Summary Key Takeaways The key takeaways for this exercise are: A full merge to a new base image combines a chain of differencing disks and base image disks into a new single base disk. This new disk is the next version in the chain, which is given the file extension of.vhd. This method allows for the fastest disk access to the base image and is recommended when performance is more important than disk space (a new base disk is created for every merge performed). A partial merge combines a chain of VHD differencing disks up to, but not including, the base disk into a new differencing disk. The new differencing disk has the same parent base disk image and is given the extension.avhd. A merge can only occur when no Maintenance version exists for this vdisk or when the vdisk is in Private Image Mode. A merge starts from the top of the chain down to a base disk. A starting disk cannot be specified for the merge. A consolidated differencing disk merge is recommended when disk storage is limited or when the bandwidth between remote locations is limited, which makes copying large images impractical. Exercise 2: Merging vdisks Page 36

37 Exercise 3: vdisk Replication Overview In this exercise you will verify the replication status for a particular version of a vdisk and for all versions of a vdisk. Step-by-step guidance Estimated time to complete this lab: 15 minutes. Step Action 1. Still on PVS1, expand the PVS Console tree. Select the vdisk Pool in the tree and then right-click the Win7 vdisk, select Versions. Select the top version and click New. A Maintenance version 7 will be created. 2. Promote the version 7 from maintenance to Test. Exercise 3: vdisk Replication Page 37

38 3. Click New and a version 8 will be created. Leave it as Maintenance. 4. Select Version 7 and click Promote. Select Scheduled, leave the default date, and click OK. Exercise 3: vdisk Replication Page 38

39 5. Click Version 8 and select Promote Leave it as Test and click OK. 6. Click New and a Version 9 will show as Maintenance. Click Done. Exercise 3: vdisk Replication Page 39

40 7. Under the Desktops node, change the Properties of the Win7-P002 target device to Type Test and click OK. 8. From XenCenter, start Win7-P002 and choose option 1) Win7.8 [test] 9. Start Win7-P001 and choose option 1) Win7.9 [maint] 10. Start Win7-P003 and Win7Target. 11. From XenCenter, start PVS2 virtual machine. Exercise 3: vdisk Replication Page 40

41 12. Switch back to PVS1 and in the PVS Console tree select the vdisk Pool, and then rightclick Win7 vdisk, and select Versions. Verify the 4 target devices are connected. Note: You might need to click Refresh to see all devices connected. 13. Click the Replication button to confirm that only PVS1 contains this vdisk at present. Click Done and click Done to close the window. Exercise 3: vdisk Replication Page 41

42 14. Open Windows Explorer on PVS1, navigate vdisks (E:) and verify the files for Win7 vdisk: 15. Connect to \\PVS2\vDisks from Windows Explorer. 16. Copy the current versions for Win7 vdisk from the local PVS1\vDisks to \\PVS2\vDisks. The.lok files do not need to be copied over. Note: It should take around 3 minutes to finish the copy. Exercise 3: vdisk Replication Page 42

43 17. Once the copy process completed, switch back to the PVS Console. Right-click Win7 vdisk and select Replication Status Verify all the versions are up-to-date on both servers. Click Done and Done. Note: If not all the versions show updated on both servers, copy the version that was not updated to PVS2 again and click Refresh on the main vdisk Version window. 18. Click the Servers node, then on the right panel right-click PVS and select Rebalance Devices Note: You might need to click Refresh to see both servers online. Exercise 3: vdisk Replication Page 43

44 19. Select the server that has more devices connected PVS or PVS2 and click the Rebalance Devices button. Status will change to Success. Click Close. 20. Go to the Action menu and select Refresh (or press F5). The target devices should be equally balanced across both servers. Note: It might take a few minutes for the devices to move over to the other server. 21. Please complete the class survey: END OF EXERCISE Key Takeaways The key takeaways for this exercise are: The vdisk Version Replication Status dialog displays the replication status availability for each server that can provide this version of the vdisk. If a version is in Maintenance (hammer icon), Test (magnifying glass), or Pending (hour glass) states, that state displays in the first row. A green checkmark indicates that the server has access to this version. An orange warning indicates that a server currently does not have access to one or more versions of this vdisk. The version that is missing, or has an issue, has an orange warning under that version column. Exercise 3: vdisk Replication Page 44

45 Revision History Revision Change Description Updated By Date 1.0 Original Version Elisabeth Teixeira May 2013 About Citrix Citrix Systems, Inc. designs, develops and markets technology solutions that enable information technology (IT) services. The Enterprise division and the Online Services division constitute its two segments. Its revenues are derived from sales of Enterprise division products, which include its Desktop Solutions, Datacenter and Cloud Solutions, Cloud-based Data Solutions and related technical services and from its Online Services division's Web collaboration, remote access and support services. It markets and licenses its products directly to enterprise customers, over the Web, and through systems integrators (Sis) in addition to indirectly through value-added resellers (VARs), value-added distributors (VADs) and original equipment manufacturers (OEMs). In July 2012, the Company acquired Bytemobile, provider of data and video optimization solutions for mobile network operators Citrix Systems, Inc. All rights reserved. Page 45