Install File Size Optimization and Installation Verification System
US-2018136920-A1 · May 17, 2018 · US
US10558450B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10558450-B2 |
| Application number | US-201715426578-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 7, 2017 |
| Priority date | Feb 7, 2017 |
| Publication date | Feb 11, 2020 |
| Grant date | Feb 11, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
When it is desired to update a group of thin clients that have a common configuration, the update can be deployed to a reference device on which a replicate tool executes. The replicate tool can examine the file system and registry of the reference device and create a manifest that describes the current state. The manifest can then be published for access by an agent that executes on the thin clients in the group. When the agent receives the manifest, it can compare the received manifest to an existing manifest on the thin client that defines the thin client's current state to identify any artifacts that differ. The agent can then retrieve and install any artifacts the thin client needs to match the current state of the reference device.
Opening claim text (preview).
What is claimed: 1. A method for updating a group of computing devices comprising: scanning a file system and a registry database of a reference device to identify each file of a plurality of files in the file system and each registry key of a plurality of registry keys in the registry database; based on the scanning, generating a reference device manifest that includes an entry for each identified file of the files in the file system and an entry for each identified registry key of the registry keys in the registry database, each entry identifying the file or registry key to which the entry pertains; publishing the reference device manifest along with a copy of each identified file of the files and each identified registry key of the registry keys; receiving, by an agent on each of the computing devices, the reference device manifest; comparing, by the agent on each of the computing devices, the reference device manifest to a local manifest that includes entries for each file in a file system of the computing device and each registry key in a registry database of the computing device; based on the comparison, determining, by the agent one each of the computing devices, that the reference device manifest includes a plurality of entries that are not included in the local manifest, the plurality of entries pertaining to one or more files and one or more registry keys; employing, by the agent on each of the computing devices, each of the plurality of entries in the reference device manifest that are not included in the local manifest to retrieve the copy of the file or registry to which the entry pertains such that a copy of each of the one or more files and a copy of each of the one or more registry keys are retrieved; and copying, by the agent on each of the computing devices, the one or more retrieved files to the file system of the computing device and the one or more retrieved registry keys to the registry database of the computing device to thereby cause the files in the file system of each of the computing devices to match the files in the file system of the reference device and the registry keys in the registry database of each of the computing devices to match the registry keys in the registry database of the reference device. 2. The method of claim 1 , further comprising: prior to receiving the reference device manifest, determining that a version of the local manifest does not match a version of the reference device manifest. 3. The method of claim 2 , wherein the version of the local manifest is lower than the version of the reference device manifest. 4. The method of claim 1 , further comprising: based on the comparison, determining, by the agent on each of the computing devices, that the reference device manifest includes an entry that identifies a first file and a first version and that the local manifest includes an entry that identifies the first file and a second version; retrieving the first version of the first file; and copying the first version of the first file to the file system of the computing device in place of the second version of the first file that is present in the file system of the computing device. 5. The method of claim 4 , wherein the first and second versions are defined in the respective entries by a date of last modification such that the determination comprises determining that the dates of last modification do not match. 6. The method of claim 4 , wherein the first and second versions are defined in the respective entries by a cyclic redundancy check (CRC) of the corresponding file such that the determination comprises determining that the respective CRCs do not match. 7. The method of claim 4 , wherein copying the first version of the first file to the file system of the computing device comprises causing the first version of the first file to be copied on reboot to a desired location in the file system of the computing device. 8. The method of claim 7 , wherein causing the first version of the first file to be copied on reboot to the desired location in the file system of the computing device comprises causing a write filter to commit one or more registry entries to a protected volume. 9. The method of claim 4 , wherein copying the first version of the first file to the computing device comprises causing a write filter to commit the first version of the first file to a protected volume on which the file system is maintained. 10. The method of claim 1 , wherein copying the one or more retrieved files to the file system of the computing device and the one or more retrieved registry keys to the registry database of the computing device comprises causing a write filter to commit the one or more retrieved files and the one or more retrieved registry keys to a protected volume. 11. The method of claim 1 , further comprising: based on the comparison, determining that the local manifest includes entries that are not included in the reference device manifest; and deleting, from the computing device, the files or registry keys that pertain to the entries that are included in the local manifest but are not included in the reference device manifest. 12. The method of claim 1 , wherein the one or more files and the one or more registry keys retrieved and copied by one of the computing devices is different from the one or more files and the one or more registry keys retrieved and copied by another one of the computing devices. 13. The method of claim 1 , wherein the one or more retrieved files comprise one or more .exe or .dll files. 14. One or more non-transitory computer storage media storing computer executable instructions which when executed implement a method for updating a group of computing devices comprising: scanning a file system and a registry database of a reference device to identify each file of a plurality of files in the file system and each registry key of a plurality of registry keys in the registry database; based on the scanning, generating a reference device manifest that includes an entry for each identified file of the files in the file system and an entry for each identified registry key of the registry keys in the registry database, each entry identifying the file or registry key to which the entry pertains; publishing the reference device manifest along with a copy of each identified file of the files and each identified registry key of the registry keys; receiving, by an agent on each of the computing devices, the reference device manifest; comparing, by the agent on each of the computing devices, the reference device manifest to a local manifest that includes entries for each file in a file system of the computing device and each registry key in a registry database of the computing device; based on the comparison, determining, by the agent one each of the computing devices, that the reference device manifest includes a plurality of entries that are not included in the local manifest, the plurality of entries pertaining to one or more files and one or more registry keys; employing, by the agent on each of the computing devices, each of the plurality of entries in the reference device manifest that are not included in the local manifest to retrieve the copy of the file or registry to which the entry pertains such that a copy of each of the one or more files and a copy of each of the one or more registry keys are retrieved; and copying, by the agent on each of the computing devices, the one or more retrieved files to the file system of the computing device and the one or more retrieved registry keys to the registry database of the computing device to thereby cause the f
Update request formulation · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Configuring for program initiating, e.g. using registry, configuration files · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.