Management Platform Recovery via Partitioned Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Enterprise Mobility Management (EMM) and Mobile Device Management (MDM) systems, refreshing or resetting a device's operating system (OS) is time-consuming and poses security risks due to the loss of management application configurations and communication channels, making it burdensome for users and administrators to re-establish management platforms.

Innovation Solution

A method where device identification data, management application installation files, and managed application files are stored in a recovery folder, allowing for the creation of a new OS instance while preserving these files, enabling automatic re-installation and re-enrollment with a management server upon user login, using command files that can execute without user or administrator intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the OS is refreshed or reset to improve device performance, then device performance is improved, but the management application configurations and communication channels are lost requiring time-consuming reinstallation

Engineering Contradiction:
Improvedevice performanceVSAvoidtime to re-install management applications
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating a recovery folder before OS refresh/reset that stores all necessary management application installation files, device identification data, and configuration information. This pre-prepared recovery environment enables automatic reinstallation and re-enrollment processes to occur quickly after the OS is refreshed, eliminating the need for manual reconfiguration and reducing the time loss associated with management platform restoration.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the OS is refreshed or reset to eliminate security risks from viruses or corrupted applications, then security is improved, but the authenticated communication channel with the management server is lost

Engineering Contradiction:
Improvedevice securityVSAvoidauthenticated communication channel
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent applies copying by creating a recovery folder that contains copies of all essential management platform components including device identification data, enrollment keys, authentication tokens, and installation files. These copied elements preserve the authenticated communication channel information separately from the OS, allowing the device to be re-enrolled and restore secure communication with the management server after the OS is refreshed to eliminate security threats.

Inventive Principle:
Principle #26Copying

3Reliability

If manual reinstallation of management applications is performed after OS refresh, then complete management platform restoration is achieved, but user and administrator effort increases significantly

Engineering Contradiction:
Improvemanagement platform restorationVSAvoiduser effort for reinstallation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service by designing an automatic reinstallation process that uses command files stored in the recovery folder to autonomously reinstall management applications and re-enroll the device with the management server. This automated system performs the restoration tasks without requiring manual user or administrator intervention, significantly reducing operational effort while ensuring complete and reliable management platform restoration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11263021B2Management platform recovery for a user device
Publication Date: 2022.03.01 OMNISSA LLC
  • US11263021B2 patent drawing
  • US11263021B2 patent drawing
  • US11263021B2 patent drawing

AI summary

Examples described here include systems and methods for refreshing the operating system (“OS”) of a device enrolled in a management platform. Execution of a first command file ensures that necessary components of the management platform residing on the device are stored in a partitioned portion of the device hard drive to preserve them during the OS refresh. After a new instance of the OS has been installed, execution of a second command file migrates the necessary components from the partitioned portion of the hard drive to the new OS instance. When the user logs back into the refreshed device, a third command file installs all necessary device management components at the new OS instance and re-enrolls the device with the management platform. In this manner, the OS of a managed device can be refreshed and re-enrolled in the management platform without significant input from a user or administrator.