Install VDAs
Introduction
This article begins with a description of Windows VDAs and the available VDA installers. The remainder of the article describes the steps in the VDA installation wizard. Command-line equivalents are provided. For details, seeInstall VDAs using the command line.
For information about Linux VDAs, seeLinux Virtual Delivery Agent.
View an introduction to VDAs.
Installation considerations
TheCitrix DaaSarticle describes what VDAs are and what they do. Here’s more information.
Analytics collection:当你ins自动收集分析tall or upgrade components. By default, that data is uploaded to Citrix automatically when the installation completes. Also, when you install components, you are automatically enrolled in theCitrix Customer Experience Improvement Program (CEIP), which uploads anonymous data. Also, during an installation or upgrade, you’re offered the opportunity to enroll in Call Home.
如果VDA安装失败,MSI分析器解析s the failing MSI log, displaying the exact error code. The analyzer suggests a CTX article, if it is a known issue. The analyzer also collects anonymized data about the failure error code. This data is included with other data collected by CEIP. If you end enrollment in CEIP, the collected MSI analyzer data is no longer sent to Citrix.
For information about these programs, seeCitrix Insight Services.
Citrix Workspace app:Citrix Workspace app for Windows is not installed by default when you install a VDA. You can download and install or upgrade Citrix Workspace app for Windows and other Citrix Workspace apps from the Citrix website. Alternatively, you can make those Citrix Workspace apps available from the Workspace or a StoreFront server.
Print Spooler Service:The Microsoft Print Spooler Service must be enabled. You cannot successfully install a VDA if that service is disabled.
Microsoft Media Foundation:Most supported Windows editions come with Media Foundation already installed. If the machine on which you’re installing a VDA does not have Microsoft Media Foundation (such as N editions), several multimedia features are not installed and do not work.
- Flash Redirection
- Windows Media Redirection
- HTML5 Video Redirection
- HDX RealTime Webcam Redirection
You can acknowledge the limitation, or end the VDA installation and restart it later, after installing Media Foundation. In the graphical interface, this choice is presented in a message. In the command line, you can use the
/no_mediafoundation_ack
option to acknowledge the limitation.Local user group:When you install the VDA, a new local user group called Direct Access Users is created automatically. For a single-session OS VDA, this group applies only to RDP connections. For a multi-session OS VDA, this group applies to ICA and RDP connections.
Cloud Connector address requirement:The VDA must have at least one valid Cloud Connector address (in the same resource location) with which to communicate. Otherwise, sessions cannot be established. You specify Cloud Connector addresses when you install the VDA. For information about other ways to specify Cloud Connector addresses where VDAs can register, seeVDA registration.
- Operating system considerations:
- Review theSystem requirementsfor supported platforms, operating systems, and versions.
- Ensure that each operating system maintains the latest updates.
- Ensure that VDAs have synchronized system clocks. The Kerberos infrastructure that secures communication between the machines requires synchronization.
- Optimization guidance for Windows 10 machines is available inCTX216252.
- If you try to install (or upgrade to) a Windows VDA on an OS that is not supported for that VDA version, a message describes your options. For example, if you try to install the latest VDA on an older Windows machine, a message guides you toCTX139030. For more information, seeEarlier operating systems.
Installed MSIs:Several MSIs are installed automatically when you install a VDA. You can prevent the installation of some MSIs on theAdditional Componentspage of the graphical interface or with the
/exclude
option in the CLI. For others, the only way to prevent their installation is with the/exclude
CLI option.- Domain-joined:Ensure that the machine is domain-joined before installing the VDA software.
VDA supportability tools
Each VDA installer includes a supportability MSI that contains Citrix tools for checking the VDA’s performance, such as its overall health and the quality of connections. Enable or disable installation of this MSI on theAdditional Componentspage of the VDA installer’s graphical interface. From the command line, disable installation with the/exclude "Citrix Supportability Tools"
option.
By default, the supportability MSI is installed inC:\Program Files (x86)\Citrix\Supportability Tools\
. You can change this location on theComponentspage of the VDA installer’s graphical interface, or with the/installdir
command-line option. Keep in mind that changing the location changes it for all installed VDA components, not just the supportability tools.
Current tools in the supportability MSI:
If you do not install the tools when you install the VDA, the CTX article contains a link to the current download package.
Restarts during VDA installation
A restart is required at the end of the VDA installation. That restart occurs automatically by default.
To minimize the number of other restarts needed during VDA installation:
- Ensure that a supported Microsoft .NET Framework version is installed before beginning the VDA installation.
- For Windows multi-session OS machines, install and enable the RDS role services before installing the VDA.
If you do not install those prerequisites before installing the VDA:
- If you are using the graphical interface or the command line interface without the
/noreboot
option, the machine restarts automatically after installing the prerequisite. - If you are using the command line interface with the
/noreboot
option, you must initiate the restart.
After each restart, the VDA installation continues. If you’re installing from the command line, you can prevent the automatic resumption with the/noresume
option.
When upgrading a VDA to version 7.17 or a later supported version, a restart occurs during the upgrade. This restart cannot be avoided.
Restore on install or upgrade failure
Note:
This feature is available only for single-session VDAs.
If a single-session VDA installation or upgrade fails, and the “restore on failure” feature is enabled, the machine is returned to a restore point that was set before the installation or upgrade began.
When a single-session VDA installation or upgrade starts with this feature enabled, the installer creates a system restore point before beginning the actual install or upgrade. If the VDA installation or upgrade fails, the machine is returned to the restore point state. The%temp%/Citrix
folder contains deployment logs and other information about the restore.
By default, this feature is disabled.
If you plan to enable this feature, make sure that system restore is not disabled through a GPO setting (Computer Configuration > Administrative Templates > System > System Restore
).
To enable this feature when installing or upgrading a single-session VDA:
When using a VDA installer’s graphical interface (such as usingAutostartor the
XenDesktopVDASetup.exe
command without any restore or quiet options), select theEnable automatic restore if update failscheck box on theSummarypage.If the install/upgrade completes successfully, the restore point is not used, but is retained.
Run a VDA installer with either the
/enablerestore
or/enablerestorecleanup
option.If you use the
/enablerestorecleanup
option, and the install/upgrade completes successfully, the restore point is removed automatically.If you use the
/enablerestore
option, and the install/upgrade completes successfully, the restore point is not used, but is retained.
VDA installers
VDA installers can be downloaded directly from the Citrix Cloud console.
By default, files in the self-extracting installers are extracted to theTemp
folder. The files extracted to theTemp
folder are automatically deleted after the installation completes. Alternatively, you can use the/extract
command with an absolute path.
Three standalone VDA installers are available for download.
VDAServerSetup.exeInstalls a multi-session OS VDA.
VDAWorkstationSetup.exeInstalls a single-session OS VDA.
VDAWorkstationCoreSetup.exeInstalls a single-session OS VDA that is optimized for Remote PC Access deployments or core VDI installations. Remote PC Access uses physical machines. Core VDI installations are VMs that are not being used as an image. This installer deploys only the core services necessary for VDA connections. Therefore, it supports only a subset of the options that are valid with the VDAWorkstationSetup installer.
This installer for the current release does not install or contain the components used for:
- App-V.
- Profile Management. Excluding Citrix Profile Management from the installation affects Monitor displays.
- Machine Identity Service.
- Citrix Workspace app for Windows.
- Citrix Supportability Tools.
- Citrix Files for Windows.
- Citrix Files for Outlook.
- MCSIO write cache for storage optimization.
This installer does not install or contain a Citrix Workspace app for Windows.
This installer automatically installs the Browser Content Redirection MSI. Automatic installation applies to VDA release 2003 and later supported releases.
UsingVDAWorkstationCoreSetup.exe
is equivalent to using theVDAWorkstationSetup.exe
installer to install a single-session OS VDA and either:
- In the graphical interface: Selecting theRemote PC Accessoption on theEnvironmentpage.
- In the command-line interface: Specifying the
/remotepc
option. - In the command line interface: Specifying
/components vda
and/exclude "Citrix Personalization for App-V - VDA" "Personal vDisk" "Machine Identity Service" "Citrix Profile Management" "Citrix Profile Management WMI Plugin" "Citrix Supportability Tools" "Citrix Files for Windows" "Citrix Files for Outlook" "Citrix MCS IODriver"
.
如果你我nstall a VDA with theVDAWorkstationCoreSetup.exe
installer and later upgrade that VDA using theVDAWorkstationSetup.exe
installer, you can optionally install the omitted components and features.
Step 1. Download the product software and launch the wizard
- On the machine where you’re installing the VDA, sign in toCitrix Cloud.
- In the upper left menu, select the Citrix DaaS in theMy Serviceslist.
- On the right side, clickDownloadsand selectDownload VDA. You are redirected to the VDA download page. Find the VDA installer you want and then selectDownload File.
- After the download completes, right-click the file and selectRun as administrator. The installation wizard launches.
As an alternative to steps 1-3, you can download the VDA directly from theCitrix download page.
Step 2. Specify how the VDA will be used
On theEnvironmentpage, specify how you plan to use the VDA, indicating whether you’ll use this machine as an image to provision machines. The option you choose affects which Citrix provisioning tools are installed automatically (if any), and the default values on theAdditional Componentspage of the VDA installer.
Choose one of the following:
Create a master MCS image:Select this option to install a VDA on a VM image, if you plan to use Machine Creation Services to provision VMs. This option installs the Machine Identity Service. This is the default option.
Command-line option:
/mastermcsimage
or/masterimage
Create a master image using Citrix Provisioning or third-party provisioning tools:Select this option to install a VDA on a VM image, if you plan to use Citrix Provisioning or third-party provisioning tools (such as Microsoft System Center Configuration Manager). Use this option for previously provisioned VMs that were booted from a Citrix Provisioning read/write disk.
Command-line option:
/masterpvsimage
(Appears only on multi-session OS machines)Enable brokered connections to a server:Select this option to install a VDA on a physical or virtual machine that will not be used as an image.
Command-line option:
/remotepc
(Appears only on multi-session OS machines)Enable Remote PC Access:Select this option to install a VDA on a physical machine for use with Remote PC Access.
Command-line option:
/remotepc
SelectNext.
This page does not appear:
- When upgrading a VDA.
- When using the
VDAWorkstationCoreSetup.exe
installer.
Step 3. Select the components to install and the installation location
On theCore componentspage:
Location:By default, components are installed in
C:\Program Files\Citrix
. This default is fine for most deployments. If you specify a different location, that location must have execute permissions for the network service.Command-line option:
/installdir
Components:By default, Citrix Workspace app for Windows is not installed with the VDA. If you are using the
VDAWorkstationCoreSetup.exe
installer, Citrix Workspace app for Windows is never installed, so this check box is not displayed.Command-line option:
/components vda,plugin
to install the VDA and the Citrix Workspace app for Windows
SelectNext.
Step 4. Install additional components
TheAdditional Componentspage contains check boxes to enable or disable installation of other features and technologies with the VDA. In a command-line installation, you can use the/exclude
or/includeadditional
option to omit or include one or more available components.
The following table indicates the default setting of items on this page. The default setting depends on the option you selected on theEnvironmentpage.
Additional Components page | Environment page: “Master image with MCS” or “Master image with Citrix Provisioning …” selected | Environment page: “Enable brokered connections to server” (for multi-session OS) or “Remote PC Access” (for single-session OS) selected |
---|---|---|
Citrix Personalization for App-V | Not selected | Not selected |
User Personalization Layer | Not selected | Not shown because it’s not valid for this use case |
Citrix Supportability tools | Selected | Not selected |
Citrix概要Management | Selected | Not selected |
Citrix概要Management WMI Plug-in | Selected | Not selected |
Citrix VDA Upgrade Agent | Not selected | Not selected |
Citrix Files for Windows | Not selected | Not selected |
Citrix Files for Outlook | Not selected | Not selected |
Machine Creation Services (MCS) storage optimization | Not selected | Not selected |
Rendezvous protocol configuration | Not selected | Not selected |
This page does not appear when:
- Using the
VDAWorkstationCoreSetup.exe
installer. Also, the command-line options for the additional components are not valid with that installer. - 升级的共识和所有的额外组件are already installed. If some of the additional components are already installed, the page lists only the components that are not installed.
The components list can include:
Citrix Personalization for App-V:Install this component if you use applications from Microsoft App-V packages. For details, seeApp-V.
Command-line option:
/includeadditional "Citrix Personalization for App-V – VDA"
to enable component installation,/exclude "Citrix Personalization for App-V – VDA"
to prevent component installationCitrix User Personalization Layer:Installs the MSI for the user personalization layer. For details, seeUser personalization layer.
This component appears only when installing a VDA on a single-session Windows 10 machine.
Command-line option:
/includeadditional "User Personalization Layer"
to enable component installation,/exclude "User Personalization Layer"
to prevent component installationCitrix Supportability Tools:Installs the MSI that contains Citrixsupportability tools.
Command-line option:
/includeadditional "Citrix Supportability Tools"
to enable component installation,/exclude "Citrix Supportability Tools"
to prevent component installationCitrix概要Management:This component manages user personalization settings in user profiles. For details, seeProfile Management.
Excluding Citrix Profile Management from the installation affects the monitoring and troubleshooting of VDAs in Citrix Cloud.
- On theUser detailsandEndPointpages of theMonitortab, thePersonalizationpanel and theLogon Durationpanel fail.
- On theDashboardandTrendspages, theAverage Logon Durationpanel display data only for machines that have Profile Management installed.
Even if you are using a third-party user profile management solution, Citrix recommends that you install and run the Citrix Profile Management Service. Enabling the Citrix Profile Management Service is not required.
Command-line option:
/includeadditional "Citrix Profile Management"
to enable component installation,/exclude "Citrix Profile Management"
to prevent component installationCitrix概要Management WMI Plug-in:This plug-in provides Profile Management runtime information in WMI (Windows Management Instrumentation) objects (for example, profile provider, profile type, size, and disk usage). WMI objects provide session information to Director.
Command-line option:
/includeadditional "Citrix Profile Management WMI Plugin"
to enable component installation,/exclude "Citrix Profile Management WMI Plugin"
to prevent component installationVDA Upgrade Agent:(Applicable only to Citrix DaaS deployments.) Enables the VDA to participate in theVDA Upgrade feature. You can use that feature to upgrade a catalog’s VDAs from the management console, immediately or at a scheduled time. If this agent is not installed, you can upgrade a VDA by running the VDA installer on the machine.
Command-line options:
/includeadditional "Citrix VDA Upgrade Agent"
to enable component installation,/exclude "Citrix VDA Upgrade Agent"
to prevent component installationCitrix Files for Windows:This component enables users to connect to their Citrix Files account. They can then interact with Citrix Files through a mapped drive in the Windows file system, without requiring a full sync of their content.
Command-line options:
/includeadditional "Citrix Files for Windows"
to enable component installation,/exclude "Citrix Files for Windows"
to prevent component installationCitrix Files for Outlook:This component allows you to bypass file size restrictions and add security to your attachments or emails by sending them through Citrix Files. You can provide a secure file upload request directly in your email. For more information, seeCitrix Files for Outlook.
Command-line options:
/includeadditional "Citrix Files for Outlook"
to enable component installation,/exclude "Citrix Files for Outlook"
to prevent component installationMachine Creation Services (MCS) storage optimization:Installs the Citrix MCS IO driver. For more information, seeStorage shared by hypervisorsandConfigure cache for temporary data.
Command-line options:
/includeadditional "Citrix MCS IODriver"
to enable component installation,/exclude "Citrix MCS IODriver"
to prevent component installationRendezvous Proxy Configuration:Install this component if you plan to use the Rendezvous protocol with the Citrix Gateway Service in your environment, and you have a non-transparent proxy in your network for outbound connections. Only HTTP proxies are supported.
如果你我nstall this coponent, specify the address of the proxy or PAC file path on theRendezvous Proxy Configurationpage. For feature details, seeRendezvous protocol.
Command-line option:
/includeadditional "Citrix Rendezvous V2"
to enable component installation,/exclude "Citrix Rendezvous V2"
to prevent component installation
Step 5. Cloud Connector addresses
On theDelivery Controllerpage, selectDo it manually.Enter the DNS name of an installed Cloud Connector and then selectAdd. If you’ve installed additional Cloud Connectors in the resource location, add their DNS names.
SelectNext.
Considerations:
- The address can contain only alphanumeric characters.
- Successful VDA registration requires that the firewall ports used to communicate with the Cloud Connector are open. That action is enabled by default on theFirewallpage of the wizard.
Command-line option:/controllers
Step 6. Rendezvous Proxy Configuration
TheRendezvous Proxy Configurationpage appears only if you enabled theRendezvous Proxy Configurationcheck box on theAdditional Componentspage.
- Select whether you will specify the proxy source by proxy address or PAC file path.
Specify the proxy address or PAC file path.
- Proxy address format:
http://
: - PAC file format:
http://
: / / .pac
- Proxy address format:
The firewall for the proxy port must be open for the connection test to succeed. If a connection cannot be made to the proxy, you can choose whether to continue with the VDA installation.
Command-line option:/proxyconfig
Step 7. Enable or disable features
On theFeaturespage, use the check boxes to enable or disable features you want to use.
Use Windows Remote Assistance:When this feature is enabled, Windows Remote Assistance is used with the user shadowing feature of the Director component in Citrix Cloud. Windows Remote Assistance opens the dynamic ports in the firewall. (Default = disabled)
Command-line option:
/enable_remote_assistance
Use Real-Time Audio Transport for audio:Enable this feature if voice-over-IP is widely used in your network. The feature reduces latency and improves audio resilience over lossy networks. It allows audio data to be transmitted using RTP over UDP transport. (Default = disabled)
Command-line option:
/ enable_real_time_transport
Use screen sharing:When enabled, ports used by screen sharing are opened in the Windows firewall. (Default = disabled)
Command-line option:
/enable_ss_ports
Is this VDA installed on a VM in a cloud:This setting helps Citrix to correctly identify resource locations for on-premises and service (Citrix Cloud) VDA deployments for telemetry purposes. This feature has no impact on customer side utilization. Enable this setting if your deployment uses Citrix DaaS. (Default = disabled)
Command-line option:
/xendesktopcloud
SelectNext.
If this page contains a feature namedMCS I/O, do not use it. The MCS IO feature is configured on theAdditional Componentspage.
Step 8. Firewall ports
TheFirewallpage indicates which ports the VDA and Cloud Connectors use to communicate with each other. By default, these ports are opened automatically if the Windows Firewall Service is running, even if the firewall is not enabled. This default setting is fine for most deployments.
For port information, seeNetwork ports.
SelectNext.
Command-line option:/enable_hdx_ports
Step 9. Review prerequisites and confirm installation
TheSummarypage lists what will be installed. You can return to earlier wizard pages and change selections, if needed.
(Single-session VDAs only) Select theEnable automatic restore if update failscheck box to enable the restore on failure feature. For details, seeRestore on install or upgrade failure.
When you’re ready, selectInstall.
Step 10. Diagnose
On theDiagnosticspage, choose whether to participate in Citrix Call Home. If you choose to participate (the default), selectConnect. When prompted, enter your Citrix account credentials.
After your credentials are validated (or if you choose not to participate), selectNext.
For more information, seeCall Home.
Step 11. Complete this installation
TheFinishpage contains green check marks for all prerequisites and components that installed and initialized successfully.
SelectFinish. By default, the machine restarts automatically. Although you can disable this automatic restart, the VDA cannot be used until the machine restarts.
If you are installing a VDA on individual machines (rather than an image), repeat the steps above to install a VDA on other machines, as needed.
Troubleshoot
In theManage > Full Configurationdisplay for a delivery group, theInstalled VDA versionentry in the details pane might not be the version installed on the machines. The machine’s Windows Programs and Features display shows the actual VDA version.
Citrix Optimizer
Citrix Optimizer is a tool for Windows OS that helps Citrix administrators optimize VDAs by removing and optimizing various components.
After installing a VDA and completing the final restart, download and install Citrix Optimizer. SeeCTX224676. The CTX article contains the download package, plus instructions about installing and using Citrix Optimizer.
Customize a VDA
之后,to customize (change information for) an installed VDA:
- From the Windows feature for removing or changing programs, selectCitrix Virtual Delivery AgentorCitrix Remote PC Access/VDI Core Services VDA. Then right-click and selectChange.
- Select自定义虚拟投递代理设置.
When the installer launches, change any available settings.
Customize the port for communicating with Cloud Connectors
You can customize the port that VDAs use to communicate with Cloud Connectors based on your specific security requirements. This feature is useful if your security team doesn’t allow the default port (port 80) to be open or if the default port is already in use.
自定义端口,完成以下步骤s:
Add the Controller port number on Citrix Cloud Connectors.
Add the VDA port number on VDAs.
Add the Controller port number on Citrix Cloud Connectors
Go to the Citrix Cloud Connector and run the following two PowerShell commands:
PS C:\> & 'C:\Program Files\Citrix\XaXdCloudProxy\XaXdCloudProxy.exe' -VdaPort
PS C:\> & 'C:\Program Files\Citrix\Broker\Service\HighAvailabilityService.exe' -VdaPort
-ConfigureFirewall
Example:
PS C:\> & 'C:\Program Files\Citrix\XaXdCloudProxy\XaXdCloudProxy.exe' -VdaPort 18000
PS C:\> & 'C:\Program Files\Citrix\Broker\Service\HighAvailabilityService.exe' -VdaPort 18000 -ConfigureFirewall
When customizing the port, consider the following:
- You must use the same port number in both commands.
- You must run both commandson all Cloud Connectors.
- To successfully communicate with Cloud Connectors, ensure that all VDAs use the same port number.
- The port you configure persists across connector updates.
Add the VDA port number on VDAs
Install the VDA with default settings and configure as follows. If the VDA is already installed, continue with the steps below.
On the VDA, openXenDesktopVdaSetup.exe, which is located at
C:\Program Files\Citrix\XenDesktopVdaSetup\XenDesktopVdaSetup.exe
.On theProtocol and Portpage, add the custom port number.
On theDelivery Controllerpage, enter the FQDN of the Controller.
ClickNextto proceed through the wizard to complete the configuration.
The port numbers are then reconfigured successfully.
Note:
You might see the following error message when you test a Controller connection: No running instance of a Controller found on < the Controller address you entered >. If the address is correct, you can dismiss the message.
Troubleshooting
To check whether the custom ports are configured correctly, go to the Cloud Connector and perform the following troubleshooting steps:
Verify that the following two registry keys exist.
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XaXdCloudProxyPersist Name: CustomVDAPortNumber Type: REG_DWORD Data: 18000
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XaXdCloudProxyPersist Name: CustomVDAPortNumberHA Type: REG_DWORD Data: 18000
Run the following command to create a .txt file.
netsh http show urlacl >
.txt
Example:
netsh http show urlacl > c:\reservations.txt
Open the .txt file and check the following four URLs to verify that the correct port is used.
http://+:18000/Citrix/CdsController/IRegistrar/
http://+:18000/Citrix/CdsController/ITicketing/
http://+:18000/Citrix/CdsController/IDynamicDataSink/
http://+:18000/Citrix/CdsController/INotifyBroker/
Verify that the following two firewall rules are created and required ports are open.
- Citrix XaXdProxy
- Citrix Broker Service (TCP-In)
Other information
- After you install a VDA, you can check the health and availability of the site and its components with aCloud Health check.
Where to go next
To review the entire configuration process, seePlan and build a deployment.
In this article
- Introduction
- Installation considerations
- VDA installers
- Step 1. Download the product software and launch the wizard
- Step 2. Specify how the VDA will be used
- Step 3. Select the components to install and the installation location
- Step 4. Install additional components
- Step 5. Cloud Connector addresses
- Step 6. Rendezvous Proxy Configuration
- Step 7. Enable or disable features
- Step 8. Firewall ports
- Step 9. Review prerequisites and confirm installation
- Step 10. Diagnose
- Step 11. Complete this installation
- Troubleshoot
- Citrix Optimizer
- Customize a VDA
- Customize the port for communicating with Cloud Connectors
- Other information
- Where to go next