Abstract: Examples of device-driven management are described. A management service can transmit a device-driven management workflow to a number of client devices. The device-driven management workflow can include workflow objects that define a branching sequence of instructions. The client devices can provide a corresponding plurality of completion statuses for a step of the device-driven management workflow. The management service can identify a failure of the step according to a set of failure rules, and visually emphasize the failure within a representation of the device-driven management workflow.

Abstract: Disclosed are various examples for distributed profile and key management. In one example, a client device can include an agent application and a PIV-D application. The agent application can receive a partially populated device profile generated by a management service to configure a setting on the client device. The PIV-D application can generate a derived credential and provide the derived credential to the agent application. The agent application can modify the partially populated device profile to include the credential to create a fully populated device profile and configure the client device in accordance with the fully populated device profile.

Abstract: Examples of device-driven management are described. A management service can transmit a device-driven management workflow to a number of client devices. The device-driven management workflow can include workflow objects that define a branching sequence of instructions. The client devices can provide a corresponding plurality of completion statuses for a step of the device-driven management workflow. The management service can identify a failure of the step according to a set of failure rules, and visually emphasize the failure within a representation of the device-driven management workflow.

Abstract: Disclosed are various examples for distributed profile and key management. In one example, a management service can generate a partially populated device profile and provide the partially populated device profile to a client application executable on a client device. The client application can generate a credential and insert the credential into the partially populated device profile to generate a fully populated device profile. The credential can be shared with at least one other client application on the client device. The management service can use the fully populated device profile to generate multiple profiles that rely on a single credential, such as a single X.509 security certificate.

Abstract: Disclosed are various examples for distributed profile and key management. In one example, a client device can include an agent application and a PIV-D application. The agent application can receive a partially populated device profile generated by a management service to configure a setting on the client device. The PIV-D application can generate a derived credential and provide the derived credential to the agent application. The agent application can modify the partially populated device profile to include the credential to create a fully populated device profile and configure the client device in accordance with the fully populated device profile.

Abstract: Disclosed are various examples for distributed profile and key management. In one example, a management service can generate a partially populated device profile and provide the partially populated device profile to a client application executable on a client device. The client application can generate a credential and insert the credential into the partially populated device profile to generate a fully populated device profile. The credential can be shared with at least one other client application on the client device. The management service can use the fully populated device profile to generate multiple profiles that rely on a single credential, such as a single X.509 security certificate.