Farm 编辑

Use the information in this section to configure a farm using the Citrix Provisioning console. This section includes information about the following elements:

• General Tab
• Security Tab
• Groups Tab
• Licensing Tab
• Options Tab
• Virtual disk Version Tab
• Status Tab

The tables that follow identify and describe properties on each tab of the Farm Properties dialog.

General tab

Security tab

Groups tab

Licensing tab

Options tab

Note:

The Send anonymous statistics and usage information checkbox, which enables the Customer Experience Improvement Program (CEIP), is no longer available.

Virtual disk version tab

Status tab

Using the console to configure a farm

Run the Configuration Wizard on a provisioning server when creating a farm, adding new provisioning servers to an existing farm, or reconfiguring an existing provisioning server.

If all provisioning servers in the farm share configuration settings such as site and store information, consider Running the Configuration Wizard Silently.

Configuration wizard settings

Before running the Configuration Wizard, be prepared to make the following selections:

• Network topology
• Identify the farm
• Identify the database
• Identify the site
• Citrix License Server settings
• Select Network Cards for the Stream Service
• Configure bootstrap Server

Note:

If errors occur during processing, the log is written to a ConfigWizard.log file, which is at C:\ProgramData\Citrix\Citrix Provisioning.

Tip:

The Configuration Wizard was modified at release 7.12 to include support for Linux streaming. See the installation article for information about the Linux streaming component.

Starting the configuration wizard

The Configuration Wizard starts automatically after Citrix Provisioning software is installed. The wizard can also be started by selecting Start > All Programs > Citrix > Citrix Provisioning > Citrix Provisioning Configuration Wizard.

Network topology

Complete the network configuration steps that follow.

1. Select the network service to provide IP addresses

   Note: Use existing network services if possible. If existing network services cannot be used, choose to install the network services that are made available during the installation process.

   To provide IP addresses to target devices, select from the following network service options:

   • If the Dynamic Host Configuration Protocol (DHCP) service is on this server, select the radio button next to one of the following network services to use, then click Next:
     • Microsoft DHCP
     • Citrix Provisioning BOOTP service
     • Other BOOTP or DHCP service
   • If the DHCP service is not on this server, select the radio button next to The service is running on another computer, then click Next.

2. Select the network service to provide PXE boot information

   Each target device downloads a boot file from a TFTP server.

   Select the network service to provide target devices with PXE boot information:

   • If you use Citrix Provisioning to deliver PXE boot information, select The service that runs on this computer. Then select from either of the following options, then click Next:
     • Microsoft DHCP (options 66 and 67)
     • Citrix Provisioning PXE Service
   • If Citrix Provisioning does not deliver PXE boot information, select The information is provided by a service on another device option, then click Next.

Identify the farm

1. Select from the following farm options:

   • Farm is already configured

     1. On the Farm Configuration dialog, select the option Farm is already configured, and click Next. This option appears only if a farm has been previously configured on this server.

     2. Enter database administrator credentials in the pop-up dialog. Select Active Directory Integrated authentication if you want to use the current login. Click Ok.

        

     3. Continue to the Configure user account settings procedure.

   • Create the farm

     1. On the Farm Configuration dialog, select the option Create a Farm, and click Next.
     2. On the Databse Server dialog,

        1. Use the Browse button to browse for existing SQL databases and instances in the network, or type the database server name and instance.

           

           Note:

           The combination of the database name and farm name must not exceed 54 characters. In such cases, the farm name displays as a truncated entry in the Existing Farms screen.

        2. To enable multi-subnet failover for SQL server, specify a database mirror failover partner, or enter a TCP port number, click Connection Options ….
        3. Select Active Directory Integrated authentication if you want to use the services’ user account. Enter the database credentials that the Stream and SOAP services will use.
        4. Click Next.

     3. Enter database administrator credentials in the pop-up dialog. Select Active Directory Integrated authentication if you want to use the current login. Click Ok.

        

     4. Select the database location.

   • Join an existing farm

     1. On the Farm Configuration dialog, select the option Join Existing Farm to add this provisioning server to an existing farm, then click Next.
     2. On the Databse Server dialog:

        1. Use the Browse button to browse for the appropriate SQL database and instance within the network.

        2. Select the farm name that displays by default, or scroll to select the farm to join. Note: More than one farm can exist on a single server. This configuration is common in test implementations.
        3. To enable multi-subnet failover for SQL server, specify a database mirror failover partner, or enter a TCP port number, click Connection Options ….
        4. Select Active Directory Integrated authentication if you want to use the services’ user account. Enter the database credentials that the Stream and SOAP services will use.
        5. Click Next.

     3. Enter database administrator credentials in the pop-up dialog. Select Active Directory Integrated authentication if you want to use the current login. Click Ok.

        

     4. Select from the following site options, then click Next:
        • Existing Site: Select the site from the menu to join an existing site.
        • New Site: Create a site by typing the name of the new site and a collection.
     5. Continue on to configure the user account settings.

Identify the database

Only one database exists within a farm. To identify the database:

1. If the database server location and instance have not yet been selected, complete the following procedure.

   1. On the Database Server dialog, click Browse to open the SQL Servers dialog.
   2. From the list of SQL Servers, select the name of the server where this database exists. Specify the instance to use (to use the default instance, SQLEXPRESS, leave the instance name blank). In a test environment, this configuration can be a staged database. Note: Rerunning the Configuration Wizard to add extra provisioning server database entries, populates the Server Name and Instance Name text boxes. By default, SQL Server Express installs as an instance named SQLEXPRESS.
   3. Select Active Directory Integrated authentication if you want to use the services’ user account. Enter the database credentials that the Stream and SOAP services will use.
   4. Click Next. If this database is a new farm, continue on to the Defining a Farm procedure.

2. To change the database to a new database

   1. On the old database server, perform a backup of the database to a file.
   2. On the new database server, restore the database from the backup file.
   3. Run the Configuration Wizard on each Citrix Provisioning server.
   4. Select Join existing farm on the Farm Configuration dialog.
   5. Enter the new database server and instance on the Database Server dialog.
   6. Select Active Directory Integrated authentication if you want to use the services’ user account. Enter the database credentials that the Stream and SOAP services will use.
   7. Select the restored database on the Existing Farm dialog.
   8. Select the site that the provisioning server was previously a member of on the Site dialog.
   9. Click Next until the Configuration Wizard finishes.

3. Define a farm. Select the security group to use:

   • Use Active Directory groups for security Note: When selecting the Active Directory group to act as the farm administrator from the menu, choices include any group the current user belongs to. This list includes Built in groups, which are local to the current machine. Avoid using these groups as administrators, except for test environments. Some group names might be misleading and appear to be domain groups, but are local domain groups. For example, ForestA.local/Builtin/Administrators.
   • Use Windows groups for security

4. Click Next.

   Continue on to select the license server.

Create a store for a new farm

A new store can be created and assigned to the Citrix Provisioning server being configured:

Note: The Configuration Wizard only allows a server to create or join an existing store if it is new to the database. If a server exists in the database and it rejoins a farm, the Configuration Wizard might prompt the user to join a store or create a store. During this process, the selection is ignored.

1. On the New Store page, name the new Store.
2. Browse or enter the default path (for example: C:\PVSStore) to use to access this store, then click Next. If an invalid path is selected, an error message appears. Reenter a valid path, then continue. The default write cache location for the store is located under the store path for example: C:\PVSStore\WriteCache.

Identify the site

When joining an existing farm, identify the site where this provisioning server is a member. Identify a site by either creating a site or selecting an existing site within the farm. When a site is created, a default target device collection is automatically created for that site.

Select the license server

1. Enter the name (or IP address) and port number of the license server (default is 27000). The provisioning server must be able to communicate with the license server to get the appropriate product licenses.
2. Optionally, select the check box Validate license server version and communication. This option verifies that the license server can communicate with this server and that the appropriate version of the license server is used. If the server is not able to communicate with the license server, or the wrong version of the license server is being used, an error message appears. You cannot proceed.
3. Click Next to continue on to configure user account settings.

Configure user account settings

The Stream and Soap services run under a user account. Configure data reader and data writer database roles automatically using the Configuration Wizard to provide database access privileges to a user account.

1. On the User Account dialog, select the user account that the Stream and Soap services run under:
   • Network service account (minimum privilege local account that authenticates on the network as computers domain machine account).
   • Specified user account (required when using a Windows Share; workgroup or domain user account). Type the user name, domain, and password information in the appropriate text boxes.
2. Click Next, then continue on to selecting network cards for the Stream Service.

Group managed service accounts

Citrix Provisioning supports Group Managed Service Accounts (gMSA). These accounts are managed domain accounts providing automatic password management and simplified SPN management over multiple servers.

Creating self-signed certificates for Linux streaming

When streaming Linux desktops, the Linux target devices must be linked to the provisioning Soap server via an SSL connection. The self-signed certificate must be present on the provisioning server.

Using the Citrix Provisioning Configuration Wizard, you can choose to add the proper certificate from the provisioning Soap container, specifically for Linux desktops.

Creating self-signed certificates with PoSH

Use the following PowerShell command (as an administrator) to create a self-signed certificate that is placed into the provisioning Soap container:

$PVS_SERVER_FQDN = "PVS-01.fqdn"
$CERT_FILE = "C:\ProgramData\Citrix\Provisioning Services\cert.cer"
<!--NeedCopy-->