Sample nginx configuration for proxy when using remote device management
This is a sample configuration when using a NGINX version 1.14.1 reverse proxy. It was used for a NGINX system installed on Rocky Linux 8. You will be required to modify the highlighted unique fields for your environment. Other reverse proxy systems may …
Troubleshooting out of order packets impacting the PCoIP protocol?
Problem The PCoIP session performance is poor. The logs indicate high packet loss and the error messages related to out of order packets. Note:The default PCoIP server logs will indicate when out of order mode is activated and deactivated. To see …
How do I check for packet loss on the ESX interface?
If there is packet loss on a PCoIP protocol session, but an analysis of network devices in the path show no loss and they have been properly configured (see  Network session checklist for PCoIP protocol LAN and WAN deployments ) then you may want to …
Troubleshooting Management Console Connectivity with Firmware 20.01
Firmware version 17.05 or 20.01 or newer is intended to be managed by PCoIP Management Console 20.01 or newer. HP Anyware recommends upgrading to PCoIP Management Console 20.01 prior to deploying firmware 17.05 or 20.01. Before using PCoIP Zero Client or …
Configuration of smart cards with PCoIP Zero Clients and VMWare Horizon
This article is provided to help administrators in setting up smart card authentication in zero clients connecting to VMWare Horizon. This article has been reviewed against the following supported hardware and software versions: VMware Horizon 7.2 PCoIP …
Using HP Anyware PCoIP Zero Clients and Remote Workstation Cards on a direct-connect (no IP) network
Direct-connect (no IP network) configurations, sometimes incorrectly referred to as "home-run networks", refer to a direct connection between 2 devices without network switches/hubs installed using straight through cables via patch-panels. Although zero …
PCoIP Zero Client refuses to connect to a View Connection Server
This is a common issue we run into especially when we depreciate older security components from our firmware. We ran into this issue when we depreciated TLS1.0 and are once again seeing it mow that we have depreciated TLS1.1 The typical message the user …