Vmware, Inc.

Omnissa, LLC

Kishore Krishnakumar

Vijay Chari Narayan

Brooks Peppin

Paul Adam Ryman

Rupesh Jain

Ameya Jambavalikar

Rob Schlotman

Jason Roszak

Ahmad Bilal

Ondrej Stastny

Mohamed Elsherif

Ian Drennan

Adarsh Subhash Chandra Jain

Kevin B Sheehan

Muhammad Anadil Furqan

Senthil Parthasarathy

Amruta Moghe

Haroon Barlas

Disclosed are various embodiments for provisioning client devices. An enterprise credential can be obtained from a provisioning service. A client device can send an enrollment request to a management service specific to the enterprise associated with the client device. The management service can send an enrollment response to the client device. Then, the client device can receive a provisioning package from the management service. Next, the computing device can then be configured based upon the enrollment response.

Connected provisioning

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.

Multiuser unified endpoint management

Disclosed are various approaches for remotely deploying provisioned packages. An installer for an application is stored in a cache location of the client device. A hash of the installer is then written to a registry of the client device. The installer is then executed to install the application on the client device. Then, the client device is registered with a management service. Subsequently, a registration confirmation is received from the management service. The hash of the installer is then confirmed and the installed application is identified to the management service as a managed application installed on the client device.

Remote deployment of provisioned packages

Systems and methods are included for managing persistent enrollment of a user device. The persistent enrollment can be controlled by an administrator at an administrator console. The administrator can enable or disable persistent enrollment for the user device at the admin console. A deployment agent can be provided to the user device. During the boot process, the deployment agent can verify the persistent enrollment status of the user device. The deployment agent can retrieve and install a software package for a management agent. The management agent can enroll the user device with an enterprise under a staging user profile. The management agent can install a provisioning package associated with the staging user profile. The management agent can receive user input login credentials. The management agent can change the ownership of the user device with the enterprise. The management agent can configure the user device for the user profile.

Managing persistent enrollment of a user device

Disclosed are various embodiments for provisioning client devices. A configuration file previously installed on the computing device can be read. The configuration file can contain a provisioning address. Then, a user account is automatically created using a predefined username and credential stored in the configuration file. Next, an enrollment request can be sent to the provisioning address to enroll the computing device with a provisioning service using the user account. In response, an enrollment response can be received from the provisioning service. The computing device can then be configured based upon the enrollment response.

Disclosed are various approaches for preauthorizing the joining of a client device to a domain managed by a cloud-based directory service. An authorization token can be generated prior to a client device joining the domain. The authorization token can be subsequently installed on a client device at an OEM facility. When a user first logs into the client device, the client device can send the authorization token to the cloud-based directory service in lieu of administrative credentials to prove that the client device has been previously authorized to join the domain.

Preauthorized domain join

Growing community of inventors

Atlanta, GA, United States of America

Kishore Krishnakumar