Skip to content

Configurations

Manage Users

Users are the people who interact with Entgra UEM Server. Users can belong to either the administrator or user role type. The super tenant administrator and a tenant administrator belongs to the administrator role type; while, all other end-users belong to the user role type. The organization does not need to add users manually, if Entgra UEM Server is connected to a user store. UEM Server users are not allowed to edit user details once they have been added. You need to delete the current user and create a new user, if the need arises to change user details.

Add Users

Follow the instructions below to add a user:

  1. Sign in to the Entgra UEM Server console.
  2. Click Create + in the top right corner and select User.

    Add new user

  3. Provide the required details and click Add.

    Add new user

    Field Description
    User Store Domain Specify the user store domain.
    First Name Provide the first name.
    Last Name Provide the last name.
    Username Provide the user name. This should be minimum 3 characters long and without any whitespaces.
    Email Address Provide the email address.
    Password Provide a passowrd.
    Confirm Password Re-type the password to confirm it.
    User Roles Specify the role of the user. A single user can can have many roles.

View Users

  1. You can view existing users via the user table.

    View user

Search Users

  1. Click on the Search Users bar on top of the users table.

  2. Add the searching tags and then click Search.

    Search user

Update Users

  1. Go to Actions section of the user you want to update.
  2. Click Edit User.
  3. Edit the required fields and click Update.
  4. If you wish to reset the password, add the new password and click Reset Password.

    Update user

Remove Users

  1. Go to the Users tab in the navigation bar.
  2. Go to the Actions section of the user you want to remove.
  3. Click Remove Role.

    Delete user

Manage Roles

Entgra UEM Server is shipped with a set of default roles. However, if required, tenant administrators are able to create new customized roles. Tenant administrators can use roles to manage the users and their devices, while end users allocated with device operation permissions can manage their own devices via the Entgra UEM Server Console. Administrators can create roles, assign them to a user or a group of users, and edit or delete existing roles.

Add New Roles and Assigning Permissions

Follow the instructions below to add a role:

  1. Sign in to the Entgra UEM Server console.

  2. Click Create + in the top right corner and select Role.

    Add new role

  3. Provide the required details and click Add.

    Add new role

  4. Define the permissions that need to be associated with the role you created by selecting the permissions from the permission tree.

    Add new role

    Device Management Permissions
    Permission Description
    device-mgt/roles/view Permission to access the view roles API.
    device-mgt/roles/manage Permission to access the manage roles API.
    Permission Description
    device-mgt/authorization/verify Permission to access the API that enable to verify authorization.
    Permission Description
    device-mgt/notifications/view Permission to access the view notification API.
    Permission Description
    device-mgt/devices/dep/add Permission to access the add dep devices API.
    device-mgt/devices/dep/view Permission to access the view dep devices API.
    device-mgt/devices/disenroll/android Permission to access the disenroll android devices API.
    device-mgt/devices/enroll/windows Permission to access the enroll windows devices API.
    device-mgt/devices/enroll/ios Permission to access the enroll ios devices API.
    device-mgt/devices/enroll/android Permission to access the enroll android devices API.
    device-mgt/devices/change-status Permission to access the change device status API.
    device-mgt/devices/owing-device/view-analytics Permission to access the API that enable analytics of owing devices to be viewed
    device-mgt/devices/owing-device/add Permission to access the API that enable owing devices to be added
    device-mgt/devices/owing-device/remote-session Permission to access the API that enable remote session for owing devices to be created
    device-mgt/devices/owing-device/manage-geo-fence Permission to access the manage geo fence on owing devices API.
    device-mgt/devices/owing-device/remove Permission to access the remove owing devices API.
    device-mgt/devices/owing-device/operations/mac-os/shut-down Permission to access the shut down macOS devices API.
    device-mgt/devices/owing-device/operations/mac-os/app-store-restriction Permission to access the API that enable app store restriction on macOS devices
    device-mgt/devices/owing-device/operations/mac-os/restart Permission to access the restrat macOS devices API.
    device-mgt/devices/owing-device/operations/ios/vpn Permission to access the vpn API
    device-mgt/devices/owing-device/operations/ios/email Permission to access the email API
    device-mgt/devices/owing-device/operations/ios/per-app-vpn Permission to access the per app vpn API
    device-mgt/devices/owing-device/operations/ios/location Permission to access the location API
    device-mgt/devices/owing-device/operations/ios/wipe-data Permission to access the wipe data API
    device-mgt/devices/owing-device/operations/ios/wifi Permission to access the wifi API
    device-mgt/devices/owing-device/operations/ios/cellular Permission to access the cellular data API
    device-mgt/devices/owing-device/operations/ios/app-list Permission to access the application list API
    device-mgt/devices/owing-device/operations/ios/app-configurations Permission to access the app configuration API
    device-mgt/devices/owing-device/operations/ios/passcode-policy Permission to access the passcode policy API
    device-mgt/devices/owing-device/operations/ios/install-font Permission to access the install font policy API
    device-mgt/devices/owing-device/operations/ios/restriction Permission to access the restriction policy API
    device-mgt/devices/owing-device/operations/ios/lock Permission to access the device lock policy API
    device-mgt/devices/owing-device/operations/ios/apn Permission to access the APN policy API
    device-mgt/devices/owing-device/operations/ios/enterprise-wipe Permission to access the enterprise wipe policy API
    device-mgt/devices/owing-device/operations/ios/boolean-setting Permission to access the boolean setting policy API
    device-mgt/devices/owing-device/operations/ios/device-info Permission to access the API related to device info
    device-mgt/devices/owing-device/operations/ios/app-lock Permission to access the API related to device app lock
    device-mgt/devices/owing-device/operations/ios/notification Permission to access the API related to notifications
    device-mgt/devices/owing-device/operations/ios/wallpaper Permission to access the API related to device wallpaper policy
    device-mgt/devices/owing-device/operations/ios/clear-passcode Permission to access the API related to clear passcode policy
    device-mgt/devices/owing-device/operations/ios/ring Permission to access the API related to ring device
    device-mgt/devices/owing-device/operations/ios/app-to-per-app-vpn Permission to access the API related to app policyto per app VPN policy
    device-mgt/devices/owing-device/operations/ios/remove-app Permission to access the API related to remove apps on ios device
    device-mgt/devices/owing-device/operations/ios/global-proxy Permission to access the API related to global proxy setting policy
    device-mgt/devices/owing-device/operations/android/change-LockTask Permission to access the API related to change lock task policy
    device-mgt/devices/owing-device/operations/android/mute Permission to access the API related to mute android device
    device-mgt/devices/owing-device/operations/android/vpn Permission to access the API related to VPN setting policy
    device-mgt/devices/owing-device/operations/android/display-message Permission to access the API related to display message policy
    device-mgt/devices/owing-device/operations/android/global-proxy Permission to access the API related to global proxy setting policy
    device-mgt/devices/owing-device/operations/android/logcat Permission to access the API related to logcat
    device-mgt/devices/owing-device/operations/android/device-theme-audio Permission to access the API related to device theme audio
    device-mgt/devices/owing-device/operations/android/file-transfer Permission to access the API related to file transfering
    device-mgt/devices/owing-device/operations/android/update-app Permission to access the API related to update apps on android devices
    device-mgt/devices/owing-device/operations/android/change-lock-code Permission to access the API related to change lock code on android device
    device-mgt/devices/owing-device/operations/android/encrypt Permission to access the API related to encryption policy
    device-mgt/devices/owing-device/operations/android/enterprise-wipe Permission to access the API related to enterprise wipe
    device-mgt/devices/owing-device/operations/android/password-policy Permission to access the API related to password policy
    device-mgt/devices/owing-device/operations/android/permission-alternate-install Permission to access the API related to alternate app installation policy
    device-mgt/devices/owing-device/operations/android/clear-password Permission to access the API related to clear password on android device
    device-mgt/devices/owing-device/operations/android/send-app-conf Permission to access the API related to send application configurations to android device
    device-mgt/devices/owing-device/operations/android/camera Permission to access the API related to camera on android device
    device-mgt/devices/owing-device/operations/android/wipe Permission to access the API related to wipe android device
    device-mgt/devices/owing-device/operations/android/clear-application-data Permission to access the API related to clear application data on android device
    device-mgt/devices/owing-device/operations/android/reboot Permission to access the API related to reboot android device
    device-mgt/devices/owing-device/operations/android/unlock Permission to access the API related to unlock android device
    device-mgt/devices/owing-device/operations/android/applications Permission to access the API related to android device applications
    device-mgt/devices/owing-device/operations/android/ring Permission to access the API related to ring android device
    device-mgt/devices/owing-device/operations/android/location Permission to access the API related to android device location
    device-mgt/devices/owing-device/operations/android/dvice-theme-wallpaper Permission to access the API related to device theme wallpaper policy
    device-mgt/devices/owing-device/operations/android/info Permission to access the API related to android device information
    device-mgt/devices/owing-device/operations/android/lock Permission to access the API related to lock android device
    device-mgt/devices/owing-device/operations/android/wifi Permission to access the API related to wifi setting on android device
    device-mgt/devices/owing-device/operations/android/send-notification Permission to access the API related to send notifications to android device
    device-mgt/devices/owing-device/operations/android/uninstall-app Permission to access the API related to uninstall applications on android device
    device-mgt/devices/owing-device/operations/android/blacklist-app Permission to access the API related to blacklist applications on android device
    device-mgt/devices/owing-device/operations/android/install-app Permission to access the API related to install applications on android device
    device-mgt/devices/owing-device/operations/windows/ring Permission to access the API related to ring windows device
    device-mgt/devices/owing-device/operations/windows/enterprise-application Permission to access the API related to enterprise applications on windows device
    device-mgt/devices/owing-device/operations/windows/lock-reset Permission to access the API related to reset lock on windows device
    device-mgt/devices/owing-device/operations/windows/disenroll Permission to access the API related to disenroll windows device
    device-mgt/devices/owing-device/operations/windows/permission-scan
    device-mgt/devices/owing-device/operations/windows/location Permission to access the APIs related to windows device location
    device-mgt/devices/owing-device/operations/windows/applications Permission to access the API related to applications on windows device
    device-mgt/devices/owing-device/operations/windows/reboot Permission to access the API related to reboot windows device
    device-mgt/devices/owing-device/operations/windows/wipe Permission to access the API related to wipe windows device
    device-mgt/devices/owing-device/operations/windows/lock Permission to access the API related to lock windows device
    Permission Description
    device-mgt/app-usage/view Permission to access the API related to view app usage
    Permission Description
    device-mgt/admin/certificates/verify Permission to access the API related to verify certificates
    device-mgt/admin/certificates/details Permission to access the API related to certificates details
    device-mgt/admin/certificates/delete Permission to access the API related to delete certificates
    device-mgt/admin/certificates/view Permission to access the API related to view certificates
    device-mgt/admin/certificates/add Permission to access the API related to add new certificates
    device-mgt/admin/devices/permission-usage/view Permission to access the API related to view permission usages of devices
    device-mgt/admin/devices/permanent-delete Permission to access the API related to permanently delete devices
    device-mgt/admin/devices/update enrollment Permission to access the API related to update enrollment
    device-mgt/admin/device-type/view Permission to access the API related to view device type
    device-mgt/admin/device-type/config Permission to access the API related to configure device type
    device-mgt/admin/groups/view Permission to access the API related to view groups
    device-mgt/admin/groups/add Permission to access the API related to add new groups
    Permission Description
    device-mgt/device/api/subscribe Permission to access the API that enabling subscribe to APIs.
    Permission Description
    device-mgt/platform-configurations/view Permission to access the view platform configurations API.
    device-mgt/platform-configurations/manage Permission to access the manage platform configurations API.
    Permission Description
    device-mgt/metadata/view Permission to access the view metadata API.
    device-mgt/metadata/remove Permission to access the remove metadata API.
    device-mgt/metadata/update Permission to access the update metadata API.
    device-mgt/metadata/create Permission to access the create metadata API.
    Permission Description
    device-mgt/devicetype/deploy Permission to access the API that enable device type to be deployed.
    Permission Description
    device-mgt/policies/view Permission to access the view policy API.
    device-mgt/policies/manage Permission to access the manage policy API.
    Permission Description
    device-mgt/certificate/manage Permission to access the manage certificate API.
    Permission Description
    device-mgt/groups/add Permission to access the add new group API.
    device-mgt/groups/view Permission to access the view all groups API
    device-mgt/groups/devices/view Permission to access the API that enable devices of a group to be viewed.
    device-mgt/groups/devices/permission_types Permission to access the API that enable permission type of the devices to be viewed.
    device-mgt/groups/devices/add Permission to access the API that enable a device to be added to a group.
    device-mgt/groups/devices/remove Permission to access the API that enable a device to be removed from a group.
    device-mgt/groups/remove Permission to access the remove group API.
    device-mgt/groups/update Permission to access the update group API.
    device-mgt/groups/share Permission to access the share group API.
    device-mgt/groups/roles/view Permission to access the API that enable roles of a group to be viewed.
    Permission Description
    device-mgt/applications/manage Permission to access the manage application on devices API
    Permission Description
    device-mgt/users/manage Permission to access the manage users API
    device-mgt/users/view Permission to access the view all users API
    App Management Permissions
    Permission Description
    app-mgt/life-cycle/application/approve Permission to access the approve application API
    app-mgt/life-cycle/application/create Permission to access the create application API
    app-mgt/life-cycle/application/reject Permission to access the reject application API
    app-mgt/life-cycle/application/block Permission to access the block application API
    app-mgt/life-cycle/application/review Permission to access the review application API
    app-mgt/life-cycle/application/retire Permission to access the retire application API
    app-mgt/life-cycle/application/deprecate Permission to access the deprecate application API
    app-mgt/life-cycle/application/publish Permission to access the pub application APIlish
    Permission Description
    app-mgt/store/application/view Permission to access the API that enable app store applications to be viewed
    app-mgt/store/application/modify Permission to access the API that enable app store applications to be modified
    app-mgt/store/review/update Permission to access the API that enable app store reviews to be updated
    app-mgt/store/review/view Permission to access the API that enable app store reviews to be viewed
    app-mgt/store/subscription/install Permission to access the application install API
    app-mgt/store/subscription/uninstall Permission to access the application uninstall API
    app-mgt/store/admin/subscription/view Permission to access the API that enable app store subscriptions to be viewed
    app-mgt/store/admin/subscription/modify Permission to access the API that enable app store subscriptions to be modified
    app-mgt/store/admin/review/update Permission to access the API that enable app store reviews to be updated
    Permission Description
    app-mgt/publisher/admin/review/view Permission to access the API that enable app publisher reviews to be viewed
    app-mgt/publisher/admin/application/update Permission to access the API that enable app publisher applications to be updated
    app-mgt/publisher/application/view Permission to access the API that enable app publisher applications to be viewed
    app-mgt/publisher/application/update Permission to access the API that enable app publisher applications to be updated
    Other Permissions
    Permission Description
    Login Enables users to log in
  1. Click Assign.

Remove Roles

  1. Go to the Roles tab in the navigation bar.

  2. Go to the Actions section of the role you want to remove.

  3. Click Remove Role.

    Remove role

Search Roles

  1. Click on the Search Roles bar on top of the roles table.

  2. Add the searching tags and then click Search.

    Search role

Update Roles

  1. Go to the Actions section of the role you want to edit.

  2. Click Edit Role.

  3. Edit the required fields and click Update.

    Update role

Update Role Permissions

  1. Go to the Actions section of the role of which you want to update the permissions.

  2. Click Edit Permissions button.

  3. Add the required permissions and click Assign.

    Update role

Default Roles and Permissions

By default, Entgra UEM Server includes a set of roles. These default roles and permissions have been explained in the following subsections.

Default User Roles

The admin role is available by default in Entgra UEM Server:

  • If you are defining the permissions for a UEM Server administrator who needs to perform operations and configure policies, make sure to select admin. The admin permission allows the user to perform operations and configure policies for devices.

  • If you wish to create a user with administrative permission other than the default administrator in Entgra UEM Server, follow the steps given below:

    1. Add a new a role.
    2. Configure role permissions by specifically selecting the admin permission.

Manage Groups

This tutorial takes you through on how to group your enrolled devices. Grouping allows you to monitor and view device data of several devices at once.

Entgra UEM lets you to create groups in a Hierarchical Manner. It involves creating top-level groups as main categories and then further divide them into more specific groups (subgroups).

This way you can view any abnormal behavior of the devices at a glance and take necessary actions to prevent it.

Example

For example, sharing the devices in your lobby with your technician. For this purpose, you can create a group named Lobby, add the devices in the lobby to the created group, and share the group with the technician. Now the technician is able to view the devices in the group, analyze the data gathered by the devices and come to a conclusion on the devices that need attention.

By default, Entgra UEM Server has following groups:

  1. Bring Your Own Device (BYOD)
  2. Corporate-Owned Personally Enabled (COPE)

Let’s get started!

Add New Groups

Start off by creating a new device group in the Entgra UEM Server:

  1. Sign in to the Entgra UEM Server console.

  2. Click Create + in the top right corner and select Group.

    Add group

    Or go to Configurations, select Groups and click More groups.

    Add group

  3. Select the group type.

    1. Top Level Group

      • A top-level group, also known as a parent group, is the highest level in the hierarchical structure.
      • To create a top-level group, Click Continue after selecting this option.

      Add group

    2. Hierarchical Group

      • When you select this option, the new group you are creating will be placed as a sub-group under the selected top-level group in the hierarchical structure.

      • Select Hierarchical Group.

        Add group

      • Click on the group you want to create a sub group.

        Add group

      • Click Continue.

  4. Enter the appropriate Group Name and Group Description. Click Continue.

    Add group

  5. Select user roles from the dropdown to share the new group (Optional). Click Continue. Add group

    Click + icon to create a new user role and share the new group.

    Add group

    Refer to Create User Role for more details.

    Add group

View Groups

Grid View

  1. Sign in to the Entgra UEM Server console.

  2. Go to Configurations and select Groups.

  3. You can view all the existing top level groups here.

    View group

Single Group View

  1. Click on a specific group that you want to view more info.

  2. You can view all the available group actions and sub groups of the selected group in the detailed view.

    View group

Hierarchical View

  1. Click Hierarchical View to view all available top-level groups and sub groups in hierarchical manner.

    View group

  2. Select a specific group you want to view more info.

    View group

  3. Click Go to the group.

    View group

  4. You can view all the available group actions and sub groups of the selected group.

Search Groups

  1. Click on the Search Groups bar.

  2. Add relevant tags for searching and then click Search icon.

    Search group

Note

  • You can perform following actions to both top-level groups and subgroups. In this tutorial, we will focus on top-level groupsbut the same process can be used for subgroups.
  • Additionally, you can perform the same actions within the Single Group View as well.

Add Devices to Groups

Follow the steps given below to add device/s to the group that you created:

  1. Click Devices under the group you want to add the devices to.

    Add device

  2. Select the devices you need to add to the group and click Assign Devices.

    Select device

  3. To ensure that the devices have been added to the group, click on the device group and check if the devices are listed under the Already Assigned Devices section.

Share Groups with User Roles

You need to share the device groups you created with other users so that they too can access the devices.

Follow the steps given below:

  1. Click the Share icon on the group you want to share.

    Share group

  2. Share the groups with user roles.

    • Share the group with existing user roles by selecting the role name or names and clicking Share.

      Share group

    • Do you want to create a new role and share with the group? Click New Role and create the new role.

      Share group

    • Next, share the group with the user role you just created by selecting the role name from the same dropdown and clicking Share

    The permissions of the roles you selected will be merged to create the permissions for the new role.

Update Group Details

Follow the steps given below, to update the group name or description.

  1. Click the Edit icon on the group you want to update.

    Update group

  2. Update the details and click Update.

    Update group

Remove a Group

Note

After deleting a group with subgroups, those subgroups will be elevated to the same hierarchical level as the deleted group. This ensures that the structure and organization of the remaining groups are maintained even after the deletion.

Follow the steps given below, to delete a group from Entgra UEM Server.

  1. Click the Remove icon on the group you want to remove.

    Remove group

  2. Click Yes, to confirm that you want to delete the group.

Add Operations to Groups

  1. Click the Operations icon on the group you want to trigger operations.

    Remove group

  2. Click on the operation that you need to apply to the group. (Example: Reboot)

    Remove group

View Devices Location History

  1. Click Devices History on the group you want to view the location history of its corresponding devices.

    Device History

  2. Provide duration you want to see devices history and click on the serach icon.

    Device History

  3. You can view the location history of devices belongs to the selected group.

Manage Certificates

Add Certificates

  1. Sign in to the Entgra UEM Server console.

  2. Click Create + in the top right corner and select Certificate.

    Add certificate

  3. Enter the serial number and attach the certificate in the given fields. Click Save.

    Geofencing

View Certificates

  1. Sign in to the Entgra UEM Server console.

  2. Go to Certificates under Configurations.

    Add certificate

Remove Certificates

  1. Select the certificate record that you wish to delete and click on the delete icon.
  2. A dialog box will be prompted asking you to confirm that you wish to delete the record, where you can click OK, if so.

    Delete certificate

  3. Your certificate record will now be deleted.

Platform Configurations

General Configurations

Follow the instructions below to configure the general platform settings:

  1. Sign in to the Entgra UEM Server Endpoint Management Console.

  2. Click Platform Configurations under Configurations.

    Platform Configurations

  3. Click General Configurations under Platform Configurations.

    General Configurations

There are 8 main configuration sections for General Configurations:

  1. General
  2. Theme
  3. Enrolment
  4. FTP Server
  5. Location update
  6. Billing
  7. Evaluate tenant
  8. View Roles

General

The general platform configurations for Entgra UEM Server involves setting up configurations for monitoring how often the devices are enrolled with the server.

By following the steps below, you can modify general configurations;

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select General.

    General

  4. Fill in the required fields.

    Field Description
    Monitoring Frequency Define the Monitoring Frequency in seconds, to monitor the enforced policies on the devices.
    Publish for analytics The available options have been explained as follows: False - Use this option not to publish analytics, True - Use this option to publish analytics
  5. Click on Save.

Theme

The theme configuration allows customization of the visual appearance of the platform, providing a consistent and personalized user experience. Tenant admins can customize the platform's theme to align with the organization's branding guidelines.

Follow the instructions below to modify theme configurations:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select Theme.

    General

  4. Fill in the required fields.

    Field Description
    App Title The app title that appears in browser tabs. (I.E Endpoint Management).If not set, Entgra is used as default.
    Favicon The favicon will appear in browser tabs. Recommended: 16px x 16px
    Logo The logo uploaded will be shown on the sidebar. Recommended: min: 320px max: 1920px
    Logo Icon The logo icon uploaded will be shown when the sidebar is collapsed. If not set, the default Entgra icon is used.
    Footer Text The footer text uploaded will be shown in the footer of the console. Recommended: max. 100 char.
  5. Click Save.

Further explore this feature by referring to our comprehensive blog article

Unlocking The Power Of Personalization With Entgra UEM 5.2’S Per-Tenant Theming Feature

Enrolment

This functionality is used for uploading a set of serial numbers of devices and the user/group that they should be assigned to.

If you upload a JSON file with the device serial and its group prior to enrolling the devices, when enrolling, the server checks the incoming device's serial and looks up the matching group in the JSON, and assigns the device to the correct group.

Follow the steps given below to upload an enrollment config file:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select Enrolment.

    General

  4. Upload the enrollment config file (JSON file).

    Supported Foramt Examples
    • Enroll devices having the serial numbers only
      {"serialNumbers":["1","2","3"]}
      
    • Enroll devices having the serial numbers assigned against users
      {"userConfigurations":[{"username":"user1","serialNumbers":["1","2","3"]},{"username":"admin","serialNumbers":["4","5"]}]}
      
    • Enroll devices having the serial numbers to the specified group
      {"groupConfigurations":[{"groupName":"group1","serialNumbers":["1","2","3"]},{"groupName":"group2","serialNumbers":["4"]},{"groupName":"group3","serialNumbers":["6","7","8"]}]}
      
    • Enroll devices having the serial numbers assigned against users and then add those devices to assigned groups
      {"userConfigurations":[{"username":"user1","serialNumbers":["1","2","3","4","5"]},{"username":"user2","serialNumbers":["6","7","8","9"]}],"groupConfigurations":[{"groupName":"group1","serialNumbers":["1","2","3"]},{"groupName":"group2","serialNumbers":["4"]},{"groupName":"group3","serialNumbers":["6","7","8"]},{"groupName":"group4","serialNumbers":["9"]}]}
      
  5. Click on Save.

FTP Server

Under the FTP server section in General Platform settings, you can add a new FTP server.

Follow the steps given below to add a new FTP server:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select FTP server.

    FTP Server

  4. Add a new FTP server in there and click Add.

Location Update

The Location Update configuration is for enabling the geofencing feature required for Location-Based Services [LBS] in a multi-tenant environment. The feature is used for tracking the device using continuous location publishing on the Entgra UEM server.

By following the steps below, you can see the location being published continuously:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

    Location Update

  3. Select Location Update.

    Location Update

  4. Select Enable Location Tracker check box.

    Location Update

  5. Next, enroll a device to be tracked.

  6. Move the device to different locations (i.e., carry it around over to different loations).

  7. In the Endpoint Management Portal, locate the device.

  8. Select the Location History under Device Location.

    Location Update

  9. On the map view, you can see the locations that the device was moved to. The locations can also be filtered by date and time, as well by different types of views (plain view, timestamp view, location point view, animated view etc.).

    Location Update

There are some important points that need to be addressed to help the device send consistent location tracking data.

  • For location publishing to work consistently, location publishing permission should be configured as Allow all the time.

  • Any power saving/battery optimization configurations should be disabled.

The settings below are on different vendors about where and when the power saving configuration enables and exists:

  • Huawei: App launch (Settings > Apps > App launch)

  • Xiaomi Redmi: Auto Start

  • iPhone: Low power mode

  • Samsung: Power saving mode (Settings > Battery and device care > Battery > Limit apps and home screen)

Note: These settings may change according to the device model and the Android version.

Billing

The billing feature is used to generate the usages of the devices enrolled by each tenant.

Follow the instructions below to access the feature:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select Billing.

    FTP Server

  4. The super admin user has access to add the annual cost for a device for each tenant. Click Add a New Billing.

    FTP Server

  5. Select the tenant domain from the dropdown list.

    FTP Server

  6. Add the annual cost for a device belonging to the tenant.

    FTP Server

  7. Click Add.

  8. Super admin and other admins of the tenant will have the ability to generate usage reports for the devices they have utilized. Go to the Usage section in the main profile dropdown menu.

    FTP Server

  9. Enter start date and end date.

    FTP Server

    Field Description
    Start date The start of the usage period.
    End date The end of the usage period.
  10. Select the tenant domain from the dropdown list.

    FTP Server

    Note

    This option is only visible for super tenant admin users and is used to check the usage of other tenants.

  11. Click View Usage and then the usages of the tenant devices will be generated for the entered period.

    FTP Server

  12. Click Export Usage to generate the CSV file containing the usage data.

    FTP Server

Evaluate Tenant

In order to enable the Entgra UEM live chat feature for customers, a super admin must evaluate and approve their access.

Follow the instructions below to evaluate tenants for live chat feature:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select Evaluate Tenant.

    FTP Server

  4. Click Add a Tenant.

    FTP Server

  5. Select a new tenant to be evaluated from the dropdown list.

    FTP Server

  6. Click on Add.

  7. Click on the remove icon if you want to delete an existing evaluate tenant.

    FTP Server

View Roles

This functionality is used to define whether the publisher is able to view all available roles when publishing an app.

Follow the instructions below to modify the View Roles configs:

  1. Log in to the Endpoint Management Portal.

  2. Go to General Configurations under the Platform Configurations.

  3. Select View Role.

    View Roles

Android Configurations

Multiple tenants can use Entgra UEM Server. While maintaining tenant-based isolation, the Android configurations enable the tenants to customize the Android settings based on their own requirements.

PREREQUISITES

Follow the steps given below to configure the Android platform:

  1. Click the menu icon.

  2. Click CONFIGURATIONS.

  3. Click PLATFORM CONFIGURATIONS.

  4. Select Android Configurations.

There are 4 main configuration sections for Android:

  1. General configurations

  2. Policy configurations

  3. COPE/Kiosk configurations

  4. Android For Work

General

This section covers details about the preferred communication mechanisms used by Android device for server communication, user agreements and multiple other Android specific general configurations.

Android communication protocol

Local Polling

Type of Communication : Configures the preferred communication mechanisms used by Android device to server communication. There are 2 methods of communication available: Local Polling and FCM.

  1. Local Polling

    • The device will contact the Entgra UEM server periodically.
    • When Local poling is selected, a new field called polling interval is enabled. The agent will contact the server and try to fetch commands, based on the interval provided here (in seconds). Note that lowering this number will mean more network callls and high device battery usage.

    Note

    Due to Android restrictions, the minimum frequency here is 60 seconds.

  2. Firebase Cloud Messaging (FCM)

    • FCM will send a notification to the device when there are pending operations available for a specific device.
    • If FCM has been selected as the notifier type, a new field called API key will be enabled where the server key of the FCM configuration needs to be provided. FCM is more network and barrery usage friendly and recommended over local polling.
    • Also note that we do not send any sensitive data over FCM. FCM is mearly a wake up call to the agent and the agent will poll the server when it recieves such a wakeup to fetch the real commands.

    Note

    From Android 4.4 (KitKat) onwards, the OS does not allow applications to trigger wake-up commands when the trigger period is set to less than a minute. Therefore, make sure to set the notifier frequency to 60 seconds or more.

End User License Agreement (EULA) - This text will be shown to a user while enrolling via the agent. This can be used to show the end user agreement or any other information that the user must agree, in order to proceed with enrolment.

Android Location Configurations

Enable Continuous Device Location Publishing - If this is ticked, the server will publish data from devices to the analytics component. Note that the analytics must be enabled and configured prior to enabling this configuration

Android Firewall Configuration

Enable UEM Server Firewall Service - If this is enabled, the agent will to look up the entgra firewall application and start the firewall service. Note this requires certain components which are only available to certain customers. Please contact Entgra for more details

Policy

The configurations below serve as prerequisites for enforcing certain policies:

Field Description
Allowing Application List Set of comma separated package names. This is typically a set of system applications that are always allowed to run on devices. When a policy calculates the applications to be allowed-listed on a device, the list given here is always considered allowed. The reason for this is that certain OS level applications should not be disabled while allow-listing as those apps are critical to the operation of the device.
Force device renaming on enrollment If this is selected, the agent will prompt the user to provide a name for the device at enrolment. The given name will be the name that appears on the endpoint management portal. If this is not selected, the device name provided by the system will be used.

COPE/Kiosk

Fill the fields with required values and click Save to apply the changes to the device.

COPE/KIOSK

Field Details
Provisioning Component Package name of the Entgra Android agent’s device policy manager component. This is always the bellow value, unless the package name is customized ​​io.entgra.iot.agent/org.wso2.iot.agent.services.AgentDeviceAdminReceiver
Package checksum During the enrollment, this checksum is validated by Android to determine if the downoaded apk matches the checksum. Run the following command to get the checkSum value of the agent, cat <AGENT_APK_FILE_PATH> | openssl dgst -binary -sha256 | openssl base64 | tr '+/' '-_' | tr -d '='
Download Location Android agent download location. (ex: http://192.168.8.20:8080/android.apk)
Server Address The address of the server. This is used as the server address when enrolling the device. (ex:https://gw.entgra.net:443
Enable Encryption Upon enrolment if this device must be encrypted, select this option. Not applicable to BYOD devices
Enable All System Apps This will indicate whether all system apps should be enabled after the device is enrolled.
Ownership Type Type of the ownership

Android For Work

Android enterprise configurations

Before you start using the capabilities of Android Enterprise, there is a configuration step that enables Entgra to connect to Google Enterprise. This step will allow Entgra to manage your device uniquely for your enterprise. In more technical terms, Entgra requires a special token to talk to Google APIs (known as ESA) and a unique enterprise ID to identify your organization and its devices and apps uniquely.

The steps below will enable you to configure Android Enterprise:

  1. Get an access token from Entgra - This token provided by Entgra is only valid for a period of 1 hour. Therefore, please make sure to mention the time that you are planning to perform these steps. This is a token that gives you access to start the onboarding process which will allow you to register a new enterprise ID and a token from Google known as ESA.

    • If you are using Entgra UEM cloud, create a new ticket in the support system with the following title Requesting a token for Android Enterprise Onboarding. In the description, please mention the time window you are planning to perform the onboarding steps. Example: We are planning to configure at 9AM EST on 24/02/2021.

    • If you are using the on-premises version, please send an email to biz-dev@entgra.io with the following subject Requesting a token for Android enterprise onboarding. In the body, please mention the time window you are planning to perform the onboarding steps. Example: We are planning to configure at 9AM EST on 24/02/2021.

  2. You will need a Google account which is dedicated to EMM related work. We recommend creating a new Google account (a free account). Please keep this account details securely as this will be having administrative rights over your enterprise account.

  3. If you have any other Google accounts you have signed in using your browser, please open a private browser window and sign in to your new Google account.

  4. Before you begin, please note that during the onboarding process, you will be prompted to provide your organization name and fill the following form. Filling this form is optional based on your countries regulations such as GDPR. Also note that agreeing to the managed Google Play agreement at the bottom of this form is mandatory. Please review this prior to starting the onboarding process.

Google Play Agreement

Configuration Steps

This step will allow Entgra to manage your device uniquely to your enterprise. In more technical terms, Entgra requires a special token to talk to Google APIs (known as ESA) and a unique enterprise ID to identify your organization and its devices and apps uniquely.

  1. On the Android Platform Configurations, Go to Android For Work section as shown in the bellow image.

    Android Enterprise Configuration

  2. Under EMM initiating section, click here.

  3. A popup will be displayed as below. Enter the token you received from Entgra and click OK.

    Google Play Agreement

  4. You will be redirected to Google’s Enterprise onboarding page where you are required to provide your organisation name.

    Google Play Agreement

  5. Fill the form and click Confirm. On the next screen that appears, click Complete registration.

    Google Play Agreement

  6. You will be redirected to the platform configuration page. Stay on this page until you see the following notification on the top right corner that shows the end of successful completion of configurations.

    Google Play Agreement

  7. Enter the ESA and the Enterprise ID received from entgra and click Save.

Now the link between Entgra UEM and your new enterprise is established successfully! We have everything we need to start enrolling and importing applications from Google Play store to the UEM server.

Follow our Android Enterprise Guide for details on the enterprise configurations for Android.

Unenroll Enterprise from EMM

If you want to Unregister your enterprise from the UEM server, click Unenroll. This action cannot be undone.

Unenroll

iOS configuration

This section takes you through the additional server configurations required for setting up an iOS device. Apple server configurations, both for iOS and Mac OS are given here in detail along with the platform configurations, based on the required enrollment method. The configurations necessary for enrolling the device at the Apple ABM (Apple Business Manager), for both iO and Mac OS, are listed in the section that follows.

Multiple tenants can use Entgra UEM while maintaining tenant-based isolation. The iOS configurations enable the tenants to customize the iOS settings based on their own requirements.

Follow the steps given below to configure the Android platform:

  1. Sign in to the Entgra UEM Server Endpoint Management console.

  2. Click Platform Configurations under Configurations.

  3. Click iOS Configurations under Platform Configurations.

    iOS Configurations

There are 4 main configuration sections for iOS Configurations:

  1. MDM Profile
  2. EULA
  3. APNS
  4. ABM

MDM Profile

By following the steps below, you can modify SCEP Certificate, Profile and MDM Configurations;

  1. Log in to the Endpoint Management Portal.

  2. Go to iOS Configurations under the Platform Configurations.

  3. Select MDM Profile.

    MDM Profile

iOS SCEP Certificate Configurations

When an iOS device enrolls with Entgra UEM two iOS Simple Certificate Enrollment Protocol (SCEP) certificates will be created on the fly based on the given SCEP configurations.

Field Description
Country (C) The country where the tenant is based.
State (ST) The state where the tenant is based.
Locality (L) The locality where the tenant is based.
Organization (O) The name of the organization where the tenant is based.
Organization unit (OU) The name of the organization unit where the tenant is based.

iOS Profile Configurations

The details of the organization need to be added.

Field Description
Organization Display Name The name of the organization.

iOS MDM Configurations

The details with respect to the iOS IoTS APNS certificate need to be added.

Field Description
MDM Certificate Select the iOS IoTS APNS certificate that was previously created.
MDM Certificate Password The password that was used when converting the IoTS certificate from a .pem file to the .pfx file.
MDM certificate topic ID The USER ID mentioned in the IoTS signing certificate.
Mode The available modes have been explained as follows: Production - Use this option if you are configuring IoTS for a production environment, Developer - Use this option if you are configuring IoTS for a testing environment.

EULA

Provide the End User License Agreement(EULA) that a user must adhere to when enrolling an iOS device with IoTS.

By following the steps below, you can modify the license agreement for end users;

  1. Log in to the Endpoint Management Portal.

  2. Go to iOS Configurations under the Platform Configurations.

  3. Select EULA.

    EULA

APNS

The details with respect to the Apple Push Notification Service(APNS) need to be added here. By following the steps below, you can configure APNS;

  1. Log in to the Endpoint Management Portal.

  2. Go to iOS Configurations under the Platform Configurations.

  3. Select APNS.

    APNS

    Field Description
    APNS Certificate Select the APNS certificate that was previously created.
    APNS Certificate Password Enter the password provided when exporting the iOS APNS certificate.
    Mode The available modes have been explained as follows: Production - Use this option if you have configured a production APNS certificate, Developer - Use this option if you have configured a development APNS certificate.

ABM

To effectively manage your DEP-enrolled devices within the Entgra UEM console, follow these steps to enable and configure the Apple Business Manager(ABM).

By following the steps below, you can configure ABM;

  1. Log in to the Endpoint Management Portal.

  2. Go to iOS Configurations under the Platform Configurations.

  3. Select ABM.

    ABM

    Field Description
    Agent App Id The App ID of the ABM agent stored in the internal app store.
    Consume Key Consumer key value of the ABM token.
    Consumer Secret Consumer secret value of the ABM token.
    Access Token Access token value of the ABM token.
    Access Secret Access secret value of the ABM token.
    Access Token Expiry Access token expiry value of the ABM token.

Windows configuration

Multiple tenants can use Entgra UEM while, maintaining tenant based isolation. The Windows configurations enable the tenants to customize the Windows settings based on their own requirements.

Follow the steps given below to configure the Windows platform:

  1. Sign in to the Entgra UEM Server Entgra UEM Console.

  2. Click Platform Configurations under Configurations.

  3. Click Windows Configurations under Platform Configurations.

    Windows Additional Config

There are 2 main configuration sections for Windows Configurations:

  1. General
  2. Agent

General Configurations

By following the steps below, you can modify the general configurations for Windows;

  1. Log in to the Endpoint Management Portal.

  2. Go to Windows Configurations under the Platform Configurations.

  3. Select General Configurations and enter the requested information.

    Windows Additional Config

    Field Description
    Polling Interval Specify the time period for the wake-up command to automatically trigger the Entgra UEM client as the notifier frequency. Ensure to specify the notifier frequency in seconds.
    End User License Agreement (EULA) Provide the license agreement that a user must adhere to, when enrolling an Windows device with Entgra UEM Server.
  4. Click SAVE.

Agent Configuration

Apart from the General Configurations, there is Windows Agent Configuration as well. By following the steps below, you can modify the general configurations for Windows;

  1. Log in to the Endpoint Management Portal.

  2. Go to Windows Configurations under the Platform Configurations.

  3. Select Agent Configurations and enter the requested information.

    Windows Additional Config

    Field Description
    Appx Hosted Location Location of the appx package of the Windows agent where it hosted.
    Appx Package Family Name This field should contain the family name of the Windows agent package.
    Appx Certificate Upload the appx certificate.
    Appx Certificate Hash Hash number of the appx certificate
    MSI Hosted Location Location of the MSI package of the Windows agent where it hosted
    MSI Product ID The product id is a GUID identifying Windows Installer package. It associates with an MSI file and can be used to verify sources.
    MSI File Hash Hash number of the MSI file that needs to configure the MSI file for agent installation.
  4. Click SAVE.

Alerting Configurations

Geo Alerts

  1. Sign in to the Entgra UEM Server Endpoint Management Console.
  2. Click Configurations.
  3. Go to Platform Configuration.
  4. In Alerting Configurations, select the Geo Alerts.

    Geo

  5. Fill in the required fields.

    Geofencing

  6. Click Save.

Reporting Configurations

Mail Alerts

This feature enables users to configure an email template from the Platform Configurations and receive mail alerts when a SIM change is detected.

By following the steps below, you can modify the mail alert configurations;

Note

Before proceeding, make sure to enable analytics on general platform configurations.

  1. Sign in to the Entgra UEM Server console.

  2. Click Platform Configurations under Configurations.

  3. Click Reporting Configurations under Platform Configurations.

    Reporting

  4. Select Mail Alerts.

    Mail

  5. Fill in the required fields.

    Reporting Email Configurations

    Field Description
    Mail Sender The email address of the account that will be used to send mails.
    Mail Sender Name A custom name can be given to the mail sender. Otherwise the default name will be “Reporting Mail Alerts”.
    Mail Sender Password The app password for the given email address. Note: The password for your account should not be an ordinary password but an application password generated for your Google account. Visit Support for more details.
    Mail Receivers A list containing one or more email addresses to send the mail alert.
    Mail Subject The subject of the email.

    Email Template

    Field Description
    Mail Logo URL A logo URL which is publicly accessible to anyone on the internet will be added to the header of the email template. If no value is given by default, the tenant’s allowlist logo URL will be added to the email template.
    Mail Greeting A mail greeting can be added. If no value is given by default, “Hello!” will be added to the mail template.
    Mail Body A mail body can be added if needed with multi-line support. If no value is given by default, “We have detected a SIM change. You might want to take a look.” will be added to the mail template.
    Mail Signature A mail signature can be added if needed with multi-line support. If no value is given by default, “Regards, Entgra” will be added to the mail template.
    Mail Footer Text An email footer can be added which supports hyperlink support.

    Email Template Color Theme

    Field Description
    Mail Header Background Color Changes the email template header background color. Default color is a variation of Steel Blue (#4288ba).
    Mail Footer Background Color Changes the email template footer background color. Default color is a variation of Steel Blue (#4288ba).
  6. Click Save.