# US 2022/0045908 A1 · Configuration management for co-management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0045908 A1
- Document ID: US20220045908A1
- Status: Published application
- Kind: A1
- Application number: 17/452,152
- Filed: 2021-10-25
- Published: 2022-02-10
- Earliest claimed: 2019-10-22
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Paul Adam Ryman; Maxwell Christopher Fox; Richard Jason Croft
- Web page: https://patentgrep.com/patent/US20220045908A1

## CPC

- H04L 41/042: comprising distributed management centres cooperatively managing the network
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0869: Validating the configuration within one network element
- H04L 41/0893: Assignment of logical groups to network elements
- H04L 41/0894: Policy-based network configuration management
- H04L 67/025: for remote control or remote monitoring of applications
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Various examples for discovering policy bindings between group policy rules in a legacy management framework and unified endpoint management rules that are utilized in a modern mobile device management (MDM) device management framework. A configuration state view can allow an administrator to understand inconsistencies or conflicts between group policy rules and UEM rules.

## Claims

### Claim 1

A non-transitory computer-readable medium embodying program code executable in a computing device that, when executed by the computing device, causes the computing device at least:
identify a combination of a user and a device that is enrolled as a managed device with a remotely executed management service;
identify a plurality of group policy rules defined for the user and the device, the group policy rules defined in a directory service;
identify a plurality of unified endpoint management (UEM) rules defined by the remotely executed management service for the user and the device;
identify ones of the group policy rules that have at least one an analog from the UEM rules;
build a configuration state view of the user and the device, the configuration state view identifying group policy rules and UEM rules that affect the same functionality of the device; and
identify inconsistencies between the group policy rules and the UEM rules.

### Claim 2 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the program code identifies inconsistencies by determining that a UEM rule and a compliance rule specify a conflicting setting for a feature of the device.

### Claim 3 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the UEM rules are enforced by a management component installed on the client device, and the management component comprises an application installed on the client device with elevated privileges and registered as a local device administrator with an operating system of the client device.

### Claim 4 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the group policy rules are defined in a directory service associated with the user or the device, and the group policy rules specify settings within an operating system of the client device.

### Claim 5 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein the program code identifies ones of the group policy rules that have at least one analog from the compliance rules by inconsistencies by determining that the at least one analog from the compliance rules affects the same operating system setting as one of the group policy rules.

### Claim 6 (depends on 1)

The non-transitory computer-readable medium of claim 1, further comprising program code that, when executed by the computing device, causes the computing device to generate a plurality of policy bindings that link together the UEM rules and the group policy rules.

### Claim 7 (depends on 1)

The non-transitory computer-readable medium of claim 1, wherein program code identifies inconsistencies between the group policy rules and the UEM rules by identifying that at least one of a group policy rule or a UEM rule specifies a conflicting value for an operating system setting on the client device.

### Claim 8

A system comprising:
at least one computing device comprising a processor; and
program instructions executable in the computing device that, when executed by the computing device, cause the client device to:
identify a combination of a user and a device that is enrolled as a managed device with a remotely executed management service;
identify a plurality of group policy rules defined for the user and the device, the group policy rules defined in a directory service;
identify a plurality of unified endpoint management (UEM) rules defined by the remotely executed management service for the user and the device;
identify ones of the group policy rules that have at least one an analog from the UEM rules;
build a configuration state view of the user and the device, the configuration state view identifying group policy rules and UEM rules that affect the same functionality of the device; and
identify inconsistencies between the group policy rules and the UEM rules.

### Claim 9 (depends on 8)

The system of claim 8, wherein the program code identifies inconsistencies by determining that a UEM rule and a compliance rule specify a conflicting setting for a feature of the device.

### Claim 10 (depends on 8)

The system of claim 8, wherein the group policy rules are defined in a directory service associated with the user or the device, and the group policy rules specify settings within an operating system of the client device.

### Claim 11 (depends on 8)

The system of claim 8, wherein the UEM rules are enforced by a management component installed on the client device, and the management component comprises an application installed on the client device with elevated privileges and registered as a local device administrator with an operating system of the client device.

### Claim 12 (depends on 8)

The system of claim 8, wherein the program code identifies ones of the group policy rules that have at least one analog from the compliance rules by inconsistencies by determining that the at least one analog from the compliance rules affects the same operating system as one of the group policy rules.

### Claim 13 (depends on 8)

The system of claim 8, further comprising program code that, when executed by the computing device, causes the computing device to generate a plurality of policy bindings that link together the UEM rules and the group policy rules.

### Claim 14 (depends on 8)

The system of claim 8, wherein program code identifies inconsistencies between the group policy rules and the UEM rules by identifying that at least one of a group policy rule or a UEM rule specifies a conflicting value for an operating system setting on the client device.

### Claim 15

A method comprising:
identifying a combination of a user and a device that is enrolled as a managed device with a remotely executed management service;
identify a plurality of group policy rules defined for the user and the device, the group policy rules defined in a directory service;
identify a plurality of unified endpoint management (UEM) rules defined by the remotely executed management service for the user and the device;
identify ones of the group policy rules that have at least one an analog from the UEM rules;
build a configuration state view of the user and the device, the configuration state view identifying group policy rules and UEM rules that affect the same functionality of the device; and
identify inconsistencies between the group policy rules and the UEM rules.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15, further comprising identifying inconsistencies by determining that a UEM rule and a compliance rule specify a conflicting setting for a feature of the device.

### Claim 17 (depends on 15)

The computer-implemented method of claim 15, wherein the group policy rules are defined in a directory service associated with the user or the device, and the group policy rules specify settings within an operating system of the client device.

### Claim 18 (depends on 15)

The computer-implemented method of claim 15, wherein the UEM rules are enforced by a management component installed on the client device, and the management component comprises an application installed on the client device with elevated privileges and registered as a local device administrator with an operating system of the client device.

### Claim 19 (depends on 15)

The computer-implemented method of claim 15, wherein the program code identifies ones of the group policy rules that have at least one analog from the compliance rules by inconsistencies by determining that the at least one analog from the compliance rules affects the same operating system as one of the group policy rules.

### Claim 20 (depends on 15)

The computer-implemented method of claim 15, wherein program code identifies inconsistencies between the group policy rules and the UEM rules by identifying that at least one of a group policy rule or a UEM rule specifies a conflicting value for an operating system setting on the client device.
