WO2007141780A2 - A system and method for software application remediation - Google Patents

A system and method for software application remediation Download PDF

Info

Publication number
WO2007141780A2
WO2007141780A2 PCT/IL2007/000677 IL2007000677W WO2007141780A2 WO 2007141780 A2 WO2007141780 A2 WO 2007141780A2 IL 2007000677 W IL2007000677 W IL 2007000677W WO 2007141780 A2 WO2007141780 A2 WO 2007141780A2
Authority
WO
WIPO (PCT)
Prior art keywords
client
image block
present
application
characterization data
Prior art date
Application number
PCT/IL2007/000677
Other languages
French (fr)
Other versions
WO2007141780A3 (en
Inventor
Zak Dechovich
Yossi Koren
Original Assignee
Reimage Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Reimage Ltd filed Critical Reimage Ltd
Priority to US12/303,375 priority Critical patent/US9104574B2/en
Publication of WO2007141780A2 publication Critical patent/WO2007141780A2/en
Publication of WO2007141780A3 publication Critical patent/WO2007141780A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793Remedial or corrective actions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0748Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a remote unit communicating with a single-box computer node experiencing an error/fault

Definitions

  • the present invention relates generally to the field of computing. More specifically, the present invention relates to a method and system for software application or operating system remediation.
  • Software corruption i.e. corruption of software applications and operating system objects
  • Computers usually malfunction because of missing, corrupted or redundant software elements or components, damage caused by malicious software, incompatibility, and user's actions.
  • Software applications such a MS Word or Outlook are comprised of multiple components (e.g. .dll files or software objects), each of which may be subject to corruption or deletion.
  • the corruption, deletion or misconfiguration of any application component may cause anomalous behavior.
  • the repair costs money.
  • the user cannot work on the malfunctioned computer during this period which may last for some time.
  • Discrete information and passwords that are on the machine are out of his home and become a breech of user's privacy.
  • the technician may decide that it is faster and cheaper for him to reformat the machine without backing up and reinstalling everything again.
  • fixing a computer there are more issues that just making the machine work. Repairing the computer is becoming not so simple task; especially when computers are a constant part of our daily life.
  • Making the computer work means making all of its components work.
  • a component is software or its part that can be fixed, reinstalled or removed. Formatting the hard drive and reinstalling everything back is a way to repair computers. Removing a faulty program may solve a problem. Updating or patching may yield good results. Fixing a component will resolve the problem without affecting on other components.
  • Fixing anomalies within component requires specialty in that specific component.
  • Each component has its own set of data, configuration, files, and logic. Knowing how to fix MS windows XP does not guarantee that one will know how to fix RAR's archiving software crashing issues.
  • Each component is a world of its own. This usually is why components are seldom fixed and often reinstalled. Consequently, fixing components is not simple and not common. [008] It would be useful, therefore to have a method for repairing of computer operating systems and software components by eliminating anomalies.
  • the present invention is a method and system for repairing or remediation of one or more software applications, including an operating system, running on a computer, by detecting anomalies in one or more components associated with the software application.
  • a faulty software component may be repaired or replaced by comparing its state to the state of a corresponding reference component and modifying, replacing, or removing the faulty component based on the results of the comparison.
  • a software remediation system server may store sets of related software application image blocks in a software image repository.
  • the software image repository may be located on the remediation server.
  • the software image repository may be distributed across one more servers and/or end-users' computers functionally associated with the remediation server.
  • the repository may be located on one or more mass storage devices (e.g. removable HD, USB storage, etc.) functionally associated with the client.
  • reference image blocks associated a given application may be generated by parsing the application's installation files.
  • a reference image block may be generated by monitoring an installation process of the given application.
  • an image block may be generated by collecting data from a number of client computers, and identifying the similarities and differences between them. Any method or technology for generating reference image blocks known today or to be devised in the future may be applicable to the present invention.
  • an application image block may be defined as: (1) a partial or full image of a file associated with the application, (2) an image of one or more files associated with the application, (3) registry keys and values associated with the application, and (4) entries in configuration files and/or any other data associated (i.e. operating system objects) with the application.
  • an Image block of a given software application may be defined and/or composed of any data which constitutes or is otherwise associated with the software application.
  • an image block may be normalized, i.e. with installation- specific information (e.g. installation path, environment variables, user names, and other such settings) replaced with generic variables.
  • relative configuration between a normalized reference image block and the installed application image block may be taken into account and the corresponding object structures and may be mapped from the reference object structure to the installed object structure.
  • an image block may be stored as absolute data, containing a true replicate image of an installed component.
  • a remediation server and a client computer may communicate via a distributed data network (e.g. Internet).
  • Image block characterization data relating to applications installed on the client may be exchanged between the client and the remediation server.
  • an application identification module on the client may identify installed applications or components associated with installed applications, and may transmit through a communication module the data associated with identified applications.
  • the application identification module may transmit only a list of identified applications, or, according to further embodiments of the present invention, may derive image block characterization data for identified applications or application components and may transmit the characterization data to the remediation server.
  • the remediation server may send to the client image block characterization data associated with applications installed on the client.
  • the remediation server may send the image block characterization data in response to a list of applications or application components sent by the client, or it may send characterization data of all applications/components image blocks stored in the repository.
  • the server may respond by sending back a list of image blocks required for software remediation/repair.
  • the remediation server may send to the client customized check procedures which may be designed to perform complex validation and/or consistency checks on data content of components.
  • a customized check procedure may be one or more of: checking that a field in a configuration file is within its valid range, checking that a specified path value really exists on the client, checking that a specified resource a value points to (e.g. an IP port) is really useable, checking that an application data file is consistent, and/or any other check that may require application-specific knowledge.
  • the characterization data may consist of: (1) checksum (such as MD5), (2) cryptographic signature, (3) file size and modification time, and/or any other file and data characterization parameter known today or to be devised in the future.
  • an image block comparison module operating either on the client or on the remediation server, may compare characterization data of reference image blocks with characterization data of image blocks associated with applications installed on the client.
  • the comparison module may designate or flag an image block of an application stored on the client as being anomalous if there is a mismatch between that image block's characterization data the characterization data of a corresponding reference image block.
  • the comparison module may compare a substantial portion of the data bits of the client image block its corresponding reference image block.
  • the application comparison module may take into account normalization factors, as described above, during the process of comparing a normalized reference image block and an image block on the client.
  • the comparison module may take into account relative configuration deltas between a normalized reference image block and the installed application image block, and may map corresponding object structures from the installed object structure to the reference object structure.
  • comparison of reference image blocks and installed image block may be performed according to numerous methodologies and using various techniques. Any method, code or technology for comparing reference components or structures to installed components or structures, known today or to be devised in the future, may be applicable to the present invention.
  • the server may send the application image blocks to the client.
  • the transmission of image blocks and needing repair/replacement/removal may be performed in response to a request from the client.
  • a user of the client computer may respond to a report of detected anomalous image blocks, which response may be the basis of the image block request to the remediation server.
  • the report may be based on the results of the comparison and customized checks performed by the comparison module, either running on the client or on the remediation server.
  • the user may select which image blocks to repair/replace/removal, and thus an image block request to the server may be generated and transmitted.
  • an application repair module running on the computer may use reference image blocks and customized repair procedures received from the remediation server to repair/replace/remove corresponding image blocks on the client, which corresponding image blocks have been designated as anomalous.
  • the application repair module on the client computer may replace the normalized image's generic variables with values specific to the corresponding image block installed on the client computer.
  • the repair module may take into account relative configuration deltas between a normalized reference image block and the installed application image block and may map corresponding object structures from the reference object structure to the installed object structure.
  • the client computer may identify which settings are general and which are installation-specific, and may modify them accordingly.
  • the repair module may remove image blocks associate with application components and operating system components or structures which have been found to be redundant or conflicting by the
  • the remediation server may send to the client customized repair procedures which may be designed to perform complex repair operations on data content of components.
  • a customized repair procedure may be one or more of: changing a field in a configuration file to one a valid value, creating a nonexistent path specified, changing an unusable resource value specified (e.g. an IP port) to a usable one, repairing an inconsistent application data file, and/or any other action that requires application-specific knowledge.
  • FIG. 1 is a block diagram illustrating the main components of an exemplary software remediation system in accordance with some embodiments of the present invention
  • FIG. 2A is a block diagram illustrating the functional building blocks of a software remediation server including an image comparison module in accordance with some embodiments of the present invention
  • FIG. 2B is a block diagram illustrating the functional building blocks of a software remediation server in accordance with some embodiments of the present invention.
  • FIG. 3A is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention
  • FIG. 3B is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention
  • FIG. 4A is a block diagram illustrating the functional building blocks of a software remediation client system in accordance with some embodiments of the present invention.
  • FIG. 4B is a block diagram illustrating the functional building blocks of a software remediation client system including an image comparison module in accordance with some embodiments of the present invention
  • FIG. 5A is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client in accordance with some embodiments of the present invention.
  • FIG. 5B is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client in accordance with some embodiments of the present invention.
  • Embodiments of the present invention may include apparatuses for performing the operations herein. This apparatus may be specially constructed for the desired purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer.
  • Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.
  • a computer readable storage medium such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.
  • the present invention is a method and system for repairing or remediation of one or more software applications, including an operating system, running on a computer, by detecting anomalies in one or more components associated with the software application.
  • a faulty software component may be repaired or replaced by comparing its state to the state of a corresponding reference component and modifying, replacing, or removing the faulty component based on the results of the comparison.
  • a software remediation system server may store sets of related software application image blocks in a software image repository.
  • the software image repository may be located on the remediation server.
  • the software image repository may be distributed across one more servers and/or end-users' computers functionally associated with the remediation server.
  • the repository may be located on one or more mass storage devices (e.g. removable HD, USB storage, etc.) functionally associated with the client.
  • reference image blocks associated a given application may be generated by parsing the application's installation files.
  • a reference image block may be generated by monitoring an installation process of the given application.
  • an image block may be generated by collecting data from a number of client computers, and identifying the similarities and differences between them. Any method or technology for generating reference image blocks known today or to be devised in the future may be applicable to the present invention.
  • an application image block may be defined as: (1) a partial or full image of a file associated with the application, (2) an image of one or more files associated with the application, (3) registry keys and values associated with the application, and (4) entries in configuration files and/or any other data associated (i.e. operating system objects) with the application.
  • an Image block of a given software application may be defined and/or composed of any data which constitutes or is otherwise associated with the software application.
  • an image block may be normalized, i.e. with installation- specific information (e.g. installation path, environment variables, user names, and other such settings) replaced with generic variables.
  • relative configuration between a normalized reference image block and the installed application image block may be taken into account and the corresponding object structures and may be mapped from the reference object structure to the installed object structure.
  • an image block may be stored as absolute data, containing a true replicate image of an installed component.
  • a remediation server and a client computer may communicate via a distributed data network (e.g. Internet).
  • Image block characterization data relating to applications installed on the client may be exchanged between the client and the remediation server.
  • an application identification module on the client may identify installed applications or components associated with installed applications, and may transmit through a communication module the data associated with identified applications.
  • the application identification module may transmit only a list of identified applications or, according to further embodiments of the present invention may derive image block characterization data for identified applications or application components and may transmit the characterization data to the remediation server.
  • the remediation server may send to the client image block characterization data associated with applications installed on the client.
  • the remediation server may send the image block characterization data in response to a list of applications or application components sent by the client, or it may send characterization data of all applications/components image blocks stored in the repository.
  • the server may respond by sending back a list of image blocks required for software remediation/repair.
  • the remediation server may send to the client customized check procedures which may be designed to perform complex validation and/or consistency checks on data content of components.
  • a customized check procedure may be one or more of: checking that a field in a configuration file is within its valid range, checking that a specified path value really exists on the client, checking that a specified resource a value points to (e.g. an IP port) is really useable, checking that an application data file is consistent, and/or any other check that may require application-specific knowledge.
  • the characterization data may consist of: (1) checksum (such as MD5), (2) cryptographic signature, (3) file size and modification time, and/or any other file and data characterization parameter known today or to be devised in the future.
  • an image block comparison module operating either on the client or on the remediation server, may compare characterization data of reference image blocks with characterization data of image blocks associated with applications installed on the client.
  • the comparison module may designate or flag an image block of an application stored on the client as being anomalous if there is a mismatch between that image block's characterization data the characterization data of a corresponding reference image block.
  • the comparison module may compare a substantial portion of the data bits of the client image block its corresponding reference image block.
  • the application comparison module may take into account normalization factors, as described above, during the process of comparing a normalized reference image block and an image block on the client.
  • the comparison module may take into account relative configuration deltas between a normalized reference image block and the installed application image block, and may map corresponding object structures from the installed object structure to the reference object structure.
  • comparison of reference image blocks and installed image block may be performed according to numerous methodologies and using various techniques. Any method, code or technology for comparing reference components or structures to installed components or structures, known today or to be devised in the future, may be applicable to the present invention.
  • the server may send the application image blocks to the client.
  • the transmission of image blocks and needing repair/replacement/removal may be performed in response to a request from the client.
  • a user of the client computer may respond to a report of detected anomalous image blocks, which response may be the basis of the image block request to the remediation server.
  • the report may be based on the results of the comparison and customized checks performed by the comparison module, either running on the client or on the remediation server.
  • the user may select which image blocks to repair/replace/removal, and thus an image block request to the server may be generated and transmitted.
  • an application repair module running on the computer may use reference image blocks and customized repair procedures received from the remediation server to repair/replace/remove corresponding image blocks on the client, which corresponding image blocks have been designated as anomalous.
  • the application repair module on the client computer may replace the normalized image's generic variables with values specific to the corresponding image block installed on the client computer.
  • the repair module may take into account relative configuration deltas between a normalized reference image block and the installed application image block and may map corresponding object structures from the reference object structure to the installed object structure.
  • the client computer may identify which settings are general and which are installation-specific, and may modify them accordingly.
  • the repair module may remove image blocks associate with application components and operating system components or structures which have been found to be redundant or conflicting by the comparison module.
  • the remediation server may send to the client customized repair procedures which may be designed to perform complex repair operations on data content of components.
  • a customized repair procedure may be one or more of: changing a field in a configuration file to one a valid value, creating a nonexistent path specified, changing an unusable resource value specified (e.g. an IP port) to a usable one, repairing an inconsistent application data file, and/or any other action that requires application-specific knowledge.
  • FIG. 1 is a block diagram illustrating the main components of an exemplary software remediation system in accordance with some embodiments of the present invention.
  • a remote server 200 may be functionally associated with an application image repository 270, which is created and maintained by the image generator 300.
  • a client computer 100 may connect over a network to a server, and exchange information related to the application components installed on it, and to the application image blocks stored in the repository 270.
  • FIG. 2A is a block diagram illustrating the functional building blocks of a software remediation server including an image comparison module in accordance with some embodiments of the present invention
  • FIG. 3A is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention.
  • a client computer 100 connects to the server 200 via the communication module 250, and sends it characterization data for components it has identified (step 3000).
  • the server 200 may then construct a list of all the application image blocks associated with the components the client has identified (step 3100).
  • the comparison module 260 may then compare the received characterization data with characterization data of components stored in the repository 270 and construct a list of suspected anomalies (step 3200).
  • the server 200 may then send the client 100 a set of customized checks, which may be specific for some of the identified application blocks (step 3300). After receiving the customized check results (step 3400), the server may send the comprehensive results to the client (step 3500).
  • the client computer 100 may then present the user with a list of anomalous components which can be repaired, and forward their choice to the server 200 (step 3600).
  • the server 200 may send the full application image blocks and customized repair procedures to the client for it to restore (step 3700).
  • FIG. 2B is a block diagram illustrating the functional building blocks of a software remediation server in accordance with some embodiments of the present invention
  • FIG. 3B is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention.
  • a remediation server 200 accepts a connection from a client computer 100 via the communication module 250, and sends it characterization data of all components/image blocks and customized checks stored in the repository 270 (step 3050).
  • the client computer 100 compares its application components/image blocks with the reference image blocks on the server 200, and sends to the server 200 a list of required image blocks (step 3150).
  • the server 200 then sends the requested image blocks and customized repair procedures to the client 100 via the communication module 250 (step 3250).
  • FIG. 4A is a block diagram illustrating the functional building blocks of a software remediation client system in accordance with some embodiments of the present invention
  • FIG. 5A is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client computer in accordance with some embodiments of the present invention.
  • a client computer 100 connects to the server 200 and sends it a characterization data of components identified by the application identification module 140 (step 5000).
  • the server 200 may then send a set of customized check procedures, which may be specific for some of the identified application blocks (step 5100).
  • the client 200 may then perform the customized checks, and send the results to the server (step 5200).
  • the server 200 may then combine the results of the customized checks and the characterization data comparisons it had performed, and send a comprehensive list of anomalies to the client 100, which may present it to the user as a report, containing the identified anomalies that can be repaired (step 5300).
  • the client may then accept and forward the user's choice of which components/application blocks to repair to the server (step 5400).
  • the server 200 may send the full application image blocks and customized repair procedures to the client (step 5500), where they are restored by the application repair module 150, after converting normalized data to absolute data (step 5600).
  • FIG. 4B is a block diagram illustrating the functional building blocks of a software remediation client system including an image comparison module in accordance with some embodiments of the present invention
  • FIG. 5B is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client computer in accordance with some embodiments of the present invention.
  • a client computer 100 connects to the server 200 and receives characterization data for all components/image blocks known to the server (step 5050).
  • the application identification module 140 identifies components/image blocks related to installed application found on the local storage 170, and generates characterization data for them (step 5150).
  • the image comparison module 150 may then compare the characterization data generated for the identified components/image blocks with the corresponding characterization data of the reference image blocks received from the remediation server 200 (step 5250).
  • the comparison module 160 may then generate a comprehensive anomalies report based the comparison and present it to the user (step 5350).
  • the client 200 sends a list of requested image blocks to the server 200 (step 5450).
  • the server 200 then sends the requested image blocks and customized repair procedures to the client (step 5550), where they are restored by the application repair module 150 (step 5650).

Abstract

Disclose is a method and system for software remediation. According to some embodiments of the present invention, a data storage device may store one or more sets of related software application image blocks, wherein a set of image blocks is associated with a software application and is generated by parsing components of the software application. A communication module may exchange characterization data relating to image blocks with a client computer and corrupted block may be sent to the client.

Description

A SYSTEM AND METHOD FOR SOFTWARE APPLICATION REMEDIATION
FIELD OF THE INVENTION
[001] The present invention relates generally to the field of computing. More specifically, the present invention relates to a method and system for software application or operating system remediation.
BACKGROUND
[002] To repair a malfunctioning computer is a money and time consuming operation. The average user is incapable of repairing his/hers own computer. Therefore, Users are dependent on costly, non immediate, professional tech-support. On the other hand, techs have no tools to make a pc and all of its installed applications work, and the repair process is labor-intensive.
[003] Software corruption, i.e. corruption of software applications and operating system objects, is a primary cause for computer malfunction. Computers usually malfunction because of missing, corrupted or redundant software elements or components, damage caused by malicious software, incompatibility, and user's actions. Software applications such a MS Word or Outlook are comprised of multiple components (e.g. .dll files or software objects), each of which may be subject to corruption or deletion. The corruption, deletion or misconfiguration of any application component may cause anomalous behavior.
[004] The majority of the users are incapable of fixing their computers by themselves; the average user knows at most how to browse the Internet. A user has no simple and easy way to know that he has a wrong version of his mouse drivers which causes a mouse not to be recognized, or to know why windows explorer is constantly crashing, or why the media player does not play movies, or why a trial expired version of Nero viewer prevents the viewing of JPG images. Average users are lacking the knowledge to repair their own machines and need professional help. Thus, even the simplest problem that can be resolved in a mouse click is a major problem for the average user. [005] Repairing the machine involves spending money, time, down-time, and privacy issues. Even if there are no guarantees that all of the installed software and files will operate normally after the repair. The repair costs money. The user cannot work on the malfunctioned computer during this period which may last for some time. Discrete information and passwords that are on the machine are out of his home and become a breech of user's privacy. The technician may decide that it is faster and cheaper for him to reformat the machine without backing up and reinstalling everything again. In fixing a computer there are more issues that just making the machine work. Repairing the computer is becoming not so simple task; especially when computers are a constant part of our daily life.
[006] Making the computer work means making all of its components work. A component is software or its part that can be fixed, reinstalled or removed. Formatting the hard drive and reinstalling everything back is a way to repair computers. Removing a faulty program may solve a problem. Updating or patching may yield good results. Fixing a component will resolve the problem without affecting on other components. Although there are various ways to make the component work, the nature of the solution is the same - in order to make the computer work its faulty components must be repaired.
[007] Fixing anomalies within component requires specialty in that specific component. Each component has its own set of data, configuration, files, and logic. Knowing how to fix MS windows XP does not guarantee that one will know how to fix RAR's archiving software crashing issues. Each component is a world of its own. This usually is why components are seldom fixed and often reinstalled. Consequently, fixing components is not simple and not common. [008] It would be useful, therefore to have a method for repairing of computer operating systems and software components by eliminating anomalies.
SUMMARY OF THE INVENTION
[009] The present invention is a method and system for repairing or remediation of one or more software applications, including an operating system, running on a computer, by detecting anomalies in one or more components associated with the software application. According to some embodiments of the present invention, a faulty software component may be repaired or replaced by comparing its state to the state of a corresponding reference component and modifying, replacing, or removing the faulty component based on the results of the comparison.
[010] According to some embodiments of the present invention, a software remediation system server may store sets of related software application image blocks in a software image repository. According to some embodiments of the present invention, the software image repository may be located on the remediation server. According to alternative embodiments of the present invention, the software image repository may be distributed across one more servers and/or end-users' computers functionally associated with the remediation server. According to other embodiments of the present invention, the repository may be located on one or more mass storage devices (e.g. removable HD, USB storage, etc.) functionally associated with the client. [011] According to some embodiments of the present invention, reference image blocks associated a given application may be generated by parsing the application's installation files. According to alternative embodiments of the present invention, a reference image block may be generated by monitoring an installation process of the given application. According to other embodiments of the present invention, an image block may be generated by collecting data from a number of client computers, and identifying the similarities and differences between them. Any method or technology for generating reference image blocks known today or to be devised in the future may be applicable to the present invention.
[012] According to some embodiments of the present invention, an application image block may be defined as: (1) a partial or full image of a file associated with the application, (2) an image of one or more files associated with the application, (3) registry keys and values associated with the application, and (4) entries in configuration files and/or any other data associated (i.e. operating system objects) with the application. It should be clear to one of ordinary skill in the art that an Image block of a given software application may be defined and/or composed of any data which constitutes or is otherwise associated with the software application. According to further embodiments of the present invention, an image block may be normalized, i.e. with installation- specific information (e.g. installation path, environment variables, user names, and other such settings) replaced with generic variables. According to further embodiments of the present invention, relative configuration between a normalized reference image block and the installed application image block may be taken into account and the corresponding object structures and may be mapped from the reference object structure to the installed object structure. According to alternative embodiments of the present invention, an image block may be stored as absolute data, containing a true replicate image of an installed component.
[013] According to some embodiments of the present invention, a remediation server and a client computer may communicate via a distributed data network (e.g. Internet). Image block characterization data relating to applications installed on the client may be exchanged between the client and the remediation server. According to some embodiments of the present invention, an application identification module on the client may identify installed applications or components associated with installed applications, and may transmit through a communication module the data associated with identified applications. The application identification module may transmit only a list of identified applications, or, according to further embodiments of the present invention, may derive image block characterization data for identified applications or application components and may transmit the characterization data to the remediation server. [014] According to some embodiments of the present invention, the remediation server may send to the client image block characterization data associated with applications installed on the client. The remediation server may send the image block characterization data in response to a list of applications or application components sent by the client, or it may send characterization data of all applications/components image blocks stored in the repository. According to embodiments of the present invention where the server sends characterization data of all application/component image blocks stored in the repository, the client may respond by sending back a list of image blocks required for software remediation/repair.
[015] According to some embodiments of the present invention, the remediation server may send to the client customized check procedures which may be designed to perform complex validation and/or consistency checks on data content of components. According to some embodiments of the present invention, a customized check procedure may be one or more of: checking that a field in a configuration file is within its valid range, checking that a specified path value really exists on the client, checking that a specified resource a value points to (e.g. an IP port) is really useable, checking that an application data file is consistent, and/or any other check that may require application-specific knowledge.
[016] According to some embodiments of the present invention, the characterization data may consist of: (1) checksum (such as MD5), (2) cryptographic signature, (3) file size and modification time, and/or any other file and data characterization parameter known today or to be devised in the future.
[017] According to some embodiments of the present invention, an image block comparison module, operating either on the client or on the remediation server, may compare characterization data of reference image blocks with characterization data of image blocks associated with applications installed on the client. The comparison module may designate or flag an image block of an application stored on the client as being anomalous if there is a mismatch between that image block's characterization data the characterization data of a corresponding reference image block. According to some embodiments of the present invention, the comparison module may compare a substantial portion of the data bits of the client image block its corresponding reference image block.
[018] It should be understood by one of ordinary skill in the art that the application comparison module may take into account normalization factors, as described above, during the process of comparing a normalized reference image block and an image block on the client. The comparison module may take into account relative configuration deltas between a normalized reference image block and the installed application image block, and may map corresponding object structures from the installed object structure to the reference object structure.
[019] It should be understood by one of ordinary skill in the art that comparison of reference image blocks and installed image block may be performed according to numerous methodologies and using various techniques. Any method, code or technology for comparing reference components or structures to installed components or structures, known today or to be devised in the future, may be applicable to the present invention.
[020] According to some embodiments of the present invention, upon determining which applications and/or related components have anomalous image blocks (i.e. need repair), the server may send the application image blocks to the client. The transmission of image blocks and needing repair/replacement/removal may be performed in response to a request from the client. According to some embodiments, a user of the client computer may respond to a report of detected anomalous image blocks, which response may be the basis of the image block request to the remediation server. The report may be based on the results of the comparison and customized checks performed by the comparison module, either running on the client or on the remediation server. The user may select which image blocks to repair/replace/removal, and thus an image block request to the server may be generated and transmitted. [021] According to some embodiments of the present invention, an application repair module running on the computer may use reference image blocks and customized repair procedures received from the remediation server to repair/replace/remove corresponding image blocks on the client, which corresponding image blocks have been designated as anomalous. According to further embodiments of the present invention, if a reference image block received from the remediation server is normalized, the application repair module on the client computer may replace the normalized image's generic variables with values specific to the corresponding image block installed on the client computer. The repair module may take into account relative configuration deltas between a normalized reference image block and the installed application image block and may map corresponding object structures from the reference object structure to the installed object structure.
[022] According to alternative embodiments of the present invention, if an image block sent by the server was absolute, the client computer may identify which settings are general and which are installation-specific, and may modify them accordingly. [023] According to some embodiments of the present invention, the repair module may remove image blocks associate with application components and operating system components or structures which have been found to be redundant or conflicting by the
comparison module.
[024] According to some embodiments of the present invention, the remediation server may send to the client customized repair procedures which may be designed to perform complex repair operations on data content of components. According to some embodiments of the present invention, a customized repair procedure may be one or more of: changing a field in a configuration file to one a valid value, creating a nonexistent path specified, changing an unusable resource value specified (e.g. an IP port) to a usable one, repairing an inconsistent application data file, and/or any other action that requires application-specific knowledge.
BRIEF DESCRIPTION OF THE DRAWINGS
[025] The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:
[026] FIG. 1 is a block diagram illustrating the main components of an exemplary software remediation system in accordance with some embodiments of the present invention;
[027] FIG. 2A is a block diagram illustrating the functional building blocks of a software remediation server including an image comparison module in accordance with some embodiments of the present invention;
[028] FIG. 2B is a block diagram illustrating the functional building blocks of a software remediation server in accordance with some embodiments of the present invention;
[029] FIG. 3A is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention;
[030] FIG. 3B is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention;
[031] FIG. 4A is a block diagram illustrating the functional building blocks of a software remediation client system in accordance with some embodiments of the present invention;
[032] FIG. 4B is a block diagram illustrating the functional building blocks of a software remediation client system including an image comparison module in accordance with some embodiments of the present invention; [033] FIG. 5A is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client in accordance with some embodiments of the present invention; and
[034] FIG. 5B is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client in accordance with some embodiments of the present invention.
[035] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity.
Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.
DETAILED DESCRIPTION
[036] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the
present invention.
[037] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing", "computing", "calculating", "determining", or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices. [038] Embodiments of the present invention may include apparatuses for performing the operations herein. This apparatus may be specially constructed for the desired purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.
[039] The processes and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the desired method. The desired structure for a variety of these systems will appear from the description below. In addition, embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the inventions as described
herein.
[040] The present invention is a method and system for repairing or remediation of one or more software applications, including an operating system, running on a computer, by detecting anomalies in one or more components associated with the software application. According to some embodiments of the present invention, a faulty software component may be repaired or replaced by comparing its state to the state of a corresponding reference component and modifying, replacing, or removing the faulty component based on the results of the comparison. [041] According to some embodiments of the present invention, a software remediation system server may store sets of related software application image blocks in a software image repository. According to some embodiments of the present invention, the software image repository may be located on the remediation server. According to alternative embodiments of the present invention, the software image repository may be distributed across one more servers and/or end-users' computers functionally associated with the remediation server. According to other embodiments of the present invention, the repository may be located on one or more mass storage devices (e.g. removable HD, USB storage, etc.) functionally associated with the client. [042] According to some embodiments of the present invention, reference image blocks associated a given application may be generated by parsing the application's installation files. According to alternative embodiments of the present invention, a reference image block may be generated by monitoring an installation process of the given application. According to other embodiments of the present invention, an image block may be generated by collecting data from a number of client computers, and identifying the similarities and differences between them. Any method or technology for generating reference image blocks known today or to be devised in the future may be applicable to the present invention.
[043] According to some embodiments of the present invention, an application image block may be defined as: (1) a partial or full image of a file associated with the application, (2) an image of one or more files associated with the application, (3) registry keys and values associated with the application, and (4) entries in configuration files and/or any other data associated (i.e. operating system objects) with the application. It should be clear to one of ordinary skill in the art that an Image block of a given software application may be defined and/or composed of any data which constitutes or is otherwise associated with the software application. According to further embodiments of the present invention, an image block may be normalized, i.e. with installation- specific information (e.g. installation path, environment variables, user names, and other such settings) replaced with generic variables. According to further embodiments of the present invention, relative configuration between a normalized reference image block and the installed application image block may be taken into account and the corresponding object structures and may be mapped from the reference object structure to the installed object structure. According to alternative embodiments of the present invention, an image block may be stored as absolute data, containing a true replicate image of an installed component.
[044] According to some embodiments of the present invention, a remediation server and a client computer may communicate via a distributed data network (e.g. Internet). Image block characterization data relating to applications installed on the client may be exchanged between the client and the remediation server. According to some embodiments of the present invention, an application identification module on the client may identify installed applications or components associated with installed applications, and may transmit through a communication module the data associated with identified applications. The application identification module may transmit only a list of identified applications or, according to further embodiments of the present invention may derive image block characterization data for identified applications or application components and may transmit the characterization data to the remediation server. [045] According to some embodiments of the present invention, the remediation server may send to the client image block characterization data associated with applications installed on the client. The remediation server may send the image block characterization data in response to a list of applications or application components sent by the client, or it may send characterization data of all applications/components image blocks stored in the repository. According to embodiments of the present invention where the server sends characterization data of all application/component image blocks stored in the repository, the client may respond by sending back a list of image blocks required for software remediation/repair.
[046] According to some embodiments of the present invention, the remediation server may send to the client customized check procedures which may be designed to perform complex validation and/or consistency checks on data content of components. According to some embodiments of the present invention, a customized check procedure may be one or more of: checking that a field in a configuration file is within its valid range, checking that a specified path value really exists on the client, checking that a specified resource a value points to (e.g. an IP port) is really useable, checking that an application data file is consistent, and/or any other check that may require application-specific knowledge.
[047] According to some embodiments of the present invention, the characterization data may consist of: (1) checksum (such as MD5), (2) cryptographic signature, (3) file size and modification time, and/or any other file and data characterization parameter known today or to be devised in the future.
[048] According to some embodiments of the present invention, an image block comparison module, operating either on the client or on the remediation server, may compare characterization data of reference image blocks with characterization data of image blocks associated with applications installed on the client. The comparison module may designate or flag an image block of an application stored on the client as being anomalous if there is a mismatch between that image block's characterization data the characterization data of a corresponding reference image block. According to some embodiments of the present invention, the comparison module may compare a substantial portion of the data bits of the client image block its corresponding reference image block.
[049] It should be understood by one of ordinary skill in the art that the application comparison module may take into account normalization factors, as described above, during the process of comparing a normalized reference image block and an image block on the client. The comparison module may take into account relative configuration deltas between a normalized reference image block and the installed application image block, and may map corresponding object structures from the installed object structure to the reference object structure.
[050] It should be understood by one of ordinary skill in the art that comparison of reference image blocks and installed image block may be performed according to numerous methodologies and using various techniques. Any method, code or technology for comparing reference components or structures to installed components or structures, known today or to be devised in the future, may be applicable to the present invention.
[051] According to some embodiments of the present invention, upon determining which applications and/or related components have anomalous image blocks (i.e. need repair), the server may send the application image blocks to the client. The transmission of image blocks and needing repair/replacement/removal may be performed in response to a request from the client. According to some embodiments, a user of the client computer may respond to a report of detected anomalous image blocks, which response may be the basis of the image block request to the remediation server. The report may be based on the results of the comparison and customized checks performed by the comparison module, either running on the client or on the remediation server. The user may select which image blocks to repair/replace/removal, and thus an image block request to the server may be generated and transmitted. [052] According to some embodiments of the present invention, an application repair module running on the computer may use reference image blocks and customized repair procedures received from the remediation server to repair/replace/remove corresponding image blocks on the client, which corresponding image blocks have been designated as anomalous. According to further embodiments of the present invention, if a reference image block received from the remediation server is normalized, the application repair module on the client computer may replace the normalized image's generic variables with values specific to the corresponding image block installed on the client computer. The repair module may take into account relative configuration deltas between a normalized reference image block and the installed application image block and may map corresponding object structures from the reference object structure to the installed object structure.
[053] According to alternative embodiments of the present invention, if an image block sent by the server was absolute, the client computer may identify which settings are general and which are installation-specific, and may modify them accordingly. [054] According to some embodiments of the present invention, the repair module may remove image blocks associate with application components and operating system components or structures which have been found to be redundant or conflicting by the comparison module.
[055] According to some embodiments of the present invention, the remediation server may send to the client customized repair procedures which may be designed to perform complex repair operations on data content of components. According to some embodiments of the present invention, a customized repair procedure may be one or more of: changing a field in a configuration file to one a valid value, creating a nonexistent path specified, changing an unusable resource value specified (e.g. an IP port) to a usable one, repairing an inconsistent application data file, and/or any other action that requires application-specific knowledge.
[056] Reference is now made to FIG. 1 , which is a block diagram illustrating the main components of an exemplary software remediation system in accordance with some embodiments of the present invention. According to some embodiments of the present invention, a remote server 200 may be functionally associated with an application image repository 270, which is created and maintained by the image generator 300. A client computer 100 may connect over a network to a server, and exchange information related to the application components installed on it, and to the application image blocks stored in the repository 270.
[057] Reference is now made to FIG. 2A, which is a block diagram illustrating the functional building blocks of a software remediation server including an image comparison module in accordance with some embodiments of the present invention, and to FIG. 3A, which is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention. According to some embodiments of the present invention, a client computer 100 connects to the server 200 via the communication module 250, and sends it characterization data for components it has identified (step 3000). The server 200 may then construct a list of all the application image blocks associated with the components the client has identified (step 3100). The comparison module 260 may then compare the received characterization data with characterization data of components stored in the repository 270 and construct a list of suspected anomalies (step 3200). The server 200 may then send the client 100 a set of customized checks, which may be specific for some of the identified application blocks (step 3300). After receiving the customized check results (step 3400), the server may send the comprehensive results to the client (step 3500). The client computer 100 may then present the user with a list of anomalous components which can be repaired, and forward their choice to the server 200 (step 3600). Upon receiving the user's choice, the server 200 may send the full application image blocks and customized repair procedures to the client for it to restore (step 3700).
[058] Reference is now made to FIG. 2B, which is a block diagram illustrating the functional building blocks of a software remediation server in accordance with some embodiments of the present invention, and to FIG. 3B, which is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a remediation server in accordance with some embodiments of the present invention. According to some embodiments of the present invention, a remediation server 200 accepts a connection from a client computer 100 via the communication module 250, and sends it characterization data of all components/image blocks and customized checks stored in the repository 270 (step 3050). The client computer 100 then compares its application components/image blocks with the reference image blocks on the server 200, and sends to the server 200 a list of required image blocks (step 3150). The server 200 then sends the requested image blocks and customized repair procedures to the client 100 via the communication module 250 (step 3250).
[059] Reference is now made to FIG. 4A, which is a block diagram illustrating the functional building blocks of a software remediation client system in accordance with some embodiments of the present invention, and to FIG. 5A, which is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client computer in accordance with some embodiments of the present invention. According to some embodiments of the present invention, a client computer 100 connects to the server 200 and sends it a characterization data of components identified by the application identification module 140 (step 5000). The server 200 may then send a set of customized check procedures, which may be specific for some of the identified application blocks (step 5100). The client 200 may then perform the customized checks, and send the results to the server (step 5200). The server 200 may then combine the results of the customized checks and the characterization data comparisons it had performed, and send a comprehensive list of anomalies to the client 100, which may present it to the user as a report, containing the identified anomalies that can be repaired (step 5300). The client may then accept and forward the user's choice of which components/application blocks to repair to the server (step 5400). Upon receiving the user's choice, the server 200 may send the full application image blocks and customized repair procedures to the client (step 5500), where they are restored by the application repair module 150, after converting normalized data to absolute data (step 5600).
[060] Reference is now made to FIG. 4B, which is a block diagram illustrating the functional building blocks of a software remediation client system including an image comparison module in accordance with some embodiments of the present invention, and to FIG. 5B, which is a flowchart illustrating an exemplary method by which a software remediation server repairs a client computer from the viewpoint of a client computer in accordance with some embodiments of the present invention. According to some embodiments of the present invention, a client computer 100 connects to the server 200 and receives characterization data for all components/image blocks known to the server (step 5050). The application identification module 140 identifies components/image blocks related to installed application found on the local storage 170, and generates characterization data for them (step 5150). The image comparison module 150 may then compare the characterization data generated for the identified components/image blocks with the corresponding characterization data of the reference image blocks received from the remediation server 200 (step 5250). The comparison module 160 may then generate a comprehensive anomalies report based the comparison and present it to the user (step 5350). After the user has chosen which components/image blocks to repair/restore, the client 200 sends a list of requested image blocks to the server 200 (step 5450). The server 200 then sends the requested image blocks and customized repair procedures to the client (step 5550), where they are restored by the application repair module 150 (step 5650).
[061] While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to
those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.

Claims

CLAIMSWhat is claimed:
1. A software remediation system comprising: a data storage device storing one or more sets of related software application image blocks, wherein a set of image blocks is associated with a software application and is generated by parsing components of the software application; and a communication module adapted to exchange characterization data relating to image blocks with a client computer.
2. The system according to claim 1 , further comprising an image comparison module adapted to compare received image block characterization data relating to an installed application image block on the client computer with characterization data of a corresponding reference image block stored on the data storage device.
3. The system according to claim 2, wherein said comparison module is adapted to generate a list in response to a mismatch between received image block characterization data relating to an installed application image block on the client computer the characterization data of a corresponding reference image block.
4. The system according to claim 3, wherein said comparison module is adapted to generate a list which indicates which image blocks are mismatched and to transmit at least a portion of the list the client.
5. The system according to claim 1 , wherein said communication module is adapted to transmit a reference image block to the client in response to a signal indicating a corresponding image block on the client is in a corrupt state.
6. The system according to claim 1 , further comprising an image generator module adapted to parse an installed software application into one or more image blocks.
7. A method of remediating software on an computer comprising: storing on a data storage device one or more sets of related software application image blocks, wherein a set of image blocks is associated with a software application and is generated by parsing components of the software application; and exchanging with a client characterization data relating to image blocks.
8. The method according to claim 7, further comprising comparing received image block characterization data relating to an installed application image block on the client computer with characterization data of a corresponding reference image block stored on the data storage device.
9. The method according to claim 9, further comprising generating a list in response to a mismatch between received image block characterization data relating to an installed application image block on the client computer the characterization data of a corresponding reference image block.
10. The method according to claim 9, wherein the generated list indicates which image blocks are mismatched
11. The method according to claim 9, further comprising transmitting at least a portion of the list the client.
2. The method according to claim 7, further comprising transmitting a reference image block to the client in response to a signal indicating a corresponding image block on the client is in a corrupt state.
PCT/IL2007/000677 2006-06-05 2007-06-04 A system and method for software application remediation WO2007141780A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/303,375 US9104574B2 (en) 2006-06-05 2007-06-04 System and method for software application remediation

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US81070406P 2006-06-05 2006-06-05
US60/810,704 2006-06-05

Publications (2)

Publication Number Publication Date
WO2007141780A2 true WO2007141780A2 (en) 2007-12-13
WO2007141780A3 WO2007141780A3 (en) 2009-04-09

Family

ID=38801892

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL2007/000677 WO2007141780A2 (en) 2006-06-05 2007-06-04 A system and method for software application remediation

Country Status (2)

Country Link
US (1) US9104574B2 (en)
WO (1) WO2007141780A2 (en)

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8015450B1 (en) * 2009-03-26 2011-09-06 Symantec Corporation Systems and methods for detecting and automatically installing missing software components
KR20110080448A (en) * 2010-01-06 2011-07-13 삼성전자주식회사 Application developing system and method for developing the same
EP2400389B1 (en) * 2010-06-24 2016-05-25 Alcatel Lucent A method, a system, a server, a device, a computer program and a computer program product for transmitting data in a computer network
US9158605B2 (en) * 2010-12-01 2015-10-13 Microsoft Technology Licensing, Llc Method, system and device for validating repair files and repairing corrupt software
US20130111018A1 (en) * 2011-10-28 2013-05-02 International Business Machines Coporation Passive monitoring of virtual systems using agent-less, offline indexing
US20140372998A1 (en) * 2013-06-14 2014-12-18 Microsoft Corporation App package deployment
US9202167B1 (en) 2013-06-27 2015-12-01 Emc Corporation Automated defect identification and resolution
US9235802B1 (en) 2013-06-27 2016-01-12 Emc Corporation Automated defect and optimization discovery
US9313091B1 (en) * 2013-09-26 2016-04-12 Emc Corporation Analytics platform for automated diagnosis, remediation, and proactive supportability
US9471594B1 (en) * 2013-09-30 2016-10-18 Emc Corporation Defect remediation within a system
US9274874B1 (en) 2013-09-30 2016-03-01 Emc Corporation Automated defect diagnosis from machine diagnostic data
US10360044B2 (en) * 2016-09-13 2019-07-23 Nutanix, Inc. Massively parallel autonomous reimaging of nodes in a computing cluster
US11068333B2 (en) 2019-06-24 2021-07-20 Bank Of America Corporation Defect analysis and remediation tool

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6425125B1 (en) * 1999-03-30 2002-07-23 Microsoft Corporation System and method for upgrading client software
US6751795B1 (en) * 1998-12-24 2004-06-15 Nec Corporation System and method for software installation
US6789215B1 (en) * 2000-04-21 2004-09-07 Sprint Communications Company, L.P. System and method for remediating a computer
US7367027B1 (en) * 2002-08-22 2008-04-29 Hewlett-Packard Development Company, L.P. System for generating efficient and compact update packages

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7389442B1 (en) * 1997-12-26 2008-06-17 Samsung Electronics Co., Ltd. Apparatus and method for self diagnosis, repair, removal by reversion of computer problems from desktop and recovery from booting or loading of operating system errors by removable media
US6397381B1 (en) * 1998-09-21 2002-05-28 Microsoft Corporation System and method for repairing a damaged application program
US6718549B1 (en) * 1999-05-05 2004-04-06 Microsoft Corporation Methods for managing the distribution of client bits to client computers
KR100496056B1 (en) * 2000-02-26 2005-06-17 주식회사 하우리 Restoring service system and a method thereof for internet-based remote data and file
US20050010916A1 (en) * 2003-05-24 2005-01-13 Hagen David A. System for providing software application updates to multiple clients on a network
JP2007516495A (en) * 2003-08-11 2007-06-21 コーラス システムズ インコーポレイテッド System and method for the creation and use of adaptive reference models
US20050102669A1 (en) * 2003-10-15 2005-05-12 Siemens Medical Solutions Usa, Inc. Software installation file verification media and methods for medical equipment
US20050240815A1 (en) * 2004-04-13 2005-10-27 Sony Corporation Modular imaging of computer software for system install and restore
EP1899814B1 (en) * 2005-06-30 2017-05-03 Sling Media, Inc. Firmware update for consumer electronic device
US7546492B2 (en) * 2005-12-22 2009-06-09 Sony Corporation Remotely repairing files by hierarchical and segmented cyclic redundancy checks
US8127412B2 (en) * 2007-03-30 2012-03-06 Cisco Technology, Inc. Network context triggers for activating virtualized computer applications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6751795B1 (en) * 1998-12-24 2004-06-15 Nec Corporation System and method for software installation
US6425125B1 (en) * 1999-03-30 2002-07-23 Microsoft Corporation System and method for upgrading client software
US6789215B1 (en) * 2000-04-21 2004-09-07 Sprint Communications Company, L.P. System and method for remediating a computer
US7367027B1 (en) * 2002-08-22 2008-04-29 Hewlett-Packard Development Company, L.P. System for generating efficient and compact update packages

Also Published As

Publication number Publication date
WO2007141780A3 (en) 2009-04-09
US20100064285A1 (en) 2010-03-11
US9104574B2 (en) 2015-08-11

Similar Documents

Publication Publication Date Title
US9104574B2 (en) System and method for software application remediation
US7523340B2 (en) Support self-heal tool
US20070073907A1 (en) Device, method and computer program product readable medium for determining the identity of a component
CN101821727A (en) Management update is to create virtual machine duplicate
US10229023B2 (en) Recovery of storage device in a redundant array of independent disk (RAID) or RAID-like array
US20150169310A1 (en) Maintaining firmware
US10146628B2 (en) Software backup and restoration procedures using application and file monitoring
US20200293306A1 (en) Off-board flash memory
US9164857B2 (en) Scalable structured data store operations
KR20180046617A (en) Update management apparatus of industry control system, apparatus and method for update verification
WO2021139355A1 (en) Method and apparatus for starting ram os for data collection
JP5352027B2 (en) Computer system management method and management apparatus
US20090150882A1 (en) System and method for software application installation
WO2019169771A1 (en) Electronic device, access instruction information acquisition method and storage medium
CN109933351B (en) Method and device for repairing and upgrading Linux system
US8887145B2 (en) Storage device and configuration-information storing method
US20100094949A1 (en) Method of Backing Up Library Virtual Private Database Using a Web Browser
CN111209606A (en) Method, device and equipment for early warning of hard disk change behind RAID card
EP1645969B1 (en) Remote configuration management for data processing units
JP7279351B2 (en) Verification device, verification method, program
US20040064784A1 (en) Document management system, method and computer program
CN108959604B (en) Method, apparatus and computer readable storage medium for maintaining database cluster
US20160085649A1 (en) Disk drive repair
CN113656208B (en) Data processing method, device, equipment and storage medium of distributed storage system
US20230126244A1 (en) Method, electronic device, and computer program product for managing operating system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07736417

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 07736417

Country of ref document: EP

Kind code of ref document: A2

WWE Wipo information: entry into national phase

Ref document number: 12303375

Country of ref document: US