Install the latest version of Wyse Management Suite
on Microsoft Windows 2012 Server or later versions. Threadx 5.x and
6.x devices works with the latest version of the operating system.
Install and enable the EMSDK component.
The FQDN of the Wyse Management Suite server must
be available for DHCP or DNS configurations.
Cert.pem must be placed in the default
path C:\Program Files\Dell\WMS\Teradici\EMSDK. It is used to discover Threadx devices.
Security Level
Depending on an endpoint's configured security level,
you may also need to provision endpoints with an EBM/EM
certificate.
Endpoints configured for medium or high security must have a
trusted certificate in their certificate store before they can
connect to an EBM or EM. For some endpoints, certificates may be
pre-loaded by the vendor as a factory default. Otherwise,
you can manually upload certificates using an endpoint's
AWI.
Endpoints that are configured for low security do not need an MC
certificate in their trusted certificate stores if either of the
following is true:
They are using DHCP discovery or DNS discovery
and the DHCP or DNS server has provisioned
them with the EBM certificate's fingerprint.
They are discovered using the manual discovery method.
Table 1. Certificate
Requirements for EndpointsCertificate
Requirements for Endpoints
Discovery Method
Low Security
Medium Security
High Security
DHCP/DNS discovery without EBM fingerprint provisioned
Certificate required
Certificate required
Not applicable
DHCP/DNS discovery with EBM fingerprint provisioned
Certificate not required
Certificate required
Not applicable
Discovery initiated by an endpoint configured for a high security
environment
Not applicable
Not applicable
Certificate required
Manual discovery initiated by the MC
Certificate not required
Not applicable
Not applicable
Manual discovery from
the client
Go to, https://<clientIP>.
Accept the certificate warning message.
Enter the administrator password
(default password is Administrator) and login.
Go to, upload > certificate. Select the Cert.pemfile from the default path and click Upload.
Go to Configuration > Management. Click the clear
management state button to register the device to the new Management
Server.
Set the manager discovery mode to manual
Enter the Endpoint Bootstrap Manager
URL in the following format wss://<IP Address of the WMS
server>
NOTE: If EMSDK is installed with custom port then provide Endpoint Bootstrap
Manager URL in the following format wss://<IP Address:Custom
port.
Click Apply, and then click Continue.
The management status is displayed
as Connected to the Endpoint server.
Adding the PCoIP endpoint
vendor class to DHCP server
Log in to your DHCP server.
Right-click the DHCP server in the SERVERS pane, and select DHCP Manager.
Right-click the IPv4 option,
and then select Define Vendor Classes.
Click Add to add
a new DHCP vendor class.
Enter the PCoIP Endpoint in the Display name field.
Enter the PCoIP Endpoint in the ASCII column as the Vendor ID.
Click OK to save the settings.
Configuring DHCP options
Right-click the IPv4 option,
and the select Set Predefined Options.
Select PCoIP Endpoint as
the Option class, and then click Add.
In the Option Type dialog
box, enter the name as EBM URI, data type as String, code as 10, and description as Endpoint Bootstrap
Manager URI, and then click OK.
Click OK to save
the settings.
Expand the DHCP scope to which you
want to apply the options.
Right-click the Scope Options, and then select Configure Options.
Click the Advanced tab,
and then select the PCoIP Endpoint vendor class.
Select the 010 EBM URI check
box, and then enter a valid Management Console URI in the String field. Click Apply. This URl requires a
secured WebSocket prefix, for example, wss://<MC
IP address>:[port number]. 5172 is the MC's listening port
. Entering this port number is an optional step.
Click OK to save
the settings.
Select PCoIP Endpoint as
the Option class, and then click Add.
In the Option Type dialog,
enter the name as EBM X.509 SHA-256 fingerprint, data type
as String, code as 11, and the description as EBM
X.509 SHA-256 fingerprint, and then click OK.
Expand the DHCP scope to which you
want to apply the options.
Right-click the Scope Options, and then select Configure Options.
Click the Advanced tab,
and then select the PCoIP Endpoint vendor class.
Select the 011 EBM X.509 SHA-256
fingerprint check box, and paste the SHA-256 fingerprint.
Click OK to save the settings.
Go to the client web browser.
Go to Configuration > Management, and set the manager
discovery mode to Automatic
The client is connected to the server
which is mentioned in the DHCP server.
Log in to the DNS server.
Right-click the DNS server in the SERVERS pane, and the select DNS Manager from
the context menu.
In Forward Lookup Zones, right-click the domain, and then select Other New Records from the context menu.
In the Resource Record Type dialog box, select Service Location (SRV) from
the list, and click Create Record.
Set Service to _pcoip-bootstrap, protocol to _tcp, and Port
number to 5172, which is MC's default listening
port. For Host offering this service, enter the MC's FQDN.
NOTE: The MC's FQDN
must be entered because the DNS specification does not allow an IP
address in the SRV records.
Click OK.
Adding a DNS TXT record
In Forward Lookup Zones, right-click
the domain, and then select Other New Records from the context
menu.
In the Resource Record Type dialog box, select the Text (TXT) from the list, and then
click Create Record.
Enter the following details:
In the Record name field,
enter the host name of the Wyse Management Suite server offering the
service. The FQDN field is populated automatically. This should match
the FQDN of the Wyse Management Suite server.
In the Text field, enter pcoip-bootstrap-cert= and then paste the Wyse Management Suite
server certificate SHA-256 fingerprint.
Click OK.
Go to the client web browser.
The client is connected to the Wyse
Management Suite server which is mentioned in the DNS server.
Creating SHA-256 fingerprint
Start the Mozilla Firefox.
Navigate to Options Advanced Tab
Click Certificates to view the certificates.
Under Certificate Manager , click Authorities, and the click Import.
Browse the certificate, and the click View.
Copy the SHA-256 fingerprint.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\