IP Library Granted Patent US 11,531,532
Granted Patent B2
US 11,531,532 · App. 16/249,214 · Granted Dec 20, 2022

Remote deployment of provisioned packages

Inventors: Mohamed Elsherif (Redmond, WA); Kishore Krishnakumar (Atlanta, GA); Ian Drennan (Atlanta, GA); Ondrej Stastny (Kirkland, WA); Brooks Peppin (Colorado Springs, CO); Jason Roszak (Brookhaven, GA); Ahmad Bilal (Renton, WA)
Assignee: VMware, Inc.
G06F8/65G06F8/61G06F9/44505H04L41/0803H04L67/34
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,531,532
App. No.
16/249,214
Granted
Dec 20, 2022
Kind
B2
Abstract

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.

Claims (65)

1. A system, comprising:

a computing device comprising a processor and a memory;

machine-readable instructions stored in the memory that, when executed by the processor, cause the computing device to at least:

obtain a package file comprising an installer for an application, the package file exported from a network environment associated with an enterprise;

store the installer for the application in a cache location of the computing device;

write a hash of the installer to a registry of the computing device;

execute the installer from the cache location to install the application on the computing device;

store a management agent in a location of the computing device, the management agent configured to communicate with a management service of the network environment;

execute the management agent from the location to register the computing device with the management service;

receive a registration confirmation from the management service;

confirm the hash of the installer;

identify, by the management agent, the application to the management service as a managed application installed on the computing device based at least in part on a search of the cache location for the installer;

in an instance in which a device policy specifies an updated version of the managed application, send a request to the management service for the updated version of the managed application;

receive from the management service an updated version of the installer; and

execute the updated version of the installer to install the updated version of the managed application on the computing device.

2. The system of claim 1 , wherein the management agent is executed in an instance in which a first logon event for the computing device is identified.

3. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

write a version number of the installer to the registry of the computing device;

confirm the version number of the installer in response to receipt of the registration confirmation; and

wherein identification of the application as the managed application occurs in response to confirmation of the version number of the installer.

4. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least write a size in bytes of the installer to the registry of the computing device.

5. The system of claim 1 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to unpack the installer from the package file.

6. The system of claim 5 , wherein the package file is a version of a provisioning package file.

7. A method, comprising:

obtaining a package file comprising an installer for an application, the package file exported from a network environment associated with an enterprise;

storing the installer for the application in a cache location of a client device;

writing a hash of the installer to a registry of the client device;

executing the installer from the cache location to install the application on the client device;

storing a management agent in a location of the client device, the management agent configured to communicate with a management service of the network environment;

executing the management agent from the location to register the client device with the management service;

receiving a registration confirmation from the management service; confirming the hash of the installer;

identifying, by the management agent, the application to the management service as a managed application installed on the client device based at least in part on a search of the cache location for the installer;

in an instance in which a device policy specifies an updated version of the managed application, sending a request to the management service for the updated version of the managed application;

receiving from the management service an updated version of the installer; and

executing the updated version of the installer to install the updated version of the managed application on the client device.

8. The method of claim 7 , wherein the management agent is executed in an instance in which a first logon event for the client device is identified.

9. The method of claim 7 , further comprising:

writing a version number of the installer to the registry of the client device;

confirming the version number of the installer in response to receiving the registration confirmation; and

wherein identifying the application as the managed application occurs in response to confirming the version number of the installer.

10. The method of claim 7 , further comprising:

writing a size of the installer to the registry of the client device;

confirming the size of the installer in response to receiving the registration confirmation; and

wherein identifying the application as the managed application occurs in response to confirming the size of the installer.

11. The method of claim 7 , further comprising unpacking the installer from the package file.

12. The method of claim 11 , wherein the package file is a version of a provisioning package file.

13. A non-transitory, computer-readable medium comprising machine-readable instructions that, when executed by a processor, cause a computing device to at least:

obtain a package file comprising an installer for an application, the package file exported from a network environment associated with an enterprise;

store the installer for the application in a cache location of the computing device;

write a hash of the installer to a registry of the computing device;

execute the installer from the cache location to install the application on the computing device;

store a management agent in a location of the computing device, the management agent configured to communicate with a management service of the network environment;

execute the management agent from the location to register the computing device with the management service;

receive a registration confirmation from the management service;

confirm the hash of the installer;

identify, by the management agent, the application to the management service as a managed application installed on the computing device based at least in part on a search of the cache location for the installer;

in an instance in which a device policy specifies an updated version of the managed application, send a request to the management service for the updated version of the managed application;

receive from the management service an updated version of the installer; and

execute the updated version of the installer to install the updated version of the managed application on the computing device.

14. The non-transitory, computer-readable medium of claim 13 , wherein the management agent is executed in an instance in which a first logon event for the computing device is identified.

15. The non-transitory, computer-readable medium of claim 13 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least:

write a version number of the installer to the registry of the computing device; confirm the version number of the installer in response to receipt of the registration confirmation; and

wherein identification of the application as the managed application occurs in response to confirmation of the version number of the installer.

16. The non-transitory, computer-readable medium of claim 13 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to at least write a size in bytes of the installer to the registry of the computing device.

17. The non-transitory, computer-readable medium of claim 13 , wherein the machine-readable instructions, when executed by the processor, further cause the computing device to unpack the installer from the package file.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2019
From: ELSHERIF, MOHAMED; KRISHNAKUMAR, KISHORE; DRENNAN, IAN; STASTNY, ONDREJ; PEPPIN, BROOKS; ROSZAK, JASON; BILAL, AHMAD
To: VMWARE, INC.
Reel/Frame 048217/0799 →
Continuity (1)
Related Publication 20200225929A1 · Jul 16, 2020