HP mt40 Mobile Thin Client Deployment Guide
HP Velocity Server Side
Deployment Guide
Copyright © 2013 LiveQoS Incorporated All Rights Reserved
Microsoft, Windows, and Windows Vista are U.S. registered trademarks of Microsoft Corporation.
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.
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.
Fourth Edition: May 2013
First Edition: June 2012
Document Part Number: 689167-004
Contents
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
About this document 6
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Document styles and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
HP Velocity functional overview 8
Operational modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Establishing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Deployment configurations 11
Deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Direct. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Proxied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Direct and proxied. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Terminal services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Deployment considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Maximum number of protected flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
About HP Velocity beacons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installations 17
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Server-side installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing HP Velocity on Microsoft Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing HP Velocity on servers with Broadcom teaming interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 21
HP thin client installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
HP Velocity management 23
HP Velocity Management Application modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Identifying the HP Velocity operational mode on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Setting the HP Velocity operational mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Displaying the protected or monitored flow count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
HP Velocity group policy 26
HP Velocity Policy Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Microsoft Group Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring HP Velocity using Group Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Adding the HP Velocity Administrative Template to a GPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Updating the HP Velocity configuration using the Group Policy Editor. . . . . . . . . . . . . . . . . . . . 28
About the HP Velocity Administrative Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Management Application Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Boot Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Policy Filters (Port & IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
LiveQ - Target Loss Rate Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
LiveTCP - Protocol Latency Mitigation Policy Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
LiveQ - Packet Loss Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
LiveTCP - Latency Mitigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Registry keys used in HP Velocity configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Using the Management Application 45
Network Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Statistics view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Advanced Statistics view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Working with network statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Network Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Flow Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Local and remote system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring global system settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Displaying system boot settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configuring policy filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
LiveQ policy filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
LiveTCP policy filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring LiveQ packet loss settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring LiveTCP - Latency Mitigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Configuring the network simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
General settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Troubleshooting 73
Why does the “Another version of this product is already installed” message appear? . . . . . . . . . . . 73
Why does the “Do you want to allow the following program from an unknown publisher to make changes to
your system” message appear? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Why does a message about a driver that has not passed Windows Logo Compatibility testing appear?73
Why are there multiple protected streams for one PCoIP or RGS connection? . . . . . . . . . . . . . . . . . 74
Is traffic between two HP Velocity servers only monitored? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A procedure in this document doesn’t work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
This troubleshooting section does not have the solution to my problem. . . . . . . . . . . . . . . . . . . . . . . 74
About this document
Purpose
This document describes deployment scenarios and installation methods for HP Velocity. It
contains the following sections:
• HP Velocity functional overview—Information on HP Velocity operational modes and how
connections are established
• Deployment configurations—Information on different HP Velocity deployment
configurations
• Installations—Installation procedures for HP Velocity on the server side
• HP Velocity management—Procedures for launching the basic and advanced user modes
• HP Velocity group policy—Procedures for creating a custom HP Velocity configuration
• Using the Management Application—Procedures for using the Management Application
• Troubleshooting—Basic troubleshooting information
Intended audience
This document is intended for network and IT administrators who will be deploying, installing,
configuring, and managing HP Velocity.
Document styles and conventions
In this document, the following styles are used.
Style Description
Start > Edit > Cut Any elements on screen such as menus or buttons use this format.
Select directory
screen
myfile.txt Filenames and directory names use this format.
Sample Product Links to locations inside and outside this document use this format.
Example book Links to external published documents, books, and articles use this
HP Velocity Server Side Deployment Guide 6
A screen or dialog box name uses this format.
format.
About this document Document styles and conventions
In this document, the following conventions are used.
Convention Description
<sample_name> Replace the whole text including angle brackets with the expected value.
For example, replace <exec_filename> with example.exe when
entering this command.
{option1 |
option 2}
When entering the command, choose one of the options presented.
HP Velocity Server Side Deployment Guide 7
HP Velocity functional overview
Operational modes
HP Velocity protects and optimizes data flows between HP thin clients and HP Velocityenabled virtual desktops or terminal services servers. It provides three operational modes:
Protect, Monitor, and Off.
Protect mode
Protect mode is the default and recommended operational mode. In this mode, HP Velocity
provides session establishment, HP Velocity-protected flow statistics, packet loss protection,
WiFi optimization, and latency mitigation.
Monitor mode
In Monitor mode, HP Velocity monitors for packet loss and continuously profiles the end-toend network conditions over established flows. This mode disables all HP Velocity network
optimizers and is useful for acquiring baseline network characteristics.
Off mode
In Off mode, HP Velocity passes all network flows transparently and does not perform any
monitoring or optimization.
HP Velocity Server Side Deployment Guide 8
HP Velocity functional overview Establishing a connection
Establishing a connection
An HP Velocity-protected connection is established over four steps (Figure 1):
• Initialization
• Beaconing
• Handshaking
• Protected state
Figure 1. Establishing a connection
Initialization
During initialization, HP Velocity-enabled endpoints start streaming data transparently. No
optimizations are performed.
HP Velocity Server Side Deployment Guide 9
HP Velocity functional overview Establishing a connection
Beaconing
Once an HP Velocity-enabled endpoint detects that a bidirectional network path is available, it
periodically modifies packet headers (both IP and TCP) in a seamless way to advertise itself to
other HP Velocity-enabled endpoints (Figure 2).
IP headers can contain both IP ID-based beacons (using an option value of 0x420B) and IP
Option-based beacons (using an option value of 0x880477FB). TCP flows can use TCP
Option-based beacons (using an option value of 0x01 No-Operation and seven sets of End of
Option Lists 00000000000000).
Once an HP Velocity-enabled endpoint processes enough beacons on a network flow to
discover that another HP Velocity-enabled endpoint is at the other end, handshaking occurs.
NOTE: The use of TCP Option-based beacons for TCP flows and IP
Option-based beacons for UDP flows can be controlled through the
HP Velocity Policy Engine.
Figure 2. IPQ beaconing
Handshaking
An HP Velocity-enabled endpoint will initiate a three-way handshaking procedure with an
HP Velocity-enabled endpoint discovered during beaconing. Once the handshake is
completed, both HP Velocity-enabled endpoints enter the protected state.
Protected state
In the protected state, HP Velocity-enabled endpoints exchange information about current and
trending network conditions. This information is then used to intelligently activate and adjust
various optimizers.
HP Velocity Server Side Deployment Guide 10
Deployment configurations
HP Velocity server-side deployments vary based on the virtualization architecture in use.
This chapter covers the following information:
• Deployments
• Deployment considerations
Deployments
HP Velocity is preinstalled on HP thin clients. Use the following table to determine where to
install HP Velocity on the server side.
Virtualization architecture
HP thin clients are directly connected to virtual
desktops or applications.
HP thin clients use a connection broker as a proxy to
access virtual desktops or applications.
The virtualization environment supports both direct
and proxied connections to virtual desktops and
applications.
HP thin clients connect to a terminal services server.
“
Direct” on page 12
“
Proxied” on page 13
“
Direct and proxied” on page 14
“
Terminal services” on page 15
NOTE: HP Velocity server-side components are currently supported on Windows
operating systems.
HP Velocity Server Side Deployment Guide 11
Deployment configurations Deployments
Server Side
Original
IP packets
Client
application
Client Side
HP
Velocity
Client
Original
IP packets
Client
application
Client Side
s
s
k
HP
Velocity
Client
Thin Client A
Thin Client B
Application
Virtual
desktop
B
HP
Velocity
Server
Application
Virtual
desktop
A
HP
Velocity
Server
Original
IP packets
Direct
Virtualization architectures that allow an HP thin client to connect directly to a virtual desktop
must have the HP Velocity server installed on the virtual desktop. In this deployment, a
connection broker does not act as a proxy.
In Figure 3, thin clients A and B are directly connected to their respective virtual desktops A
and B, as indicated by the color of the dotted lines.
Figure 3. Example of a direct deployment
Protected flow between thin client and virtual desktop
networ
Firewall
outer
HP Velocity Server Side Deployment Guide 12
Deployment configurations Deployments
Server Side
Application
Virtual
desktop
B
Application
Virtual
desktop
A
Original
IP packets
Client Side
Original
IP packets
Client
application
Client Side
lls
terster
s
k
HP
Velocity
Client
Thin Client A
Thin Client B
Connection
Broker
HP
Velocity
Server
Client
application
HP
Velocity
Client
Original
IP packets
Proxied
Virtualization architectures that require an HP thin client to access their virtual desktop via a
proxy service provided by a connection broker (such as VMware View Manager) must have an
HP Velocity server installed on the connection broker.
In Figure 4, thin clients A and B are connected to their virtual desktops via the connection
broker. An HP Velocity server is installed on the connection broker. This results in flows that
are protected by HP Velocity between the thin clients and the connection broker.
Figure 4. Example of a proxied deployment
Protected flows between thin client and connection broker
nmana
rewa
wor
NOTE: Additional configuration is not required after the HP Velocity server is
installed on the connection broker.
HP Velocity Server Side Deployment Guide 13
Deployment configurations Deployments
Protected flow between thin client and virtual desktop
Protected flow between thin client and connection broker
Server Side
Original
IP packets
Client
application
Client Side
HP
Velocity
Client
Original
IP packets
Client
application
Client Side
s
d
wor
k
HP
Velocity
Client
Thin Client A
Thin Client B
Connection
Broker
HP
Velocity
Server
Original
IP packets
Application
Virtual
desktop
A
Application
Virtual
desktop
B
HP
Velocity
Server
Direct and proxied
Some virtualization architectures allow both direct and proxied access to virtual desktops. In
this deployment, the HP Velocity server must be installed on:
• Virtual desktops that are accessed directly
• Connection brokers that provide a proxy service to access the virtual desktop
In Figure 5, thin client A connects to virtual desktop A through the connection broker, and thin
client B connects to virtual desktop B directly.
Figure 5. Example of a direct and proxied deployment
nmanage
irewall
outers
HP Velocity Server Side Deployment Guide 14
Deployment configurations Deployments
Original
IP packets
Client
application
Client Side
s
s
Client Side
HP
Velocity
Client
Thin client A
Thin client B
Terminal services / virtual desktop server
Word
Applications
Mail
Applications
Virtual
desktop
HP
Velocity
Server
Original
IP packets
Client
application
HP
Velocity
Client
Terminal services
In a terminal services deployment, multiple HP thin clients are connected to a terminal
services server such as a Windows Server.
In this deployment, the HP Velocity server must be installed on the terminal services server
(Figure 6).
Figure 6. Example of a terminal services deployment
Protected flows - Multiple thin clients to terminal services server
irewall
outer
HP Velocity Server Side Deployment Guide 15
Deployment configurations Deployment considerations
Deployment considerations
Maximum number of protected flows
HP Velocity supports a range of 16 to 1024 simultaneously protected flows.
The minimum supported protected flows are:
• 16 for HP thin clients
• 16 for virtual desktops
• 256 terminal services servers
HP Velocity defaults to the minimum supported simultaneous flows. If the default setting is
changed, the system must be rebooted for the change to take effect.
NOTE: HP Velocity server-to-server flows are only monitored, not protected. Only
flows between a server enabled with HP Velocity and an HP thin client are
protected.
NOTE: LiveTCP will provide latency mitigation for up to 32 simultaneous
protected flows.
About HP Velocity beacons
HP Velocity advertises its presence in a non-intrusive way by modifying IP and TCP headers
in compliance with International Engineering Task Force (IETF) standards.
If either IP or TCP Option beacons are enabled, HP Velocity will add up to 4 bytes of data to
the IP or TCP headers. This is in compliance with RFC 791 and RFC 793. Some applications
might not be compliant with RFC 791 or RFC 793, and as a result might not be able to process
IP or TCP Option beacons. If this occurs, disabling IP and/or TCP Option beacons should
resolve the issue.
For more information on configuring beacons, see the HP Velocity User Guide.
NOTE: HP Velocity beacons are:
IP Option - 0x880477FB (UDP Flows)
TCP Option - 0x010000000000000000 (TCP Flows)
HP Velocity Server Side Deployment Guide 16
Installations
This section outlines the requirements for installing the HP Velocity server and covers the
following information:
• System requirements
• Server-side installation
• Installing HP Velocity on Microsoft Hyper-V
• Installing HP Velocity on servers with Broadcom teaming interfaces
System requirements
Before installing the HP Velocity server, ensure that the following resources are available. The
different requirements for server operating system (OS) and virtual desktop OS installations.
Requirement Server OS Virtual desktop OS
CPU Any Any
Memory 30 MB 3 MB
Disk space 10 MB 10 MB
OS Windows Server 2008
OS variants 32-bit and 64-bit
Clients HP thin clients
Windows Server 2003
Windows 8
Windows 7
Windows Vista
Windows XP (SP3 and above)
NOTE: Memory requirements are proportional to the number of simultaneous
protected flows supported by HP Velocity.
HP Velocity Server Side Deployment Guide 17
Installations Server-side installation
Server-side installation
HP Velocity installs as a network driver on the following platforms:
• Virtual desktops
• Host OS of Microsoft Terminal Services
• Microsoft Hyper-V server
NOTE: During installation, HP Velocity will reset the system’s network
interfaces, briefly interrupting network connections. If HP Velocity is
installed over a remote connection, network connectivity might be
disrupted.
To install HP Velocity server:
1. Locate the correct HP Velocity server installation package for the server-side operating
system (see the following table). Read the release notes and documentation for the version
of HP Velocity being installed.
.
Supported operating systems • Server: Windows Server 2003, Windows Server 2008
• Virtual desktop: Windows 8, Windows 7, Windows Vista,
Windows XP
32-Bit Installer HPVelocity_SERVER_32_REL#_R#.msi
64-Bit Installer HPVelocity_SERVER_64_REL#_R#.msi
Note: In the HP Velocity package filename, REL# is the software release
number and R# is the revision number of the package that matches the
release number.
2. Log on as an administrator to the system where the HP Velocity server will be installed.
3. Select the appropriate installation package for the server-side operating system and
architecture, and start the installer.
The Welcome to the HP Velocity Setup Wizard screen appears.
4. Click Next.
The License Agreement screen appears.
5. Read the end user license agreement:
HP Velocity Server Side Deployment Guide 18
Installations Server-side installation
•Select I Agree and click Next to continue.
•Select Cancel to end the installation.
The Select Installation Folder screen appears with the default location
C:\Program Files\LiveQoS\HP Velocity\.
6. Either select the location where HP Velocity will be installed or accept the default location.
7. Either select Everyone (default) to install HP Velocity for all user accounts and
administrators or select Just me to install HP Velocity only for the current user account.
8. Click Next.
The Confirm Installation screen appears.
9. Click Next to confirm the selections and start installing HP Velocity.
IMPORTANT: Depending on the version of the Windows OS, a warning
message about software installed by LiveQoS might appear. This
message is expected; allow the installation to proceed.
The Installation Complete screen appears when the installation is finished.
10. Click Close.
NOTE: If you are installing on Microsoft Hyper-V, see “Installing
HP Velocity on Microsoft Hyper-V” on page 20.
NOTE: If you are installing on servers with Broadcom teaming interfaces,
see “Installing HP Velocity on servers with Broadcom teaming interfaces”
on page 21
HP Velocity Server Side Deployment Guide 19
Installations Installing HP Velocity on Microsoft Hyper-V
Installing HP Velocity on Microsoft Hyper-V
Installing HP Velocity on Microsoft Hyper-V might require the following additional steps.
If HP Velocity is installed directly on Microsoft Hyper-V and there is a “Local Area Connection Virtual Network” entry (Figure 7), ensure that the LiveQoS NDIS 6 Filter Driver is disabled for
the physical network adapter (Figure 8).
Figure 7. Microsoft Hyper-V network connections
Figure 8. Disabled LiveQoS NDIS 6 Filter Driver
HP Velocity Server Side Deployment Guide 20
Installations Installing HP Velocity on servers with Broadcom teaming inter-
Installing HP Velocity on servers with Broadcom teaming interfaces
Installing HP Velocity on Windows Servers using the Broadcom Advanced Control Suite NIC
Teaming feature might require the following additional steps.
If HP Velocity is installed on Windows Servers, ensure that the LiveQoS NDIS 6 Filter Driver is
disabled in the adapter settings (Figure 10).
To disable the LiveQoS NDIS 6 Filter Driver:
1. Install the HP Velocity server-side component as described in “Server-side installation” on
page 18.
2. Once the installation is complete, a prompt asking to reboot the system will appear. Click
NO.
3. Open the Network and Sharing Center from the Control Panel.
4. Click Change Adapter Settings.
5. Right-click Team 1 (Figure 9).
Figure 9. Adapter settings
6. In the list titled This connection uses the following items, deselect the checkbox next to
LiveQoS NDIS 6 Filter Driver (Figure 10).
HP Velocity Server Side Deployment Guide 21
Installations HP thin client installation
Figure 10. Setting adapter properties
7. Click OK.
HP thin client installation
HP Velocity is preinstalled on select HP thin client images as of March 2012. HP Velocity
updates may be available as an add-on. For more information, visit http://www.hp.com/
support.
HP Velocity Server Side Deployment Guide 22
HP Velocity management
This section covers the following information:
• HP Velocity Management Application modes
• Identifying the HP Velocity operational mode on Windows
• Setting the HP Velocity operational mode
HP Velocity Management Application modes
HP Velocity supports two Management Application display modes on Windows: Basic and
Advanced.
• Basic mode is launched by clicking the HP Velocity Management Application icon in the
taskbar. By default, the Basic mode is enabled for HP thin clients.
• Advanced mode provides a toolset for monitoring and troubleshooting HP Velocity-
protected flows and is launched by right-clicking the HP Velocity Management Application
icon in the taskbar (Figure 11) and selecting Management. By default, the Advanced mode
is enabled for server-side installations. For information, see “Using the Management
Application” on page 45.
Identifying the HP Velocity operational mode on Windows
The HP Velocity Management Application automatically launches on system startup and runs
in the background. The HP Velocity Management Application icon appears in the Windows
taskbar (Figure 11).
Figure 11. HP Velocity taskbar icon on Windows
The HP Velocity Management Application icon appears in one of four colors that correspond to
the HP Velocity operational modes (Tab le 1).
HP Velocity Server Side Deployment Guide 23
Loading...