Administrator Guide

ManualsBrandsDell ManualsConverged InfrastructureWyse Management Suite

201

202

203

204

205

206

207

208

209

210

Table Of Contents

Dell Wyse Management Suite Version 1.4 Administrator’s Guide
Introduction to Wyse Management Suite
- Editions
- What is new in this release?
Getting started with Wyse Management Suite
- Logging in to Wyse Management Suite on public cloud
  - Changing your password
  - Logging out
- Prerequisites to deploy Wyse Management Suite on the private cloud
- Functional areas of management console
- Configuring and managing thin clients
Wyse Management Suite dashboard
- View alerts
- View the list of events
- View the device status
- Change user preferences
- Access online help
- Change your password
- Log out
Managing groups and configurations
- Add a group
- Edit a group
- Remove a group
- Edit an unmanaged group
- Configure a global level policy
- Configure a group level policy
- Configure a device level policy
- Export group policies
- Import group policies
- Edit the ThinOS policy settings
  - ThinOS—Wizard mode
  - ThinOS—Advanced mode
- Edit the Windows Embedded Standard policy settings
- Edit the Linux policy settings
- Edit the ThinLinux policy settings
- Editing Teradici policy settings
- Edit the Wyse Software Thin Client policy settings
Managing devices
- Methods to register devices to Wyse Management Suite
  - Registering ThinOS devices by using Wyse Device Agent
  - Registering Wyse Software Thin Client to Wyse Management Suite by using Wyse Device Agent
  - Registering Linux thin clients using Wyse Device Agent
  - Registering Wyse Embedded Standard Thin Clients to Wyse Management Suite by using Wyse Device Agent
  - Registering ThinLinux version 2.0 devices by using FTP INI method
  - Registering ThinLinux version 1.0 devices by using FTP INI method
  - Registering ThinOS devices by using the FTP INI method
  - Registering ThinLinux thin clients by using Wyse Device Agent
  - Registering devices by using DHCP option tags
  - Registering devices by using DNS SRV record
- Searching a device using filters
- Saving the current filter
- Querying the device status
- Locking the devices
- Restarting the devices
- Unregistering the devices
- Resetting to factory default settings
- Changing a group assignment
- Sending messages to devices
- Activating the devices
- Viewing device details
- Managing device summary
- Viewing system information
- Viewing device events
- Viewing installed applications
- Rename the thin client
- Configuring remote shadow connection
- Shutting down devices
- Tagging devices
- Device compliance status
- Pulling Windows Embedded Standard or ThinLinux image
- Upgrading ThinLinux 1.x to 2.1 and later versions
  - Prepare the ThinLinux 2.x image
  - Upgrade ThinLinux 1.x to 2.x
- Requesting a log file
- Troubleshooting your device
Apps and data
- Application policy
- Image policy
- Managing file repository
  - How to change wallpaper for all devices belonging to marketing group
Managing rules
- Editing a registration rule
- Creating unmanaged device auto assignment rules
- Editing unmanaged device auto assignment rule
- Disabling and deleting rule
- Saving the rule order
- Adding a rule for alert notification
- Editing an alert notification rule
Managing Jobs
- Searching a scheduled job by using filters
- Scheduling the image policy
- Scheduling an application policy
- Scheduling the device command job
Managing Events
- Searching an event or alert by using filters
Managing users
- Adding a new admin profile
- Editing an admin profile
- Deactivating an admin profile
- Deleting an admin profile
- Editing a user profile
- Importing the CSV file
Portal administration
- Adding the Active Directory server information
- Importing users to public cloud through active directory
- Alert classifications
- Creating an Application Programming Interface-API accounts
- Accessing file repository
- Configuring other settings
- Managing Teradici configurations
- Enabling Two-Factor authentication
- Generating reports
- Enabling multi-tenant accounts
- Enabling custom branding
- Managing license subscription
- Managing system setup
Configuring Wyse Easy Setup by using Wyse Management Suite
- Installing Wyse Easy Setup
- Deploying a Wyse Easy Setup configuration
Configuring Wyse Converter for PCs by using Wyse Management Suite
- Registering Wyse Software thin client to Wyse Management Suite
- Registering Wyse Software Thin Client to Wyse Management Suite by using Wyse Device Agent
- Registering devices by using DHCP option tags to Wyse Management Suite
- Registering Wyse Software thin clients by using DNS SRV record to Wyse Management Suite
- Configuring the Wyse Software thin client by using Wyse Management Suite
Teradici device management
- Discovering Teradici devices
- CIFS use case scenarios
Wyse Device Agent
Troubleshooting Wyse Management Suite
Installing or upgrading Wyse Device Agent
- Upgrading Wyse Device Agent using Wyse Management Suite application policy
- Installing Wyse Device Agent manually
- Installing or upgrading Wyse Device Agents on ThinLinux and Linux clients
Wyse Management Suite feature matrix
Supported thin clients on Wyse management Suite
Wireless profiles password editor
- Configuring windows wireless profile
- Configuring the Wireless Profiles Password Editor
- Limitations of Wireless Profiles Password Editor
Create and configure DHCP option tags
Create and configure DNS SRV records
Steps to change the host name to IP address

Teradici device management

The Teradici device management section provides the information about managing and discovering the teradici divices. The teradici

management console uses SDK’s to support management, conguration for tera devices. This is applicable only for Wyse Management

Suite private cloud with pro license type. For more information on Teradici conguration policies, see Editing Teradici policy settings.

Topics:

• Discovering Teradici devices

• CIFS use case scenarios

Discovering Teradici devices

Prerequisites

• 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 congurations.

• 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 congured security level, you may also need to provision endpoints with an EBM/EM certicate.

Endpoints congured for medium or high security must have a trusted certicate in their certicate store before they can connect to an

EBM or EM. For some endpoints, certicates may be pre-loaded by the vendor as a factory default. Otherwise, you can manually upload

certicates using an endpoint's AWI.

Endpoints that are congured for low security do not need an MC certicate in their trusted certicate 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 certicate's

ngerprint.

• They are discovered using the manual discovery method.

Table 296.

Certicate Requirements for Endpoints

Discovery Method Low Security Medium Security High Security

DHCP/DNS discovery without

EBM ngerprint provisioned

Certicate required Certicate required Not applicable

DHCP/DNS discovery with EBM

ngerprint provisioned

Certicate not required Certicate required Not applicable

Discovery initiated by an

endpoint congured for a high

security environment

Not applicable Not applicable Certicate required

Teradici device management 207