Abstract: Disclosed are various embodiments of a multiuser unified endpoint management (UEM) system. A device check-in can be received from a client device. The device check-in can include a device identifier that uniquely identifies the client device with respect to other client devices and a user identifier that uniquely identifies the user of the client device with respect to other users of the client device. In response, a device channel identifier associated with the device identifier and a user channel identifier associated with both the user identifier and the device identifier can be obtained. Then a first set of entitlements associated with the device channel identifier and a second set of entitlements associated with the user channel identifier can be selected. Both sets of entitlements can be provided to the client device in response to the device check-in.

Abstract: Examples of scheduled and on-demand volume encryption suspension are described. A management service can identify multi-volume encryption rules for local volumes of a client device including the operating system volume as well as non-operating-system volumes. The encryption rules can be transmitted to the client device. Volume encryption samples for the client device can be received, and a console user interface can be generated to indicate compliance status information for the multi-volume encryption rules for local volumes of a client device.

Abstract: In some examples, a computing system may receive a document comprising a paragraph associated with a purchase order. The paragraph may be converted into text. The computing system may use a parser to parse the text to identify particular portions associated with address-related information. The computing system may parse the text based on a pre-determined sequential order and also may remove the particular portions from the text based on the pre-determined sequential order. The computing system may then label and store the particular portions in fields of a data structure.

Abstract: Disclosed are various examples for verification and management of firmware for client devices enrolled with a management service of an enterprise. The firmware verification includes a verification process using multiple checkpoints for determining whether status responses associated with firmware installed on and received from a managed client device can be trusted. The multiple checkpoints can include verifying certificate data, signature data, and an exit code included in status responses received from managed devices. In the event that one of the verification steps fails, the device can be considered compromised and subject to various compliance actions. The compliance actions can include limiting access to enterprise data, limiting access to one or more applications, wiping a device clean to reset the devices to the original factory settings, sending a notification to an enterprise administrator providing an indication of the detected compromise, and other types of compliance actions.

Abstract: In some examples, a computing system may receive a document comprising a paragraph associated with a purchase order. The paragraph may be converted into text. The computing system may use a parser to parse the text to identify particular portions associated with address-related information. The computing system may parse the text based on a pre-determined sequential order and also may remove the particular portions from the text based on the pre-determined sequential order. The computing system may then label and store the particular portions in fields of a data structure.