AUTOMATIC UPDATING OF AN APPLICATION OR A DRIVER ON A CLIENT DEVICE USING A DEPLOYMENT CONFIGURATION FILE

• US 20130139139A1
• Filed: 11/28/2011
• Published: 05/30/2013
• Est. Priority Date: 11/28/2011
• Status: Abandoned Application

• Current Assignee: Wyse Technology L.L.C. (Dell Technologies Inc.)
• Original Assignee: Wyse Technology Incorporated (Dell Technologies Inc.)
• Inventors: Mallur, Muralidhara, Bandakka, Jyothi, Tukol, Sanmati
• Application Number:
  US13/305,692
• Publication Number:
  US 20130139139A1
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

The automatic updating of an application or a driver on a client device is described. At least one deployment configuration file, including a deployment entry corresponding to a package for updating an application or a driver, is obtained at the client device. The deployment configuration file is stored on the client device in a memory location that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored with the write-filter enabled from persisting across a reboot of the device. A check is performed to determine whether the deployment entry identifies an application or driver that is installed on the client device, and identifies a version of the application or driver that is higher than a version installed on the client device. The application or driver corresponding to the deployment entry is then updated on the client device using the package, while the write-filter is disabled.

Claims

1. A method for automatically updating an application or a driver on a client device, the method comprising:

facilitating obtaining at the client device at least one deployment configuration file from a configuration repository,

wherein the at least one deployment configuration file includes a deployment entry corresponding to a package for updating an application or a driver, and the deployment entry includes identifiers for the package and for a version of the package;

facilitating storing the at least one deployment configuration file in a location of a memory of the client device that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored on the client device with the write-filter enabled from persisting across a reboot of the client device;

for each of the at least one deployment configuration file, facilitating operations of;

checking that a deployment entry of the at least one deployment configuration file corresponds to a package for updating an application or a driver that is installed on the client device, and that the deployment entry is identified with a version of the package that is higher than a version of the application or the driver that is installed on the client device; and

updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file using the package, while the write-filter is disabled.

2. The method of claim 1, wherein prior to updating on the client device the application or the driver, the method comprises:

facilitating a determination that the write-filter is enabled on the client device;

facilitating disabling of the write-filter on the client device; and

facilitating a reboot of the client device.

3. The method of claim 2, wherein following the reboot of the client device, the method comprises:

determining whether at least one deployment configuration file is stored in the memory of the client device; and

upon determining that at least one deployment configuration file is stored in the memory of the client device, retrieving the at least one deployment configuration file stored in the memory of the client device and facilitating the checking and updating operations using the retrieved at least one deployment configuration file.

4. The method of claim 2, wherein following the updating on the client device the application or the driver, the method comprises:

facilitating enabling of the write-filter on the client device; and

facilitating a reboot of the client device.

5. The method of claim 1, wherein the facilitating obtaining at the client device at least one deployment configuration file comprises:

facilitating locating the configuration repository;

facilitating determining that an autoupdate folder exists on the configuration repository; and

facilitating receiving at the client device the at least one deployment configuration file from the autoupdate folder of the configuration repository.

6. The method of claim 1, further comprising:

determining that an autoupdate flag is set on the client device, prior to facilitating obtaining the at least one deployment configuration file.

7. The method of claim 1, wherein:

each of the at least one deployment configuration file is stored in a respective subfolder in the memory of the client device; and

after updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file, the method comprises facilitating deletion of the respective subfolder of the at least one deployment configuration file.

8. The method of claim 1, wherein the updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file comprises operations of:

facilitating retrieving an indicator for an amount of storage space required for updating the application or the driver identified in the deployment entry of the at least one deployment configuration file;

facilitating determining whether an amount of storage space available in a memory of the client device is greater than the retrieved indicator for the amount of storage space required for updating the application or the driver;

facilitating retrieving a list of argument values included in the deployment entry of the at least one deployment configuration file; and

facilitating updating of the application or the driver using the list of argument values retrieved from the deployment entry of the at least one deployment configuration file.

9. The method of claim 8, the method further comprising operations of:

facilitating determination of whether at least one deployment configuration file exists in the configuration repository;

retrieving from the configuration repository the at least one deployment configuration file, upon determining that at least one deployment configuration file exists in the configuration repository.

10. A machine-readable storage medium encoded with instructions executable by one or more processors to perform one or more operations for automatically updating an application or a driver on a client device, the one or more operations comprising:

facilitating obtaining at the client device at least one deployment configuration file from a configuration repository,

wherein the at least one deployment configuration file includes a deployment entry corresponding to a package for updating an application or a driver, and the deployment entry includes identifiers for the package and for a version of the package;

facilitating storing the at least one deployment configuration file in a location of a memory of the client device that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored on the client device with the write-filter enabled from persisting across a reboot of the client device;

for each of the at least one deployment configuration file, facilitating operations of;

checking that a deployment entry of the at least one deployment configuration file corresponds to a package for updating an application or a driver that is installed on the client device, and that the deployment entry is identified with a version of the package that is higher than a version of the application or the driver that is installed on the client device; and

updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file using the package, while the write-filter is disabled.

11. The machine-readable storage medium of claim 10, wherein prior to updating on the client device the application or the driver, the one or more operations comprise:

facilitating a determination that the write-filter is enabled on the client device;

facilitating disabling of the write-filter on the client device; and

facilitating a reboot of the client device.

12. The machine-readable storage medium of claim 11, wherein following the reboot of the client device, the one or more operations comprise:

determining whether at least one deployment configuration file is stored in the memory of the client device; and

upon determining that at least one deployment configuration file is stored in the memory of the client device, retrieving the at least one deployment configuration file stored in the memory of the client device and facilitating the checking and updating operations using the retrieved at least one deployment configuration file.

13. The machine-readable storage medium of claim 11, wherein following the updating on the client device the application or the driver, the one or more operations comprise:

facilitating enabling of the write-filter on the client device; and

facilitating a reboot of the client device.

14. The machine-readable storage medium of claim 10, wherein the facilitating obtaining at the client device at least one deployment configuration file comprises:

facilitating locating the configuration repository;

facilitating determining that an autoupdate folder exists on the configuration repository; and

facilitating receiving at the client device the at least one deployment configuration file from the autoupdate folder of the configuration repository.

15. The machine-readable storage medium of claim 10, wherein the one or more operations comprise:

determining that an autoupdate flag is set on the client device, prior to facilitating obtaining the at least one deployment configuration file.

16. The machine-readable storage medium of claim 10, wherein:

each of the at least one deployment configuration file is stored in a respective subfolder in the memory of the client device; and

after updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file, the one or more operations comprise facilitating deletion of the respective subfolder of the at least one deployment configuration file.

17. The machine-readable storage medium of claim 10, wherein the updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file comprises operations of:

facilitating retrieving an indicator for an amount of storage space required for updating the application or the driver identified in the deployment entry of the at least one deployment configuration file;

facilitating determining whether an amount of storage space available in a memory of the client device is greater than the retrieved indicator for the amount of storage space required for updating the application or the driver;

facilitating retrieving a list of argument values included in the deployment entry of the at least one deployment configuration file; and

facilitating updating of the application or the driver using the list of argument values retrieved from the deployment entry of the at least one deployment configuration file.

18. The machine-readable storage medium of claim 17, wherein the one or more operations comprise:

facilitating determination of whether at least one deployment configuration file exists in the configuration repository; and

retrieving from the configuration repository the at least one deployment configuration file, upon determining that at least one deployment configuration file exists in the configuration repository.

19. A hardware apparatus for automatically updating an application or a driver on a client device, the hardware apparatus comprising:

one or more modules configured to perform one or more operations comprising;

facilitating obtaining at the client device at least one deployment configuration file from a configuration repository,

wherein the at least one deployment configuration file includes a deployment entry corresponding to a package for updating an application or a driver, and the deployment entry includes identifiers for the package and for a version of the package;

facilitating storing the at least one deployment configuration file in a location of a memory of the client device that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored on the client device with the write-filter enabled from persisting across a reboot of the client device;

for each of the at least one deployment configuration file, facilitating operations of;

checking that a deployment entry of the at least one deployment configuration file corresponds to a package for updating an application or a driver that is installed on the client device, and that the deployment entry is identified with a version of the package that is higher than a version of the application or the driver that is installed on the client device; and

updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file using the package, while the write-filter is disabled.

20. The hardware apparatus of claim 19, wherein prior to updating on the client device the application or the driver, the one or more operations further comprise:

facilitating a determination that the write-filter is enabled on the client device;

facilitating disabling of the write-filter on the client device; and

facilitating a reboot of the client device.

21. The hardware apparatus of claim 20, wherein following the reboot of the client device, the one or more operations further comprise:

determining whether at least one deployment configuration file is stored in the memory of the client device; and

upon determining that at least one deployment configuration file is stored in the memory of the client device, retrieving the at least one deployment configuration file stored in the memory of the client device and facilitating the checking and updating operations using the retrieved at least one deployment configuration file.

22. The hardware apparatus of claim 20 wherein following the updating on the client device the application or the driver, the one or more operations further comprise:

facilitating enabling of the write-filter on the client device; and

facilitating a reboot of the client device.

23. The hardware apparatus of claim 19, wherein the facilitating obtaining at the client device at least one deployment configuration file comprises:

facilitating locating the configuration repository;

facilitating determining that an autoupdate folder exists on the configuration repository; and

facilitating receiving at the client device the at least one deployment configuration file from the autoupdate folder of the configuration repository.

24. The hardware apparatus of claim 19, wherein the one or more operations further comprise:

determining that an autoupdate flag is set on the client device, prior to facilitating obtaining the at least one deployment configuration file.

25. The hardware apparatus of claim 19, wherein:

each of the at least one deployment configuration file is stored in a respective subfolder in the memory of the client device; and

after updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file, the one or more operations further comprise facilitating deletion of the respective subfolder of the at least one deployment configuration file.

26. The hardware apparatus of claim 19, wherein the updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file comprises operations of:

facilitating retrieving an indicator for an amount of storage space required for updating the application or the driver identified in the deployment entry of the at least one deployment configuration file;

facilitating determining whether an amount of storage space available in a memory of the client device is greater than the retrieved indicator for the amount of storage space required for updating the application or the driver;

facilitating retrieving a list of argument values included in the deployment entry of the at least one deployment configuration file; and

facilitating updating of the application or the driver using the list of argument values retrieved from the deployment entry of the at least one deployment configuration file.

27. The hardware apparatus of claim 26, wherein the one or more operations further comprise:

facilitating determination of whether at least one deployment configuration file exists in the configuration repository; and

retrieving from the configuration repository the at least one deployment configuration file, upon determining that at least one deployment configuration file exists in the configuration repository.

28. An apparatus for automatically updating an application or a driver on a client device, the apparatus comprising:

means for facilitating obtaining at the client device at least one deployment configuration file from a configuration repository,

wherein the at least one deployment configuration file includes a deployment entry corresponding to a package for updating an application or a driver, and the deployment entry includes identifiers for the package and for a version of the package;

means for facilitating storing the at least one deployment configuration file in a location of a memory of the client device that is exempt from a write-filter restriction, wherein the write-filter restriction prohibits a file stored on the client device with the write-filter enabled from persisting across a reboot of the client device;

means for, for each of the at least one deployment configuration file, facilitating operations of;

checking that a deployment entry of the at least one deployment configuration file corresponds to a package for updating an application or a driver that is installed on the client device, and that the deployment entry is identified with a version of the package that is higher than a version of the application or the driver that is installed on the client device; and

updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file using the package, while the write-filter is disabled.

29. The apparatus of claim 28, further comprising:

means for, prior to updating on the client device the application or the driver, facilitating a determination that the write-filter is enabled on the client device;

means for facilitating disabling of the write-filter on the client device; and

means for facilitating a reboot of the client device.

30. The apparatus of claim 29, further comprising:

means for, following the reboot of the client device, determining whether at least one deployment configuration file is stored in the memory of the client device; and

means for, upon determining that at least one deployment configuration file is stored in the memory of the client device, retrieving the at least one deployment configuration file stored in the memory of the client device and facilitating the checking and updating operations using the retrieved at least one deployment configuration file.

31. The apparatus of claim 29, further comprising:

means for, following the updating on the client device the application or the driver, facilitating enabling of the write-filter on the client device; and

means for facilitating a reboot of the client device.

32. The apparatus of claim 28, wherein the means for facilitating obtaining at the client device at least one deployment configuration file further comprise:

means for facilitating locating the configuration repository;

means for facilitating determining that an autoupdate folder exists on the configuration repository; and

means for facilitating receiving at the client device the at least one deployment configuration file from the autoupdate folder of the configuration repository.

33. The apparatus of claim 28, further comprising:

means for determining that an autoupdate flag is set on the client device, prior to facilitating obtaining the at least one deployment configuration file.

34. The apparatus of claim 28, wherein:

each of the at least one deployment configuration file is stored in a respective subfolder in the memory of the client device; and

the apparatus further comprises means for, after updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file, facilitating deletion of the respective subfolder of the at least one deployment configuration file.

35. The apparatus of claim 28, wherein the means for updating on the client device the application or the driver corresponding to the deployment entry of the at least one deployment configuration file comprise:

means for facilitating retrieving an indicator for an amount of storage space required for updating the application or the driver identified in the deployment entry of the at least one deployment configuration file;

means for facilitating determining whether an amount of storage space available in a memory of the client device is greater than the retrieved indicator for the amount of storage space required for updating the application or the driver;

means for facilitating retrieving a list of argument values included in the deployment entry of the at least one deployment configuration file; and

means for facilitating updating of the application or the driver using the list of argument values retrieved from the deployment entry of the at least one deployment configuration file.

36. The apparatus of claim 35, further comprising:

means for facilitating determination of whether at least one deployment configuration file exists in the configuration repository; and

means for retrieving from the configuration repository the at least one deployment configuration file, upon determining that at least one deployment configuration file exists in the configuration repository.