HP ConvergedSystem 100 for Hosted Desktops Getting …The Citrix PVS server is a key technology for...

HP ConvergedSystem 100 for Hosted Desktops Getting Started Guide

Abstract This document provides information on the deployment and configuration of HDI using the HP ProLiant Moonshot m700 server cartridge for Hosted Desktops integrated into an existing Citrix XenDesktop environment. The intended audience for this guide includes system and network administrators. It is assumed that you have a working set of virtual or physical desktops, existing database servers, and license servers.

Part Number: 752097-002 January 2014 Edition: 2

© Copyright 2013, 2014 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

Microsoft®, Windows®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation. AMD is a trademark of Advanced Micro Devices, Inc.

Contents 3

Contents

Overview ..................................................................................................................................... 5 Hosted Desktop Infrastructure ........................................................................................................................ 5 Citrix XenDesktop ......................................................................................................................................... 5

Citrix components and deployments ..................................................................................................... 5 Citrix PVS server ................................................................................................................................ 7 Citrix HDX ......................................................................................................................................... 8

HP Moonshot system HDI software and hardware............................................................................. 9 HP Moonshot system HDI software ................................................................................................................. 9 HP Moonshot 1500 chassis ........................................................................................................................... 9

Shared power and cooling ................................................................................................................ 10 Shared management ........................................................................................................................ 10 Shared networking ........................................................................................................................... 10

HP ProLiant m700 Server Cartridge ............................................................................................................. 11 Cartridge SoCs ................................................................................................................................ 11 Kyoto node features ......................................................................................................................... 12 GPU/APU ....................................................................................................................................... 13 Storage ........................................................................................................................................... 13 Networking ..................................................................................................................................... 13 BIOS ............................................................................................................................................... 13

HP Moonshot system CLIs ............................................................................................................................ 14 HP Moonshot iLO Chassis Management firmware CLI .......................................................................... 14 HP Moonshot switch CLI .................................................................................................................... 14

HP Moonshot system HDI deployment configurations ...................................................................... 15 Deployment types ....................................................................................................................................... 15 PoC configuration ...................................................................................................................................... 15

PoC networking ............................................................................................................................... 15 PoC supporting systems .................................................................................................................... 16

Production configuration ............................................................................................................................. 16 Production networking ...................................................................................................................... 16 Production supporting systems ........................................................................................................... 17

PVS network topologies .............................................................................................................................. 17 Domain/PVS combined .................................................................................................................... 17 Domain/PVS separated .................................................................................................................... 18 Domain/PVS teamed ........................................................................................................................ 18

HP Moonshot system HDI integration with Citrix XenDesktop ............................................................ 20 Integration overview ................................................................................................................................... 20 Support server setup ................................................................................................................................... 20

PVS server ....................................................................................................................................... 20 DHCP server .................................................................................................................................... 20

Preparing a VM for PVS installation ............................................................................................................. 20 Installing Citrix PVS .................................................................................................................................... 21 Configuring the PVS console ....................................................................................................................... 33 Creating a PVS desktop image .................................................................................................................... 37

Windows Deployment Services network configuration .......................................................................... 38

Contents 4

Cartridge node boot configuration ..................................................................................................... 38 Deploying Microsoft Windows on HP ProLiant m700 Server Cartridge .................................................. 38 PVS network configuration ................................................................................................................ 38 Device driver installation ................................................................................................................... 38 AMD GPU driver .............................................................................................................................. 38 Broadcom BACS utility ...................................................................................................................... 39 Citrix XDT VDA installation ................................................................................................................ 39 PVS client installation ........................................................................................................................ 39 PVS Convert Wizard ........................................................................................................................ 43 vDisk image publication .................................................................................................................... 51 Application installation ..................................................................................................................... 52

Image maintenance .................................................................................................................................... 52 PVS console integration .............................................................................................................................. 52

Moonshot specific device node creation ............................................................................................. 53

HP Moonshot system HDI sample scripts ........................................................................................ 60 HP Moonshot tools for PowerShell ................................................................................................................ 61

HP Moonshot tools set up .................................................................................................................. 61 HP Moonshot tools functions .............................................................................................................. 61

Moonshot CM script examples .................................................................................................................... 66 Setting all nodes to PXE boot ............................................................................................................. 66 Preparing nodes for WDS imaging .................................................................................................... 66

Moonshot switch script examples ................................................................................................................. 67 Configuring VLANs .......................................................................................................................... 67 Preparing NICs for WDS deployment ................................................................................................. 70

Support and other resources ........................................................................................................ 72 Additional information ................................................................................................................................ 72 HP contact information ................................................................................................................................ 72

Acronyms and abbreviations ........................................................................................................ 73

Documentation feedback ............................................................................................................. 77

Index ......................................................................................................................................... 78

Overview 5

Overview

Hosted Desktop Infrastructure HDI provides users a Microsoft Windows desktop by using high-density, unshared desktop images running in an enterprise environment. These desktop images run on dedicated, unshared hardware. End users remotely access the desktop image using a combination of a thin client and a monitor that are located on a local desktop. HDI leverages the HP Project Moonshot server platform to provide these dedicated desktops. The HP Moonshot System HDI solution leverages the latest SoC from AMD with built-in GPU/APU. This enables delivery of a natural desktop video experience, all in a low power envelope with high density. The following sections describe the parts of this platform that are leveraged for HDI.

Citrix XenDesktop Citrix XenDesktop provides a complete delivery model for virtual/remote desktops. The HP Moonshot System HDI solution uses this technology to manage HDI dedicated desktops.

Citrix components and deployments The Citrix-Moonshot System HDI deployment is similar to a standard Citrix deployment model. It includes a Moonshot desktop element added to indicate management through XenDesktop management tools. HDI desktops are offered to users with the same brokering tools as XenDesktop. The following figure illustrates the key components of a typical Citrix-Moonshot System HDI deployment.

Overview 6

Citrix deployments contain several compute elements that deliver an HDI experience. Some of these are commonly found in enterprise environments with domain controllers, DNS services, and DHCP services. Citrix XenDesktop elements, such as Studio and Storefront, can run on separate servers or run on the same server. They can also be set up as VMs. The following figure illustrates the components of a Citrix deployment.

Overview 7

Citrix PVS server The Citrix PVS server is a key technology for enabling Moonshot System HDI. Citrix PVS streams a complete OS and application image to desktops running in both virtual and physical environments. The vDisk image can be shared by many desktops, becoming a common read repository. Desktops can write to many different locations, including local disk, memory, or back to the PVS server; however, this is recommended for image maintenance only. Moonshot nodes do not have the local storage capacity to host a complete desktop, but do have enough fast storage to act as write cache. Reads from the Citrix PVS server are usually cached in memory and local read/write traffic is cached to iSSD, which results in good desktop disk performance. The following figure illustrates how to boot a cartridge with an OS image streaming from a Citrix PVS server.

Overview 8

A multi-site PVS farm is comprised of several compute elements. Some of the elements are the same as those illustrated in the previous figure, and are generally shared, such as the database server, license server, and active directory. Additionally, other compute elements can run in the enterprise or are specific to the PVS. The following figure illustrates a multi-site PVS farm.

Citrix HDX Citrix HDX provides remote thin clients the capability to access remote desktop PC images running in a variety of environments, including bare metal remote PCs and HDI desktops. The standard HDX protocol, starting with XenDesktop version 7.1, has assimilated a key feature from HDX VDA providing higher performance graphics from DirectX applications. This enables thin clients to access a high performance graphics environment as long as the hosted machine is equipped with GPU support. Built-in GPU hardware is a key feature of the HP Moonshot System HDI solution.

NOTE: The HDX driver updates may be required to enhance the user experience within HDX on HP ProLiant m700 server cartridges. The 64-bit hotfix can be found at: http://support.citrix.com/article/CTX139622 (http://support.citrix.com/article/CTX139622)

http://support.citrix.com/article/CTX139622�

HP Moonshot system HDI software and hardware 9

HP Moonshot system HDI software and hardware

HP Moonshot system HDI software The HP Moonshot system HDI solution requires the following software for successful installation and deployment.

Software Description Version

Moonshot Firmware Entire Moonshot firmware recipe for HP ProLiant m700 server cartridges, chassis, and switches

http://www.hp.com/go/moonshot/download (http://www.hp.com/go/moonshot/download)

Windows 7 Enterprise SP1

MSDN or VL ISO from Microsoft containing the Windows 7 Enterprise Edition with SP1 slipstreamed

—

WinPE Installation OS for Windows. This is resident on the installation ISO in the boot.wim. Using version later than 3.0 may cause issues with Citrix VDA installation.

3.0 only

Citrix XenDesktop XenDesktop distributed by Citrix 7.1 or later

Moonshot PowerShell Tools

Tools to aid in management of Moonshot chassis and integration with Citrix XenDesktop

1.8 or later

m700 NIC Driver Broadcom network device driver for the BCM5720

16.2.0.4

BACS Utility Broadcom administration utility for their device driver software stack

16.3.1.0

AMD GPU Driver AMD graphics device driver to enable high performance video

13.200.0.0

HP Moonshot 1500 chassis The HP Moonshot 1500 chassis provides several shared functions that are leveraged by HDI solutions. The following figure illustrates the key components of the chassis.

http://www.hp.com/go/moonshot/download�

http://www.hp.com/go/moonshot/download�


Item Component

1 Five fans, dual-rotored, rear-serviceable shared/hot-plug fans

2 Redundant switches

3 Four HP common-slot power supplies

4 Single federated iLO CM module

Shared power and cooling The HP Moonshot 1500 chassis supports up to four 1500 W hot-plug power supplies for N+1 redundancy. The chassis also supports five hot-plug fan modules, each containing two fans, for a total of ten. The HP Moonshot 1500 chassis also supports advanced power management using the SL-APM and HP power distribution for racks.

Shared management The HP Moonshot 1500 chassis has an integrated management network that provides command line access to view status and control resources. The HDI solution comes with a set of PowerShell scripts to view desktop management and enable the integration of application management environments. For sample scripts, see HP Moonshot system HDI sample scripts (on page 60). for a complete OS image before it is moved to the Citrix XenDesktop PVS server. After the image is in PVS and being streamed to m700 nodes, the storage is used as a local write cache.

Shared networking The HP Moonshot 1500 chassis can accommodate up to two hot-plug Ethernet switches. Most deployment models for HDI deploy with two switches. Each m700 node has two NICs. One NIC is connected to Switch A, and one NIC is connected to Switch B. This enables dual active/active teaming, failover support, and 2 GB of aggregate bandwidth. Each switch has 180 downlink ports, one for each node. This provides a total of 360 1 GB downlink ports.

Both switches have a corresponding uplink module, each with four 40 GB QSFP+ uplink ports. You can use these ports for switch stacking and uplinks to a ToR or network core switch.


Item Component

1 Uplink module A

2 Switch module A

3 Cartridges

4 Switch module B

5 Uplink module B

HP ProLiant m700 Server Cartridge The HP ProLiant m700 server cartridge is the centerpiece of the HDI solution. This cartridge has four AMD Kyoto class SoCs on each cartridge. Each SoC represents a complete desktop computing environment with features that are commonly found on desktop computers. A Moonshot 1500 chassis holds between 15 to 45 m700 cartridges in 4.3U of rack space. The following figure illustrates the key components of the HP ProLiant m700 server cartridge.

Item Component

1 Four AMD Kyoto CPUs

2 Four 8 GB SORDIMMs (located on back of cartridge)

3 Four 32 GB iSSD (SATA connected)

Cartridge SoCs Each HP ProLiant m700 server cartridge has four AMD Kyoto SoCs, or nodes. Each node has the following specifications:

• 8 GB of RAM

• 32 GB of SATA attached iSSD disk

• Two 1 GB network interfaces.


The nodes "share nothing” with other nodes on the cartridge. The following figure shows the components of an AMD Kyoto node.

Kyoto node features The AMD Kyoto SoC is a low-power, highly-integrated desktop-on-a-chip with the following features:

• Power efficient cores

o Four next-gen Jaguar cores with 1 MB shared L2 cache

o Core and Northbridge P-States

o C-States: CC1/CC6 and PC6

o DDR3 Memory P-States

• High performance memory

o Single channel 64-bit DDR3 controller with ECC support

o Two DIMMs per channel up to 1600MHz speeds

o 1.25 V, 1.35 V and 1.5 V UDIMM and SODIMM

• Efficient I/O

o One 8x PCIe Gen 2 lanes

o Four x1 links for GPP

o One x4 link

• Power management

o Core and Northbridge P-States

o C-States: CC1/CC6 and PC6

o DDR3 Memory P-States

• Integrated SCH

o 2x SATA 2/3 ports

o 2x USB 3.0 and 8x USB 2.0

o SPI, LPC interfaces


• 28nm process technology

o 15 W total die TDP

The following figure illustrates the key components of the AMD Kyoto SoC.

GPU/APU The AMD Kyoto SoC has an 8400 Sea Islands GPU core with DCE 8.3, UVD 4.2, VCE 2.0, and SAMU 1.2. This GPU supports both OpenGL 4.1 (not supported with standard Citrix VDA) and DX11.1. The screen buffer resides in system and is accessed remotely by protocols for transmission to user desktops. The Citrix solution uses HDX (Microsoft RDP) for standard connectivity to lower-end thin clients and HDX, which provides high performance graphics to high-end thin clients.

Storage Each node connects to a 32 GB iSSD that offers high performance storage for each desktop node. The system uses this storage in multiple ways. Microsoft Windows 7 Enterprise with SP1 (x64) is deployed as a complete OS image before it is moved to the Citrix XenDesktop PVS server. The storage is used as a local write cache once the image is streaming from the PVS to the m700 nodes.

Networking Each m700 node is connected to a Broadcom 5720 NIC that has two 1 GB network ports. Advanced functionality is managed by the Broadcom BACS network management utility. Functionality includes Teaming and VLAN support.

BIOS All nodes on the HP ProLiant m700 server cartridge share the BIOS image. The iLO CM firmware sets the BIOS options before node power-on. The iLO CM firmware currently allows the selection of a PXE or HDD boot.


HP Moonshot system CLIs

HP Moonshot iLO Chassis Management firmware CLI Management for the cartridges and the chassis is performed through the HP Moonshot iLO CM firmware CLI. This interface is accessed by administrators in the following ways:

• Locally, using a serial cable

• Remotely, using SSH

For easy access, this interface should be defined in DNS with a static IP address.

PowerShell scripts can also be used when deploying cartridge configurations.

For more information, see the HP Moonshot iLO Chassis Management CLI User Guide on the HP Moonshot System website (http://www.hp.com/go/moonshot/docs).

HP Moonshot switch CLI The HP Moonshot switch CLI can be accessed in the following ways:

• Locally using a serial console cable

• Remotely using SSH

• Remotely using the iLO CM firmware VSP feature

For sample network configuration and maintenance scripts, see "HP Moonshot system HDI sample scripts (on page 60)."

Moonshot switches support SNMP and sFLOW for management and configuration. For more information, see the switch documentation in the HP Moonshot Information Library (http://www.hp.com/go/moonshot/docs).

http://www.hp.com/go/moonshot/docs�


HP Moonshot system HDI deployment configurations 15

HP Moonshot system HDI deployment configurations

Deployment types There are two basic deployment types: PoC and full high availability. This document focuses on the PoC version.

PoC configuration The PoC configuration consists of a single HP Moonshot System chassis with a compliment of a minimum of 15 m700 cartridges (60 desktops) to a maximum of 45 m700 cartridges (180 desktops). HP recommends deploying this chassis with two 180-port 1 GB switches. The following figure illustrates the HDI PoC deployment model.

PoC networking HP recommends using a management network when configuring and controlling HP Moonshot nodes and switches. It is also very useful when managing ToR switches and any servers in the configuration, such as a 1 GB RJ45-based Ethernet network, separate from all data networks.

Use Switch A to deliver PVS network traffic. PVS nodes use PXE boot and m700 nodes always try to boot from NIC-A first. Therefore, delivering PVS using Switch A provides the quickest boot possible. To achieve the best disk performance, use Switch A and a NIC-A for PVS traffic only.

Use Switch B to deliver domain traffic, user data traffic, and general internet traffic. HP recommends using the available VLANs for advanced production deployments.


PoC supporting systems With a complete and working Citrix XenDesktop environment already installed and functional, you only need a PVS server to stream desktop OSs to the HP Moonshot 1500 chassis. The PVS server can be a virtual machine, but tends to scale better on non-virtualized platforms. HP recommends the following minimum configuration:

• 1P AMD processor

• 128 GB RAM

• 600 GB RAID10 SAS storage

• 10 GB NIC for the PVS network

• 1 GB NIC for the management network

• Microsoft Windows Server 2012 with Hyper-V

Production configuration Production Moonshot System HDI deployments are sometimes very large, including up to eight Moonshot 1500 chassis enclosures in a single rack. A rack is considered the largest building block for large deployments and includes ToR switching and redundant PVS servers. Network configuration for this model is significantly more complex, requiring NIC teaming and VLANs to properly deploy. The following figure illustrates the HDI high availability deployment model.

Production networking You need a hardware management network to configure and control Moonshot System nodes and networking. The hardware management network is also very useful in managing ToR switches and any


servers in the configuration. Usually this includes a 1 GB RJ45-based Ethernet network, separate from all data networks.

To support PXE functionality, make sure that Switch A and Switch B run identical, trunked VLANs with the PVS network as the native untagged network. All other networks should be presented to both NIC-A and NIC-B with these NICs teamed in active/active mode to provide performance and high availability.

Production supporting systems With a complete and working XenDesktop environment installed and functional, the configuration requires only a PVS server to stream desktop operating systems to the HP Moonshot 1500 chassis. The PVS server can be a virtual machine, but PVS generally scales better on a non-virtualized platform. The following list provides the recommended minimum configuration for a production supporting system:

• 1P AMD processor

• 64 GB RAM

• 300 GB RAID10 SAS storage

• 10 GB NIC for the PVS network

• 1 GB NIC for the management network

• Microsoft Windows Server 2012 with Hyper-V

PVS network topologies There are three distinct PVS network topologies to consider using when deploying HP Moonshot System HDI:

• Domain/PVS combined

• Domain/PVS separated

• Domain/PVS teamed

For PoC use the Domain/PVS combined topology or the Domain/PVS separated topology. The Domain/PVS teamed topology uses teamed NICs with trunked VLANs, which is more difficult to set up.

Domain/PVS combined One of the easiest deployment models for PVS is to place the streaming network on the same network as the XenDesktop domain. This requires setting DHCP scope options on the domain DHCP server to include options 66 and 67. For information, see the Citrix PVS documentation and installation utilities on the Citrix website (http://support.citrix.com/proddocs/topic/infocenter/ic-how-to-use.html).

http://support.citrix.com/proddocs/topic/infocenter/ic-how-to-use.html�


XenDesktop environments typically require user data storage delivered using CIFS shares. This storage can also be used by the PVS server for storing vDisk files. Depending on the core network configuration, enabling this functionality might require another network tap in the PVS server.

Domain/PVS separated Separating the PVS network from the domain and data networks can provide a performance advantage and isolate the PXE protocol that PVS uses to boot nodes. This configuration requires installing DHCP and PXE/TFTP on the PVS server. HP recommends selecting Provisioning Services PXE during the PVS server configuration provided by Citrix.

XenDesktop environments typically require user data storage, which is delivered through CIFS shares. The PVS server can also use this storage for vDisk files. Depending on the core network configuration, enabling the PVS server storage requirements might mean including another tap in the PVS server.

Domain/PVS teamed The domain/PVS teamed configuration provides high availability, but is more difficult to set up, primarily because of additional switch configuration, NIC teaming, and VLAN definitions that must be configured in


the machine image. Configure both switches to deliver identical VLAN trunks to their consuming node NICs. Use the Broadcom BACS utility to define the NICs as a team with the PVS network as the untagged network on the trunk. Surface all other networks used by the node as tagged VLANs.

For a detailed discussion of this configuration and initial PVS image creation, see Creating a PVS desktop image (on page 37).

HP Moonshot system HDI integration with Citrix XenDesktop 20

HP Moonshot system HDI integration with Citrix XenDesktop

Integration overview PVS scales with the desktop environment. As additional desktops are added to the environment, additional PVS support servers are needed. PVS servers should be located near the HP Moonshot 1500 chassis to keep PVS traffic off of the core network.

Assuming that PVS must be deployed with the HP Moonshot System, this section describes the integration of a new PVS server into the environment. Customers using XenDesktop should be familiar with this process. A few key points are specific to Moonshot, such as Moonshot node import as devices and node power control and monitoring.

NOTE: The following procedures assume a XenDesktop environment is installed. You must have a working set of virtual or physical desktops, existing database servers, and license servers.

Support server setup

PVS server When configuring the PVS server, be sure the network interface connecting to the PVS network is assigned an available static IP address to support PXE boots and PVS streaming.

DHCP server When configuring the DHCP server with scope options for the PVS subnet, use the following options to configure the DHCP scope:

• Option 66: Boot Server Host Name

String value: IP address of the PVS server

• Option 67: Bootfile Name

String value: ARDBP32.BIN

Preparing a VM for PVS installation Prepare a virtual machine to deliver provisioning services:

1. Assign at least 500GB of virtual hard disk space for the PVS server. Configure the vDisk store using Independent and Persistent options (do not use dynamic disk).

2. Install Microsoft Windows Server 2012.

3. Assign a static IP address to the VM. Verify that the IP address is available for use on the PVS network.


4. Join the VM to the domain where provisioning services are required.

5. Verify that the FQDN is in use.

6. Log on to the VM using the <PVS domain>\Administrator account.

Installing Citrix PVS 1. Copy the Citrix installer bits from the following directory to the PVS server:

\\talldog\Citrix\PVS-XD7\Citrix Partner Access - XD7 RTM\PVS7 RTM to the PVS server.

2. Launch Autorun.exe.

3. Start the Console Installation and install the PVS console using the default settings.

4. To install the PVS server, start the Server Installation, and then select Install Server.

5. Start the Provisioning Services Configuration Wizard, and then click Next.

6. When prompted by the DHCP Services screen, select one of the following options that matches your

DHCP configuration and then click Next:

o If DHCP services are running on the PVS server, select The service that runs on this computer along with the appropriate DHCP service.

o If DHCP services are running on a different system, select The service that runs on another computer.

NOTE: In this example, the DHCP service is running on this PVS server.


7. On the PXE Services screen, select the appropriate DHCP option based on the current configuration,

and then click Next.


8. On the Farm Configuration screen, select Create farm, and then click Next.

9. On the Database Server screen, enter the FQDN of the SQL server in the Server name field, and then

click Next.


Do not enter information into the Instance name or Optional TCP port fields. If configuring mirroring for the PVS database, select Specify database mirror failover partner and enter the FQDN of the partner SQL server. This option requires that you have previously configured SQL mirroring.


10. On the New Farm screen, enter data for the first four fields, select Use Active Directory groups for security, and then click Next.


11. On the New Store screen, enter the vDisk Store name and Default path for vDisks storage, and then click Next.

12. Verify the vDisk location has sufficient disk space for vDisk storage.


13. On the License Server screen, enter the FQDN of the license server, whether local on this system or remote on another system, select Validate license server version and communication, and then click Next.


14. On the User Account screen, select Specified user account, enter the domain administrator credentials, and then click Next.

15. On the Active Directory Computer Account Password screen, click Next to accept the default settings.


16. On the Network Communications screen, select the network interfaces used for streaming vDisks and accessing the PVS console, and then click Next.

In this example, the 172.25.0.18 network is used for streaming vDisks, and the 172.20.0.18 network is used for Active Directory, PVS management, and accessing the PVS console.


17. On the TFTP Option and Bootstrap Location screen, select Use the Provisioning Services TFTP service, and then click Next.

18. On the Stream Servers Boot List screen, select the PVS server that responds to the PXE boot requests.

NOTE: Using multiple PVS servers and NetScaler for load balancing requires additional configuration of NetScaler and Load Balancing.


19. Click on the PVS server, and then click Edit.

20. In the Device section of the Network Address screen, verify that the subnet mask is correct, and then

click OK.

21. On the Stream Servers Boot List screen, click Advanced and enable Verbose Mode. Click OK, and then

click Next.


This provides output text on the client during the PXE boot process for debugging purposes.

22. On the Finish screen, verify the settings, and then click Finish.


23. On the Finish screen, click Done.

Configuring the PVS console The PVS console is installed as part of the PVS Server installation. You can install the PVS console on other systems, however, that is outside the scope of this documentation. If installed on other servers, administrators can manage multiple farms from a desktop without directly logging into the PVS servers.


1. From the Start Menu, open the Provisioning Services Console.


2. Right-click Provisioning Services Console, and then select Connect to Farm.


3. On the Connect to Farm screen, enter the FQDN of the PVS server in the Name field, and then click Connect.


After the connection is made, the previously configured Sites, Device Collections, and Stores groups populate under the Farm.

The PVS server is ready for streaming vDisks to device clients.

Creating a PVS desktop image The following steps must be performed to create and import a deployable image to the Citrix PVS server:

1. Configure the switch port VLANs, if needed.

2. Configure the node boot order.

3. Install Microsoft Windows 7 Enterprise with SP1 (x64) using Windows Deployment Services.

4. Restore the switch port VLANs, if needed.

5. Using RDP, remote in to the OS and install the following:

o Standard drivers

o AMD GPU driver

o Broadcom BACS utility

o Additional applications

o Citrix VDA

o Citrix PVS client

6. Capture the image using the Citrix PVS client to the PVS server.


Windows Deployment Services network configuration You must change the imaging node networking by removing it from the PVS PXE network and placing it on the Windows Deployment Services PXE network. Microsoft recommends maintaining both NICs on the same network as the Windows Deployment Services because the binding order of NICs cannot be guaranteed at boot time.

Cartridge node boot configuration Change the node boot order to boot once from PXE, then from the iSSD by default. To change the boot sequence, log in to the iLO CM firmware and enter the following commands:

SET NODE BOOT HDD <CxNy> SET NODE BOOTONCE PXE <CxNy>

where C is the cartridge number and N is the node, for example, C1N1.

Deploying Microsoft Windows on HP ProLiant m700 Server Cartridge

For documentation on how to setup and install Microsoft Windows on an HP ProLiant m700 server cartridge, see the Operating System Deployment on HP ProLiant Moonshot Server Cartridges guide in the HP Moonshot Information Library (http://www.hp.com/go/moonshot/docs).

This guide describes using Microsoft Windows Deployment Services (WDS) as an example utility to deploy Microsoft Windows to an HP ProLiant m700 server cartridge. The guide also contains information on the installation and use of the Server Administration Console, which enables serial support for installation, runtime logging, and administration of any streaming images to a node.

PVS network configuration After the node is imaged with Windows Deployment Services, you must reconfigure the Moonshot network switches to put the node back on the PVS and production networks before continuing with the image creation.

Device driver installation After the base image is loaded on the iSSD drive, you must install other drivers to enable full hardware functionality.

AMD GPU driver Install the AMD GPU driver to support high performance video. This driver package comes in two forms, one with the Catalyst management GUI, and one without. The full package enables detailed control of the graphics environment. The package without Catalyst is smaller and installs more quickly. Because most installations do not require Catalyst, you can install the smaller package. This package includes other important drivers for embedded hardware functions. HP strongly recommends that you install one of these driver packages, such as Supports SATA, USB, SMBus, and so on.



Broadcom BACS utility The Broadcom NIC driver is installed during Windows Deployment Services deployment and does not need to be updated. If advanced networking features are necessary, install the BACS management utility.

Citrix XDT VDA installation HP recommends installing Citrix HDX to support high performance graphics on the user desktop. For more information about the installation of this software package, see the Citrix eDocs website (http://support.citrix.com/proddocs/topic/infocenter/ic-how-to-use.html).

PVS client installation The PVS client software is found in the XenDesktop distribution from Citrix. Using RDP, log in to the node used for image creation. To locate, mount, and run the PVS client software:

1. Run autorun.exe.

2. On the Provisioning Services screen, select Target Device Installation.

3. Select Target Device Installation again.

NOTE: This documentation assumes that you have installed a XenDesktop environment prior to completing these procedures. You must have a working set of virtual or physical desktops, existing database servers, and license servers.



4. On the Welcome screen, click Next.


5. On the License Agreement screen, select I accept the terms in the license agreement, and then click Next.

On the Customer Information screen, enter the User Name and Organization.

6. Select Anyone who uses this computer (all users), and then click Next.


7. On the Destination Folder screen, accept the default installation location or change it to your preferred location, and then click Next.

8. On the Ready to Install the Program screen, click Install.


9. On the Installation Wizard Completed screen, clear the Launch Imaging Wizard checkbox, and then click Finish.

10. On the Restart screen, click Yes.

The image creation node reboots.

PVS Convert Wizard 1. After the PVS imaging reboot, use RDP to log in to the node as the domain administrator.

2. From the Windows Start menu, click Imaging Wizard.


3. On the Welcome to the Imaging Wizard screen, click Next.

4. On the Connect to Farm screen, enter the PVS server details in the Server information section, and then

click Next.


5. On the Select New or Existing vDisk screen, select Create new vDisk, and then click Next.

6. On the New vDisk screen:

a. Enter the vDisk name you want to assign.

b. In the Store field, select the PVS Store to save the disk image.

c. Change the vDisk type to Static.


d. Click Next.

7. On the Microsoft Volume Licensing screen, select the licensing model used by your organization, and

then click Next.

8. On the Configure Image Volumes screen:

a. In the Source Volume column in row 1, select C: (Windows) Boot.


b. In the Source Volume column in rows 2, 3, and 4, select None.

c. If needed, in the Free Space column, increase the size of free space for the C: (Windows) Boot drive. Click Next.

The sum of used and free space equals the total capacity of the c:\ drive.

9. On the Add Target Device screen, enter the target device name for this m700 node, such as

MS02_c3n1.

NOTE: The target device name is the name of the device connecting to the vDisk in PVS.


10. On the Add Target Device screen:

a. Select the even-numbered MAC address for NIC1 in the MAC field.

b. Select the PVS collection name.

c. Click Next.

11. On the Summary of Farm Changes screen:


a. Click Optimize for Provisioning Services and then, verify all items are selected. Optimize removes the selected features from the OS to reduce the vDisk file size to and improve runtime characteristics. If you are familiar with this part of Citrix image optimization, you can clear selections as necessary.

b. Click OK.

c. Click Finish.

The vDisk is created on the PVS1 vDisks store.

IMPORTANT: Click No when prompted to Reboot.

12. To shutdown the m700 node through the OS, select Start>Windows_Security>Power_Menu>Shut

down.


13. Set the imaging node to boot from the PXE, and then boot the node.

You can use the virtual serial port can to view the boot process and the connection to the Provisioning Services.

14. To set the boot source, connect to the VSP and enter the following from the iLO CM firmware CLI: SET NODE BOOTONCE PXE <node> SET NODE POWER ON <node> CONNECT NODE VSP <node>

where <node> is the iLO CM firmware notation for the node that is being used for image creation. These steps allow the node to connect to Provisioning Services and setup communication with PVS to save the disk image.

The imaging node reboots to HDD after PXE booting to PVS.

15. To start the image capture, log in as the domain administrator.


This process automatically starts after you log in and takes 10 to 30 minutes depending on the overall size of the vDisk you specified.

16. After the disk is created, click Finish.

17. To shutdown the imaging node through the OS, select

Start>Windows_Security>Power_Menu>Shut_down.

vDisk image publication To make the new image public and assign the image to multiple Moonshot System HDI nodes:

1. Allow the image to be publicly shared:

a. From the PVS console, select Sites>PVSSite1>vDisk_Pool.

b. Right-click the appropriate vDisk, and then select Properties.

2. On the vDisk Properties screen, change the attributes of the image captured:

a. Select Standard Image for the Access mode.

b. Select Cache on device hard drive for the cache type.


c. Click OK.

Application installation You can now assign the newly captured image to another node in private mode, and then make additional changes, such as installing OS patches and additional software, before making the image public and booting on a large collection of nodes.

Image maintenance Use standard PVS facilities to create snapshots of images over time. You can also mount virtual hard drive disks as local drives on the PVS server so they can be altered. Virtual hard drive image files can also be modified with virtual hard drive tools provided with installations of Microsoft Windows Server 2012 with Hyper-V. For example, you can use Resize-VHD to increase the size of the image virtual hard drive.

PVS console integration The Moonshot m700 nodes can now be booted from the iLO CM firmware CLI by entering the following command:

SET NODE POWER ON <node_list>

where <node_list> is a collection of nodes to be acted on. Initially, it is recommended that you boot one node and view its boot progress using VSP. After one node boots successfully, all the nodes can be powered on at one time using the value ALL for the <node_list> variable.


Moonshot specific device node creation If PVS is configured using the auto-add mode, nodes are automatically assigned a default image as they are discovered and booted by the PVS PXE service. These nodes are also assigned a generic device number in sequence as they are recognized. The mapping between generic device numbers and actual physical node location can be difficult. The administrator should use the import feature for PVS devices defined in a local .csv file.

The following procedure describes the process for creating and importing a list of nodes with well-formed names that are meaningful to the administrator. This method preserves the correlation between device name in PVS and the cartridge-node location in the HP Moonshot 1500 chassis.

The .csv file is created from the Get-HPMoonshotMACs PowerShell function, which is located in the HPMoonshotTools.psm1 file. For more information about using the HPMoonshotTools.psm1, see "HP Moonshot Tools for PowerShell."

NOTE: If importing nodes into a predefined device collection in PVS, the PVS Site Name and Collection Name must match the site and collection name that you previously created.


1. On the PVS console, navigate to

Farm>Sites>SiteName>Device_Collections>CollectionName>Target_Device Import Devices.


2. On the Import File screen, navigate to the directory of the .csv files created in the previous step, and then click Next.


3. On the Import Target Device Options screen, select Apply template device of device collection to imported device, and then click Next.

Unique devices are added into the PVS Device Collection.


4. On the New Target Device Selection screen, click Finish.

5. On the Import Target Devices screen, click Done.

Imported devices appear under Device Collections in the PVS console.


6. To create the machine accounts in the PVS console, select all devices listed under Device Collections, right-click the highlighted devices, and then select Active_Directory>Create_Machine_Account.

7. On the Create Machine Accounts in Active Directory screen, select the Domain and Organizational

unit, and then click Create Account.


After machine accounts are created in Active Directory, the nodes can be powered on. After the nodes are fully booted, each node appears in the PVS console with its status and IP address on the PVS network.

HP Moonshot system HDI sample scripts 60

HP Moonshot system HDI sample scripts


HP Moonshot tools for PowerShell

HP Moonshot tools set up

Installing HP Moonshot tools for PowerShell module Use standard PVS facilities to create snapshots of images over time. You can also mount virtual hard drive disks as local drives on the PVS server so they can be altered. Virtual hard drive image files can also be modified with virtual hard drive tools provided with installations of Microsoft Windows Server 2012 with Hyper-V. For example, you can use Resize-VHD to increase the size of the image virtual hard drive.

Uninstalling HP Moonshot tools for PowerShell module Use standard PVS facilities to create snapshots of images over time. You can also mount virtual hard drive disks as local drives on the PVS server so they can be altered. Virtual hard drive image files can also be modified with virtual hard drive tools provided with installations of Microsoft Windows Server 2012 with Hyper-V. For example, you can use Resize-VHD to increase the size of the image virtual hard drive.

HP Moonshot tools functions

Get HPMoonshotCreds The Get-HPMoonshotCreds function displays the alias, username, device name, and SSH Port for all devices stored in the HP Moonshot Credentials database, if the database exists. Passwords are excluded from the displayed results.

NOTE: To initialize the HP Moonshot Credentials database, see the Set-HPMoonshotCreds function.

NOTE: The database is stored in the C:\Users\<current_user>\AppData\Local\HP\MoonshotTools\db directory. This database file is local to the system and user on which it is generated.

Extended Help within Windows PowerShell

To see the examples, enter:

get-help Get-HPMoonshotCreds -examples

For more information, enter:

get-help Get-HPMoonshotCreds -detailed

For technical information, enter:

get-help Get-HPMoonshotCreds -full

For online help, enter:

get-help Get-HPMoonshotCreds -online


Get HPMoonshotMACs The Get-HPMoonshotMACs function generates a .csv file with well-formed node names that are meaningful to the administrator. This .csv is useful for importing HP Moonshot nodes into PVS when the node <cXnY> notation should be included in the device hostname in lieu of using the Citrix PVS Auto-Add Wizard.

NOTE: This function requires SSH access to the HP Moonshot Chassis Manager.



get-help Get-HPMoonshotMACs -examples


get-help Get-HPMoonshotMACs -detailed


get-help Get-HPMoonshotMACs -full


get-help Get-HPMoonshotMACs -online

Get HPMoonshotCreds The Get-HPMoonshotNodePower function displays power states for the given HP Moonshot node range.

The Power State options are as follows:

–PowerState all option - Displays all device power states within node range are displayed

–PowerState on option - Displays all powered on devices within node range are displayed

–PowerState off option - Displays all powered off devices within node range are displayed


Extended Help within Windows PowerShell To see the examples, enter:

get-help Get-HPMoonshotNodePower -examples


get-help Get-HPMoonshotNodePower -detailed


get-help Get-HPMoonshotNodePower -full


get-help Get-HPMoonshotNodePower -online


Open HPMoonshotConsole The Open-HPMoonshotConsole function starts an SSH session via Putty.exe to a given username@IP. Putty.exe must be installed in the default directory C:\Program Files (x86)\PuTTY\.



get-help Open-HPMoonshotConsole -examples


get-help Open-HPMoonshotConsole -detailed


get-help Open-HPMoonshotConsole -full


get-help Open-HPMoonshotConsole -online

Remove HPMoonshotCreds The Remove-HPMoonshotCreds function deletes either the entire Moonshot Credentials database or a set of credentials from the database.




get-help Remove-HPMoonshotCreds -examples


get-help Remove-HPMoonshotCreds -detailed


get-help Remove-HPMoonshotCreds -full


get-help Remove-HPMoonshotCreds -online

Send HPMoonshotCMCommands The Send-HPMoonshotCMCommands function executes a list of commands from the specified remote file onto the specified CM.



NOTE: This function is not recommended for vsp commands within the CM. To start a vsp session within the CM, use the Open-HPMoonshotConsole function and execute the following CM command via PuTTy: connect <node|switch> vsp <cXnY|sa|sb> CM command



get-help Send-HPMoonshotCMCommands -examples


get-help Send-HPMoonshotCMCommands -detailed


get-help Send-HPMoonshotCMCommands -full


get-help Send-HPMoonshotCMCommands -online

Get HPMoonshotCreds The Send-HPMoonshotSwitchCommands function executes a list of commands from the specified remote file onto the specified Moonshot or Top of Rack switch.


NOTE: This function uses Plink.exe which must be installed in the default directory C:\Program Files (x86)\PuTTY.



get-help Send-HPMoonshotSwitchCommands -examples


get-help Send-HPMoonshotSwitchCommands -detailed


get-help Send-HPMoonshotSwitchCommands -full


get-help Send-HPMoonshotSwitchCommands -online


Set HPMoonshotCreds The Set-HPMoonshotCreds function saves device SSH credentials into the Moonshot Credentials database once credentials and network connectivity have been verified. This enables the HPMoonshot functions to execute with less user interaction to the given Moonshot chassis by use of the Alias option.




get-help Set-HPMoonshotCreds -examples


get-help Set-HPMoonshotCreds -detailed


get-help Set-HPMoonshotCreds -full


get-help Set-HPMoonshotCreds -online

Set HPMoonshotNodeBoot The Set-HPMoonshotNodeBoot function executes the CM command set node <boot|bootonce> <pxe|hdd> <range> for the given HP Moonshot node range.



get-help Set-HPMoonshotNodeBoot -examples


get-help Set-HPMoonshotNodeBoot -detailed


get-help Set-HPMoonshotNodeBoot -full


get-help Set-HPMoonshotNodeBoot -online


Set HPMoonshotNodePower The Set-HPMoonshotNodePower function executes the CM command set node power <on|off force|off shutdown> for the given HP Moonshot node range.




get-help Set-HPMoonshotNodePower -examples


get-help Set-HPMoonshotNodePower -detailed


get-help Set-HPMoonshotNodePower -full


get-help Set-HPMoonshotNodePower -online

Moonshot CM script examples

Setting all nodes to PXE boot !

! CM Node configuration for PVS

!

! Insure all nodes are off. Set all nodes to boot from PXE.

!

set node power shutdown all

set node boot pxe all

!

! CM Boot All Nodes

!

set node power on all

Preparing nodes for WDS imaging ! CM Configuration for WDS

!

! Set up all nodes on a cartridge for WDS Imaging


! (cartridge 45, nodes 1-4)

!

! WDS requires that a node boot normally from HDD, with the first

! boot being from PXE to start the installation process. In the

! case of the M700, the HDD is a 32GB iSSD disk attached to the

! SATA port of the Kyoto CPU/APU. The following commands handle

! this node boot configuration. A node shutdown is forced to

! insure the node is powered off, ready for WDS installation.

!

! The following commands should be pasted into an SSH session

! connected to the Chassis Manager (aka CM).

!

set node power shutdown c45n1-4

set node boot hdd c45n1-4

set node bootonce pxe c45n1-4

!

! CM Start WDS Install

!

! Turn the nodes on that are to be installed by WDS and connect

! to the console of one of them to track its progress.

!

set node power on c45n1-4

connect node vsp c45n1

Moonshot switch script examples

Configuring VLANs !!!!!!!!!!!!!!!!Use this section to reset to factory defaults

!enable

!clear config

!y

!!!!!!!!!!!!!!!!

! configure the uplink module to be 10Gbit or 40Gbit

enable

config


! interface Q1 = 1/1/1, Q2 = 1/1/6, Q3 = 1/1/11, Q4 = 1/1/16

interface 1/1/1

hardware profile portmode 4x10g !enable as 4x10Gbit

interface 1/1/6


interface 1/1/11


interface 1/1/16


exit

exit

write memory

y

exit

reload

y

!!!!!!!!!!!!!!!!Do not continue until switch reloads

enable

! Turn off mvrp since we don't want dynamic vlans

config

no mvrp

exit

!

! Define our VLAN database

vlan database

vlan 1

vlan 21

vlan 22

vlan 29

vlan 30

vlan 103

vlan 104

vlan 105

vlan 106


vlan 117

vlan 118

vlan name 1 default

vlan name 21 virtsw

vlan name 22 iscsi

vlan name 29 DLdomain

vlan name 30 DLpvs

vlan name 103 moonshot

vlan name 104 glenn

vlan name 105 orbit

vlan name 106 corp

vlan name 117 pvsdev

vlan name 118 mspvs

exit

write memory

y

exit

!!! Assign ports 1-180 to the DLpvs VLAN.

!!!

enable

config

interface 1/0/1-1/0/180

vlan pvid 30 ! untagged vlan 30 on this port

vlan participation exclude 1 ! block vlan 1 on this port








vlan participation include 30 ! allow vlan 30 on this port

exit

exit

write memory

y


exit

! Assign switch uplink trunk

enable

config

interface 1/1/1-1/1/20

vlan acceptframe vlanonly

vlan participation include 21,22,29,30,103,104,105,106,117,118

vlan participation exclude 1

vlan tagging 21,22,29,30,103,104,105,106,117,118

vlan ingressfilter

exit

exit

write memory

y

exit

Preparing NICs for WDS deployment !

! Switch SA Configuration Prior to WDS

!

! It is recommended that both Kyoto NICs be on the WDS network

! during deployment to avoid problems with binding order. This

! may require changing the configuration of both switches. Below

! is an example of modifying both switch A (SA) and switch B (SB). Note

! the formula for computing the switch port number for a node is

! as follows:

!

! port = ((cartridge_number - 1) * 4) + node_number

!

! Example: node_3 on cartrige_5 is port 19

!

enable

config

interface 1/0/177-1/0/180

vlan pvid 29 ! untagged vlan 29 on this port



vlan participation include 29 ! allow vlan 29 on this port


exit

exit

write memory

y

exit

Support and other resources 72

Support and other resources

Additional information • HP Moonshot System documentation

http://www.hp.com/go/moonshot/docs (http://www.hp.com/go/moonshot/docs)

• Citrix documentation

http://support.citrix.com/proddocs/topic/infocenter/ic-how-to-use.html (http://support.citrix.com/proddocs/topic/infocenter/ic-how-to-use.html)

• Windows Deployment Services documentation

http://technet.microsoft.com/en-us/windowsserver/dd448616 (http://technet2.microsoft.com/WindowsServer/en/Library)

• Windows Server Administration Console documentation

http://technet.microsoft.com/en-us/library/cc463427(v=ws.10).aspx (http://technet.microsoft.com/en-us/library/cc463427(v=ws.10).aspx)

HP contact information For United States and worldwide contact information, see the Contact HP website (http://www.hp.com/go/assistance).

In the United States:

• To contact HP by phone, call 1-800-334-5144. For continuous quality improvement, calls may be recorded or monitored.

• If you have purchased a Care Pack (service upgrade), see the Support & Drivers website (http://www8.hp.com/us/en/support-drivers.html). If the problem cannot be resolved at the website, call 1-800-633-3600. For more information about Care Packs, see the HP website (http://pro-aq-sama.houston.hp.com/services/cache/10950-0-0-225-121.html).



http://technet2.microsoft.com/WindowsServer/en/Library�

http://technet.microsoft.com/en-us/library/cc463427(v=ws.10).aspx�

http://www.hp.com/go/assistance�

http://www8.hp.com/us/en/support-drivers.html�

http://pro-aq-sama.houston.hp.com/services/cache/10950-0-0-225-121.html�

Acronyms and abbreviations 73

Acronyms and abbreviations

APU accelerated processing unit

BACS Broadcom Advanced Control Suite

CIFS Common Internet File System

CM chassis management

DCE

Distributed Computing Environment

DDR3

double data rate-3

DHCP

Dynamic Host Configuration Protocol

DNS

domain name system

FQDN

Fully Qualified Domain Name

GPU graphics processing unit

HDD hard drive

HDI Hosted Desktop Infrastructure


HDX

High definition experience

ID

identification

iLO

Integrated Lights-Out

iSSD

integrated solid state drive

MAC Media Access Control

PoC proof of concept

PVS Provisioning Server

PXE preboot execution environment

QSFP+

enhanced quad small form-factor pluggable

RDP

Remote Desktop Protocol

SAMU

Security Asset Management Unit

SATA

serial ATA

SLAPM SL Advanced Power Manager

SoC system on chip


SODIMM

Small Outline Dual In-line Memory Module

SORDIMM

Small Outline Registered Dual In-line Memory Module

SPI

system peripheral interface

SSH

Secure Shell

SSL Secure Sockets Layer

TDP Thermal Design Power

TFTP Trivial File Transfer Protocol

ToR top of rack

UDIMM

unregistered dual in-line memory module

USB

universal serial bus

UVD

Unified Video Decoder

VCE

Video Codec Engine

VDA Virtual Desktop Agent

VHD Virtual Hard Disk


VLAN

virtual local-area network

VM

Virtual Machine

VSP

virtual serial port

Documentation feedback 77

Documentation feedback

HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (mailto:[email protected]). Include the document title and part number, version number, or the URL when submitting your feedback.

mailto:[email protected]�

Index 78

C

chassis components 9, 10, 13 components, Citrix 5 creating a disk image 35

H

HP Moonshot 1500 Chassis 9 HP Moonshot System components 9 HP technical support 69 HP website 69 HP, contacting 69

I image creation 35 introduction 5

O

overview 5

P

provisioning server 20, 21, 32, 35 provisioning server, configuring 32 provisioning server, installing 21

S

scripts 57, 64 server setup 20 server, DHCP 17, 20, 21 server, provisioning 17, 20, 21

W

website, HP 69

Index

HP ConvergedSystem 100 for Hosted Desktops Getting …The Citrix PVS server is a key technology for...

Documents

Transcript of HP ConvergedSystem 100 for Hosted Desktops Getting …The Citrix PVS server is a key technology for...