This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Install VDAs using scripts
Note:
Citrix is not responsible for issues caused by scripts that are adapted to match customer production environments. For any install related Citrix issues, open a technical support case with the relevant install logs using the Citrix Support portal.
This article applies to installing VDAs on machines with Windows operating systems. For information about VDAs for Linux operating systems, see the Linux Virtual Delivery Agent documentation.
The installation media contains sample scripts that install, upgrade, or remove Virtual Delivery Agents (VDAs) for machines in Active Directory. You can also use the scripts to maintain master images used by Machine Creation Services and Citrix Provisioning (formerly Provisioning Services).
Required access:
- The scripts need Everyone Read access to the network share where the VDA installation command is located. The installation command is
XenDesktopVdaSetup.exein the full product ISO, orVDAWorkstationSetup.exeorVDAServerSetup.exein a standalone installer. - Logging details are stored on each local machine. To log results centrally for review and analysis, the scripts need Everyone Read and Write access to the appropriate network share.
To check the results of running a script, examine the central log share. Captured logs include the script log, the installer log, and the MSI installation logs. Each installation or removal attempt is recorded in a time-stamped folder. The folder title indicates the operation result with the prefix PASS or FAIL. You can use standard directory search tools to find a failed installation or removal in the central log share. Those tools offer an alternative to searching locally on the target machines.
Before beginning any installation, read and complete the tasks in Prepare to install.
Install or upgrade VDAs using the script
- Obtain the sample script InstallVDA.bat from \Support\AdDeploy\ on the installation media. Citrix recommends that you make a backup of the original script before customizing it.
- Edit the script:
- Specify the version of the VDA to install:
SET DESIREDVERSION. For example, version 7 can be specified as 7.0. The full value can be found on the installation media in the ProductVersion.txt file. However, a complete match is not required. - Specify the network share where the installer will be invoked. Point to the root of the layout (the highest point of the tree). The appropriate version of the installer (32-bit or 64-bit) is called automatically when the script runs. For example:
SET DEPLOYSHARE=\\fileserver1\share1. - Optionally, specify a network share location for storing centralized logs. For example:
SET LOGSHARE=\\fileserver1\log1). - Specify VDA configuration options as described in Install using the command line. The
/quietand/norebootoptions are included by default in the script and are required:SET COMMANDLINEOPTIONS=/QUIET /NOREBOOT.
- Specify the version of the VDA to install:
- Using Group Policy Startup Scripts, assign the script to the OU containing your machines. This OU should contain only machines on which you want to install the VDA. When the machines in that OU are restarted, the script runs on all of them. A VDA is installed on each machine that has a supported operating system.
Remove VDAs using the script
- Obtain the sample script UninstallVDA.bat from \Support\AdDeploy\ on the installation media. Citrix recommends that you make a backup of the original script before customizing it.
- Edit the script.
- Specify the version of the VDA to remove:
SET CHECK\_VDA\_VERSION. For example, version 7 can be specified as 7.0. The full value can be found on the installation media in the ProductVersion.txt file (such as 7.0.0.3018). However, a complete match is not required. - Optionally, specify a network share location for storing centralized logs.
- Specify the version of the VDA to remove:
- Using Group Policy Startup Scripts, assign the script to the OU containing your machines. This OU should contain only machines from which you want to remove the VDA. When the machines in the OU are restarted, the script runs on all of them. The VDA is removed from each machine.
Troubleshoot
-
The script generates internal log files that describe script execution progress. The script copies a
Kickoff_VDA_Startup_Scriptlog to the central log share within seconds of starting the deployment. You can verify that the overall process is working. If this log is not copied to the central log share as expected, troubleshoot further by inspecting the local machine. The script places two debugging log files in the%temp%folder on each machine:Kickoff_VDA_Startup_Script_<DateTimeStamp>.logVDA_Install_ProcessLog_<DateTimeStamp>.log
Review these logs to ensure that the script is:
- Running as expected.
- Properly detecting the target operating system.
- Correctly configured to point to the
ROOTof theDEPLOYSHAREshare (contains the file namedAutoSelect.exe). - Capable of authenticating to both the
DEPLOYSHAREandLOGshares.
-
For information about how Citrix reports the result of component installations, see Citrix installation return codes.
-
In the Studio display for a delivery group, the Installed VDA version entry in the Details pane might not be the version installed on the machines. The machine’s programs and features display shows the actual VDA version.
-
After a VDA is installed, it cannot deliver apps or a desktop to users until it registers with a Delivery Controller.
To learn about VDA registration methods and how to troubleshoot registration issues, see VDA registration.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.