Automated Device Definition Previewing Impacted Entities
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current unified endpoint management (UEM) solutions struggle to accurately determine the impact of policy changes on diverse devices with varying operating systems, hardware, and software configurations, often leading to potential device malfunctions or non-operational issues due to rough estimates and failure to account for stored device profiles.
Innovation Solution
A management service that allows administrators to define conditions, triggers, and actions within an administrator console, enabling matching against both periodically updated and newly received device profiles, providing real-time metrics and granular automation capabilities to assess and implement changes effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If rough estimates are used to determine impacted devices, then the assessment process is fast and simple, but the accuracy and reliability of impact determination deteriorates
Solution Approach 1:
The system performs preliminary actions by maintaining stored device profiles and continuously updating device states before policy changes are implemented. This allows the system to have device information ready in advance, enabling accurate impact determination without complex real-time analysis when policies are changed.
Solution Approach 2:
The system creates and maintains copies of device profiles and states in stored memory. These copies allow the system to accurately determine policy impact by comparing against stored device information without requiring complex real-time data collection and analysis processes.
2Reliability
If only incoming device profiles are matched against rules, then the processing is simpler, but the completeness of device coverage deteriorates by failing to account for stored device profiles
Solution Approach 1:
The system merges incoming device profiles with stored device profiles into a unified device state repository. This combination allows the rule-matching process to comprehensively evaluate all devices (both newly received and previously stored) against policy changes, ensuring complete device coverage without duplicating processing logic.
3Ease of operation
If policy changes are rolled out to all enrolled devices, then the implementation is straightforward, but the risk of device malfunction increases when only a subset should be impacted
Solution Approach 1:
The system provides feedback to administrators by displaying the number of devices that will be impacted by a policy change before implementation. This feedback mechanism allows administrators to review and adjust policy scope, ensuring policies are applied only to appropriate devices and reducing the risk of widespread malfunctions.
Data Source
AI summary
Various examples are described for defining automations for client devices enrolled with a management service. A computing environment can cause one or more user interfaces to be shown in a display of an administrator device that include at least one field for generating an automation that includes a trigger, a condition, and an action to automatically be performed when the condition is satisfied. The trigger defines a time at which the management service compares the condition to device profiles generated for client devices enrolled with the management service. The user interface can forecast a number of client devices that will be affected or subject to an automation, and can display results of the automation as it is executed in real time.