Vmware, Inc.

Airwatch LLC

Daniel Benjamin Quintas

Anthony Kueh

Eric Matthew Stillman

Lokeswar Akuthota

Kashyap Kumar Sharma

Adam Stephen Rykowski

Adarsh Subhash Chandra Jain

Huda Osman

Kai Chen

Sridhara Babu Kommireddy

Sagar Date

Adarsh Jain

Bhavesh Krishna Kumar

Kiran Rohankar

Urvashi Goverdhan

Janani Vedapuri

Gaurav Halbe

Akshay Galande

Examples described herein include systems and methods managing firmware versions of user devices that are enrolled in an enterprise mobility management system. The system can include a management server that sends profiles to enrolled devices, causing those devices to restrict further firmware updates and register with a firmware server. The management server can retrieve available firmware versions and display those in a console. An administrator can select target firmware versions in the console. The management server can the cause the enrolled devices to update to the target firmware versions. This can include sending a call from the management server to the firmware server, causing an automatic update. It can also include sending a command from the management server to an enrolled device, causing the enrolled device to prompt a user prior to requesting a firmware update. This can allow an administrator to prevent user devices from installing firmware updates that could expose the enterprise to security risks or negatively impact operation of enterprise applications.

Enterprise firmware management

In one example of federated mobile device management, a first management service federates with a second management service based on an exchange of one or more identity authentication certificates. After the management services have federated or affiliated, the first service can enroll a client device for management based on federated management data, where the federated management data includes first device management data of the first management service and second device management data of the second management service. The first service can also identify a change in affiliation associated with at least one of the client device or the second management service and cause the client device to check in for a device management update based on the change in affiliation.

Federated mobile device management

Disclosed are various embodiments that related to rendering a data driven user interface used to configure device profiles in an enterprise device management environment. In some examples, the enterprise device management environment can include a platform messaging service and a platform specific adapter. In one example, a system can receive a request to generate a device profile for a platform. The system can render a data driven user interface for configuring the device profile based on a definition file. The system can also receive input of a value for a user interface element and retrieve the values from the other user interface elements. The system can generate the device profile based on a translation of the values and transmit a command to a platform messaging service to facilitate an installation of the device profile in a mobile device. Various delivery methods for installing the device profile are disclosed.

Data driven user interfaces for device management

In one example of federated mobile device management, a first management server federates with a second management server based on an exchange of one or more identity authentication certificates between them. After the first and second management servers have federated or affiliated, they can exchange mobile device management data, including compliance policies, rules, resources, etc., with each other. Based on a request from a client device for affiliated mobile device management, the first management server can request and receive device management data from the second management device. The first management server can evaluate the device management data received from the second management device for conformity with a baseline management policy. If it conforms, the first management server can use the device management data from the second management server, at least in part, to manage the client device.

Disclosed are various embodiments related to rendering a data driven user interface used to configure device profiles in an enterprise device management environment. In some examples, the enterprise device management environment can include a definition file repository and a platform specific adapter. In one example, among others, a system can establish a communication channel with a definition file repository, and then receive a definition file for a target platform from the definition file repository. The system can also receive a request to generate a device profile and render a data driven user interface for configuring the device profile based on the definition file. The system can generate the device profile based at least in part on a platform translation of the values retrieved from the data driven user interface. The device profile can execute in association with the target platform on a client device.

Disclosed are various embodiments for automating the provision of applications to managed client devices. A search string is passed through an iFrame embedded in a web page to a remote computing device that provides an application programming interface (API) for an application store. A search result is then received through the iFrame from the remote computing device and displayed in the iFrame. The iFrame then provides a notification of an approval for publication of an application identified by the search result and details of the application. The details of the application are then sent to the remote computing device to cause the application store to distribute the application to a client device.

Automated provisioning of applications

Disclosed are approaches for distributing credentials using derived credentials, such as by relaying a simple certificate enrollment protocol (SCEP) payload. A computing device configures a device profile corresponding to a client device. The device profile can include a SCEP payload. The computing device later receives an override for the SCEP payload from a broker service. In response, the computing device creates a copy of the device profile that includes the override for the SCEP payload. The computing device then sends the copy of the device profile to the client device.

Growing community of inventors

Atlanta, GA, United States of America

Daniel Benjamin Quintas