Configuring an Endpoint Manager Manually from an Endpoint¶
For environments that do not use automatic DHCP or DNS discovery, you can manually configure each zero client with the IP address or FQDN of the PCoIP Management Console to which it should connect. The endpoint must also have a trusted PCoIP Management Console certificate in its certificate store in order for discovery to succeed. Typically, this method is used in medium and high security environments. If your endpoint does not have a pre-loaded certificate, you can use the alternative method of manual endpoint discovery initiated by the PCoIP Management Console. See Discovering Endpoints Manually from PCoIP Management Console.
This example shows how to configure a zero client for discovery by a specific Endpoint Manager from the endpoint’s AWI Management page. For information about configuring endpoints for automatic discovery from this page, please see the PCoIP Zero Client Administrators’ Guide.
Note: PCoIP Management Console servers as both Endpoint Bootstrap Manager and Endpoint Manager
In the zero client Management page, your PCoIP Management Console serves as both the Endpoint Bootstrap Manager and the Endpoint Manager. Use the PCoIP Management Console’s IP address or FQDN when specifying either an Endpoint Bootstrap Manager or an Endpoint Manager URI.
To configure your endpoint with a specific Endpoint Manager:
Note: Complete the following steps in sequence
It is necessary to complete these steps in the sequence shown next.
Enter the zero client’s IP address in your browser’s address bar, then log in to its AWI.
From the Configuration menu, select Management.
Select the desired security level:
Low Security Environment - Zero Client is discoverable by Endpoint Managers: This security level is intended for discovery that is initiated manually by a PCoIP Management Console. It enables endpoints that are shipped with empty certificate stores to use trust information retrieved during the discovery process.
Note: Low Security Environment also works for endpoints configured for DHCP options or DNS SRV record discovery
You can also use this security level for endpoints that are configured for DHCP options discovery or DNS SRV record discovery when the DHCP or DNS server also provisions the endpoint with the Endpoint Bootstrap Manager certificate’s fingerprint.
Medium Security Environment - Endpoint Bootstrap Manager must be trusted by installed certificate: When this security level is selected, the endpoint must have a trusted PCoIP Management Console certificate in its certificate store in order for discovery to succeed. The certificate can be provisioned either by the vendor when an endpoint is shipped or by uploading the PCoIP Management Console certificate to the endpoint. See Uploading the PCoIP Management Console Certificate to an Endpoint.
High Security Environment - Bootstrap phase disabled: With this security level, a user must manually enter an internal (and optionally an external) URI for the PCoIP Management Console from the endpoint’s AWI Management page. The user must also upload a PCoIP Management Console certificate to the endpoint’s trusted certificate store. Automatic provisioning and discovery methods cannot be used in a high security environment.
In the Manager Discovery Mode drop-down list, select Manual.
If the endpoint is not in the Idle state, click Clear Management State and then Continue.
Enter the URI for your PCoIP Management Console.
Note: URIs require a secure WebSocket prefix
URIs require a secured WebSocket prefix (for example, wss://< internal EM IP address|FQDN >:[port number]). The PCoIP Management Console’s listening port is 5172. Entering this port number is optional. If you do not include it, port 5172 will be used by default.
Click Apply and then Continue once more.
If discovery succeeds, the endpoint’s Management page will show the following information:
Note: Automatically name and group endpoints
You can configure the PCoIP Management Console to automatically name endpoints and place them in a specific group when they are discovered. See Auto Naming Endpoints and Auto Configuring Endpoints (Enterprise) for details.