Administrator Guide

Whats new in this release?
Windows 10 IoT Enterprise 2016 LTSB support for the following devices:
Edge Gateway—5000 Series
Embedded PC 3000
Embedded PC 5000
Updated EDM help URL—EDM help has a separate URL which is determined based on the available licenses.
Advanced application policy
Ability to push multiple application packages within single policy.
Applies policy to the devices that matches operating system or platform lters; or operating system and platform lters.
Supports preinstallation, and postinstallation scripts.
Supports auto publish image, and application policies for new devices. The list of the group image, and application policies from the
server should be obtained, when a device registers, re-registers, or changes the group.
NOTE: This feature is available for the Windows devices.
Localization support for French, Italian, German, Simplied Chinese, Japanese, and Spanish in the Wyse Management Suite web
console.
On-premise installer enhancements—The on-premise installer enhancements for the following actions:
Option to use existing database that can be installed on a same machine or separate machine as EDM Server.
Option to change default ports of all the services.
Upgrade support from Edge Device Manager R15.
Unied Wyse Device AgentThe Unied Wyse Device Agent is a simple and fast installer for windows devices. It is a single agent for
thin clients and the IoT devices.
Groups page enhancement—The User count is removed and if you click the number of devices, it takes you to the devices page with
the selected group lter, and if you click the number of noncompliant devices, it takes you to the devices page with the selected group
and noncompliance lter.
Supports BIOS update for the Windows devices—Windows Gateway and Embedded PC BIOS can be updated from the Wyse
Management Suite console.
Performance—EDM R16 is tested with 120,000 devices.
NOTE
: Administrator must follow the document to congure this environment.
Operating system and agent version lters—New lters for operating system and agent versions are added. When a device is
registered, the operating system and agent lter are added with the versions.
MySQL for private cloud—EDM can be installed with MySQL by using the Custom Installation option.
NOTE
: The feature is tested for the version 5.6.37.
Heartbeat and check-in-v2You can congure heartbeat and check-in interval in the Portal Administration page. The agents fetches
the pending commands post heartbeat conguration. For private cloud, the heartbeat interval ranges from 5–6 hours, and for public
cloud ranges from 1–6 hours and the Check-in interval ranges from 8 to 24 hours. The Heartbeat interval is not aected by the device
status—oine or online.
CA Validation for le repository—Private or public cloud of EDM allows CA validation conguration to download les from a remote
repository and it is available for all license types. Without this conguration, WDM le repository should have a CA signed certicate or
HTTP download must be enabled. It is not applicable for imaging jobs. CA validation aects les which are present only in the le
repository only. Downloading the le from WDA server APIs such as EULA, wallpaper, and logo is not aected. A global administrator
can turn the CA validation to ON/OFF for each repository from
Portal Administration > File Repository.
EDM console page size and lter enhancementYou can congure the size from the server for 10 to 100. It provides an option to save
the lter and administrator can make it as default lter.
Supports Apply to devices on check-in option—The Advanced application policies—for pro license has a drop-down Apply to devices
on check-in, when this option is selected, you can select the maximum number of retries. The Standard application policies for a pro
2
Whats new in this release? 11