Administrator Guide

repository and local repository. The software can be installed on a physical or a virtual machine. Also, it is not necessary that
the software repository and the Wyse Management Suite server have the same operating system.
Functional areas of management console
The Wyse Management Suite console is organized into the following functional areas:
● The Dashboard page provides information about the current status on each functional area of the system.
● The Groups & Configs page employs a hierarchical group policy management for device configuration. Optionally,
subgroups of the global group policy can be created to categorize devices according to corporate standards. For example,
devices may be grouped based on job function, device type, and so on.
● The Users page enables local users and users imported from the Active Directory to be assigned as global administrator,
group administrator, and viewer roles to log in to Wyse Management Suite. Users are given permissions to perform
operations based on the roles that are assigned to them. Also, the End User tab is added for end user management.
● The Devices page enables you to view and manage devices, device types, and device-specific configurations.
● The Apps & Data page enables management of device applications, application inventory, and file repository.
● The Rules page enables you to add, edit, and enable or disable rules such as auto grouping and alert notifications.
● The Jobs page enables you to create jobs for tasks such as reboot, Wakeup On LAN, and application or image policy that
must be deployed on registered devices.
● The Events page enables you to view and audit system events and alerts.
● The Portal Administration page enables you to configure various system settings such as local repository configuration,
Dell Hybrid Client license subscription, active directory configuration, and two-factor authentication.
Configuring and managing thin clients
● Configuration management—Wyse Management Suite supports a hierarchy of groups and subgroups. Groups can be
created manually or automatically based on the rules that are defined by the system administrator. You can organize the
groups based on the functional hierarchy, for example marketing, sales, and engineering, or based on the location hierarchy,
for example, country/region, state, and city.
NOTE:
In the Pro edition, you can add rules to create groups. You can also assign devices to an existing group
depending on the device attributes such as subnet, time zone, and location.
You can also configure the following:
○ Settings that apply to all devices in the tenant account which are set at the Default Policy group. These settings are the
global set of parameters that all groups and subgroups inherit from. The settings that are configured at lower-level
groups take precedence over the settings that were configured at the parent or higher-level groups.
For example,
￭ Configure the policies for default policy group (parent group). After configuring the policies, check the custom group
(child group) policies. Same sets of policies are applied to child group as well. Configurations in Default Policy Group
settings are the global set of parameters that all groups and subgroups inherit from parent group.
￭ Configure different settings for the custom group. The custom group receives both the payloads, but devices in the
Default Policy Group do not receive the payload that is configured for Custom Policy Group.
￭ Configure different settings for the custom group. The settings that are configured at lower-level groups take
precedence over the settings that were configured at the parent or higher-level groups.
○ Settings that are specific to a particular device which can be configured from the Device Details page. These settings,
like lower-level groups, take precedence over the settings that are configured in the higher-level groups.
When you create and publish the policy, the configuration parameters are deployed to all the devices in that group including
the subgroups.
After a policy is published and propagated to the devices, the settings are not sent again to the devices until you make a
change. New devices that are registered, receive the configuration policy that is effective for the group to which it was
registered. This includes the parameters that are inherited from the global group and intermediate level groups.
Getting started with Wyse Management Suite
15