Why does the Management Console not recognize the DNS-SRV records and not connect with my PCoIP Zero Clients?
Scenario On a non-Microsoft DNS server, the DNS records have been created and the SRV record set for auto-discovery. However, the PCoIP Management Console is not recognizing these records and the PCoIP Zero Client devices are not registering in the …
Profile application to Remote Workstation Card fails
Scenario : The remote workstation card is at a factory default. You set a basic Profile in the management console and apply the Profile. The Profile application fails. If you check the management console, there is no clue as to why the Profile failed. If …
How long before a PCoIP Management Console certificate expires should I replace it?
Before the PCoIP Management Console certificate can be replaced, the new certificate or the signing root CA certificate must be installed in the PCoIP Zero Client or PCoIP Remote Workstation Card certificate store. Once a PCoIP Endpoint is manged by an …
Cannot import profile from Management Console 1.x into the PCoIP Management Console 2.x or 3.x
Answer : Importing Profiles from MC 1.x into MC 2.x is supported and documented in the user guide. Refer to the Administrators' guide for the release of the PCoIP Management Console in use. There have been a couple reports of users experiencing an issue …
What does "MCU not initialized" log message mean?
Problem You are unable to manage a zero client using the HP Anyware PCoIP Management Console 1.x (MC). The event logs reveal the following MCU errors: LVL:1 RC:-500        MCU :(tera_mcu_read_eeprom_bit): Cannot read from EEPROM, MCU not initialized. …
Why Imported Profile(s) from PCoIP Management Console 1.x/2.x to PCoIP Management Console 3.x cannot be applied? Status shows skipped.
Scenario Imported a profile from PCoIP Management Console 1.x /2.x  to PCoIP Management Console 3.x where firmware 6.0.0 is the only uploaded version in Settings -> Software. Pushing the profile to PCoIP Zero Clients results in a 'skipped' status.   Cause …
Default HP Anyware Connector docker network conflicts with VPN network
Scenario: The default HP Anyware Connector docker network is conflicting with VPN network. When specifying the --connector-network-cidr flag during the installation of HP Anyware Connector the docker network is that same range as the default 172.x How can …
Unable to start docker containers connector_cm and connector_connectorgateway during HP Anyware Connector installation
In Ubuntu 18.04.4 LTS or Ubuntu 18.04.5 LTS setting up HP Anyware Connector, if IPV6 was disabled in the vm  those 2 containers will always fail to start. During the installation or reinstallation of the HP Anyware Connector, connector_cm and …
Why my HP anyware Connector (CACv2) does not connect after the recent Ubuntu 18.04 OS Nov-13-2019 Update?
The latest patch release of Ubuntu 18.04 (Nov-13 patch) will break CAM CACv2 connectivity. Affected Ubuntu 18.04 OS patch version: Nov-13-2019 release:  ubuntu-1804-bionic-v20191113 ubuntu-os-cloud ubuntu-1804-lts Recommendation: If you experience this …