Airwatch LLC

Vmware, Inc.

Bhavesh Krishna Kumar

Shruti Phanse

Adarsh Subhash Chandra Jain

Abhishek Mishra

Daniel Benjamin Quintas

Eric Matthew Stillman

Adarsh Jain

Nigitha Alugubelli

Naveen Pitchandi

Kai Chen

Janani Vedapuri

Colleen Caporal

Akshay Galande

Sachin Ramachandran

Sarmishta Akkala

Allan Howard

Disclosed are examples related to data driven interfaces for decoupling management system components from a manufacturer or a platform of client devices managed by the management system. In some examples, among others, a system can generate a data driven interface template that can be used to cause rendering of a data driven user interface for configuring a profile payload of a device profile for the client device. The system can generate, based on values associated with the data driven user interface, a profile document in an instance in which values are obtained from the data driven user interface. In some aspects, the profile document is a generic representation of the profile payloads for the platform, the manufacturer or the type of the client device.

Data driven interfaces for decoupling components of a management system from manufacturer and platform of managed client devices

Systems and methods are provided for analyzing application usage on a user device and optimizing application and license distribution for user devices in an enterprise. An example system includes a management server and a data server. The management server can provide instructions to the user device to install a tracking application that gathers application-usage data using built-in functionality of the user device. The data server can receive and compile the application-usage data, creating compiled usage data. Using this compiled usage data, the management server can execute a rules engine to determine an action to take associated with at least one application on the user device, such as redistributing application licenses.

Systems and methods for analyzing application usage on a user device

Systems and methods are provided for an improved GUI workflow that supports complex bundle arrays for configuring devices. The method can also include displaying, on a GUI, a first top-level array of configuration fields described in a schema file having configuration options for a user device. A top-level array can include at least one group of nested (or 'lower-level') configuration options, where the grouping is represented by a graphical element in the top-level array. In response to a selection of a second-level array, the example method can include extracting lower-level configuration information from the schema file, generating a lower-level array based on the extracted information, and displaying, within the first top-level array, the first lower-level array of configuration fields. The method can also include various options for copying stored settings into a new array. The settings can be implemented on a device through a management server.

Supporting complex arrays in a data-driven user interface

Disclosed are various approaches for integrating application scanning into a mobile enterprise computing management system. A management service instructs the client device to provide a list of installed applications to the management service and receives the list of installed applications from the client device. The management service then adds the list of installed applications to an aggregate listing of applications representing a list of client applications installed on one or more client devices. Subsequently, the management service sends to a scanning service a policy comprising an identifier of a client application that is prohibited on the client device. The management service also sends the aggregate listing of applications to the scanning service. The management service then receives a notification from the scanning service that the prohibited client application is present in the aggregate listing of applications. In response, the management service determines whether the prohibited client application is installed on the client device and instructs the client device perform a remedial action specified by the policy.

Anonymized application scanning for mobile devices

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 various approaches for integrating application scanning into a mobile enterprise computing management system. A management service instructs the client device to provide a list of installed applications to the management serviceand receives the list of installed applications from the client device. The management service then adds the list of installed applications to an aggregate listing of applications representing a list of client applications installed on one or more client devices. Subsequently, the management service sends to a scanning service a policy comprising an identifier of a client application that is prohibited on the client device. The management service also sends the aggregate listing of applications to the scanning service. The management service then receives a notification from the scanning service that the prohibited client application is present in the aggregate listing of applications. In response, the management service determines whether the prohibited client application is installed on the client device and instructs the client device perform a remedial action specified by the policy.

Disclosed are various approaches for integrating application scanning into a mobile enterprise computing management system. A management service can add a first command to a command queue associated with a client device, wherein the first command instructs the client device to provide a unique device identifier associated with the client device to the management service and the unique device identifier uniquely identifies the client device with respect to at least one other client device. Then, the management service can receive a first request from the client device for the first command stored in the command queue. Later, the management service sends the first command to the client device. When the management service receives the unique device identifier from the client device, the management service sends the unique device identifier to a scanning service and a policy linked with the unique device identifier to the scanning service. The policy comprises an identifier of a client application prohibited on the client device. The management service then receives a notification from the scanning service. The notification comprises the unique device identifier and an indication that the client application is present on the client device. Later, the management service adds a second command to the command queue, wherein the second command instructs the client device to perform a remedial action specified by the policy. When the management service receives a second request from the client device for the second command stored in the command queue, the management service sends the second command to the client device.

Growing community of inventors

Atlanta, GA, United States of America

Bhavesh Krishna Kumar