Home » HP Manuals » Desktops » HP t505 » Manual Viewer

HP t505 Administrator Guide 9 - Page 36

FAQs, All HP Velocity application flows are blocked

Add to My Manuals
Save this manual to your list of manuals

Page 36 highlights

Administrator Guide for Thin Clients | HP Velocity FAQs All HP Velocity application flows are blocked HP Velocity uses the IP ID value 0x0DF4 and the TCP option 0x0100000000000000 in TCP headers. Intrusion Detection Systems (IDS) and firewall systems might require configuration to support HP Velocity-enabled traffic so that devices do not block it. See your device documentation to configure these settings. Traffic between HP Velocity servers is only monitored In bookended deployments, HP Velocity protects only the flows between HP thin clients and HP Velocity-enabled servers where HP Velocity Sender Side is installed on a terminal server or directly on virtual desktops. HP Velocity only monitors the flows of server-to-server connections. Protected flows are not established Virtualization architectures that require HP thin clients to access virtual desktops via a proxy service provided by a connection broker must have HP Velocity installed on the server hosting the connection broker. This ensures that protected flows are established for connections to a virtual desktop where HP Velocity is installed. For information, see HP Velocity deployments for thin clients on page 3. 32

Section	Page
HP Velocity functional overview	5
Establishing a connection	5
Initialization	5
Beaconing	5
Handshaking	6
Protected state	6
Single-sided acceleration	6
HP Velocity deployments for thin clients	7
Direct deployment	7
Proxied deployment	8
Direct-and-proxied deployment	8
Terminal-server deployment	8
Single-sided or mixed deployment	9
HP Velocity installation	10
HP Velocity Server Side system requirements	10
Installing HP Velocity Server Side	11
HP Velocity operation on Windows	12
HP Velocity operational modes	12
Setting the HP Velocity operational mode on Windows	13
Identifying the HP Velocity version on Windows	13
HP Velocity configuration	14
HP Velocity policy engine	14
Adding an HP Velocity administrative template to a GPO	14
Configuring HP Velocity using the GPO	14
HP Velocity configuration settings	15
Product ID	16
Management Application Mode	17
System settings	19
Boot settings	20
Policy filters (port & IP) settings	21
LiveQ - Packet Loss Protection settings	23
LiveTCP - Latency Mitigation settings	24
Logging settings	25
HP Velocity account privileges	27
HP Velocity management	28
Network statistics	28
Network Statistics operation	29
Flow information	30
Latency and throughput data	31
Flow Information operations	32
Configuration settings	33
Restoring default configuration settings	34
Generating the HP Velocity configuration report	34
FAQs	36
All HP Velocity application flows are blocked	36
Traffic between HP Velocity servers is only monitored	36
Protected flows are not established	36
Decision trees	37
VDI connectivity issue	37
Non-VDI connectivity issue	38
HP Velocity-protected flows not established	39
Quality of Experience: Packet-loss issue	40
Quality of Experience: Latency issue	41
Appendix: HP Velocity configuration on HP ThinPro	42
Changing the value of a configuration parameter	42
config/about	42
Description	42
Read / Write	42
config/commit	43
Description	43
Read / Write	43
config/general/factorydefault	43
Description	43
Read / Write	43
config/liveq	43
Description	43
Read / Write	43
Parameters	44
config/livetcp	44
Description	44
Read / Write	44
Parameters	44
config/system/boot	45
Description	45
Read / Write	45
Parameters	45
config/system/policy	46
Description	46
Read / Write	46
Parameters	46
config/system/settings	47
Description	47
Read / Write	47
Parameters	47
flowinfo/flows	48
Description	48
Read / Write	48
stats	49
Description	49
Read / Write	49

Match case Limit results 1 per page

Administrator Guide for Thin Clients

HP Velocity

FAQs

All HP Velocity application flows are blocked

HP Velocity uses the IP ID value 0x0DF4

and the TCP option 0x0100000000000000 in TCP headers.

Intrusion Detection Systems (IDS) and firewall systems might require configuration to support HP Velocity-enabled

traffic so that devices do not block it. See your device documentation to configure these settings.

Traffic between HP Velocity servers is only monitored

In bookended deployments, HP Velocity protects only the flows between HP thin clients and HP Velocity-enabled servers

where HP Velocity Sender Side is installed on a terminal server or directly on virtual desktops. HP Velocity only monitors

the flows of server-to-server connections.

Protected flows are not established

Virtualization architectures that require HP thin clients to access virtual desktops via a proxy service provided by a

connection broker must have HP Velocity installed on the server hosting the connection broker. This ensures that

protected flows are established for connections to a virtual desktop where HP Velocity is installed. For information, see

HP Velocity deployments for thin clients

on page 3