Administrator Guide

Table Of Contents
4. Click Export.
NOTE: The number of Public Cloud licenses is adjusted based on the number of thin client seats exported to the Private
Cloud.
5. Copy the generated license key.
6. Log in to Wyse Management Suite Private Cloud console.
7. Go to Portal Administration > Accounts > Subscription.
8. Import the exported license key to the Private Cloud.
NOTE: The license cannot be imported if it has insufficient thin client seats to manage the number of devices currently
being managed in the Private Cloud. In this case repeat steps 38 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 certificate 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 Certificate: Select the Certificate Validation check box to enable the CA validation for private cloud. All the
communication from the server and the client including file download, OS image download from Local Repo uses the
certificate.
NOTE:
To Enable CA Validation for Remote Repo, Go to Portal Administration > File Repository > Select the Repository
> Edit > Enable CA Validation > Save Settings.
NOTE:
a. When CA Validation from Wyse Management Suite server is enabled, the certificate should be present in the
client. All the operations such as, Apps and Data, Image Pull/Push is successful. If certificate is not present in
the client, the Wyse Management Suite server provides one generic audit event message Failed to Validate
Certificate Authority under Events page. All the operations such as, Apps and Data, Image Pull/Push is not
successful.
b. When CA Validation from Wyse Management Suite server is disabled, then the communication from server and
client happens in secure channel without Certificate Signature validation.
5. Select the following options and enter the details:
Key/Certificate: Upload HTTPS key/certificate file pair (only PEM format is supported).
PKCS-12: Upload HTTPS PKCS-12 (.pfx, .p12). Apache intermediate certificate is required for IIS pfx.
6. Click Save.
182
Portal administration