Skip to main content

KMA Quick Start

Updated over 5 months ago

Pre-Setup Requirements for This Guide

Your enterprise account has been created and the subscription license has been authorized by the KiwiCloud team.

The Serial Number (SN) of the device you will be operating has already been imported into your enterprise account and can be found under [Device Enrollment Info] → [Pending Management].

The following content is referenced with the KMA equipment

Notice: The KMA management mode currently supports only iMin-branded devices. To use this mode with devices from other brands, compatibility adaptation is required. For adaptation requests, please contact our sales team.

1. System Initialization

Note: After the account is created, the system will send the KiwiCloud Console URL, login account, and password to the account holder's email.

  1. Open a browser and enter the KiwiCloud platform URL.

  2. Enter the account username and password, then click the Login button.

Step 2: Configure the Default Policy (Optional)

Navigate to: ☰ System Management > ☰ System Settings > 📑 Default Device Policy > 📑 Default KMA Device Policy.

  1. Modify the Password, Restrictions, and Wi-Fi policy settings as needed. For example: ➊ Disable Hotspot and Network Sharing, ➋ Set screen timeout to 30 seconds.

  2. Click the Save button at the bottom to save—changes will take effect immediately.

Additional Info: For devices managed via KMA control, once they complete the enrollment process, the "Default KMA Device Policy" configured here will be automatically applied to those newly enrolled devices.

Step 3: Set Non-Compliance Actions (Optional)

Navigate to: ☰ System Management > ☰ System Settings > 📑 Compliance Settings.

  1. Set Prohibit Use Equipent to 0 days (if the device is non-compliant, it will be disabled immediately), and Restore Factory Setting to 3 days (if the device remains non-compliant for more than 3 days, it will be reset to factory settings).

  2. Click the Save button at the bottom to apply—changes will take effect immediately.

2. Enroll Device (KMA Enrollment)

Step 1: Prepare the Device

  1. Ensure the device already has the KiwiCloud App installed.

    If the KiwiCloud App is not installed on the device, please contact your enterprise administrator!

  2. Power on the device, connect it to a network, and ensure the device can access the Internet.

Step 2: Perform Enrollment

  1. Open the KiwiCloud App. The app will display the Enrollment page.

  2. Tap the Enroll button to enroll the device. Upon successful enrollment, the KiwiCloud App will enter its main page.

  3. (Optional) Verify the device was enrolled successfully. In the KiwiCloud UEM console, navigate to ☰ Enrollment > ☰ Device Enrollment Info > 📑 Managed, and search for the device’s Serial Number. If the SN is found, it confirms the device has completed enrollment.

If the SN record cannot be found, please contact the enterprise administrator or the KiwiCloud support team.

3. Device Group Management (Optional)

Step 1: Create a Group

  1. Navigate to: ☰ Device Management > ☰ Device Grouping.

  2. Click the Create Device Group button. Then ➊ Enter a group name (e.g., "Singapore"), ➋ Select the devices to include in this group, ➌ Click Submit to create the device group.

4. Recommended Process for Initial Business Configuration

4.1 Configure Device Policy

Step 1: Configure and Deploy a Device Policy

  1. Navigate to: ☰ Device Management > ☰ Device Policies.

  2. Create and publish a policy. Click the Create Policy → KMA Policy button:

2.1 Enter a policy name (e.g., "Singapore KMA Device Policy") and click the Next Step button.

2.2 Configure the device policy. For example, under the System Settings tab: ➊ Disable "Bluetooth", then ➋ Click the Next Step button.

2.3 Associate devices/groups. Under the Device Grouping tab, ➊ Find and select the previously created "Singapore" group, then ➋ Click the Save and Publish button to deploy the policy.

Step 2: Verify the Policy Deployment Result

  1. Console verification: Find the device policy "Singapore KMA Device Policy" that was just published, click the Detailsbuttonto open the policy details page. Click the Operation Log 📑 tab to check the deployment status.

  2. Device-side verification method 1: On the device, open the KiwiCloud App to verify compliance. Tap the Compliance Policybuttonand check if the compliance list contains the "Singapore KMA Device Policy" entry that was just applied.

  3. Device-side verification method 2: Pull down the Android notification panel and check whether Bluetooth has been disabled. If the policy was applied successfully, under the Bluetooth setting it will show “Not allowed by your organization”.

Image for illustration only

4.2 Add Application

Step 1: Create Application Category

  1. Navigate to: ☰ Application Management > ☰ Application Categories.

  2. Click the Create Application Category button.

  3. ➊ Enter the “Category Name”, ➋ Upload a “Category Icon”, then ➌ Click the Save button.

Step 2: Add Application

  1. Navigate to: ☰ Application Management > ☰ Application Library.

  2. Click Add Application > Add KC Private Application button.

  3. Upload the application APK file (for example, the Via browser APK), then click the Next Stepbutton.

  4. ➊ Select an “Application Category”, ➋ Enter “Supported Devices”, then ➌ Click the Next Step button.

  5. ➊ Configure the application’s permissions (you may leave it unchanged at the default User Controls), then ➋ Click the Submit button.

4.3 Configure Application Release Policy

Step 1: Configure and Deploy an Application Update Policy

  1. Navigate to: ☰ Application Management > ☰ Application Release Policies.

  2. Click the Create Application Policy > Create KMA App Policy button.

  3. ➊ Enter a “Policy Name”, ➋ Enable Compliance Check, ➌ Under Required Apps select the app that was just uploaded (e.g., Via), then ➍ Click the Next Step button.

  4. On the Application Update Configuration 📑 page, ➊ Set “Update Method” to Enforcement (leave other settings as default), then ➋ Click the Next Step button.

  5. For the deployment scope, ➊ Set Device Release Scope to “Targeted Deployment”, ➋ Select the device group containing the newly enrolled device, then ➌ Click the Submit button.

Step 2: Verify the Policy Deployment Result

  1. Console verification: Find the application release policy "VIA" that was just published, click the Detailsbuttonto open the policy details page. Click the Operation Log 📑 tab to check the deployment status.

  1. Device-side verification method 1: Check the device’s home screen to see if the app has been installed (in this example, Via App).

  2. Device-side verification method 2: Open the KiwiCloud App to verify. Tap the Apps button, and under the Installed 📑 section check whether the app is now installed.

​

4.4 Application Automatic Compliance Detection

Step 1: Install a Non-Compliant App

  1. Install an app on the device that is not a required or whitelisted app (here, using the YouTube app as an example).> For example: you can download and install YouTube via a browser.

Step 2: Automatic Compliance

  1. The device will trigger the compliance check mechanism. First, the YouTube app will be disabled (its icon will turn gray, and tapping the icon will prompt “Disabled by work policy”).

  2. Next, the YouTube app will be automatically uninstalled from the device.

  3. (Optional) The KiwiCloud UEM console will log a non-compliance record for this device. Navigate to ☰ Device Management > ☰ Device List, find the device by Serial Number or Device name, click the Device Details button, then click the Policy 📑 tab.

5. Routine Operational Tasks

5.1 Modify Policy

Step 1: Modify Device Policy Configuration

  1. Navigate to: ☰ Device Management > ☰ Device Policy.

  2. Find the previously created device policy by Policy name or ID, click More > Edit button.

  3. Modify the device policy settings as needed. Here, for example, changing the Bluetooth Name: ➊ Select “Customize”, ➋ Enter a Bluetooth name (e.g., SG-Store), ➌ Click the Next Step button, then click the Save and Publish button.

Step 2: Verify the Policy Change Result

Please refer to the content in

4. Recommended Process for Initial Business Configuration

4.1 Configure Device Policy

Step 2: Verify the Policy Deployment Result

5.2 Application Version Upgrade

Step 1: Add a New App Version

  1. Navigate to: ☰ Application Management > ☰ App Library.

  2. In the list, find the app created earlier by name (here, using “Via” as an example), click More > Add New Version button.

  3. Upload a higher-version APK of the app, then click the Next Step button.

    Note: If the uploaded version is lower than the current version, the interface will prompt “App version is too low”.

  4. Select the “Application Category”, fill in “Supported Devices”, and click the Next Step button.

  5. Click the Submit button to complete publishing the new app version.

  6. To view the version release status, click More > Version List button to see all version information of the app.

Step 2: Check Application Version Update Result

  1. Device-side verification method 1: On the device, check that the app has been updated (in this example, “Via”). Long-press the app’s icon on the home screen, select App Info from the menu, scroll to the bottom of the screen, and verify the version number is the newly published version.

  2. Other verification methods：Please refer to the content in

4. Recommended Process for Initial Business Configuration

4.1 Configure Device Policy

Step 2: Verify the Policy Deployment Result

6. Remote Operations and Troubleshooting

6.1 Remote Operations

Devices under KMA control support the following remote operations:

  • Associate Device Policy

  • Associate Application Policy

  • Associate File Distribution Policy

  • Retrieve File

  • Enable Lost Mode

  • Device Location

  • Lock Device

  • Unlock Device

  • Remote Reboot

  • Remote Shutdown

  • Revoke Configuration

  • Restore Default Policy

  • Delete Device

  • Clear App Data

Step 1: Perform a Remote Operation on an Online Device (e.g., Lock Device/Unlock Device)

  1. Navigate to: ☰ Device Management > ☰ Device List.

  2. Find the target device by Device name or Serial Number, and click More > Lock Device button.

  3. Enter a lock password for the device, and click the Submit button.

  4. The interface will display the operation result.

Step 2: Verify the Remote Operation Effect

  1. On the device, the screen will be locked and an “Enter your password” interface will appear.

Step 3: Unlock Device

  1. Click More > Unlock Device button.

  2. Enter a reason for the operation, and click the Confirm button to unlock the device.

  3. The interface will display the operation result.

Step 4: Verify the Remote Operation Effect

  1. On the device, the screen lock will be removed and normal operation of the device can resume.

6.2 Remote Assistance

  1. Navigate to: ☰ Device Management > ☰ Device List.

  2. Find the target device by Device name or Serial Number, and click More > Remote Assistance button.

  3. If the device is online and Unattended Access is enabled, the system will automatically connect to the device and enter the remote assistance page.

  4. At this point, you can directly use your mouse to perform click and click-and-drag actions on the device screen.

  5. If the device is offline or Unattended Access is not enabled, it will prompt “Request failed, the device has not authorized cloud access.”

  6. To enable Unattended Access on the device side: open the Remote Assistance app on the device.

  7. Tap the Enable Unattended button to turn it on.

7. Viewing and Exporting Reports

7.1 Report Schedule

The report schedule feature allows device, application, and remote assistance report data to be compiled into document format and sent to specified email addresses on a schedule.

  1. To add a new report schedule, click the Create Scheduled Report button at the top right.

  2. ➊ Enter a Report name, ➋ Select the reports to send, then click the Next Step button at the bottom right.
    ​

  3. ➊ Select the details for the report schedule (for example, report format, delivery options, recipient email, and email subject), then ➋ Once all options are set, click Submit.

  4. In the Report Schedule list, click the Details button to view the schedule details. Click the More button, where you can ➊ Select Disable to stop sending report emails, or ➋ Select Run Now to immediately send the report email.

7.2 Device Reports

The Device Reports module provides administrators with comprehensive monitoring and analysis of the operational status of enterprise devices. Through this module, administrators can view devices’ real-time status, online duration, battery level, storage usage, and other information, and generate reports for data analysis and sharing. The module supports multi-dimensional filtering to help administrators quickly obtain the required data.

7.3 Application Reports

The Application Reports module is used to generate and view information on the installation and usage of applications on enterprise devices, as well as summary information of blacklisted applications. Administrators can use this module to understand details such as each application’s installation count, version distribution, and device usage, in order to optimize application deployment and management strategies. Application reports support multi-dimensional data filtering for convenient analysis.

7.4 Remote Assistance Reports

The Remote Assistance Reports module is used to generate and view records of enterprise remote assistance sessions. Administrators can use this module to see details such as the number of remote sessions, completion rate, unattended status, etc. The reports support multi-dimensional data filtering to facilitate data analysis.

Related Articles
Selecting Management Method and Device Type
Video walkthroughs
GMA Quick Start
Device List (GMA)
IMA Quick Start
Did this answer your question?