Admin

Use the Admin page to manage Core instances and update the Cloud API user details.

Configuring Cloud API credentials

When you log in to the Migration Portal, you are prompted to configure the Cloud API credentials if you have not done so already. Use the same procedure to modify any existing credentials.

Before you begin 

For Cloud API credentials, one of the following set of roles is mandatory in Cloud for the migrations to succeed:

• All of the following roles:
  • Low User Impact Migration Management
  • User Management
  • Device Management (necessary only if the migrating device has custom device attributes assigned to it in Core)
  • LDAP User Registration and Invite
  • Device Action
• Or, the following roles:
  • System Management
  • Low User Impact Migration Management

Procedure 

1. Go to the Admin > Cloud API Credentials page.
2. Enter the following details of the Cloud user with the previously specified set of roles:
   • User name
   • Password
   • Confirm Password
3. Click Save.

If the credentials for the Cloud or Core instances are invalid, if they are not authorized, or if they are not reachable, some features may not be available until valid credentials and roles are provided and/or until connectivity is restored.

Managing Core instances

By default, when you visit the Admin page, the Manage Core Instances page is displayed with a list of Core instances. A Core instance cannot be configured against multiple Cloud tenants.

The following roles should be assigned to the Core user being added to the Migration Portal for the migrations to succeed:

• Migration
• API (only required for notifications in Migration Portal)
• View device page, device details

Adding a Core instance

Procedure 

1. Go to the Admin > Manage Core Instances page.
2. Click +Add.
3. Enter the following details related to the Core instance:
   • Name
   • Description
   • Deployment Type (On Premise or Connected Cloud)
   • Instance Name (required in the case of Connected Cloud)
   • URL (For example, https://mdm.company.com/)
   • API User Name
   • API Password
   • Confirm API Password
4. Click Save.

Modifying a Core instance

Procedure 

1. Go to the Admin > Manage Core Instances page.
2. For a specific Core instance, click the pencil icon under the Actions column.
3. Modify any of the following details related to the Core instance:
   • Name
   • Description
   • Deployment Type (On Premise or Connected Cloud). If Connected Cloud is chosen as the deployment type, enter the instance name as well.
   • API User Name
   • API Password
   • Confirm API Password
4. Click Save.

Click the SQL icon to export SQL query. This query is used to update device status on Core in case of high-availability (HA) switchover to a secondary node.

Removing a Core instance

This procedure only removes the Core instance entry from the Migration Portal. The instance will continue to operate.

A Core instance cannot be removed:

• During a migration progress.
• If the Core instance is being used by other entities. For example, one or more devices in Cloud are associated with the Core instance.
• If there are any sync jobs being performed for the Core instance, that Core instance cannot be removed.

The removal of a Core instance is non-recoverable. All entries will be permanently deleted from the Migration Portal and Cloud databases. However:

• If the Cloud service is unavailable or not reachable, then the Migration Portal database changes are rolled back. An appropriate error message is displayed.
• If the Cloud service is reachable but the Core instance is not available or not found in Cloud, then it will be noted in the Migration Portal logs and the Core instance will be removed.

Procedure 

1. Go to the Admin > Manage Core Instances page.
2. For a specific Core instance, click the trash icon under the Actions column.
3. Click OK to confirm removing the Core instance.

Uploading or modifying certificates for a Core instance

You can upload or modify the following certificates for a Core instance:

• Migrator Certificate - For Connected Cloud type Core instances, the option to upload migrator certificate will not be available as it will be automatically uploaded by the system. Administrators can contact their Professional Services representative for the first instance upload of the migrator certificate of a Connected Cloud cluster.
• MDM Certificate - When the migrator and the MDM certificates are not uploaded, migration will fail. Select automatic or manual upload of a MDM certificate.
• Portal Certificate - Upload the portal certificate only when all the devices are migrated and when you want to shutdown the Core instance. See Portal certificate renewal information and automatic vhost configuration for more information.
• Android Work ESA - Fetch Android Enterprise Service Account (ESA) from Core and upload it to Cloud. This will enable Cloud to manage Android Enterprise devices.

Procedure 

1. Go to the Admin > Manage Core Instances page.
2. For a specific Core instance, click the upload icon under the Migrator Certificate, MDM Certificate, Portal Certificate, or Android Work ESA column as per the requirement.
3. For MDM Certificate:
   1. Select Auto Configure or Manual Upload.
   2. Click Submit.
   3. If you select the Auto Configure option, the MDM certificate is fetched from Core and uploaded to Cloud. Click OK to continue.
   4. If you select the Manual Upload option, continue with the next steps.
4. Drag and drop the certificate file or click the Choose File... button to browse and select the certificate. Only .p12 certificate files are supported.
5. Enter certificate password and confirm certificate password.
6. Click Upload.

Portal certificate renewal information and automatic vhost configuration

The Admin > Manage Core Instances page displays the expiration date of Portal certificates.

Additionally:

• The Migration portal displays a notification for the admin stating that the certificate is due for renewal in the next 15 days.

• Checks every eight hours whether a new portal certificate is newly uploaded and requires a vhost to be reconfigured.

• Automatically configures the vhost for the Core instance as part of the job run. The job runs at the end of each day, therefore, the certificates take effect at the end of the day.