Prerequisites

This section describes the prerequisite/procedures you must perform for the deployment of SureMDM OnPremise. 


Hardware Requirements

Based on the number of devices you plan to use in your deployment, 42Gears Tech Support will be able to provide the hardware specifications for SureMDM OnPremise. You can reach out to 42Gears TechSupport at techsupport@42gears.com

Note: 

  1. The customer will be responsible for handling the maintenance and support of prerequisite components.
  2. SureMDM OnPremise can be installed on a modern Linux Server. We recommend Ubuntu Server 20.04/22.04 LTS.


Software Requirements

Ensure SureMDM OnPremise is supplied with all the following software requirements:

Requirement

Description

SQL Server 
  • If system admin is using ubuntu 20.04 then SQL server 2019 should be installed.
  • If system admin is using ubuntu 22.04 then SQL server 2022 should be installed.

MongoDB 

Note: The system admin can select the Ubuntu server accordingly.

  • Click here to find out more about the MongoDB configuration process.

MinIO
  • MinIO server (latest version) should be installed on the  SureMDM machine for data storage purposes. During MinIO setup, the system admin should use the same DNS and SSL, which are used for the SureMDM OnPremise deployment.
  • Click here to find out more about the MinIO installation and configuration process.

Note: The Port(Customer-defined) used for MinIO configuration should be allowed.

  •   Create three buckets in your MinIO console with the following names:

a. suremdm-bucket

b. suremdm-icons

c. suremdm-reports

Note: The SureMDM App Icon Bucket should have public access to allow for downloads. Click here for more info.

  • Create an access key for SureMDM to access MinIO buckets. These buckets and access keys will be needed for the storage configuration of SureMDM.

Kubernetes distribution (K3s) 

Lightweight Kubernetes distribution (K3s) is used for managing containerized applications across a cluster of machines. Click here for details. 



General Requirements
Ensure SureMDM OnPremise is supplied with all the following general requirements to ensure a successful installation.

Note: 
a. System admin will be provided with SureMDM OnPremise Installer package and offline images by 42Gears Support. These files should be extracted in the SureMDM Server used for deployment. 

b. System Admin should have SUDO access to complete the deployment.


Requirement 

Description

DNS

Keep an unmapped DNS available for the SureMDM setup. The DNS should be mapped to the Public/Private IP of the SureMDM server.

Certificates

After extracting the installer package, place the following certificates in the respective folders based on the deployment.

  • SSL Certificates - Customers should have an SSL certificate in the certificate and key format. Customers can use the same certificate to set up both SureMDM and MinIO application. The files (full chain certificate and key) should be placed under k8sopinstaller\appdata\certs for SureMDM setup. 

  • Android Enterprise Setup - The MSA/ESA be placed under k8sopinstaller\appdata\api\App_Data  and /appdata/pluto folder.

  • iOS Device Setup -  The push certificates with the file names DefaultPushCertificate.p12 (APNs) and NixProductionPush.p12 should be placed under k8sopinstaller\appdata\pluto\iOS. For details on generating an Apple Push Certificate, click here. 

Note: System admin must the same file names as provided above. 

  • macOS Device Setup - The push certificate with the file name NixProductionPush.p12 should be placed under k8sopinstaller\appdata\pluto\macOS.

Note: System admin must keep the same file name as provided above. 

  • Device Management by Android Management - The credentials file should be named cred.json and placed under k8sopinstaller\appdata\api\App_Data.

Note: Please contact the 42Gears technical support team at techsupport@42gears.com  for the above-specified certificates (NixProductionPush.P12, MSA, ESA, and cred.json).

FCM keys

If System admin wish to configure FCM, FCM Project ID, Server API Key, Application ID, and Sender ID are required. Click here to learn how to generate FCM Key. Place the FCM credential file with the .json extension in the appdata/pluto directory for Android. Click here to learn how to download .json file. 

If the System admin does not want to configure FCM, normal polling will be used as a fallback. 


Note: FCM Key should be purchased by the customer and FCM V1 should be enabled for FCM project.

Window push notification

If the system admin wishes to configure the Windows push notification service, WNS values are required. Click here to learn how to get the WNS values.

Note: WNS Key should be purchased by the customer.

Email server

If the system admin wishes to configure an email server, the Server Username, Password, and MailServerBackup are required. We support email servers that use the SMTP protocol. Click here for the steps. 

Google API key for Location

If the system admin wishes to use Google Maps for location tracking, a Google API key is required. Otherwise, the system admin can use the default OpenStreet maps available in SureMDM.


  Note : Google API Key should be purchased by the customer.

Amazon S3 storage values

The system admin can use Amazon S3 if they do not have MinIO storage. The system admin needs two S3 buckets (one bucket will be used for jobs and reports, while the other will be used for icons).

Note: 

a. AWS storage values should be purchased by the customer.

b. The SureMDM App Icon Bucket should have public access to allow for downloads.

c. Below are the helpful links for S3:

  • To get started with S3, click here.
  • To create a bucket, click here.
  • To configure S3, click here. 

SureMDM Hub configuration

This is only applicable for SureMDM Hub deployment. A separate license key is required for SureMDM Hub configuration. Please contact 42Gears Support for more information. 

MTD

The system admins should contact the support team for the 42 gears MTD and Pradeo MTD feature.



Network Requirements

Other than this, SureMDM OnPremise deployment requires Internet access, and few ports should be allowed internally. Click here for more details.