The training was about designing the best/suitable Citrix solution based on the design guidelines outline in Citrix

VDI handbook 7.15. The design guidelines define the many layers of the Citrix solution from end user
requirements to the server hardware requirements. The layers are as follow:

- User Layer
Defines the end user experience from devices and peripherals support, management method, and
understanding the network connectivity to effectively optimize the HDX protocol.

- Access Layer
Defines how users could access their resources and what resources users could access on their session. The
best way of doing this is by using the Access Matrix, example below:

Defines how to position Netscaler and Storefront including placing Netscaler and/or Storefront on Citrix
Cloud. Defines the decision to create multi stores within StoreFront, and authentication types between
netscaler and storefront. Defines redundancy and how to secure communication between Netscaler
and Storefront.

- Image Layer and Application Layer

Defines users into FlexCast model (application types) such as Published apps, Published Desktop, Hosted VDI,
etc based on user requirement. The number of sessions/vms per host can be calculated as below:

The recommended VDA sizing for both server OS and Desktop OS as below:
 Once we have decided on the type of FlexCast, we decide on whether we implement it via MCS, PVS or App
Layering.

- Personaliization Layer
Defines how to setup/deploy user profile and printing to user session. It is recommended to use UPM for
profile and GPO to setup folder redirection. When designing the UPM, pay close attention to application’s
behaviour and dependency on the profile.

- Control Layer
Defines the design on Site/Farm and zones. Typical design is Single Site/Farm with multiple zones, zones are
created based on location. Pya special attention to network latency between endpoints to delivery controllers,
so in high latency connection, it is recommended to have multiple sites and 1 zone instead of 1 site and
multiple zones. Multiple site design including citrix cloud and hybrid are also discussed. The chapter also
defines how machine catalogs, delivery groups, and how to manage the site(s) with Citrix Director. Other
control layer components such as license server and database are also discussed.
- Compute Layer
Define the hypervisor decision, clustering, use of GPU, disk IOPS, network adapter, firewalls, switches,
separate host into VDA (server OS/Desktop OS) and core servers(AD, database, storefront, delivery controller,
etc)
- HA and Multilocation
Defines the HA option for all components such as netscaler, storefront, delivery controller, PVS, MCS, App
Layering, user data, application, printing, site, zone, and how to use Optimal gateway routing in storefront to
minimize network traffic

- Disaster Recovery
Defines the 7 Tiers of disaster recovery with Tier 5 and 6 being the most common and the process of planning
and testing DR

Note:

- Citrix WEM (Workspace Environment Management): a handy tool to set the many settings for managed
devices and user citrix session, but this tool requires server, database, and agents. The server and database
hold all the settings and agents installed on each endpoint talk back to server to retrieve settings and then
apply it to the endpoint/user session. The tool is more user-friendly than GPO because it has better GUI layout.
Only available for free on Platinum license, can be used in any devices that are not part of the Citrix solution
but the total number of devices must not exceed the Platinum license.
- With HDX RealTime Optimization Pack, we could setup Skype so that the calls are using the endpoint instead of
VDA sessions, minimizing the network traffic usage inside VDA session.
- Application tagging  need more info+testing
- Citrix Smart Tools
- Session Recording, records user citrix session for compliance purposes, requires platinum license