SPO-009: Deploying and Configuring Personal vDisk

stemswedishAI and Robotics

Oct 15, 2013 (3 years and 10 months ago)

77 views


Page
1






SPO
-
009:
Deploying and Configuring
Personal vDisk


Self
-
paced

lab exercise guide













Page
2


Table of Content
s

Table of
Contents

................................
................................
................................
................................
..............

2

Overview
................................
................................
................................
................................
.............................

3

Exercise 1: Deploying PvD

................................
................................
................................
..............................

4

Exercise 2 : Updating PvD
-
enabled delivery groups
................................
................................
..................

23

Exercise 3 : PvD reset

................................
................................
................................
................................
.....

27





Page
3

Overview

Objective



Learn how to configure and deploy Personal vDisk (PvD) catalogs in XenDesktop, including
updating and maintenance of PvD catalogs after deployment.

Prerequisites




The student is expected to have a basic understanding of XenDesktop concepts (Desktop
Studio, Catalogs, Delivery Groups, etc). The student is not expected to have an understanding
of PvD.



The student is expected to have a working understanding of virtual m
achines, and how to use
hypervisor consoles (XenCenter) to log into and interact with VMs managed by XenServer.

Audience



Citrix
Partners and Customers.


Scenario

In this lab you will learn how to configure Personal vDisk (PvD) desktop delivery groups. Pv
D
desktops provide persistent personalization across image updates for XenDesktop deployments. This
means your end users will be able to fully experience the ability to customize their Windows desktops
while you will still maintain the ability to manage th
ose desktops centrally. In most deployments, PvD is
used to provide the capability for end users to install their own applications (UIA, o
r user installed
applications).

PvD provides personalization capabilities by storing the user changes in the
PvD Disk
. Each VM in the
PvD
-
enabled catalog contains a PvD disk, and that disk accumulates changes over time as the end users
install applications, make changes, or otherwise alter their environment. These changes are tracked and
reincorporated into the VM each t
ime the base VM is updated.

This lab will show you how to provision PvD desktops and how to update them. It will also detail the
procedure to reset user PvDs if they become corrupt.


Lab Environment Details


V
M
N
ame

I
P

A
d
dr
e
s
s

Des
c
r
ip
t
ion

AD

192.168.10.
1
1

W
indo
w
s

S
e
rver 2008

R
2.

Domain controller
f
or

t
ra
inin
g
.l
a
b,
DNS.

Win7 Client

DHCP (varies)

W
indo
w
s

7. Used for Base VM configuration
.

PvD Pool

Machine

DHCP (varies)

W
indo
w
s

7.
PvD

user pool VM machine. Used by end users when
logging into their desktops for persistent user personalization

PVDLAB

192.168.10.

W
indo
w
s

Server 2008 R2. XenDesktop Excalibur Desktop Delivery
Controller.


Page
4

Exercise
1
:
Deploying PvD

Overview

In this exercise
you will
deploy a PvD desktop delivery group and experience the personalization
capabilities of PvD as an end user by installing an application into the managed VM.

PvD base images contain
inventories

that tell the PvD software what is ins
talled there, so that end user
changes can
be properly reintegrated into the environment upon each administrator
-
initiated image update.

Step
-
by
-
step guidance

Estimated time to complete this lab:
20

minutes
.

Step

Action

1.


Using XenCenter, log into the “AD”

癩牴畡氠浡捨cn攠⡁捴楶攠䑩牥捴潲礩⁵c楮i⁴桥⁦潬汯睩湧n
捲敤c湴楡nsW



ID: training
\
Administrator



PW: Password1!


You may use either the Default Desktop display or the Remote Desktop display, but the
Remote Desktop selection offers faster performance.


Page
5

Step

Action

2.


Add an active directory user that will be used to log into the PvD pool later, as illustrated in
the images below:



Page
6

Step

Action

3.


Using XenCenter, log into the
“Win7Client” virtual machine (Base VM image) using the
following credentials:



ID: training
\
Administrator



PW: Password1!


You may use either the Default Desktop display or the Remote Desktop display, but the
Remote Desktop selection offers faster perf
ormance.

4.


Perform a PvD Inventory operation by selecting “Update Personal vDisk” from the Start
menu. PvD inventory must be performed immediately prior to desktop catalog creation,
which is what you will shortly be performing.



Note:


In a production deplo
yment, you would perform any base VM application
installations as well as any deployment
-
wide configuration in this VM before
performing the inventory. In this lab, we will accept the base VM “as
-
is”.



Page
7

Step

Action

5.


The PvD

update will take approximately 5
-
10 minutes and will shutdown the machine
automatically on completion:


6.


Using XenCenter, log into the “PvDLab” virtual machine (XenDesktop DDC) using the
following credentials:



ID: training
\
Administrator



PW: Passwo
rd1!


You may use either the Default Desktop display or the Remote Desktop display, but the
Remote Desktop selection offers faster performance.

7.


Create a PvD
-
enabled catalog by selecting “Create Catalog” on the main DDC screen


Page
8

Step

Action

8.


Proceed through the Create

Catalog wizard as shown below, selecting default (“Next”)
values unless indicated otherwise.


In the “User Experience” panel, ensure that the “Static” assignment option is selected as
well as “…store changes on a separate Personal vDisk” option is selecte
d:




Page
9

Step

Action

9.


In the “Master Image” panel, select the Win7Client VM. This VM will contain the snapshot
(including PvD Inventory) used to create the desktop catalog:




Page
10

Step

Action

10.


In the “Add and configure Virtual Machines” screen, accept the defaults.



Select only one VM
for the pool (Number of virtual machines needed). Adding
more than one machine will just increase the time to create the pool, and you will
only need one machine for this lab. In production environments, you would of
course select the appropriate number of

machines.



In production environments, you can select a larger or smaller PvD size (the default
is 10GB)



In production environments, you can select a different PvD drive letter (the default
is P:, which you will see shortly)




Page
11

Step

Action

11.


In the Computer Accounts s
creen, enter a machine account naming scheme as shown
below, to ensure unique machine names are created:




Page
12

Step

Action

12.


In the Summary screen, enter a suitable Machine Catalog name. A good suggestion would
be “PvDLab”, for this lab:



13.


The desktop catalog will be
created. This operation may take 5
-
10 minutes:




Note

: Warnings generated during the catalog creation relating to the use of http vs.
https may be safely ignored for this lab.


Page
13

Step

Action

14.


Verify the PvD pool is activated and the machine registered by double
-
clickin
g the PvD
catalog from the Catalog screen in Desktop Studio. Verify the machine is in state
“Registered”.



Note

: It may take a few minutes for the machine to register once it is created.




Page
14

Step

Action

15.


Verify the PvD
-
enabled VM contains a 10GB PvD

disk. You can do this by accessing the
“Storage” Tab of the “PvdLab001” VM using XenCenter:




Note

: In a production deployment, you should spot
-
check a few VMs for proper
configuration. It is not necessary to inspect all VMs.




Page
15

Step

Action

16.


You will now create a delivery group for the catalog you just created, and assign the user
you created earlier to allow users to log into the PvD deployment.


In Desktop Studio, Select “Create delivery group” from the right
-
click popup menu under
“delivery

groups”:




Page
16

Step

Action

17.


Select the “PvDLab” catalog just created, and add “1” machine:




Page
17

Step

Action

18.


Select “Add Users”, then add “training
\
Domain Users”:




Page
18

Step

Action

19.


Finally, assign a suitable name (example : “PvDLab”) to this new delivery group:




Page
19

Step

Action

20.


Assign the user previously
created to the machine/delivery group. In the delivery group list
in Desktop Studio, right click the PvDLab001 machine and select “Assign User”:





Note:
In production environments, XenDesktop will assign users on first login to
unused machines. For the
purposes of this lab, we are assigning the user manually.
You may omit this step (and the next) if you would prefer to experience the
automatic user assignment facility of XenDesktop instead. The process described
here can be used in production deployments

to assign/reassign users to specific
VMs as needed.



Page
20

Step

Action

21.


Add (via the “Add” button)

the “pvduser” account previously created:



22.


You have now successfully created a PvD
-
enabled desktop catalog and delivery group.


To test this group, you may log into the
PvDlab001 machine via either receiver (shown
below) or via the hypervisor console (XenCenter). In production deployments, your users
will be using Citrix Receiver to log into their PvD
-
enabled desktops. Log into the VM using
the “pvduser” account previousl
y created and the password entered during account
creation.



Page
21

Step

Action

23.


After logging into the PvD
-
enabled VM, you can verify it is properly working by opening
“My Computer” and looking for the “P:” PvD disk, as shown below:




The presence of the PvD

disk in the above image indicates proper operation of the PvD.

Any changes performed by the user (application installs, settings changes, etc) will be
captured and preserved across administrator image updates.


Page
22

Step

Action

24.


In the PvD

VM, install a sample application as the “pvduser” end user. In this scenario,
install Google Chrome (available in the “Downloads” folder or downloadable from the
Internet):



25.


Exercise Complete!


Summary

Key
Takeaways

In this exercise, you created a
PvD catalog and delivery group, and assigned it to
users. You then logged into the PvD
-
enabled VM and customized it via installing a
user
-
installed application.


In the next exercise, you will update the base VM and roll out the update to the user,
and ver
ify the user’s changes were preserved across the update.



Page
23

Exercise
2 : Updating PvD
-
enabled delivery
groups

Overview

In this exercise
you will update the base VM with new applications and roll out this ch
ange to the PvD
-
enabled delivery group created previously. You will then verify the previous user changes are preserved.

Step by step guidance

Estimated time to complete this lab:
2
0

minutes
.

Step

Action

1.


Using XenCenter, log into the Win7Client machine

2.


Install a new application. In the image below, we installed the “VideoLan VLC Media
Player” application (www.videolan.org):






Note

: In production environments, you would install Windows Updates and any
new large applications this way. For the purposes
of this lab, if you decide to install
a different application to the base image, select a “small” application for the
灵牰ps敳e sa癩湧⁴業攠摵物湧⁴桥 戮


Page
24

Step

Action

3.


Perform a new “Update Personal vDisk” operation from the start menu:



4.


It may take 5
-
10 minutes for the PvD Inventory to update:




Page
25

Step

Action

5.


On completion, using XenCenter, log into the PvDLAB (Desktop Delivery Controller)
machine and select the PvDLab catalog. Next, select “Update Machine” from the right
-
side
menu.


Re
-
select the
Win7Client VM when prompted for the image to use. Roll out the image
“Immediately” when prompted for a rollout strategy.






Note:
This step may take 5
-
10 minutes to complete as the new image is rolled out.

During this time, the PvDLab001 pool VM will rebo
ot several times.

6.


Using either Receiver or the XenCenter console, log back into the PvDLab001 pool VM
machine, using the same credentials as the previous exercise.


Page
26

Step

Action

7.


Verify that the application installed as the end user has been “blended” with the new
base
image (in this case, Google Chrome as well as VLC Media Player):



8.


Exercise Complete!


Summary

Key
Takeaways

In this exercise, you updated the base VM image with new content and rolled out
the update to the end user VMs. You also verified that end

user changes were
properly merged with the new base VM content.





Page
27

Exercise 3 : PvD reset

Overview

In this exercise you will reset the user’s PvD, which will revert

it to a “factory default” state. This will
remove all user
-
installed applications but will preserve any user profile settings and documents the user
created. You use PvD reset in production environments to restore “broken” PvDs where the user installed
an

application that broke the environment or otherwise experienced corruption.

Step by step guidance

Estimated time to complete this lab:
5
-
10

minutes
.

Step

Action

1.


Using Receiver or XenCenter
, log into the PvdLab001 machine using the same credentials
as
the previous exercises.

2.


PvDs may be reset either from Desktop Director (not shown here


瑹灩ta汬l 畳敤⁢e
桥h灤敳欠p瑡晦⁡s敥摥搩爠癩d⁴桥⁣潭浡湤楮i⁦牯r⁷楴桩渠瑨攠偶i
-
敮e扬b搠摥獫d潰⸠
T漠牥o整⁴桥⁐癄⁦牯r⁷楴桩渠瑨攠摥s歴潰Ⱐ楳s略⁴桥⁣潭浡湤n

“CtxPvD
-
s reset” from
瑨攠偶䐠楮t瑡t污瑩潮⁦潬摥爬⁡猠r桯h渠扥n潷W




Page
28

Step

Action

3.


On reset, the PvD
-
enabled desktop will automatically reboot. On restart, log in and verify
the user
-
installed application (in the above examples, this would mean Google Chrome)
is
not present, but the admin
-
installed applications (in this case, VideoLAN/VLC Media
Player) is still present:



4.


Exercise Complete!


Page
29

Revision History

Revision

Change Description

Updated By

Date

1
.
0

Original Version

M. Larkin

04
/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 Enterpris
e 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 an
d 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 Ju
ly 2012, the
Company acquired Bytemobile, provider of data and video optimization solutions for mobile network operators.

http://www.citrix.com



© 201
3

Citrix Systems, Inc. All rights reserved.