This article details how to configure a multi-homed virtual machine used by XenDesktop to separate data traffic from ICA traffic.

Note:  With new advancements in network infrastructure, such as 10 GB networking, multi-home virtual machines, specifically Provisioning Services (PVS) Server might not be an optimal solution and can lead to a more complicated network configuration and decrease network performance in some cases.

Tested Requirements

• XenServer 5.0 with 3 Network cards

• Windows Server 2008 Domain Controller

• Windows Server 2003 PVS Server 5.0 Service Pack 1 or greater

• Windows Server 2003 Desktop Delivery Controller

• Windows XP Service Pack 3

Instructions

The procedure configures the architecture as shown in the following diagram:

Note: This was tested on a standalone XenServer with no external or internal VLAN routing.

This procedure assumes that the XenServer is in a separate IP address range attached to its own NIC and Network. In this article, this network is called Xen-network.

1. In XenCenter, create and assign the NICs and networks as:

   1. NIC1: Network called "Xen-Network"

   2. NIC2: Network called "ICA-traffic"

   3. NIC3: Network called "PVS-traffic"

2. On the Domain Controller, attach NIC2 and NIC3 and assign two static IP addresses.

   These addresses must be on different IP address ranges.

   Example:

   NIC1: 192.168.8.4

   NIC2: 192.168.9.4

3. Configure two DHCP scopes which match the IP address ranges assigned to the network cards:

   1. DHCP Scope 1: Range 192.168.8.1 - 192.168.8.254

   2. DHCP Scope 2: Range 192.168.9.1 - 192.168.9.254

4. Configure DNS as appropriate with both a forward and reverse lookup zones.

5. On the PVS Server, attach the PVS-traffic network and the dedicated Xen-network. After the Virtual Machine (VM) has started, assign a static IP address to the PVS-network card which is in the 192.168.9.* range. Once this has been done, configure DHCP options 66 and 67 on DHCP Scope 2.

6. Install and configure PVS Server, then create a vDisk of at least 8GB.

7. On the Desktop Delivery Controller, attach the ICA-traffic and Xen-network cards and assign a static IP address within the appropriate range (192.168.8.*). Install and configure the Desktop Delivery Controller as appropriate.

8. On the Windows XP VM, attach both the ICA-traffic and PVS-traffic networks. After the machine has started, ensure that both NICs have a DHCP address assigned correctly. No extra configuration is necessary to the Windows routing table. See Additional Resources for details about correct order for adding the networks.

9. In the PVS Server console, create a new device, and assign it the MAC address of the PVS-traffic NIC, which is attached to the Windows XP VM being used. After this has been created, attach the vDisk created in Step 6.

10. Install the VDA on the XP VM and restart. Install the PVS Server target device software. During the end of this installation, you will be prompted to select a network card for PVS Server to use, ensure you choose the PVS-traffic NIC.

11. Modify the vDisk into Standard Mode within the PVS Console.

12. Create a new desktop pool in the Desktop Delivery Controller and add the XP virtual desktop.

13. Check that the machine has registered and you are now able to start the desktop.

    Note: This configuration also works with the XenDesktop Setup Wizard. When using the preceding steps, follow the standard practices for creating a desktop pool using the XenDesktop Setup Wizard.

The order in which the NICs are added to the Template or the Virtual Machine used for cloning determines which NIC to use for PXE booting.

• For XenServer: Ensure that the Template has the NIC you would like to use for PXE booting added first to the list of NICs.

• For VMware: Ensure that the Template has the NIC you would like to use for PXE booting added first to the list of NICs. Also, ensure that this NIC is the first entry in the boot order within the BIOS.

• For SCVMM: Ensure that the NIC you would like to PXE boot from is the first Emulated or Legacy NIC attached to the Virtual Machine.

No​te: Although this was tested with the preceding configuration, the same principles apply for a physical environment.