Administrator Guide

8 Import the exported license key to the Private Cloud.
NOTE: The license cannot be imported if it has insucient thin client seats to manage the number of devices currently
being managed in the Private Cloud. In this case repeat steps 3–8 to allocate the thin client seats.
Managing system setup
This section provides the information about the following:
1 Log in to the Wyse Management Suite portal and click the Portal Admin tab.
2 Click Setup under Systems.
3 Select the check box to perform server certicate validation for all device-to-server communication.
4 Enter the following details in the Update SMTP for Email Alerts area:
SMTP server
Send from address
Username
Password
Test address
Current Certicate: Select the Certicate Validation check box to enable the CA validation for private cloud. All the communication
from the server and the client including le download, OS image download from Local Repo uses the certicate.
NOTE
: To Enable CA Validation for Remote Repo, Go to Portal Administration > File Repository > Select the Repository
> Edit > Enable CA Validation > Save Settings.
NOTE:
1 When CA Validation from Wyse Management Suite server is enabled, the certicate should be present in the client.
All the operations such as, Apps and Data, Image Pull/Push is successful. If certicate is not present in the client,
the Wyse Management Suite server provides one generic audit event message Failed to Validate Certicate
Authority under Events page. All the operations such as, Apps and Data, Image Pull/Push is not successful.
2 When CA Validation from Wyse Management Suite server is disabled, then the communication from server and
client happens in secure channel without Certicate Signature validation.
5
Select the following options and enter the details:
Key/Certicate: Upload HTTPS key/certicate le pair (only PEM format is supported).
PKCS-12: Upload HTTPS PKCS-12 (.pfx, .p12). Apache intermediate certicate is required for IIS pfx.
6 Click Save.
Portal administration
189