Abstract: This document relates to a process for deploying devices and automatically provisioning the devices to connect to a managed network upon powering on with minimal user involvement. Upon deployment of the device to an end point, a record can be established in a management server regarding the device, which can associate device specifications with a deployment profile to be used in provisioning the device. Upon powering on of the device at the end point, the device can automatically perform attestation with the management server, which can then provision the device according to the deployment profile without additional user intervention.

Abstract: Examples described herein generally relate to device analytics. Specifically, the present disclosure provides telemetry-based analytics to identify and remediate top end-user impacting issues. For example, a device may detect an anomaly associated with an application program at the computing device based on a detection parameter. Further, the device may automatically identify at least one remediation action associated with the detected anomaly. The device may also determine whether application of the at least one remediation action to the detected anomaly satisfies a remediation threshold. Additionally, the device may transmit the at least one remediation action to the computing device in accordance with a determination that the application of the at least one remediation action to the detected anomaly satisfies the remediation threshold.

Abstract: Translators are provided that enable automated and remote device configurations in an efficient and abstract manner. In one aspect, a device configuration system is provided. A configuration component stores one or more remote configuration trees for various devices. A translator component maps the remote configuration trees to at least one device configuration tree associated with the respective devices to enable device configuration in an automated manner.

Abstract: Various technologies and techniques are disclosed for extending the functionality of the Open Mobile Alliance (OMA) Device Management (DM) protocol. An addition is made to the OMA DM protocol that enables the server to specify node filtering criteria as part of a query to a target node on a mobile device to indicate a sub-set of the device management data for the target node that should be returned. As another variation, a modification is made to the OMA DM protocol that enables the server to specify what attributes should be selected on the mobile device in one parameter of a target URI of the Get command, and what format the device management data should be returned in as another parameter of the target URI of the Get command.

Abstract: Installing software using the configuration manager so that the rollback and security features of the configuration manager may be used during the installation process. A mobile computing device accesses files that are to be installed on the mobile computing device, and well as computer-executable instructions that define how the files are to be installed on the mobile computing device. The configuration manager then causes the computer-executable instructions to be executed (e.g., using configuration service providers), and causes a mirroring rollback document to be constructed. If the installation fails, the installation process is reversed by executing the rollback document. The configuration manager may also be used to implement security when executing the installation instructions by checking to determine whether or not execution of each installation instruction is authorized.

Abstract: Installing software using the configuration manager so that the rollback and security features of the configuration manager may be used during the installation process. A mobile computing device accesses files that are to be installed on the mobile computing device, and well as computer-executable instructions that define how the files are to be installed on the mobile computing device. The configuration manager then causes the computer-executable instructions to be executed (e.g., using configuration service providers), and causes a mirroring rollback document to be constructed. If the installation fails, the installation process is reversed by executing the rollback document. The configuration manager may also be used to implement security when executing the installation instructions by checking to determine whether or not execution of each installation instruction is authorized.

Abstract: Installing software using the configuration manager so that the rollback and security features of the configuration manager may be used during the installation process. A mobile computing device accesses files that are to be installed on the mobile computing device, and well as computer-executable instructions that define how the files are to be installed on the mobile computing device. The configuration manager then causes the computer-executable instructions to be executed (e.g., using configuration service providers), and causes a mirroring rollback document to be constructed. If the installation fails, the installation process is reversed by executing the rollback document. The configuration manager may also be used to implement security when executing the installation instructions by checking to determine whether or not execution of each installation instruction is authorized.