Configuring the 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 (described in detail below):

• Network Topology
• Identify the Farm
• Identify the Database
• Identify the Site
• 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\Provisioning Services.

Starting the Configuration Wizard

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

Tip

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

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 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
     • Provisioning Services 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 needs to download a boot file from a TFTP server.

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

   • If you choose to use this Provisioning Server 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)
     • Provisioning Services PXE Service
   • If Provisioning Services will 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

     Select this option to reconfigure an existing farm, then continue on to the “Configure user account settings” procedure. This option only appears if a farm exists.

   • Create farm

     1. On the Farm Configuration dialog, select the Create Farm radio button to create a farm, then click Next.
     2. Use the Browse button to browse for existing SQL databases and instances in the network, or type the database server name and instance. Optionally, enter a TCP port number to use to communicate with this database server. Note: The combination of the database name and farm name should not exceed 54 characters, otherwise the farm name may display truncated in the Existing Farms screen.
     3. To enable database mirroring, enable the Specify database mirror failover partner option, then type or use the Browse button to identify the failover database server and instance names. Optionally, enter a TCP port number to use to communicate with this server.
     4. Click Next to continue on to select the database location.

   • Join existing farm

     1. On the Farm Configuration dialog, select the Join Existing Farm radio button to add this Provisioning Server to an existing farm, then click Next.
     2. Use the Browse button to browse for the appropriate SQL database and instance within the network.
     3. 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.
     4. To enable database mirroring, enable the Specify database mirror failover partner option, then type or use the Browse button to identify the failover database server and instance names. Optionally, enter a TCP port number to use to communicate with this server.
     5. Click Next.
     6. Select from the following site options, then click Next:
        • Existing Site: Select the site from the drop-down menu to join an existing site.
        • New Site: Create a site by typing the name of the new site and a collection.

     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:

   • On the Database Server dialog, click Browse to open the SQL Servers dialog.
   • From the list of SQL Servers, select the name of the server where this database exists and the instance to use (to use the default instance, SQLEXPRESS, leave the instance name blank). In a test environment, this may be a staged database. Note: When rerunning the Configuration Wizard to add more Provisioning Servers database entries, the Server Name and Instance Name text boxes are already populated. By default, SQL Server Express installs as an instance named ‘SQLEXPRESS’.
   • Click Next. If this is a new farm, continue on to the “Defining a Farm” procedure.

2. To change the database to a new database:

   • On the old database server, perform a backup of the database to a file.
   • On the new database server, restore the database from the backup file.
   • Run the Configuration Wizard on each Provisioning Server.
   • Select Join existing farm on the Farm Configuration dialog.
   • Enter the new database server and instance on the Database Server dialog.
   • Select the restored database on the Existing Farm dialog.
   • Select the site that the Server was previously a member of on the Site dialog.
   • 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 drop-down list, 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. Also, be aware that some group names may 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 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 may prompt the user to join a store or create a store, but 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 to be a member, 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 to verify that the license server is able to communicate with this server and that the appropriate version of the license server is being 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 displays and does not allow you to 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. To provide database access privileges to this user account, Data reader and Data writer database roles are configured automatically using the Configuration wizard.

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 selection network cards for the Stream Service.

Creating self-signed certificates for Linux streaming

When configuring Provisioning Services for streaming Linux Desktops, the Linux target devices must be linked to the PVS Soap server via an SSL connection. The CA certificate must be present on both the PVS server and the target device.

Using the PVS Configuration Wizard, you can choose to add the proper certificate from the PVSSoap container, specifically for Linux Desktops.

Creating self-signed certificates with PoSH

To create a certificate:

1. Use the following PowerShell command (as an administrator) to create a self-signed certificate that will be placed into the PVSSoap container:

#New-SelfSignedCertificate –Type SSLServerAuthentication –Container PVSSoap –Subject “CN=PVS-01.fqdn” –CertStoreLocation “Cert:\LocalMachine\My” –KeyExportPolicy Exportable
<!--NeedCopy-->