Install Guide

Conguring and managing Edge Gateway devices
Creating a policy group and updating conguration
Registering devices to Edge Device Manager
Edge Device Manager Jobs
Publishing application to Edge Gateway/Embedded PC devices
Functional areas of the management console
The EDM management console is organized into the following functional areas:
1 Dashboard: This allows you to quickly view important summary of information for each functional area of the system.
2 Groups: This allows the exibility to employ hierarchical Group Policy management for device conguration. Optionally, sub-groups of
the Global Group Policy can be created to categorize devices according to corporate standards. For example, devices may be grouped
based on job functions, device type, bring-your-own-device, and so on.
3 Users: Local users and users imported from Active Directory can be assigned global administrator, group administrator, and viewer
roles to login to EDM. Users are given permissions to perform operations based on roles assigned to them.
4 Devices: This allows you to view and manage Devices, Device Types, and device-specic Conguration.
5 Apps & Data: This allows you to manage device Application inventory and policies.
6 Rules: This allows you to add, edit, and enable or disable rules such as auto grouping and alert notications.
7 Jobs: Creates job for any task such as reboot, WOL, and application/image policy that needs to be pushed to registered devices.
Administrator can track status of jobs by navigating to this tab.
8 Events: This allows you to view and audit system events and alerts.
9 Portal Admin: This allows administrators to perform system administration tasks such as local repositories, Active Directory Connector
operations, Subscriptions, and other Self-Service settings/agreements out of the system. You can congure on-premises services and
enable two-factor authentication here. For more information, see Managing Administrators and Viewers of the Management Console
in the Administration Guide.
Conguring and managing Edge Gateway devices
The general approach to congure and manage Edge Gateway devices consists of the following high level steps:
Conguration management is done through Policy Groups, under the Groups tab of the Web Console. Up to 10 levels deep, EDM
supports a hierarchy of groups and subgroups. These Groups can be created manually or automatically based on dened rules and
needs. You can organize and manage based on functional groups (Example: Marketing, Sales and Engineering etc.). Others may want to
organize based on the locations of the devices (Example: Time zone as the rst level group, State at the second level, City at the third
level, Building at the fourth level, Floor at the fth level).
NOTE
: You can create rules to automatically create groups or assign devices to existing groups based on device attributes
such as subnet, time zone and location.
Settings or policies that apply to all the devices in the tenant account are set at the Default Policy group. This is the global set of
parameters that all groups and subgroups will inherit from.
Settings or parameters that are congured at lower level groups takes precedence over settings that were congured at the parent
or higher level groups.
Parameters that are specic to a particular device may be congured from the Device Details page.
Conguration parameters are pushed to all devices in that group and all the subgroups, when you create and publish the policy.
Once a conguration is published and propagated to the devices, the settings will not be sent again to the devices until the next
time the Administrator makes a change.
New devices that are registered receives the conguration policy that is eective for the group to which it was registered.
New devices that are registered receives the conguration policy that is eective for the group to which it was registered.
Applications, updates, and other such operations are done from the Apps and Data tab of the UI.
Applications are deployed based on Policy Groups.
18
Installing Edge Device Manager on-premise and initial setup