IP Library Granted Patent US 9,032,052
Granted Patent B2
US 9,032,052 · App. 14/086,504 · Granted May 12, 2015

Deployment of a driver or an application on a client device having a write-filter

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 9,032,052
App. No.
14/086,504
Granted
May 12, 2015
Kind
B2
Abstract

The deployment of a driver or an application on a client device having a write-filter is described. A deployment configuration file is obtained, wherein the deployment configuration file includes a plurality of deployment entries each having information for deployment of one of a driver and an application. A first deployment entry is retrieved from the deployment configuration file, and the deployment configuration file is modified to remove the first deployment entry from the deployment configuration file. The modified deployment configuration file is stored 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. The one of the driver and the application of the first deployment entry is then deployed on the client device while the write-filter is disabled.

Claims (61)

1. A computer-implemented method for configuring a client device having a write-filter, the method comprising:

receiving a deployment file associated with the client device, the deployment file having a first deployment entry;

storing the deployment file at a first storage location of the client device that is exempt from the write-filter; and

deploying, to a second storage location of the client device, a first software module associated with the first deployment entry, wherein the write-filter, when enabled, prohibits a file stored at the second storage location subject to the write-filter from persisting across a reboot of the client device.

2. The method of claim 1 wherein deploying the first software module comprises:

disabling the write-filter;

after the write-filter is disabled, performing a first reboot of the client device, wherein the first software module is installed on the client device upon the first reboot;

after the first software module is installed on the client device, enabling the write-filter on the client device; and

after the write filter is enabled, performing a second reboot of the client device.

3. The method of claim 1 , wherein receiving the deployment file comprises:

when the deployment file is stored at the first storage location, retrieving the deployment file from the first storage location.

4. The method of claim 1 , wherein storing the deployment file comprises:

modifying the deployment file by removing the first deployment entry; and

storing the modified deployment file at the first storage location.

5. The method of claim 1 , wherein, when the write filter is disabled, the method comprises:

deploying, to the second storage location, a second software module associated with a second deployment entry in the deployment file.

6. The method of claim 1 , wherein deploying the first software module comprises:

determining whether a hardware platform associated with the client device is included among supported platforms identified in the first deployment entry;

determining whether a first amount of storage space identified in the first deployment entry is available at the second memory location;

when a first version of the first software module is installed at the second memory location and when the first version is older than a second version associated with the first software module, uninstalling the first version of the first software module from the second memory location; and

deploying the first software module at the second memory location using a list of argument values included in the first deployment entry.

7. The method of claim 1 , wherein deploying the first software module comprises:

when the deployment file corresponds to a new deployment, retrieving an installation package identifier associated with the first software module; and

deploying the first software module at the second memory location using the installation package identifier.

8. The method of claim 1 , wherein receiving the deployment file comprises:

when the deployment file is obtainable from a configuration repository server, retrieving the deployment file from the configuration repository server.

9. The method of claim 1 , wherein storing the deployment file at the first storage location comprises:

copying the deployment file to an archive file at the first storage location; and

renaming the archive file to correspond to a last successful deployment file.

10. The method of claim 1 , wherein the deployment file is an extensible markup language (XML) file, and wherein the first software module is selected from at least one of: a device driver and an application.

11. An information handling system comprising:

a processor having access to a memory medium, wherein the memory medium stores instructions executable by the processor, the instructions, when executed by the processor, cause the processor to:

receive a deployment file associated with the client device, the deployment file having a first deployment entry;

store the deployment file at a first storage location of the client device that is exempt from the write-filter; and

deploy, to a second storage location of the client device, a first software module associated with the first deployment entry, wherein the write-filter, when enabled, prohibits a file stored at the second storage location subject to the write-filter from persisting across a reboot of the client device.

12. The information handling system of claim 11 , wherein the instructions to deploy the first software module comprise instructions to:

disable the write-filter;

after the write-filter is disabled, perform a first reboot of the client device, wherein the first software module is installed on the client device upon the first reboot;

after the first software module is installed on the client device, enable the write-filter on the client device; and

after the write filter is enabled, perform a second reboot of the client device.

13. The information handling system of claim 11 , wherein the instructions to receive the deployment file comprise instructions to:

when the deployment file is stored at the first storage location, retrieve the deployment file from the first storage location.

14. The information handling system of claim 11 , wherein the instructions to store the deployment file comprise instructions to:

modify the deployment file by removing the first deployment entry; and

store the modified deployment file at the first storage location.

15. The information handling system of claim 11 , wherein, when the write filter is disabled, the instructions include instructions to:

deploy, to the second storage location, a second software module associated with a second deployment entry in the deployment file.

16. The information handling system of claim 11 , wherein the instructions to deploy the first software module comprise instructions to:

determine whether a hardware platform associated with the client device is included among supported platforms identified in the first deployment entry;

determine whether a first amount of storage space identified in the first deployment entry is available at the second memory location;

when a first version of the first software module is installed at the second memory location and when the first version is older than a second version associated with the first software module, uninstall the first version of the first software module from the second memory location; and

deploy the first software module at the second memory location using a list of argument values included in the first deployment entry.

17. The information handling system of claim 11 , wherein the instructions to deploy the first software module comprise instructions to:

when the deployment file corresponds to a new deployment, retrieve an installation package identifier associated with the first software module; and

deploy the first software module at the second memory location using the installation package identifier.

18. The information handling system of claim 11 , wherein the instructions to receive the deployment file comprise instructions to:

when the deployment file is obtainable from a configuration repository server, retrieve the deployment file from the configuration repository server.

19. The information handling system of claim 11 , wherein the instructions to store the deployment file at the first storage location comprise instructions to:

copy the deployment file to an archive file at the first storage location; and

rename the archive file to correspond to a last successful deployment file.

20. The information handling system of claim 11 , wherein the deployment file is an extensible markup language (XML) file, and wherein the first software module is selected from at least one of: a device driver and an application.

Assignments (17)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
MERGER Recorded May 13, 2022
From: WYSE TECHNOLOGY L.L.C.
To: DELL MARKETING CORPORATION
Reel/Frame 060064/0586 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061324/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL, L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058216/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
RELEASE OF SECURITY INTEREST OF REEL 032809 FRAME 0930 (TL) Recorded Sep 14, 2016
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; CREDANT TECHNOLOGIES, INC.; COMPELLENT TECHNOLOGIES, INC.; FORCE10 NETWORKS, INC.; SECUREWORKS, INC.
Reel/Frame 040045/0255 →
RELEASE OF REEL 032810 FRAME 0206 (NOTE) Recorded Sep 14, 2016
From: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; CREDANT TECHNOLOGIES, INC.; COMPELLENT TECHNOLOGIES, INC.; FORCE10 NETWORKS, INC.; SECUREWORKS, INC.
Reel/Frame 040027/0204 →
RELEASE OF REEL 032809 FRAME 0887 (ABL) Recorded Sep 13, 2016
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; CREDANT TECHNOLOGIES, INC.; COMPELLENT TECHNOLOGIES, INC.; FORCE10 NETWORKS, INC.; SECUREWORKS, INC.
Reel/Frame 040017/0314 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES) Recorded May 1, 2014
From: COMPELLENT TECHNOLOGIES, INC.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; SECUREWORKS, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 032810/0206 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL) Recorded May 1, 2014
From: COMPELLENT TECHNOLOGIES, INC.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; SECUREWORKS, INC.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032809/0887 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN) Recorded May 1, 2014
From: COMPELLENT TECHNOLOGIES, INC.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; FORCE10 NETWORKS, INC.; SECUREWORKS, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 032809/0930 →
CHANGE OF NAME Recorded Apr 24, 2014
From: WYSE TECHNOLOGY INC.
To: WYSE TECHNOLOGY L.L.C.
Reel/Frame 032747/0226 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2013
From: MALLUR, MURALIDHARA; BANDAKKA, JYOTHI; TUKOL, SANMATI
To: WYSE TECHNOLOGY INC.
Reel/Frame 031652/0095 →