Command-Line Tools
Tools are provided to enable you to install and remove controllers and the Virtual Desktop Agent using the command line. You can also use a command-line tool to configure Active Directory.
Installing and Removing Controllers Using Setup.exe
The Setup.exe file supports several command-line options for controlling the installation and removal of Desktop Delivery Controller.
If you control the installation through the command line, you must also configure Active Directory from the command line. For further information, see “Configuring Active Directory Using ADSetup” on page 122. You have to configure Active Directory not only when you create a new farm, but also when you add a controller to a farm.
Examples
The -passive option is an efficient way to install a large number of controllers compared with using the Installation wizard on individual controllers.
Example 1: Installing a Single Component
setup.exe -passive -components CONSOLES where CONSOLES (the management consoles) is the component you are installing.
Example 2: Installing all the Desktop Delivery Controller
Components on a Single Server setup.exe -passive -createfarm MyFarm
-components DDC,LIC_SERVER,CONSOLES
-edition STD
where:
MyFarm is the farm you are creating, DDC, LIC_SERVER, and CONSOLES are the components you are installing on the server, and you are licensed to use XenDesktop Standard Edition.
Example 3: Creating a New Controller and Adding it to a Farm
The following example shows how to create a new controller, installing only the core Desktop Deliver Controller component, and then add that controller to an existing farm that is using an external database on a separate server:
setup.exe -passive -joinfarm ele1985 -components DDC
-dsnfilepath c:\MF20.dsn -dbusername alexco -dbpassword libby02
where:
ele1985 is an existing controller in the farm, DDC is the component you want to install, c:\MF20.dsn is the path to the dsn file, alexco is the user name for accessing the database, and libby02 is the password for accessing the database.
In this example the MF20.dsn file was copied to the server before the installation process started.
Installing and Removing the Virtual Desktop Agent Using XdsAgent.msi
The Virtual Desktop Agent installer (XdsAgent.msi) supports the standard msiexec command-line options. For details of these options, go to:
http://msdn2.microsoft.com/en-us/library/aa367988.aspx
You can set the following properties as msiexec property arguments:
You must ensure that Microsoft .NET Framework 3.5 has already been installed before you install the Virtual Desktop Agent.
Configuring Active Directory Using ADSetup
configuration. You can use it to start the wizard described in “Configuring Active Directory” on page 50. You can also run it using any of the other parameters described in the table below.
Note: If you need to relocate or rename the farm OU, Citrix recommends that you use standard Active Directory management tools to do this.
Several of the options described in the table below refer to OU distinguished names. For more information about character-handling in these names, refer to:
http://msdn2.microsoft.com/en-us/library/aa366101(VS.85).aspx
and
http://www.ietf.org/rfc/rfc2253.txt
Tools are provided to enable you to install and remove controllers and the Virtual Desktop Agent using the command line. You can also use a command-line tool to configure Active Directory.
Installing and Removing Controllers Using Setup.exe
The Setup.exe file supports several command-line options for controlling the installation and removal of Desktop Delivery Controller.
If you control the installation through the command line, you must also configure Active Directory from the command line. For further information, see “Configuring Active Directory Using ADSetup” on page 122. You have to configure Active Directory not only when you create a new farm, but also when you add a controller to a farm.
Examples
The -passive option is an efficient way to install a large number of controllers compared with using the Installation wizard on individual controllers.
Example 1: Installing a Single Component
setup.exe -passive -components CONSOLES where CONSOLES (the management consoles) is the component you are installing.
Example 2: Installing all the Desktop Delivery Controller
Components on a Single Server setup.exe -passive -createfarm MyFarm
-components DDC,LIC_SERVER,CONSOLES
-edition STD
where:
MyFarm is the farm you are creating, DDC, LIC_SERVER, and CONSOLES are the components you are installing on the server, and you are licensed to use XenDesktop Standard Edition.
Example 3: Creating a New Controller and Adding it to a Farm
The following example shows how to create a new controller, installing only the core Desktop Deliver Controller component, and then add that controller to an existing farm that is using an external database on a separate server:
setup.exe -passive -joinfarm ele1985 -components DDC
-dsnfilepath c:\MF20.dsn -dbusername alexco -dbpassword libby02
where:
ele1985 is an existing controller in the farm, DDC is the component you want to install, c:\MF20.dsn is the path to the dsn file, alexco is the user name for accessing the database, and libby02 is the password for accessing the database.
In this example the MF20.dsn file was copied to the server before the installation process started.
Installing and Removing the Virtual Desktop Agent Using XdsAgent.msi
The Virtual Desktop Agent installer (XdsAgent.msi) supports the standard msiexec command-line options. For details of these options, go to:
http://msdn2.microsoft.com/en-us/library/aa367988.aspx
You can set the following properties as msiexec property arguments:
You must ensure that Microsoft .NET Framework 3.5 has already been installed before you install the Virtual Desktop Agent.
Configuring Active Directory Using ADSetup
configuration. You can use it to start the wizard described in “Configuring Active Directory” on page 50. You can also run it using any of the other parameters described in the table below.
Note: If you need to relocate or rename the farm OU, Citrix recommends that you use standard Active Directory management tools to do this.
Several of the options described in the table below refer to OU distinguished names. For more information about character-handling in these names, refer to:
http://msdn2.microsoft.com/en-us/library/aa366101(VS.85).aspx
and
http://www.ietf.org/rfc/rfc2253.txt
No comments:
Post a Comment