1Y0-205 Citrix Virtual Apps and Desktops 7 Administration (CCA-V) Questions and Answers

According to the Citrix documentation, the command bind cs vserver MYVPN_http -lbvserver Vserver-CS-1 binds a load balancing virtual server to a content switching virtual server. This means that the content switching virtual server will forward the requests that match its policies to the load balancing virtual server. In this case, the content switching virtual server MYVPN_http has a policy that matches requests for http://server.citrix.lab, so it will forward those requests to the load balancing virtual server Vserver-CS-1. Therefore, the users trying to access http://server.citrix.lab will be connected to the Vserver MYVPN_http, which will then connect them to Vserver-CS-1.

Citrix Profile Management includes two key filtering policies that determine which users CPM will apply to:

Processed Groups — Only users in these groups will have their profiles managed by CPM.

Excluded Groups — Users in these groups will never be processed by CPM, even if they appear in Processed Groups.

Citrix documentation states:

If Processed Groups is enabled, only the groups listed are processed.

If a user belongs to an Excluded Group, CPM is disabled for that user regardless of other group memberships.

Users not listed in either policy will not be processed by CPM when Processed Groups is enabled.

Given the policy configuration:

✔ Product Marketing Team (Processed Group)

Members are processed.

✔ Human Resources Team (Not listed anywhere)

Since Processed Groups is enabled, HR members are not processed.→ Matches Answer C

✔ IT Team (Excluded Group)

Explicitly excluded.→ Not processed.

✔ Professional Sales Team (Excluded Group)

Explicitly excluded.→ Matches Answer D

Other options incorrectly contradict Citrix Profile Management logic.

Documentation References (no URLs)

Citrix Profile Management Administrator ' s Guide → “Processed Groups”

Citrix Profile Management Policy Reference → “Excluded Groups”

Citrix Profile Management GPO-Based Configuration Overview

The absence of a power-manage option during the creation of a new machine catalog in Citrix Virtual Apps and Desktops is typically due to the lack of a defined resource connection in Citrix Studio2.

The Resource Utilization view in Citrix Director accesses historical trend information of CPU, memory, and disk latency for each machine running the VDA. This view helps the administrator to monitor the resource consumption and performance of the machines1

1: Monitor historical trends across a site | Director

 Application Prelaunch is a feature that can be enabled to reduce the perceived start time of applications. It prelaunches an application session when the user logs on, so the application is ready when the user needs it, thus reducing the wait time during the initial access

According to the Citrix Printing Quick Start Guide1, Citrix recommends that you disable Direct connections to print servers if your Worker VMs and print servers are not in the same LAN. This is because in this situation the print job sent direct to the print server is not compressed. When the print job is routed via ICA it is compressed. This setting can be configured via Citrix policy under Printing > Client Printers > Direct connections to print servers2. Disabling this setting will allow users to print to both print servers via the ICA protocol. The other options are not relevant to the issue or the scenario.

Option B is correct because spillover policies are applied on the GSLB virtual server level, not on the individual GSLB service level. Therefore, the user cannot have a backup for a subset of GSLB services1.

Option C is correct because the selection of a GSLB service is based on the load balancing method configured on the GSLB virtual server, which applies to all the GSLB services bound to it. The user cannot restrict the selection of a GSLB service from a subset of GSLB services for the given domain1.

Option A is incorrect because an administrator can define a backup for a backup Vserver in an active standby GSLB setup for a given GSLB domain by using the backup domain option2.

Option D is incorrect because a GSLB Vserver can load-balance multiple FQDNs by using the domain list option

Citrix Virtual Apps and Desktops supports multiple hosting platforms, but only certain platforms are designed for on-premises datacenter deployments.

According to the Citrix Virtual Apps and Desktops Product Documentation under “Connections and Resources – Hosting Connections”, Citrix identifies the following as on-premises hypervisors:

Citrix Hypervisor (formerly XenServer)

Microsoft Hyper-V

Nutanix Acropolis (AHV)

VMware vSphere

These platforms run entirely inside the organization ' s datacenter, allowing full administrative control and ensuring that all workloads remain local.

Because the question requires resources to remain in the corporate datacenter, the valid choices are:

✔ Nutanix Acropolis (A)

Supported as an on-prem hypervisor platform with native Citrix integration.

✔ Microsoft Hyper-V (B)

Fully supported as an on-prem virtualization platform via SCVMM hosting connections.

✔ XenServer (Citrix Hypervisor) (D)

The native Citrix hypervisor designed for on-prem deployments.

Why Not AWS (C) or Azure (E)?

Both Amazon Web Services and Microsoft Azure are classified in Citrix documentation under “Public Cloud Connections”, not on-prem hosting.

These platforms require workloads to run in the cloud, which violates the requirement that resources must remain inside the corporate datacenter.

Documentation References

Citrix Virtual Apps and Desktops – Connections and Resources: Supported On-Premises Hosting Platforms

Citrix Hypervisor (XenServer) System Requirements

Nutanix Acropolis (AHV) Support in Citrix Virtual Apps and Desktops

Microsoft Hyper-V Hosting Connection Requirements

 The Secure Ticket Authority (STA) server locations must be configured on the Citrix Gateway and StoreFront to facilitate secure external access. The Citrix Gateway uses STA to validate session requests and the StoreFront communicates with the STA to manage user sessions securely.

Citrix Director can capture utilization statistics for CPU, IOPS, and memory for each machine in a selected delivery group1. The resource utilization tab in the trends page displays the historical data for these metrics, along with the peak concurrent sessions graph2. The machine statistics page also shows the CPU and memory usage of the selected machine over time, as well as the processes contributing to high resource consumption3. Citrix Director does not capture utilization statistics for disk space or network, but it does provide other information related to these components, such as disk latency4 and network analysis5.

1: Monitor historical trends across a site | Director 2: How to use Director to monitor storage performance - Citrix 3: Machine Statistics | Citrix Analytics for Performance 4: Citrix Director Provides Disk Usage Information 5: [Network analysis | Director]

According to Citrix documentation, to make a configuration change for a StoreFront server group, the change should be made on one StoreFront server in the group, and then the Propagate Changes feature should be used to synchronize the change across the group1

According to the Create store page from the Citrix Product Documentation, the administrator can create a store for unauthenticated users by ticking the option “Allow only unauthenticated users to access this store” when creating the store. This option is suitable for contractors who will not be Active Directory users and need access to specific resources. The other options (HTTP Basic, Smart card, and Pass-through) are authentication methods that require user credentials.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration guide, the expression CLIENT.SSL.CLIENT_CERT.VALID_NOT_AFTER.EQ(GMT2020) checks whether the client certificate is valid until the specified date (GMT2020). The other expressions are either incorrect or irrelevant for this requirement.

According to the Citrix documentation, “When you configure the Citrix ADC appliance for Active Directory authentication, you must configure DNS to assign fully qualified domain names (FQDNs) to the authentication and traffic management virtual servers. This is because the domain session cookie that is used during authentication is based on the FQDN of the virtual server.” 1

1: Configure DNS to Support Active Directory Authentication

The Virtual Delivery Agent (VDA) is a software component that enables machines to deliver applications and desktops to users. The VDA registers with a Delivery Controller and communicates session information to the Controller, which brokers connections between users and their resources. Users access their resources through Citrix Workspace app or a compatible web browser1

1: Virtual Delivery Agent (VDA) | Citrix Virtual Apps and Desktops 7 2308

The redirectURL parameter of the set cs vserver command specifies the URL where the user requests are redirected if the status of the content switching virtual server is DOWN1. This parameter is used for configuring backup servers or displaying maintenance messages1.

The dig +trace command can be used to resolve DNS requests by tracing the path from the root name servers to the authoritative name servers. This can help identify any issues with DNS resolution or delegation. The nslookup command can also be used to query DNS records, but it does not provide the trace option. The curl command can be used to transfer data from or to a server, but it does not resolve DNS requests. The ping command can be used to test the connectivity and latency between two hosts, but it does not resolve DNS requests.

Pass-through from NetScaler Gateway is the authentication method that allows external users to access internal resources through StoreFront without having to enter their credentials again. This method requires that users authenticate on NetScaler Gateway, which then passes the user identity to StoreFront. This option is only available if it has been enabled for the store. See Pass-through from Citrix Gateway for more details.

Citrix Workspace app includes an Auto-Update feature that automatically checks for and installs new versions. However, Citrix documentation states:

Auto-update only functions correctly when the Workspace app is installed with administrative privileges.

Deployments through enterprise software distribution tools (such as SCCM) ensure the app is installed in the correct system context to enable auto-updates.

Methods where the user installs the Workspace app manually or through StoreFront may install it in user context, which disables auto-updates.

Therefore, to guarantee:

✔ Full feature support

✔ Automatic updates

✔ No GPO configuration

✔ No user interaction

The Workspace app should be deployed using System Center Configuration Manager (SCCM), which installs the application at the machine level.

Why the other options are incorrect:

A. Workspace for Web:Browser-only access does not support full-feature Workspace capabilities.

B. Download via StoreFront:This results in a user-context installation, which disables auto-updates.

D. Network file share installation:Again, this leads to user-context installation and prevents auto-updates.

Documentation References

Citrix Workspace App Administration Guide → Auto-Update Requirements

Enterprise Deployment Guide for Citrix Workspace App

SCCM Deployment Practices for Machine-Level Installation

 A resource location is a collection of resources that you use to deliver applications and desktops to users. It can include Citrix ADC, VDA, Active Directory Domain, and Hypervisor. These resources are required for hosting and managing the machines that deliver apps and desktops to users1. StoreFront, Citrix Director, Citrix Provisioning, and Database are not part of a resource location, but are components of the Citrix Cloud service2.

When using an HDX Session printers policy, print jobs sent to a printer managed by the print server are routed directly to the network print server and then to the specified printer3.

Machine Creation Services creates several disk components for every machine in a catalog. One of these is the identity disk, used to store machine-specific configuration such as machine identity, domain information, and MCS-related identifiers.

Citrix documentation specifies that the identity disk size varies depending on the hypervisor type. For Microsoft Hyper-V, the identity disk created by MCS is 256 MB. This is a fixed value used consistently for Hyper-V–based MCS catalogs.

Other sizes listed (16 MB, 1024 MB, 2048 MB) are not used by Citrix MCS for Hyper-V identity disk creation.

Documentation References:

Citrix Virtual Apps and Desktops → MCS Storage and Disk Structure

Citrix MCS Identity Disk Requirements for Hypervisors

Virtual MAC is a feature that allows the Citrix ADC to use the same MAC address for the primary and secondary nodes in an HA pair. This way, the upstream router does not need to update its ARP table when a failover occurs. This feature can be enabled or disabled using the command set ha node -hamac yes|no or the GUI1

1: Citrix ADC High Availability (HA) - Citrix Docs

According to the Citrix documentation1, burst capacity allows an instance to use more bandwidth than its dedicated bandwidth when there is spare bandwidth available on the SDX appliance. The priority parameter determines which instance gets the spare bandwidth first. A higher priority value indicates a higher priority. Therefore, the administrator can configure burst capacity of 1GB with priority 10 on the instance that requires more bandwidth, to meet traffic requirements.

1: Citrix Virtual Apps and Desktops 7 Deployment and Administration - Configure burst capacity

 According to the Citrix documentation, the -denySSLReneg parameter specifies the type of SSL renegotiation that the Citrix ADC denies. The possible options are:

NONSECURE: Deny renegotiation requests from a client if the initial handshake between the Citrix ADC and the client is not secure. A secure handshake is one in which both parties prove their identities to each other by presenting valid certificates.

FRONTEND_CLIENT: Deny renegotiation requests from a client on a front-end SSL connection, regardless of whether the initial handshake is secure or not. A front-end SSL connection is one in which the Citrix ADC communicates with the client over SSL.

ALL: Deny all renegotiation requests from a client on a front-end SSL connection and from a server on a back-end SSL connection. A back-end SSL connection is one in which the Citrix ADC communicates with the server over SSL.

NO: Allow all renegotiation requests.

Therefore, the correct answer is A and C.

According to the Citrix documentation, when you bind an interface to a VLAN, the native VLAN of the interface changes to the VLAN to which it is bound. In this scenario, the native VLAN of interface 1/1 was 40 before the command was executed, so it remains 40 after the command is executed. The command does not change the native VLAN of the interface, only the VLAN to which it is bound. Therefore, the correct answer is B.

To secure XML traffic between StoreFront and Delivery Controllers, a Citrix Administrator must install a private server certificate on each Delivery Controller and bind the certificates to port 4431.

According to the HDX Insight documentation, HDX Insight is the integration of NetScaler Network Inspector and Performance Manager with Director. It captures data about ICA traffic and provides a dashboard view of real time and historical details. To monitor NetScaler appliances deployed in this mode, first add the NetScaler appliance to the NetScaler Application Delivery Management (ADM) inventory, enable AppFlow, and then view the reports on the dashboard. External users who access Citrix Virtual App and Desktop applications must authenticate themselves on the NetScaler Gateway. Therefore, the three components that the administrator will need to review are:

Citrix Application Delivery Management: This is the platform that collects and analyzes the AppFlow records generated by the NetScaler appliance.

Citrix Gateway: This is the component that provides secure access to the Citrix Virtual App and Desktop applications and generates the AppFlow records for HDX Insight.

Citrix Director: This is the web-based tool that displays the HDX Insight reports and allows the administrator to troubleshoot performance issues.

The Cloud Connector requires outbound connectivity on port 443 for communication with the internet2

When using MCS to create machines, each machine is activated using the Microsoft Key Management Service (KMS) or Multiple Activation Key (MAK) licensing1. The base image that is used to create the machines must be rearmed before capturing it, and the rearm count must not be exceeded2. If the base image rearm count has been exceeded, the machines created from that image will not be activated. Similarly, if the version of Windows installed on the base image uses MAK licensing, the machines created from that image will not be activated, because MAK licensing is not supported by MCS3.

1: Create machine catalogs | Citrix Virtual Apps and Desktops 7 2308 2: Prepare a master image | Citrix Virtual Apps and Desktops 7 2308 3: Licensing | Citrix Virtual Apps and Desktops 7 2308

According to the Citrix Virtual Apps and Desktops 7 Administration On-Premises and in Citrix Cloud course, the Responder policy expression determines which requests are redirected by the Responder action. The expression http.REQ.URL.EQ(“/”) matches only the requests for the root page, and not any other pages. This prevents the redirection loop that occurs when the Responder action expression is also the root page. The other options are incorrect because they either match all requests or none.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, team members who have access to their own admin partitions do NOT have Shell access by design. Shell access is only available for the default partition. Therefore, the team member cannot use aaad.debug or any other Shell commands from the CLI1

1: Manage | Citrix Virtual Apps and Desktops 7 2308

According to the Citrix documentation1, the No-Monitor option allows the administrator to remove health checks from specific bound services. This option is useful when the administrator wants to reduce the number of health checks sent to the backend resources, or when the administrator knows that a particular service is always up and does not need to be monitored.

A SSL profile is a collection of SSL settings that define the SSL behavior of a virtual server. A Citrix Administrator can use SSL profiles to apply the same SSL settings to multiple SSL virtual servers, which simplifies the configuration and management of SSL parameters1.

1: SSL Profiles

Citrix Virtual Apps and Desktops support several high availability solutions for on-premises deployments, including Always On Availability Groups, SQL Server database mirroring, and SQL clustering. These features ensure automatic failover and continuous operation1

According to the Citrix Virtual Apps and Desktops service on Citrix Cloud documentation, the control layer is always managed by Citrix when hosting Citrix Virtual Apps and Desktops on the Citrix Cloud platform. The control layer consists of the Citrix Cloud Connector, Studio, Director, and other components that orchestrate the delivery of applications and desktops. The resource layer, which contains the VDAs, hypervisors, and storage, is managed by the customer or a service provider. The user layer, which contains the user profiles, policies, and data, is also managed by the customer or a service provider. The access layer, which contains the StoreFront and NetScaler Gateway components, can be either managed by Citrix or the customer, depending on the deployment scenario.

 According to the Citrix documentation, automatic HA synchronization will fail if the primary and secondary Citrix ADCs have different build versions. The build versions must be the same for the configuration to be synchronized. A manual synchronization, a configuration change to the primary Citrix ADC, or a force failover will not affect the automatic HA synchronization1

1: Citrix Virtual Apps and Desktops 7 Deployment and Administration - High Availability

Citrix Cloud is the hosting platform that minimizes management and maintenance for administrators while maintaining control of the VDA machines1.

 Featured App Groups in Citrix Virtual Apps and Desktops can be created based on Application names, Keywords, and Application categories. This allows administrators to organize and highlight applications for users based on these criteria

Application Prelaunch is a feature that allows users to launch applications faster by creating a session when the user logs on to Citrix Workspace app, before the user requests an application. This feature is enabled by Delivery Group and can be configured for all users or a subset of users1.

Session Sharing is a feature that allows users to launch multiple applications using the same session, reducing the load on the server and improving the user experience. This feature is enabled by default and can be configured using Citrix policies2.

1: Prelaunch and linger 2: Session Sharing Explained with Troubleshooting Steps

 According to the Citrix documentation, the cacheForSecs parameter of the set httpcallout command specifies the time, in seconds, for which the response from the HTTP callout server is cached. Therefore, the effect of the command is to set the cache duration of the HTTP callout response to 120 seconds.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, a license upgrade is a cost effective solution that allows an administrator to increase the performance of an existing Citrix ADC appliance without replacing the hardware. A license upgrade can provide more throughput, SSL transactions per second, and compression capability. In this scenario, a license upgrade from MPX 5550 to MPX 5650 can double the throughput and SSL transactions per second, which can handle the forecasted growth of the retail company1

1: Citrix Virtual Apps and Desktops 7 Deployment and Administration (CWS-215), Module 6: Citrix ADC High Availability, Lesson: Citrix ADC Optimization, Topic: Citrix ADC Optimization Overview, Slide 6.

When StoreFront must integrate with a third-party portal, the portal typically acts as the external system that captures user credentials, handles primary authentication, and then passes those credentials (usually via HTTP headers or basic authentication mechanisms) to StoreFront.

Citrix documentation notes that HTTP Basic authentication is the method suited for integrations where StoreFront must accept credentials from an external portal or non-Citrix authentication framework. This method allows StoreFront to validate credentials passed programmatically from the third-party system.

Why not the other options?

Unauthenticated: This provides anonymous access and does not support integration with authenticated external portals.

Domain pass-through: Requires a Windows-integrated authentication flow, not compatible with third-party portals.

Pass-through from NetScaler Gateway: This applies only when authentication is performed via Citrix Gateway, not an external custom portal.

Therefore, HTTP Basic is the appropriate authentication method for third-party portal integration.

Documentation References:

StoreFront Authentication Methods Overview

StoreFront Third-Party Integration Scenarios (Authentication Requirements)

The expression B matches the required traffic because it uses the IN_SUBNET function to check if the source IP address belongs to the subnet 10.107.149.0/24, and it uses parentheses to group the logical OR condition for the destination port being either UDP or TCP 53. The other expressions are either syntactically incorrect or do not match the subnet correctly. See Policy Expressions and Classic Expressions for more information.

The Get-BrokerSite PowerShell command retrieves information about the site, including the name of the deployment, the local host cache configuration, and the license level. This command is part of the Citrix Virtual Apps and Desktops 7 Administration toolkit and is used to manage various aspects of the site configuration.

The administrator needs to change the product edition in Citrix Studio to match the newly installed advanced licenses. This action ensures that the Citrix Virtual Desktops Site utilizes the correct licenses and resolves the issue with the evaluation license expiration error message.

Citrix Cloud Connector requires the machine to be joined to a domain as part of its prerequisites for installation. If the machine is not domain-joined, it could prevent the Cloud Connector from installing properly. This is because Cloud Connector needs to communicate with Citrix Cloud services and typically relies on domain credentials for authentication and other functions within a domain environment.

Citrix Director includes application probing and health monitoring that categorizes issues into:

Warnings

Faults

Failures

According to Citrix’s monitoring definitions:

✔ An Application Fault refers to a failure that impacts functionality or causes loss of service or data.

Specifically, a fault indicates that the application:

Has experienced a significant failure

Cannot provide expected functionality

Has recorded an event indicating a serious problem

Needs administrative attention

This differs from:

Warnings (A) — non-critical issues that might lead to problems

Application unavailable (C) — a condition caused by machine/host failure

Probe failures (D) — failures detected through scheduled application probes and classified differently

Therefore, an Application Fault directly relates to loss of functionality or data, making B correct.

Documentation References

Citrix Director Monitoring Guide → Application Health States

Citrix Application Probing Documentation → Fault vs Warning Definitions

When deploying a Citrix Virtual Apps and Desktops Site with SQL database mirroring, Citrix requires that the collation setting used by the Site database must be explicitly set and must match the required Citrix standard. Citrix documentation states that the database collation must be case-insensitive and consistent between the principal and mirror SQL servers.

This collation is not automatically assigned by SQL Server when you create an empty database for mirroring. Therefore, administrators must manually configure the correct collation during initial creation. If the collation does not match Citrix requirements, the Site creation or Controller functionality may fail.

Other listed options (SQL version, database type, mirroring version) do not require manual configuration at database-creation time for Citrix Sites.

Documentation References:

Citrix Virtual Apps and Desktops Database Requirements → SQL Collation Requirements

Citrix Delivery Controller Installation Requirements → Database Mirroring Configuration

The PowerShell command Get-Service -DisplayName *citrix* is used to display all the Citrix services installed on the Delivery Controller. This command filters services by their display name to only show those related to Citrix, which typically include various components of the Citrix Virtual Apps and Desktops 7 Deployment and Administration.

When a printer is a network printer mapped on the VDA, the printing workflow follows standard server-based printing logic:

The user prints from an application running on the VDA.

The print job is generated and sent from the VDA directly to the network print server.

The print server processes the job and forwards it to the print device.

This creates a “server-side printing path,” which means the job never routes through the endpoint device. The VDA communicates with the print server using the native network printing protocol (typically SMB or IPP), not HDX.

Why the other options are incorrect:

A: Endpoint is not involved — native network printing is VDA → print server.

B: HDX is not used for network printers; HDX printing applies primarily to client printers or universal printing.

D: Network printing is fully supported in HDX sessions.

Documentation References:

Citrix Virtual Apps and Desktops → Printing Pathways

Citrix Printing Guide → Network Printing Architecture

 According to the Plan your StoreFront deployment document, for single server deployments you can install StoreFront on a non-domain-joined server but certain functionality will be unavailable; otherwise, StoreFront servers must reside either within the Active Directory domain containing your users’ accounts or within a domain that has a trust relationship with the user accounts domain unless you enable delegation of authentication to the Citrix Virtual Apps and Desktops sites or farms. All the StoreFront servers in a group must reside within the same domain. Therefore, server groups are not supported for non-domain-joined StoreFront servers (option D). Also, according to the User authentication document, when you configure a store, you specify the type of authentication service to use. By default, users are authenticated on StoreFront. Alternatively, you can delegate authentication to Citrix ADC or to the Delivery Controllers (option E). Authentication does not occur at the Domain Controller (option A) or at the Citrix ADC (option C) by default. Two-factor authentication is supported for non-domain-joined StoreFront servers (option B) as long as the authentication is delegated to Citrix ADC or Delivery Controllers.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration (CWS-215) course, the LeastConnection method is used to redirect user requests to the data center with the fewest active connections. This can help balance the load across different data centers and improve the user experience. The other methods are not suitable for this scenario because they do not consider the number of active connections or the location of the user

Inline CSS is a FEO action that replaces external CSS files with inline CSS code in the HTML document. This reduces the number of HTTP requests and improves the page load time. The screenshots show that the HTML code in the second snippet has no external CSS file linked, unlike the first snippet. Therefore, the correct answer is B. Inline CSS12.

Some additional information:

FEO stands for Front-End Optimization, which is a feature of Citrix Application Delivery Management (ADM) that optimizes web pages for faster delivery and better user experience3.

FEO actions are rules that modify the HTML, CSS, JavaScript, and images of a web page to improve its performance. FEO actions can be applied globally or to specific web pages based on policies4.

Other FEO actions include Truncate CSS, which removes unused CSS selectors and properties; Move CSS to head, which moves the CSS code to the head section of the HTML document; and Rearrange CSS, which reorders the CSS code to avoid rendering delays4.

To get application enumeration working in a Citrix Cloud migration scenario with on-premises StoreFront and Citrix ADC, the administrator needs to add the Citrix Cloud Connectors as Secure Ticket Authority (STA) servers on both Citrix ADC and StoreFront12.

According to the Create machine catalogs document from Citrix Virtual Apps and Desktops 7 2308, MCS adds the machines to Active Directory, which creates unique identities. MCS creates the number of VMs specified in the wizard, with two disks defined for each VM. In addition to the two disks per VM, a master is also stored in the same storage location. The identity disk is one of the two disks per VM, and it is used to store the Active Directory identity and other unique information for each VM. The identity disk is 16 MB in size and is created for each VM regardless of the disk type selected for the catalog.

 To ensure the line-of-business application is added to Favorites and users cannot remove it, the Citrix Administrator should add the phrase “KEYWORDS: Mandatory” to the application properties3.

 To view license information in Studio, an administrator must have at least the Read Licensing delegated administration permission. The built-in Full Administrator and Read-Only Administrator roles have that permission1.