Citrix Virtual Apps and Desktops 7 Administration

On-Premises and in Citrix Cloud

Citrix Course: CWS-215-2I

Lab Manual
Version 2.01

Provisioning and Deliver App and Desktop

Resources
PUBLISHED BY
Citrix Systems, Inc.
851 West Cypress Creek Road
Fort Lauderdale, Florida 33309 USA
http://www.citrix.com

Copyright © 2020 by Citrix Systems, Inc.

All rights reserved. Citrix, the Citrix logo are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries,
and may be registered with the U.S. Patent and Trademark Office and in other countries. [Citrix Virtual Apps and
Desktops, Citrix Cloud, Citrix Virtual Apps, and Desktops Service, Citrix ADC] All other marks appearing herein are the
property of their respective owners.

Citrix Systems, Inc. (Citrix) makes no representations or warranties with respect to the content or use of this
publication. Citrix specifically disclaims any expressed or implied warranties, merchantability or fitness for any
particular purpose. Citrix reserves the right to make any changes in specifications and other information contained
in this publication without prior notice and without obligation to notify any person or entity of such revisions or
changes.

No part of the publication may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying, recording or information storage and retrieval systems, for any purpose other
than the purchaser’s personal use, without express written permission of.

2
Credits
Title Name

Architect Justin Apsley

Product Manager Nestor Hernandez
Technical Solutions Developers Arnd Kagelmacher
Aseem Shaikh
Ryan Keller

Instructional Designers Jayshree Nair

Deepak Ghosh

Graphic Designer Ryan Flowers

Publication Services Rahul Mohandas

At Citrix Education, we strive to continuously improve the quality of our course and lab materials.
We are interested in your valuable feedback Please participate in a brief online survey at the end of the
course.

3
Contents
Credits ................................................................................................................................................................... 3
Lab Manual Overview ............................................................................................................................................. 5
Lab Environment Overview..................................................................................................................................... 6
LAB ACCESS ............................................................................................................................................................ 8
Module 4: Provisioning and Deliver App and Desktop Resources ........................................................................... 10
Exercise 4-1: Create a Machine Catalog for Multi-session OS (Server OS) using MCS ......................................... 10
Exercise 4-2: Create a Delivery Group for Server OS .......................................................................................... 22
Exercise 4-3: Create Machine Catalog for Single-session OS (Desktop OS) using MCS ........................................ 35
Exercise 4-4: Create a Delivery Group for Desktop OS ....................................................................................... 45
Exercise 4-5: Update a Machine Catalog for Single-session OS (Desktop OS) ..................................................... 57

4
Lab Manual Overview
Lab Exercises:
The exercises in this Lab Manual were developed for use with the CWS-215 Citrix Virtual Apps
and Desktops 7 Administration On-Premises and in the Citrix Cloud course. The virtual machines
in this lab are running on Windows Server 2016 and Windows 10 Desktop.

At the completion of these exercises, you will gain valuable hands-on experience in installing,
configuring, administering, and supporting Citrix Virtual Apps and Desktops 7 build 1912 (LTSR).

Lab Scenario:
WW Labs is a technical company whose infrastructure topology is centrally located in New York
City, referenced as NYC in the company naming convention. The CTO has authorized the
purchase of Citrix Virtual Desktops Premium licenses. This license edition includes all of the
features of both Citrix Virtual Apps and Citrix Virtual Desktops. The Lead Citrix Architect has
tasked the Citrix Administrator team to implement a Proof of Concept (POC) Citrix Virtual Apps
and Desktops environment utilizing the current implementation of Active Directory, DHCP, DNS,
and SQL Server. Pending the resultant POC, the Citrix Administrator team will be further tasked
to scale the environment to include redundancy and security considerations.

The Lead Citrix Architect has concluded that Citrix Virtual Apps and Desktops 7 build 1912
meets the company’s requirements and has instructed the Citrix Administrator team to validate
this Citrix Virtual Apps and Desktops POC for three specific use cases:
 HR User Group: Hosted Shared Desktop and Published Apps
 Technician User Group: Hosted VDI (Random/Non-Persistent)
 Designer User Group: Remote PC

You are a Citrix Administrator on the WW Labs Citrix Administrator team and you have been
tasked to assist with this implementation.

5
Lab Environment Overview

SERVER LIST

Virtual Machine Name IP Address Operating System Description

NYC-ADC-001 192.168.10.100 12 Build 50.1 Citrix ADC
NYC-ADM-001 192.168.10.118 12 Build 51.24 Citrix Application Delivery Mgmt.
NYC-ADS-001 192.168.10.11 Windows Server 2016 Domain Controller, DNS, DHCP
NYC-CON-001 192.168.10.41 Windows Server 2016 Citrix Cloud Connector
NYC-DTP-001 DHCP Windows 10 Desktop OS VDA 7 1912
NYC-DTP-MST 192.168.10.60 Windows 10 Windows 10 Master Template
NYC-FSR-001 192.168.10.17 Windows Server 2016 File Server, Print Server
NYC-SQL-001 192.168.10.21 Windows Server 2016 SQL Server
NYC-SRV-001 DHCP Windows Server 2016 Server OS VDA – MCS Provisioned
NYC-SRV-002 DHCP Windows Server 2016 Server OS VDA – MCS Provisioned
NYC-SRV-MST 192.168.10.48 Windows Server 2016 Windows 2016 Master Template
NYC-STF-001 192.168.10.31 Windows Server 2016 StoreFront 3.16
NYC-VDC-001 192.168.10.46 Windows Server 2016 Delivery Controller
NYC-WRK-001 192.168.10.56 Windows 10 Managed Endpoint

6
CREDENTIALS LIST

User Name Password Description

WORKSPACELAB\Administrator Password1 Domain Administrator
(workspacelab.com)
Administrator Password1 Local (non-domain) user
Citrix Password1 Local (non-domain) user
WORKSPACELAB\HR1 Password1 HR User
WORKSPACELAB\Engineer1 Password1 Engineering User
WORKSPACELAB\Marketing1 Password1 Domain User
WORKSPACELAB\CTXAdmin Password1 Citrix Virtual Apps and Desktops
Admin
WORKSPACELAB\HDAdmin Password1 License Administrator

7
LAB ACCESS
Once connected to the NYC-HYP-101 Desktop, start both the lab management consoles:
Remote Desktop Connection Manager and Hyper-V Manager as shown in the example below.

The icon to start Remote Desktop Connection Manager is named VMs.rdg and the icon to start
Hyper-V is Hyper-V Manager.

You will primarily use Remote Desktop Connection Manager to log on and interact with your
virtual lab machines. You will primarily use Hyper-V Manager to manage the power state of the
virtual machines and manage the mounting and un-mounting of ISOs used in installations.

Remote Desktop Connection Manager is pre-configured with the credentials required for this
lab. To select the credentials, you wish to use as shown in the example below, right-click the
machine and select Connect server as.

8
9
Module 4: Provisioning and Deliver App and
Desktop Resources
Overview:
This module presents the Virtual Delivery Agent (VDA), its installation, and its role in the
delivery of resources to users. Directly following the preparation and installation of the VDA,
you will create catalogs and Delivery Groups to complete the resource delivery to the users.

Although not all of the machine catalog machines are virtual, most are and this course focuses
on the Citrix Machine Creation Services feature and its role in the creation of virtual machines.

Before you begin:

Estimated time to complete this lab: 45 minutes

Exercise 4-1: Create a Machine Catalog for Multi-session OS

(Server OS) using MCS
Scenario:
Your task is to proceed with the next step in creating resources for users that are hosted on a
Server OS. You will create a Machine Catalog using the Server OS that you prepared previously.

Step Action

1. Verify that the following VMs are powered on before beginning the exercises in this module:

 NYC-ADS-001
 NYC-DTP-MST
 NYC-FSR-001
 NYC-SQL-001
 NYC-SRV-MST
 NYC-VDC-001

To power manage the VMs, switch to Hyper-V Manager, right-click the VM in the Virtual Machine
pane, and select Start or Shut Down.

Note: The VMs are listed in alphabetical order.

10
2. Using Remote Desktop Connection Manager, connect to NYC-VDC-001.

To log on to NYC-VDC-001, right-click the machine and select Connect server.

Note: The following credentials are used to make the connection:

 User name: WORKSPACELAB\Administrator

 Password: Password1
3. Start the Citrix Studio management console.

To start Citrix Studio, click Start > Citrix > Citrix Studio.

4. Using Studio, expand Citrix Studio (SITE-NewYork) and click Machine Catalogs.

11
 From the Actions pane on the right side of the console, click Create Machine Catalog.

5. On the Introduction page, click Next to continue the Machine Catalog Setup wizard.

Note: Machine Catalogs are collections of physical or virtual machines that you assign to users. You
create Machine Catalogs from Master Images or physical machines in your environment. The Master
Image or physical machine that you use to create a Machine Catalog must have a VDA installed. Also,
ensure that the operating system is up-to-date and that applications are installed.

6. On the Operating System page, verify that Multi-session Multi-session OS is selected and click Next.

12
 Note: When selecting an operating system for the Machine Catalog, there are three options:

 Multi-session OS: The Server OS Machine Catalog provides hosted shared desktops for a
large-scale deployment of standardized Windows Server OS or Linux OS machines.
 Single-session OS: The Desktop OS Machine Catalog provides VDI desktops ideal for a variety
of different users.
 Remote PC Access: The Remote PC Access Machine Catalog provides users with remote
access to their physical office desktops, allowing them to work at any time.
7. On the Machine Management page, verify that the following two options are selected:

 Machines that are power managed (for example, virtual machines or blade PCs)
 Citrix Machine Creation Services (MCS)

Click Next to continue the Machine Catalog Setup wizard.

13
 Note: There are three options for the type of tool that will be used to deploy machines:

 Citrix Machine Creation Services (MCS) – Uses a master image or template to create and
manage virtual machines.
o MCS is not available for physical machines.
o Machine Catalogs in cloud environments use MCS.
 Citrix Provisioning Services (PVS) – Manages target devices as a device collection. This is also
referred to as Citrix Provisioning. A Citrix Provisioning vDisk imaged from a master target
device delivers desktops and applications.
 Another service or technology – A tool that manages machines already in the data center.
Citrix recommends you use Microsoft System Center Configuration Manager or another
third-party application to ensure that the machines in the catalog are consistent.
8. On the Master Image page, select NYC-SRV-MST as the Master machine.

On Select the minimum functional level for this catalog drop-down menu, select 1811 (or newer).

Click Next to continue the Machine Catalog Setup wizard.

14
 Note: If snapshots existed for the machine, you could select a specific snapshot to be used for the
master. Since there are no snapshots, the resultant process of this wizard will create one
automatically.

9. On the Virtual Machines page, set the number of virtual machines needed to 2 and configure the
following remaining settings:

 Total memory (MB) on each machine: 2048

 Memory allocated to cache (MB): 256
 Disk cache size (GB): 24

Click Next to continue the Machine Catalog creation wizard.

15
 Note: When you select the option Disk cache size (GB), MCS will create a formatted disk and attach it
to the VDA. Then, MCS will create a .vhdx file that is your actual temporary disk cache and inserts it
into the formatted disk.

10. On the warning message that appears, click Yes.

11. On the Active Directory Computer Accounts page, verify that the Create new Active Directory
accounts radio button is selected.

16
Under Active Directory location for computer accounts, in the drop-down next to Domain, verify that
workspacelab.com is selected.

Using the arrows, expand Citrix > New York > VDA.

Select the Servers_OnPremisesSite Organizational Unit (OU).

Note: The Servers_OnPremisesSite OU is the WW Labs' location designated for machines running the
Virtual Delivery Agent (VDA) that are used to host Server OS apps and desktop resources for users.

Enter NYC-SRV-### in the Account naming scheme box.

Verify that 0-9 is selected from the drop-down menu to the right of the naming scheme.

Click Next to continue the Machine Catalog Setup wizard.

17
 Note: If this wizard was being used to create machines on an existing naming convention, then the
resultant machines from this Machine Creation Services (MCS) process would increment to the next
numerical sequence numbers available.

12. On the Summary page, review the configurations and enter the following information:

 Machine Catalog name: NYC-CAT-ServerOS

 Machine Catalog description for administrators: Windows 2016 Published Apps and
Desktops - Machine Creation Services

Click Finish.

18
 Note: Clicking Finish begins the Machine Creation Services (MCS) process in which a combination of
the parameters specified in this Machine Catalog creation wizard and the parameters of the Citrix
Virtual Apps and Desktops Site is used to create complete virtual machines from the Master machine
specified earlier in the said wizard. Each virtual machine created is built into a Machine Catalog, visible
from Studio. Each virtual machine created has a nearly identical build to its Master machine, with a
unique SID, machine account in Active Directory, and a unique MAC address.

Note: With the Hyper-V resources allocated to this Citrix Virtual Apps and Desktops POC project by
the Lead Citrix Architect, it is expected that the Machine Creation Services (MCS) process will take an
estimated 10-15 minutes to complete. This process may appear hung, however, it is not; just let it
continue and complete itself.

13. Verify that the Machine Creation Services (MCS) process has completed. Using Studio, verify that the
Machine Catalog has been created.

Click Machine Catalogs in the left pane of Studio and view the NYC-CAT-ServerOS Machine Catalog in
the middle pane.

19
 Note: You may receive a warning message: “This machine catalog has the following warnings. The
Microsoft Remote Desktop licensing check could not run because no registered machines were
found.” If you receive the message, click Remove RDS license warning in the right bottom corner
under Actions in the right pane. Click Yes on the prompt.

14. Verify that the virtual machines that were specified to be created using Machine Creation Services
(MCS) have been successfully created and added to the NYC-CAT-ServerOS machine catalog.

Using Studio, right-click the NYC-CAT-ServerOS Machine Catalog and select View Machines.

20
 Verify that NYC-SRV-001.workspacelab.com and NYC-SRV-002.workspacelab.com are displayed.

15. Right-click NYC-SRV-001.workspacelab.com and click Start. Click Yes on the dial box that opens.

21
 Note: The Server OS Delivery Group will be created to enumerate applications from the Start menu.
Starting NYC-SRV-001 now will allow a faster application enumeration.

Key Takeaways:
 Machine catalogs group machines together that are similar in function, purpose, and
capabilities.
 All machines within a machine catalog need to be either Server OS or Desktop OS and
cannot be mixed.

Exercise 4-2: Create a Delivery Group for Server OS

Scenario:
Server OS machine catalogs contain a group of identical Server OS machines that can be used to
deliver a set of resources to users. The delivery of these resources to users is controlled through
Delivery Groups.

WW Labs has several user groups that require access to resources, including the Human
Resources, Engineers, and Auditors departments. These user groups will be dependent on
Server OS-based resources.

Your task is to create a Delivery Group and assign resources to the HR and Engineers Groups
from the Server OS catalog using a Delivery Group.

Step Action

1. Using Remote Desktop Connection Manager, confirm that you are still connected to NYC-VDC-001.

Note: In a previous exercise, you had logged on to NYC-VDC-001 using the following credentials to
make the connection:

22
  User name: WORKSPACELAB\Administrator
 Password: Password1

Note: If your Remote Desktop Connection session is disconnected, log on to NYC-VDC-001 by right-
clicking the machine and selecting Connect server.

2. Using Studio, expand Citrix Studio (SITE-NewYork) and click Delivery Groups.

From the Actions pane on the right side of the console, click Create Delivery Group.

Note: Studio was started in a previous exercise. If Studio was closed, then click Start > Citrix > Citrix
Studio.

3. On the Introduction page, click Next to continue the Create Delivery Group wizard.

23
 Note: Delivery Groups are collections of desktops and applications that created from machine
catalogs. Create Delivery Groups for specific teams, departments, or types of users, and base them on
either a desktop or a server operating system. Make sure you have enough machines available in a
suitable catalog to create the Delivery Groups you need.

4. On the Machines page, verify that the previously created machine catalog is listed.

Select NYC-CAT-ServerOS.

Enter 2 in the Choose the number of machines for this Delivery Group box.

Click Next to continue the Create Delivery Group wizard.

24
5. On the Users page, select Restrict use of this Delivery Group to the following users.

Click the Add button under the Add users and groups box.

25
Enter Auditors; Engineers; HR; in the Select Users or Groups dialog box that appears.

Click Check Names.

Click OK on the HR Group highlighted, and click OK on the Select Users or Groups dialog box.

26
Click Next to continue the Create Delivery Group wizard.

27
 Note: The WW Labs design scope for this Citrix Virtual Apps and Desktops POC deployment has
specified these user groups in Active Directory for testing these published applications (as seen in the
next step) for this POC.

6. On the Applications page, click Add and select From start menu.

Note: The wizard will begin the process of discovering applications found on NYC-SRV-001.

Select the checkbox next to each of the following applications to select them:

 Access 2016
 Excel 2016
 Notepad
 OneNote 2016
 Outlook 2016
 PowerPoint 2016
 Publisher 2016
 Word 2016

28
Click OK.

Note: Other than Microsoft Office applications, you are only publishing the Notepad application from
this Delivery Group.

Click Next to continue the Create Delivery Group wizard.

Note: The applications can take a while to populate, because the NYC-SRV-001 and NYC-SRV-002
machines may have been powered off by the Controller to save on resource consumption. To return a
list of the applications installed, the Controller has to call to the hypervisor hosting these machines
and have it powered on. Once powered on, the VDA machines will register with the Controller and
send a list of installed applications to publish.

Note: If this application list does not appear after five minutes, use Hyper-V Manager to verify that
NYC-SRV-001 or NYC-SRV-002 are powered on, and use Citrix Studio to verify that they are registered
with the Site. At least one of these machines needs to be fully powered on and registered to
enumerate applications. To attempt to manually register a VDA machine, connect to it with Remote
Desktop Connection Manager, start Command Prompt, and run the command gpupdate /force.

29
 Note: You can also add (create) applications manually by providing the executable path, working
directory, optional command line arguments, and a display name visible to users in Citrix Workspace
app and administrators in Studio.

7. On the Desktops page, click Add.

On the Add Desktop page, enter the following information:

 Display Name: HR Desktop

 Description: Desktops for HR Group

Select Restrict desktop use to and click Add.

In the Select Users or Groups window, type HR.

Click Check Names button.

30
Click OK on the HR Group highlighted, and click OK on the Select Users or Groups dialog box.

Click OK to close the Add Desktop page.

31
Click Next to continue the Create Delivery Group wizard.

32
8. On the Summary page, verify the previously configured information and enter the following:

 Delivery Group name: NYC-DG-ServerOS-Apps-Desktops

 Delivery Group description, used as label in Citrix Workspace app (optional): Windows 2016
Desktop

Click Finish.

33
 Note: The display name will appear for the published desktop and the application names will appear
for each published application to the user, using the Citrix Workspace app.

9. Verify that the applications selected during the Create Delivery Group wizard appear under the
Applications node.

Using Studio, select the Applications node in the left pane. Verify that you can see the following
published apps:

 Access 2016
 Excel 2016
 Notepad
 OneNote 2016
 Outlook 2016
 PowerPoint 2016
 Publisher 2016
 Word 2016

34
Key Takeaways:
 Use Delivery Groups to publish desktops or applications to users.
 A Delivery Group uses the machines from one or multiple machine catalogs of the same
type.

Exercise 4-3: Create Machine Catalog for Single-session OS

(Desktop OS) using MCS
Scenario:
You have already used MCS to create a machine catalog for Server OS. During that process, you
used a Server OS Machine as the machine catalog master image. Your task now is to use MCS to
create a machine catalog for Desktop OS using a virtual machine snapshot.

Step Action

1. Using Remote Desktop Connection Manager, confirm that you are still connected to NYC-VDC-001.

Note: In a previous exercise, you had logged on to NYC-VDC-001 using the following credentials to
make the connection:

 User name: WORKSPACELAB\Administrator

 Password: Password1

Note: If your Remote Desktop Connection session is disconnected, log on to NYC-VDC-001 by right-
clicking the machine and selecting Connect server.

2. Using Studio, expand Citrix Studio (SITE-NewYork) and click Machine Catalogs. From the Actions pane
on the right side of the console, click Create Machine Catalog.

35
3. On the Introduction page, click Next to continue the Machine Catalog Setup wizard.

4. On the Operating System page, select Single-session OS, and then click Next to continue the Machine
Catalog creation wizard.

36
 Note: When selecting an operating system for the Machine Catalog, there are three options:

 Multi-session OS: The Server OS Machine Catalog provides hosted shared desktops for a
large-scale deployment of standardized Windows Server OS or Linux OS machines.
 Single-session OS: The Desktop OS Machine Catalog provides VDI desktops ideal for a variety
of different users.
 Remote PC Access: The Remote PC Access Machine Catalog provides users with remote
access to their physical office desktops, allowing them to work at any time.
5. On the Machine Management page, verify that the following options are selected:

 Machines that are power managed (for example, virtual machines or blade PCs)
 Citrix Machine Creation Services (MCS)

Click Next to continue the Machine Catalog Setup wizard.

37
6. On the Desktop Experience page, select I want users to connect to a new (random) desktop each
time they log on.

Click Next to continue with Machine Catalog Setup wizard.

38
 Note: Unlike Server OS machine catalogs, there are multiple options to select how the desktops are
delivered with a Desktop OS machine catalog:

 Random: A new machine is given to the user every time a connection is made from the pool
of available machines and changes done by the user are lost on reboot.
 Static: Machine is assigned to the user who logs on to the machine first. Changes are saved
depending on the option selected:
o Personal vDisk: Changes are saved on the additional disk that is attached to each
VM when the catalog is created. Changes stored in the Personal vDisk are not
erased.
o Dedicated: Changes are saved on the differencing disk and are not lost on reboots.
o Pooled Static: Changes are not saved after a reboot, but the user gets the same
machine every time since the Static type is selected.
7. On the Master Image page, select NYC-DTP-MST.

Verify that 1811 (or newer) is selected.

Note: This is the version of the VDA installed on the master machine for this machine catalog.

39
 Click Next to continue the Machine Catalog Setup wizard.

Note: In an earlier exercise, you created a machine catalog for a Server OS, using a virtual machine as
the master machine. MCS supports the use of either a virtual machine or a virtual machine snapshot
to be used as the master machine or image to create the machine catalog. If you are using a snapshot
as the master image, you should consider naming the snapshot, because when the MCS process runs,
a snapshot is created by Studio and a name is assigned that you cannot change.

8. On the Virtual Machines page, verify the default following configuration values:

 Number of virtual machines needed: 1

 Memory (MB): 2048
 Memory allocated to cache (MB): 256
 Disk cache size (GB): 10

Click Next to continue the Machine Catalog Setup wizard.

40
 Note: When you select the option Disk cache size (GB), MCS will create a formatted disk and attach it
to the VDA. Then, MCS will create a .vhdx file that is your actual temporary disk cache and inserts it
into the formatted disk.

9. On the Active Directory Computer Accounts page, verify that the Create new Active Directory
accounts radio button is selected.

Under Active Directory location for computer accounts, in the drop-down next to Domain, verify that
workspacelab.com is selected.

Using the arrows, expand Citrix > New York > VDA.

Select Desktops_OnPremisesSite Organizational Unit (OU).

Note: The Desktops_OnPremisesSite OU is the WW Labs' location designated for machines running
the Virtual Delivery Agent (VDA) that are used to host user Desktop OS desktop resources.

41
 Enter NYC-DTP-### in the Account naming scheme box.

Verify that 0-9 is selected from the drop-down menu to the right of the naming scheme.

Click Next to continue the Machine Catalog Setup wizard.

Note: If this wizard was used to create machines on an existing naming convention, then the resultant
machines from this MCS process would increment to the next numerical sequence numbers available.

10. On the Summary page, review configurations and enter the following information:

 Machine Catalog name: NYC-CAT-DesktopOS

 Machine Catalog description for administrators: Windows 10 Desktop MCS Machine Catalog

Click Finish.

42
 Note: Clicking Finish begins the MCS process in which a combination of the parameters specified in
this Machine Catalog Setup wizard and the parameters of the Citrix Virtual Apps and Desktops Site are
used to create complete virtual machines from the Master machine specified earlier in the wizard.
Each virtual machine created is built into a machine catalog, visible from Studio. Each virtual machine
created has a nearly identical build to its Master machine, with a unique SID, machine account in
Active Directory, unique MAC, and using the DHCP scope we verified in an earlier exercise these
virtual machines have a unique IP address.

Note: With the Hyper-V resources allocated to this Citrix Virtual Apps and Desktops POC project by
the Citrix Lead Architect, we can expect this MCS process to take an estimated 10 minutes to
complete.

11. Verify that the MCS process has completed and that the machine catalog is created.

Click Machine Catalogs in the left pane of Studio and view the NYC-CAT-DesktopOS machine catalog
in the middle pane.

12. Verify that the virtual machine specified to be created by MCS has been successfully created and
added to the NYC-CAT-DesktopOS machine catalog.

43
In Studio, right-click the NYC-CAT-DesktopOS machine catalog and select View Machines.

Verify that NYC-DTP-001.workspacelab.com displays.

44
Key Takeaways:
 The Desktop OS machine catalog provides VDI desktops ideal for a variety of different
users.
 MCS can create multiple machines automatically from a machine or snapshot, including
both Server OS and Desktop OS machines.
 MCS relies on storage level cloning; make sure that the selected storage repository has
the necessary capacity and performance available.
 The desktops provided in this Delivery Group are set to be shared between the
configured users and will lose every change on reboot; this option is referred to as
random, non-persistent desktops.
 Other options include: static, non-persistent desktops and static persistent, where users
will receive the same desktop for each session, and changes will either be discarded or
saved during reboot.

Exercise 4-4: Create a Delivery Group for Desktop OS

Scenario:
To complete the assignment of a desktop from a VDI machine catalog, you will create a Delivery
Group.

45
Your task is to create a Delivery Group and set the assignment of non-persistent desktops to
the Technicians user group.

Step Action

1. Using Remote Desktop Connection Manager, confirm that you are still connected to NYC-VDC-001.

Note: In a previous exercise, you had logged on to NYC-VDC-001 using the following credentials to
make the connection:

 User name: WORKSPACELAB\Administrator

 Password: Password1

Note: If your Remote Desktop Connection session is disconnected, log on to NYC-VDC-001 by right-
clicking the machine and selecting Connect server.

2. Using Studio, expand Citrix Studio (SITE-NewYork) and click Delivery Groups.

From the Actions pane on the right side of the console, click Create Delivery Group.

Note: Studio was started in a previous exercise. If Studio was closed, then click Start > Citrix > Citrix
Studio.

3. On the Introduction page, click Next to continue the Delivery Group creation wizard.

46
4. On the Machines page, verify that the previously created machine catalog is listed.

Select NYC-CAT-DesktopOS.

In the Choose the number of machines for this Delivery Group box, confirm 1 is selected.

47
 Click Next to continue the Create Delivery Group wizard.

5. On the Users page, select Restrict use of this Delivery Group to the following users.

Click Add below Add users and groups. In the Select Users or Groups dialog box that appears, enter
Technicians and then click Check Names.

48
Click OK on the Select Users or Groups dialog box.

Click Next to continue the Create Delivery Group wizard.

49
 Note: The WW Labs design scope for this Citrix Virtual Apps and Desktops POC deployment has
specified this user group in Active Directory for testing this published desktop (as seen in the next
step).

6. On the Applications page, click Next.

50
 Note: NYC-CAT-DesktopOS has a Windows 10 machine, and you are only publishing desktops using
this catalog.

7. On the Desktops page, click Add. and enter the following information:

 Display name: Technician Desktop

 Description: Windows 10 Desktop

Select Restrict desktop use to radio button.

Click Add below Add users and groups.

51
In the Select Users or Groups dialog box that appears, enter Technicians and then click Check Names.
Click OK.

Click OK to return to Desktops page.

52
Click Next.

53
8. On the Summary page, verify the configuration information and enter the following:

 Delivery Group name: NYC-DG-DesktopOS-Desktops

 Delivery Group description, used as label in Citrix Workspace app (optional): Windows 10
Desktop for Technicians

54
 Click Finish.

9. Verify that the expected desktop is successfully added to the Delivery Group.

In Studio, select the Delivery Groups node in the left pane. In the center pane, right-click the NYC-DG-
DesktopOS-Desktops Delivery Group, and select View Machines.

55
 Verify that NYC-DTP-001.workspacelab.com displays.

Note: It may take up to five minutes for the registration state of NYC-DTP-001 to display as
Registered. If NYC-DTP-001’s registration state is displaying as Unregistered after five minutes, restart
NYC-DTP-001.

Key Takeaways:
 Use Delivery Groups to publish desktops or applications to users.
 A Delivery Group uses the machines from one or multiple machine catalogs of the same
type.

56
Exercise 4-5: Update a Machine Catalog for Single-session OS
(Desktop OS)
Scenario:
Your Lead Citrix Architect has reviewed your recent machine catalog and Delivery Group tasks
and has identified that the required software is missing from the Desktop OS catalog.

Your task is to perform an update to the Desktop OS catalog.

Step Action

1. Using Remote Desktop Connection Manager, connect to NYC-DTP-MST.

To log on to NYC-DTP-MST, right-click the machine and select Connect server.

Note: The following credentials are used to make the connection:

 User name: WORKSPACELAB\Administrator

 Password: Password1

Note: If you receive a prompt from the Citrix Workspace app, close it.

2. On the Desktop of NYC-DTP-MST, double-click the Lab Resources folder.

3. Double-click npp.7.3.Installer.exe to start the Notepad++ installation.

57
4. On the Installer Language menu, select English and click OK.

5. On the Notepad++ Setup page, click Next.

58
6. On the License Agreement page, review the license agreement, and if you agree, click I Agree.

59
7. On the Choose Install Location page, click Next.

60
8. On the first Choose Components page, click Next.

61
9. On the second Choose Components page, leave the default selection and click Install.

62
10. Wait for the installation to complete, clear Run Notepad++ v7.3 checkbox, and click Finish.

63
11. Switch to the NYC-HYP-101 host machine. On NYC-HYP-101, start the Virtual Machine Manager
Console.

Double-click Virtual Machine Manager Console icon on the desktop.

64
12. In the middle pane of the Virtual Machine Manager Console, right-click NYC-DTP-MST and select Shut
Down.

65
13. When prompted Do you want to continue?, click Yes.

Wait for the job status to show Completed before continuing.

14. In the middle pane of the Virtual Machine Manager Console, right-click NYC-DTP-MST and select
Create Checkpoint.

66
15. In the New Checkpoint dialog box, enter the following text into the appropriate box:

 Name: NYC-DTP-MST Configuration Update 1 Snapshot

 Description: NYC-DTP-MST base configuration with Notepad++ installed

Click Create.

Note: The name and description used here are only to represent that you have created a base
configuration. When creating a base image in a production environment, more software and settings
would typically be included.

16. Using Virtual Machine Manager, verify that the checkpoint was taken.

67
 In the center pane of Virtual Machine Manager, right-click NYC-DTP-MST, then select Manage
Checkpoints.

17. On the Checkpoints screen, verify that the NYC-DTP-MST Configuration Update 1 Snapshot is present.

68
18. Click Cancel to close the NYC-DTP-MST Properties window, then close the Virtual Machine Manager
console by clicking X in the top-right corner.

19. Using Remote Desktop Connection Manager, switch to NYC-VDC-001.

Note: In a previous step, you had logged on to NYC-VDC-001 using the following credentials to make
the connection:

 User name: WORKSPACELAB\Administrator

 Password: Password1

Note: If your Remote Desktop Connection session is disconnected, log on to NYC-VDC-001 by right-
clicking the machine and selecting Connect server.

20. Using Studio, expand Citrix Studio (SITE-NewYork) and click Machine Catalogs.

69
 Note: Studio was started in a previous exercise. If Studio was closed, then click Start > Citrix > Citrix
Studio.

In the center pane, right-click the NYC-CAT-DesktopOS Machine Catalog and click Update Machines.

21. On the Overview page, click Next.

22. On the Master Image page, expand NYC-DTP-MST > Citrix_XD_NYC-CAT-DesktopOS and select NYC-
DTP-MST Configuration Update 1 Snapshot.

70
 Note: This snapshot is the snapshot taken in a previous step.

Click Next to continue the Update machines wizard.

Note: When using a snapshot as the master image, you should consider naming the snapshot, because
when the MCS process runs, a snapshot is created by Studio and a name is assigned that you cannot
change.

23. On the Rollout Strategy page, select Immediately (shut down and restart the machine now).

Note: If you choose to update the image immediately, configure a distribution time and a notification.

 Distribution time: You can choose to update all machines at the same time, or specify the
total length of time it should take to begin updating all machines in the catalog. An internal
algorithm determines when each machine is updated and restarted during that interval.

71
  Notification: In the left notification drop-down, choose whether to display a notification
message on the machines before an update begins. By default, no message is displayed. If you
choose to display a message 15 minutes before the update begins, you can choose (in the
right drop-down) to repeat the message every five minutes after the initial message. By
default, the message is not repeated. Unless you choose to update all machines at the same
time, the notification message displays on each machine at the appropriate time before the
update begins, calculated by an internal algorithm.

In the drop-down menu for Distribution time, verify that Update all machines at the same time is
selected.

Note: You chose this Distribution time option because no users are logged on and you only have one
virtual machine (VM). If this machine catalog had multiple VMs running and you did not want to
restart them all at once, then you could have chosen one of the following options:

 Update all machines within 30 minutes

 Update all machines within 1 hour
 Update all machines within 2 hours
 Update all machines within 3 hours
 Update all machines within 4 hours
 Update all machines within 5 hours

All the VMs would then be rebooted during that time interval. An internal algorithm determines when
each machine is updated and restarted during that interval. The default application of this internal
algorithm is to reboot machines in sets of 10. This parameter can only be adjusted using PowerShell.

In the drop-down menu for Notify users of the update, select 1 minute before user is logged off.

Enter the following text in the Message box: As part of scheduled maintenance, your desktop has
been updated and will be rebooted. Please save all your work and log off. Thank you!

Click Next to continue the Machine Catalog Update wizard.

72
 Note: Citrix warns all Citrix Administrators when configuring messages to users, to be mindful of both
company and legal rules and to not offend, nor violate a user’s rights. Instead, keep these messages as
brief and as formal as possible.

24. On the Summary page, review the configurations and click Finish.

73
 Note: Click Close if a warning message appears.

25. While the MCS process runs to update the machine catalog, switch to NYC-DTP-001 from within
Remote Desktop Connection Manager.

To log on to NYC-DTP-001, right-click the machine and choose Connect server.

Note: The following credentials are used to make the connection:

74
  User name: WORKSPACELAB\Administrator
 Password: Password1

Verify that a dialog box shows up with the expected message: As part of scheduled maintenance, your
desktop has been updated and will be rebooted. Please save all your work and log off. Thank you!

Click OK.

Note: This message may take 5-10 minutes to appear. This message means that the message you
configured in the Update machines wizard under the notification only applies to active sessions that
are currently logged on.

26. Wait for a minute and verify that NYC-DTP-001 completes the reboot process.

Note: You may want to switch to Hyper-V Manager to monitor the progress of the reboot. To do this,
right-click NYC-DTP-001 in the center pane and click Connect.

Note: If the NYC-DTP-001 does not reboot on its own within 5 minutes after the message is displayed,
then perform a manual reboot from Hyper-V Manager.

27. Using Remote Desktop Connection Manager, connect to NYC-DTP-001.

To log on to NYC-DTP-001, right-click the machine and select Connect server.

Note: The following credentials are used to make the connection:

 User name: WORKSPACELAB\Administrator

 Password: Password1
28. Right-click Start and select Apps and Features.

75
 Verify that Notepad++ (32-bit x86) now appears as an installed program.

Close App & features.

29. Log off NYC-DTP-001.

To log off, right-click Start > Shut down or sign out > Sign out.

Key Takeaways:
• To update multiple machines in an MCS catalog at once, update the master machine,
and use the Update Machines function.
• An update can only be made to a complete catalog and all machines in it, not to Delivery
Groups.
• Updating the catalog can also be used to point to an older snapshot or a different
machine of the same type.
• After completing the update, a rollback option will appear in Studio, which can be used
to undo the recent update.

76