Installing Certificates on Anyware Clients
Installing the Internal Root CA Certificate in a Anyware client
Your root CA certificate must be installed in any Anyware client that will be used to connect to the Anyware agent.
Your root CA certificate must be installed in any Anyware client that will be used to connect to the Anyware agent.
The agent certificate and signing certificate must be installed on each desktop running a Anyware agent.
To install the agent certificate and signing certificate:
Open the Microsoft Management Console on the agent machine:
PCoIP requires a certificate to establish a session. By default, Anyware agents generate a self-signed certificate that secures the PCoIP session. Each component in the PCoIP system can generate these self-signed certificates, which will automatically work together without requiring any configuration.
This section describes how to replace HP's default certificates with your own custom certificates.
Note: These procedures use OpenSSL
Customers face licensing problems with Cloud License Service (CLS) as the OS Trusted Root Certificate Authorities are not updated.
When using non-GRID GPUs in virtualized workstation virtual machine using vSphere Client, you must specify the number of displays the virtual machine will use. You can do this when you first create the virtual machine or at any time afterwards.
This section describes how to add a shared NVIDIA GRID PCI device to your virtual machine and specify its GPU profile. The following instructions are only required for virtualized workstations using a supported NVIDIA GRID vGPU video card.
This section describes how how to add an NVIDIA GRID PCI device to your ESXi host.
The following instructions are only required for virtualized workstations using a supported NVIDIA GRID video card with pass-through. For specific supported models, see System Requirements.
This section contains reference information useful for VSphere users configuring displays with the Anyware Graphics Agent.
You can find information here for:
Sometimes, you might encounter the following issues during smart card logon:
When Single Sign-On (SSO) is enabled, smart cards are not displayed in the Device Manager list on the remote agent