Configuring DHCP for Endpoints that use Auto Discovery
Configuring DHCP for Endpoints that use Auto Discovery
This section explains how to configure your DHCP server to provision endpoints with Endpoint Bootstrap Manager information.
This section explains how to configure your DHCP server to provision endpoints with Endpoint Bootstrap Manager information.
The PCoIP Management Console virtual machine requires Linux command knowledge or a network configuration tool such as NetworkManager-tui (textual user interface) to assign a static IP address or change the PCoIP Management Console’s default network configuration.
If you have an allotment of AWS WorkSpaces that are available for a Zero Client user to use, you can add up to 50 of them to a Zero Client running firmware 21.10.0 or newer via a Management Console profile.
PCoIP Management Console Active Directory (AD) authentication uses Lightweight Directory Access Protocol (LDAP) or Secure Lightweight Directory Access Protocol (LDAPS) with Active Directory servers for user authentication.
In order to change the PCoIP Management Console's default settings and run various scripts, you must connect to the PCoIP Management Console’s virtual machine console and log in. The AMI release of PCoIP Management Console has SSH enabled by default to provide access to its virtual machine console.
If your endpoints are configured with a discovery method and security level that require them to have a PCoIP Management Console certificate in their trusted certificate store before they can connect to the PCoIP Management Console, you can either upload the PCoIP Management Console certificate to a group of
PCoIP Management Console cannot upgrade endpoints running firmware versions prior to 5.0. Instead, you can perform this step remotely for a group of endpoints using PCoIP Management Console 1 or you can update the firmware for individual endpoints locally using each endpoint’s AWI.
Firmware 20.01
Remote endpoint management allows PCoIP administrators to maintain central management of endpoints when they are no longer on-premises. Remote management is avialable with the Enterprise version of Management Console therefore it must be licensed with a trial or enterprise license.
This article will provide you with basic details to configure a Domain Controller, add test users and integrate the users for smart card authentication using Okta as the IDP. This reference is based on using Windows Server 2019 Standard with Okta IDP for Single Sign-on.
After completing these steps you will be able to:
Install PingFederate IDP on local system. See PingFederate install reference.
Limitations