Edge Endpoint Management Fallback for Primary Server Outages
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise environments, management services for multiple devices can become inaccessible, leading to compromised device states and disrupted business continuity due to network issues, affecting device management, security, and compliance.
Innovation Solution
Implementing edge-based unified endpoint management servers that act as fallback servers, replicating management data and policies to localized edge management servers, ensuring device management continuity by enforcing compliance rules and providing updates even when the primary management server is offline.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a centralized management service is used for unified endpoint management, then device management and security policies can be enforced centrally, but the system becomes vulnerable to single points of failure and network accessibility issues
Solution Approach 1:
The centralized management service is segmented into multiple distributed edge management servers that can independently operate and provide management functions. Each edge server handles a subset of devices, eliminating the single point of failure and allowing local operation even when other servers are unavailable.
Solution Approach 2:
Edge management servers act as intermediaries between devices and the central management service. They can operate autonomously when the central service is unavailable, providing a fallback mechanism that maintains service availability while still enabling centralized management when possible.
2Reliability
If edge management servers are deployed as fallback solutions, then device management continuity is maintained during outages, but system complexity increases
Solution Approach 1:
The system dynamically adjusts its operation mode based on availability requirements. Edge management servers can operate in synchronized mode when the central service is available and switch to autonomous mode during outages. This dynamic behavior provides management continuity without requiring permanently complex autonomous capabilities at all servers.
Solution Approach 2:
The system changes operational parameters such as synchronization frequency and autonomy level based on the availability of the central management service. When the central service is down, edge servers increase their operational autonomy and adjust data synchronization parameters to maintain management continuity with reduced complexity.
3Speed
If edge management servers replicate management data locally, then faster access and throughput are achieved, but data synchronization and consistency become more difficult
Solution Approach 1:
Edge management servers perform periodic synchronization with the central management service at scheduled intervals. This periodic action allows local data replication for fast access while systematically updating data to maintain consistency, reducing the complexity of continuous synchronization.
Solution Approach 2:
Management data is replicated to edge servers in advance before it is needed at device locations. This preliminary replication enables fast local data access during outages while the synchronization complexity is handled beforehand during normal operation when the central service is available.
Data Source
AI summary
The present disclosure fallback management of managed devices utilizing edge management servers that periodically poll a primary management server. If the primary management server is unreachable, the edge management servers can assume management of a population of managed devices.