Method for recovery of original registry key file data

[0002] This application is related to a co-pending application entitled “System and Method for Replicating Monitored Registry Keys”, U.S. Ser. No. 09/573,063, filed May 17, 2000, and which is incorporated herein by reference.

[0003] This invention relates to the recovery of original registry key data after providing synchronization and duplication of registry information as between a local platform and its facilities and a remote platform and its facilities.

[0004] In database management, there is the concept of a “key” which is an identifier for a record or group of records in a data file, most often the key is defined as the contents of a single field called the “key field” in some database management programs and called “the index field” in others. In most database management systems, the keys (meaning the contents of a single key field or the composite key) are maintained in key tables which are specially indexed to speed record retrieval. In many database management systems, these key tables are called index files.

[0005] A key field is a field in a record structure or an attribute of a relational table that has been designated to be part of a key. A field can be keyed (or indexed) to improve or simplify the performance of retrieval and/or to update operations.

[0006] A key word is a characteristic word, phrase or code that is stored in a key field and used to conduct sorting or searching operations on records. This also applies to any of the dozens of words (also known as reserved words) that compose a given programming language or a set of operating system routines.

[0007] There is a factor called the “key word-in-context” which describes an automatic search methodology that creates indexes of document text or titles. Each key word is stored in the resulting index along with some surrounding text, usually the word or phrase that proceeds or follows the key word in the text or title.

[0008] In present day networks, there is a common configuration used in order to provide a local platform with facilities connected through a local area network over to a remote platform and remote facilities. The remote platform, and facilities are generally used as a backup system should the local platform and facilities fail. In such a case, then the operations are transferred to the remote platform and facilities in order that operations may be carried on. However, it is necessary that the remote platform and facilities be in synchronism or have data duplication of the local platform and facilities so that proper operations can occur without using invalid stale data or using data that is no longer correct.

[0009] In Windows Operating Systems there is a database designated as the Registry. This Registry database holds all varieties of information from system configurations to performance data to data about the applications available for use in the NT platform. This Registry is kept as a secured file on disk and a typical Registry is illustrated in FIG. 2. The Registry can also be held in memory in addition to the disk file. Each item in the Registry is designated as a Registry Key.

[0010] In the earlier practice, in these situations involving a local platform and a remote backup platform, it was necessary for the user or operator to specifically provide for manually backing-up the Registry keys so that the remote platform would be updated with the present information residing in the local platform. These backup situations often required that certain periods of time, say during the night, or other times, could be used to transfer the data from the local program to the backup program when the time was available. However, this took considerable periods of time and effort to accomplish and there was always certain periods wherein there was no synchronization or duplication between the remote platform and the local platform.

[0011] The present invention eliminates the need to manually backup Registry keys. By scripting the object, which is the Component Object Model (COM) involved, one can automate the whole process with minimum operator effort and time consumption so that the remote platform will always hold the most up-to-date information. Thus, any applications that keep their settings and other vital information in the local Registry of the local platform can easily make themselves suitable for a fail-over strategy without worrying how the registry data are replicated and maintained in the remote standby platform. The remote backup registry key data in the remote platform ensures the continuing protection of any registry key data lost on the source local platform.

[0012] Now, however, another problem situation often arises when the system operator wishes to recover various data items. For example, the operator may wish to recover the original registry key data the existed at the remote destination backup platform before that particular remote registry key data was changed during operation of the automatic update component between the local and remote platforms.

[0013] And again, further, the operator may wish to recover and reconstitute the original local registry key at the local platform after some local platform fault or shutdown. To do this, there is then required an operation to access the corresponding remote registry key and transport the key data back to the local platform for restoration.

[0014] The methods for accomplishing these restoration operations are taught herein with references to FIGS. 8 and 9.

[0015] The present invention introduces a Component Object Model (COM) component that monitors a user-specified Registry on the local computer platform by duplicating the Registry keys over to a remote machine platform and instantly updating it whenever the monitored local key (including its values and subkeys) is modified.

[0016] A mechanism and method is provided (exposed through a COM object) to backup a specific Registry key from a local computer to a remote computer in order to synchronize the data involved upon the occurrence of any changes.

[0017] Most Windows applications today make use of the Registry in various different ways, and it is possible to use the described COM object to provide backup so that the remote or destination platform will always store a duplicate copy of the local registry key and be available should any problem occur within the local source platform.

[0018] It is often the case that the system operator needs to restore the remote original registry key data to replace the updated changed remote registry key data This is accomplished by storing the “original” remote registry key data on a remote disk file which can later be retrieved. On the other after a failure in the local platform, the operator will want to access original registry key data from the remote platform and convey it to the local platform to restore a particular local registry key. A special program using a remote backup subkey allows this restoration to be accomplished.

[0019] FIG. 1 is an overall environmental drawing show the relationship between a local computer platform and a remote computer platform connected through a local area network.

[0020] FIG. 2 is a sketch of a window which illustrates the Registry editor and shows the various categories of data which are on the local machine platform;

[0021] FIG. 3 is a flowchart which illustrates a simple way to initiate a Registry monitoring object and the handling of its events;

[0022] FIG. 4 is a flowchart illustrating the method StartMonitor which initiates a registry-key monitoring process;

[0023] FIG. 5 is a flowchart illustrating the method RemConnect (called by StartMonitor) for interfacing to the remote platform;

[0024] FIG. 6 is a flowchart illustrating the method RegisterMonitoredKey which registers the specified registry key to the monitoring component;

[0025] FIG. 7 is a flowchart for the method StopMonitor which stops the registry monitoring operation.

[0026] FIG. 8 is a flowchart illustrating the method RestoreRemoteKey which allows the original data of the remote key to be restored;

[0027] FIG. 9 is a flowchart illustrating the method RestoreKeyFromBackup which allows the contents of monitored registry key on the local computer to be replaced with the data of its corresponding remote registry key.

[0028] MONITORING COMPONENT: This is a scriptable component that monitors a specified Registry key on a local computer by duplicating this key to a remote machine and instantly updating the remote machine whenever the monitored local key (including its values and subkeys) is modified.

[0029] LOCAL MACHINE/COMPUTER: This is the computer where this component is installed and where the components' objects are run.

[0030] REMOTE MACHINE/COMPUTER: This involves any other connecting computer where the component stores a copy of its monitored local Registry key.

[0031] MONITORED/SOURCE REGISTRY KEY: This is the local machine's Registry key that is being monitored by an object of the component.

[0032] DESTINATION/BACKUP REGISTRY KEY: This is a copy of the local machine's monitored Registry key for the remote computer.

[0033] KEY: This involves data that identifies a record. Account number, product code and customer name are typical key fields used to identify a record in a file or data base. As an identifier, each key value must be unique in each record. A key field is a field in a record structure or an attribute of a relational table that has been designated to be part of a key. A field can be keyed (or indexed) to improve or simplify the performance of retrieval and/or to update operations.

[0034] HKEY: An abbreviation for the term “hive key”. The word “hive” is used to denote each part of the Windows Registry.

[0035] REGISTRY KEY: In Windows NT platform, there is a central hierarchical database designated as Registry. It is used to store information necessary to configure the involved system and its applications. Each node in the registry is called key. A key can contain other sub-keys and values. There are six main parent keys in the registry: HKEY_PERFORMANCE_DATA, HKEY_CURRENT_CONFIG, HKEY_CURRENT_USER, HKEY_CLASSES_ROOT, HKEY_LOCAL_MACHINE, and HKEY_USERS. The component described in this invention only makes use of the last two keys.

[0036] LOCAL KEY: A key in the Registry of the local computer platform of the NT operating system.

[0037] REMOTE RACKUP KEY: A key in the Registry of the remote backup platform of an NT Operating System.

[0038] SUBKEY: Any registry key that is a child key of another key.

[0039] KEY NODE: Each key in the registry has a specific position within the registry's hierarchical order. Such a position is denoted as a key node.

[0040] MONITORED KEY: The registry key which is being monitored for any changes.

[0041] KEY CONFLICTS: A situation in which a monitoring object attempts to monitor a sub-key or a parent key or even the very same key of a key that is currently being monitored by another monitoring object.

[0042] CONNECTIONS SUBKEY: Registry keys used internally by the monitoring component to keep track of remote connections that it makes.

[0043] AUTOMATIC UPDATE (REMOTE BACKUP KEY): A process used by a registry-key-monitoring object to automatically update the remote backup key whenever the monitored local key is changed.

[0044] DATA OF MONITORED KEY: All sub-keys and values under the monitored registry key node in the registry.

[0045] SOURCE KEY: Same as MONITORED KEY

[0046] DESTINATION KEY: A corresponding key on a remote system for the monitored key on the local machine. The monitoring object ensures data between those two keys are synchronized.

[0047] OBJECT: A software program written in an object-oriented manner which exposes data and functions to operate on data.

[0048] COMPONENT OBJECT MODEL (COM): An open architecture for cross-platform developments of client/server applications and is based on, object-oriented technologies.

[0049] REGISTRY MONITORING COMPONENT: This is a component that monitors a user-specified registry on a local computer by duplicating the key to a remote machine and instantly updating it whenever the monitored local key (including its values and subkeys) is modified

[0050] SCRIPTING THE OBJECT: An object can be scripted when it has been designed and implemented in a way that allows scripting languages to access its methods and properties. Scripting the object consists of using the object to perform tasks on behalf of scripts.

[0051] SCRIPT: A program written in a special-purpose programming language such as used in a communications program or word processor. This correlates to the term called “MACRO”.

[0052] SCRIPTABLE COMPONENT: A COM component, such as the one described in this invention, that exposes objects and interfaces that can be utilized by scripting languages such as VB script and Java script. The “script” is a type of program that consists of a set of instructions to an application or utility program. A script usually consists of instructions expressed using the application's or utilities' rules and syntax, combined with simple control structures such as loops and “if/then” expressions.

[0053] MACRO: In applications, these involve a set of keystrokes and instructions recorded and saved under a short key name or macro name. When the key code is typed or the macro name is used, the program carries out the instructions of the macro. Program users create macros to save time by replacing often-used sometimes lengthy, series of strokes with shorter versions. Doing this eliminates frequent retyping, minimizes inadvertent typing errors, and enables users who are unfamiliar with a program to play back sets of instructions pre-recorded by someone more adept with the application. If the application also includes a macro language that responds to variables and conditional statements, the user can also control the outcome of a procedure by having the macro respond differently under different conditions. In programming languages, such as “C” or assembly language, the macro is a name that defines a set of instructions that are substituted for the macro name wherever the name appears in a program (a process called micro-expansion) when the program is compiled or assembled. Macro instructions can be placed either in the program itself or in a separate file that is identified in the program. Macros are similar to “functions” in that they can take arguments, and in that they are called to lengthier sets of instructions. Unlike “functions” macros are replaced by the actual instructions they represent when the program is prepared for execution. Function instructions are copied into a program only once.

[0054] FUNCTION: This is the purpose of or the action carried out by a program or routine. This is also a general term for a sub-routine. In some languages, this involves a sub-routine that returns a single value.

[0055] MONITORING A KEY: The process of observing a key to see if it changes.

[0056] MONITORING OBJECT: The object performing any monitoring.

[0057] ENUMERATION OBJECT: An object whose purpose is to provide an enumeration of a collection. When an object wishes to provide clients with a list of items, it often creates an enumeration object to maintain the list and supply each item in a specific order.

[0058] COMPONENT: In software terms, this usually means the same as Object.

[0059] REGISTRY MONITORING COMPONENT FEATURES: The component features the following:

[0060] (i) Synchronization of both source and destination keys' data.

[0061] (ii) Backup protection of the destination key.

[0062] (iii) Redirection of destination key: The name of the destination key can be different from the name of the source key.

[0063] (iv) Restoration of the overwritten destination key: When replicating the source key to the destination key and the latter already exists, the monitoring object will save the original destination key before overwriting it. This action allows the object to be able to restore the destination key with the saved original data when requested.

[0064] (v) Restoration of the monitored key: The monitored key can be restored with data of a corresponding remote key.

[0065] (vi) Enumeration object to enumerate all monitored Registry keys on the local machine.

[0066] NT IN DOMAIN: An NT domain is an identifiable group of network computers with at least one of the computers serving as a primary domain controller.

[0067] BACKUP PROTECTION: The notion that data is protected because it has been “backed-up” somewhere, so a copy is available in case the original is destroyed, corrupted or lost.

[0068] FAILOVER ENVIRONMENT: This is a configuration where a remote computer serves as a stand-by unit for the local computer machine in case the local machine fails.

[0069] ADMINISTRATOR GROUP: The security group to which users belong if they have Administrator privilege, the privilege to alter normally secure configurations on a computer.

[0070] SYSTEM PRE-DEFINED/RESERVED KEY: This is a class of keys which are designated as the HKEY_XXXXXXX in the Windows operating system.

[0071] DESTINATION/BACKUP REGISTRY KEY: This key provides a copy of the local machine's monitored Registry key on a remote computer.

[0072] CLIENT: This is a script or a program that requests service of the component.

[0073] HKEY CLASSES ROOT: The section of the Windows registry containing information about the classes (object repositories) on the computer.

[0074] HKEY CURRENT CONFIG: The section of the Windows registry containing information about the current configuration of the computer.

[0075] HKEY CURRENT USER: The section of the Windows registry containing information about the settings, configuration and options of the currently logged-in user.

[0076] HKEY LOCAL MACHINE: The section of the Windows registry containing information about the settings and options of the computer which are independent from those used by the currently logged-in user.

[0077] HKEY USERS: The section of the Windows registry containing information about each user that has been logged-in to the computer. When one of these users logs in, the part relevant to that user becomes equivalent to the HKEY_CURRENT_USER section.

[0078] HKEY PERFORMANCE DATA: The section of the Windows registry containing performance information about the computer.

[0079] MTA THREADING MODEL: A COM threading model that supports multi-threaded apartments (MTA). In COM, an apartment determines how an object's interfaces are passed and used by its clients.

[0080] MAIN THREAD: The primary thread of the registry monitoring component. Clients only interface with this thread through the component's supported methods and properties.

[0081] WORKER THREAD: A thread created by the main thread just for the sole purpose of monitoring the specified registry key. It relieves the main thread from the monitoring responsibility, allowing the main thread to focus only on client requests.

[0082] START MONITOR: A method supplied by the component to start the monitoring process on a specified local key.

[0083] STOP MONITOR: A method supplied by the component to stop the monitoring process on a specified local key.

[0084] REGISTRY MONITORING OBJECT: See REGISTRY MONITORING COMPONENT.

[0085] BACKUP DISK FILE: This is a disk file at the remote location which contains the original data of the destination key.

[0086] EVENT NOTIFICATION: This is where the component supports an event firing mechanism if an error occurs or the monitored key is changed during the monitoring process.

[0087] STANDBY SYSTEM: A backup computer for another computer in a fail-over environment. If the main computer fails, the standby system will take over.

[0088] VISUAL BASIC ITERATION: The Visual Basic (VB) computer language has syntax to iterate through a collection of items being managed by an object. This iteration (sometimes called enumeration) is often supplied by an enumeration object.

[0089] MONITORING PROCESS: The process on the computer which has instantiated a monitoring object.

[0090] RegistryKey: This is a property of the Component which sets or returns the local registry key to be monitored. The set value cannot be null and is required. However, only keys under HKEY_LOCAL_MACHINE and HKEY_USERS are allowed.

[0091] RemServer: This is a property of a Component which sets or returns the remote computer's name. A set value cannot be null and is required. It cannot be changed while the monitoring is in progress.

[0092] RemUsername: This is a property of the Component which sets or returns the remote logon user name. The component only uses this information to connect the remote machine after it cannot establish the connection using the default user name associated with the running process.

[0093] RemPassword: This is a Component property which sets the remote logon password. The component only uses this information to connect to the remote machine after it cannot establish the connection using the default password associated with the running process.

[0094] RemLogonDialog: This is a property of the Component which sets or returns the remote logon dialog indicator. If the indicator is “true”, the client will receive a logon dialog at the connection time.

[0095] RemBackupSubkey: This is a property of the Component which sets or returns the remote backup Registry key name. If the set value is null, a backup key identical to the monitored key will be created; otherwise a copy of the monitored key will be created under the specified backup key name. Since the component requires the RemBackupSubkey value to point to the same system pre-defined key node as dictated by the Registry key property, the string for the predefined key can be omitted.

[0096] MonitorAllowed: This is a property of the Component which returns a value indicating whether the key-specified via the Registry key property can be monitored. A key is allowed to be monitored if it is not: (i) currently being monitored; (ii) a parent key of any key currently being monitored; (iii) a child key (subkey) of any key currently being monitored.

[0097] RestoreRemoteKey: This is a method which restores the overwritten remote Registry key from the back-up disk file created by the start monitor. The monitoring process must be stopped before calling this method.

[0098] RestoreKeyFromBackup: This is a method which restores the monitored key indicated by the Registry key property with the data of the remote backup key indicated by the REMBACKUPSUBKEY property. The monitoring process must be stopped before calling this method for execution.

[0099] OnMonitorError: This is an event handling method which will get called when any error occurs during the monitoring process. The method is passed with an error object where the error object is the pointer to the monitor error object which has two properties which are (i) ERR—which returns the WIN 32 error code, and (ii) the DESCRIPTION—which returns a string describing the error.

[0100] OnRegistryChange: This is an event handling method which will get called when there are changes affecting the monitored key.

[0101] FIG. 1 is an illustrative diagram showing the various elements involved in a local and remote platform. A local computer. 10 utilizing the NT operating system is connected to a disk storage unit 14 having a Registry file 16. The local computer 10 has a local memory 12 and the local computer 10 is connected to a local area network (LAN 18). The local area network provides for transmission of data and information between the local platform 10 and the remote platform 20, which is also an NT operating system. The remote platform 20 has a remote memory 22 and is also connected to a remote disk unit 24 which has a Registry file 26.

[0102] The object of the monitoring component is to ensure that any monitored Registry key in the Registry file 16 on the disk unit 14 of the local platform 10 will be duplicated and synchronized at the disk unit 24 of the remote platform 20, such that the corresponding destination key in Registry file 26 will always be updated as a current duplicate of that in the registry file 16.

[0103] FIG. 2 is an illustrative example of a window of the Registry Editor application on the local computer platform. The Registry Editor is seen to show the window of the pre-defined key HKEY_LOCAL_MACHINE. Here, under the pre-defined key, there are other sub-keys such as HARDWARE, SAM (Security Account Manager), SECURITY and then SOFTWARE.

[0104] The SOFTWARE category is seen to have other sub-keys which are indicated as Adobe, Classes, Clients, Compaq, etc. Thus, the list of items shown under the headline “SOFTWARE” indicates a set of Registry keys which can be used, accessed and occasionally modified or changed. However, when any changes occur in these registry keys, it is important that the backup system be updated as soon as possible, preferably immediately, in order that the backup system will be synchronized in order to provide a duplicate of the current information in the local systems Registry.

[0105] FIG. 3 is flowchart which is used for initiating a registry monitoring object and the subsequent handling of its events.

[0106] A. Create a Registry monitor object.

[0107] B. Set the remote server name (RemServer) where the duplicated destination key will be stored by assigning that name to the property Remserver of the monitor object.

[0108] C. Set the local Registry key to be monitored by assigning the key name to the property RegistryKey of the monitor object.

[0109] D. Initiate the monitoring process by invoking the method StartMonitor of the monitor object (as seen in FIG. 4).

[0110] E. Wait until the user indicates he wants to stop the monitoring process.

[0111] F. Stop the monitoring process by invoking the method StopMonitor of the monitor object (as seen in FIG. 7).

[0112] G. Release the registry monitor object.

[0113] FIG. 3 is a flow chart illustrating the initiation of a registry monitoring object and the handling of subsequent events.

[0114] At step A, there is first the creation of a registry monitor object. From a C++ program, this is achieved by calling the Win32 API CoCreateInstance passing the object's class identifier. From a VB script, it is as simple as calling CreateObject passing the name of the object's component. For example, a VB script to create a registry monitoring object would look something like this:

[0115] Dim RegMonObj

[0116] Set RegMonObj=WScript.CreateObject(“Unisys.RegistryMonitor”)

[0117] The next step B involves setting up the remote server name where the duplicated destination key will be stored. This is done by assigning the remote server name to the property designated RemServer of the monitor object created in step A. Continuing with the example above, the script could contain code like this:

[0118] RegMonObj.RemServer=“RemoteComputerName”

[0119] At step C, the operator then sets the local registry key which is to be monitored by assigning the key name to the property RegistryKey of the monitor object. For example:

[0120] RegMonObj.RegistryKey=“HKLM\Software\Unisys\esProcessMgr”

[0121] At step D, the monitoring process is initiated by calling up the method designated as StartMonitor of the monitor object. For example:

[0122] RegMonObj.StartMonitor

[0123] At step E there is a decision block which asks the query as to whether the user wants to stop monitoring? If the answer is no, the sequence returns back and loops back upon itself. If the answer is yes, then at step F the user stops the monitoring process by invoking the method StopMonitor of the monitor object. A simple VB script could just display a button that a user could click to stop the monitoring process. For example:

[0124] MsgBox “Click OK to stop the registry monitoring object”

[0125] RegMonObj.StopMonitor

[0126] The registry monitoring component supports the following properties and methods:

[0127] RemServer: sets/returns the name of the remote computer where a copy of the monitored key will be stored.

[0128] RegistryKey: sets/returns the name of the registry key to be monitored on the local computer.

[0129] RemUsername: sets/returns the usercode that is valid on the remote computer.

[0130] RemPassword: sets the password associated with RemUsername.

[0131] MonitorAllowed: returns TRUE if the key specified by RegistryKey can be monitored; otherwise returns FALSE.

[0132] RemLogonDialog:; sets/returns a value that indicates whether the component will display a logon dialog box.

[0133] RemBackupSubkey: sets/returns a corresponding backup key on the remote computer for the monitored key specified by the property RegistryKey. When the monitoring process starts, the data of RegistryKey will be duplicated over to RemBackupSubkey. If the key specified by RemBackupSubkey already exists, its original data will be saved to disk before being overwritten with the data of RegistryKey. This makes it possible to restore RemBackupSubkey with its original data when needed by calling the method RestoreRemoteKey. If RemBackupSubkey is not specified, RemBackupSubkey will have the same name as RegistryKey.

[0134] StartMonitor: called to start the component's monitoring process.

[0135] StopMonitor: called to stop the component's monitoring process.

[0136] RestoreRemoteKey: called to restore the backup key specified by the property RemBackupSubkey with its original data. The monitoring process should have already been stopped before invoking this method.

[0137] RestoreKeyFromBackup: called to restore the data of the registry key RegistryKey with the contents of the remote key RemBackupSubkey. The monitoring process should have already been stopped before invoking this method.

[0138] This step is shown at step D of FIG. 3 and is expanded here in FIG. 4.

[0139] STM1. Check if the monitoring is already in progress. If so, exit with error. If “No”, then go to STM2.

[0140] STM2. Check if the registry key specified by the property RegistryKey is valid. If not, exit with error. If “Yes”, go to STM3 (which is described in FIG. 5).

[0141] STM3. Call the internal method RemConnect (see “Description of the Method RemConnect” in FIG. 5) to make a connection to the remote server specified by the property RemServer. If RemConnect fails, exit with error.

[0142] STM4. Call the internal method RegisterMonitoredKey (see FIG. 6) to register the monitored key on the local machine. If RegisterMonitoredKey fails, exit with error. If Monitored key is registered O.K. (YES), then go to STM5.

[0143] STM5. Open the remote backup registry key specified by the property: RemBackupSubkey on the remote computer RemServer. If key does not exist, create it. If key already exists, save its original data to a registry disk file.

[0144] STM6. Call the internal method RegisterMonitoredKey (see FIG. 6) to register the monitored key on the remote machine. If RegisterMonitoredKey failed, exit with error. If registered O.K. (YES), then go to STM7.

[0145] STM7. Open the monitored key RegistryKey on the local computer.

[0146] STM8. Spin off a worker thread to start registry key monitoring process.

[0147] STM9. Copy the contents of the monitored key RegistryKey to the remote key RemBackupSubkey.

[0148] STM10. Exit the method.

[0149] The sole purpose of the monitor worker thread (at STMB) is to update the backup registry key RemBackupSubkey on the remote computer RemServer when there are any changes to the monitored key RegistryKey. This is accomplished so as to:

[0150] W1. Wait for either one of the two events to happen: Registry key change on the monitored key RegistryKey, or a shutdown notification from its parent (main) thread.

[0151] W2. If a registry change event occurs, copy the contents of the local monitored key RegistryKey to its backup key RemBackupSubkey on the remote computer RemServer. Once done, go back to waiting mode.

[0152] W3. If a shutdown event occurs, exit the thread.

[0153] Step (a) is a query to make (b) or to break (c) a connection:

[0154] I. If RemConnect is called to make a connection (step b):

[0155] I1. Check if the local computer already has a connection with the remote computer RemServer. If “YES”, exit the method at step e.

[0156] I2. If not already having a connection (NO), then make a connection using the current identity of the running process at step b1. If successful, register the connection (step d) to a volatile registry key and exit the method (e).

[0157] I3. Check (step b2) if the property RemLogonDialog is set. If, “YES”, at step b2ybring up a dialog box to get usercode and password from user. Attempt another connection with this usercode/password combination. If successful, at step b4, register the connection at step d to a volatile registry key and exit the method. If failed, exit with error at step b5.

[0158] I4. If step b2 is “NO”, then make another attempt to connect to the remote machine RemServer with the specified properties RemUsername and RemPassword. If successful, (YES) register the connection at step d to a volatile registry key and exit the method at (e). If failed, exit with error at b5.

[0159] II. If RemConnect (at step (a) of FIG. 5) is called to break a connection:

[0160] Check at step (c) if there is still the connection. If “YES”, stop any monitoring process this object currently has and close the remote key RemBackupsubkey, as shown at step (c1).

[0161] Un-register the connection from a volatile registry key, at step (c2) and then exit at step (e).

[0162] The method RegisterMonitoredKey is passed with the parameter bRemote to indicate whether the registration is done on the local computer or on the remote computer. Its main responsibility is to ensure that the monitored key is not already being monitored by another object running on either the local machine or remote machine. This method includes the following steps:

[0163] STM4(i) Check if the monitored key RegistryKey is already registered. If YES, it means that another object already monitors the key. Exit the method with error at (ier).

[0164] STM4(ii) Check if any sub-key of the monitored key RegistryKey is currently being monitored by another object. If YES, exit with error at (ier).

[0165] STM4(iii) Check if any parent key of the monitored key Registry Key is currently being monitored by another object. If YES, exit with error at (ier). If NO, go to step STM(iv).

[0166] STM4(iv) Register the monitored key RegistryKey by storing its name into a known volatile registry location.

[0167] STM(v) Exit with a successful code.

[0168] The StopMonitor sequence (of step F of FIG. 3) involves the following steps:

[0169] F1. Un-register the monitored key RegistryKey from the local computer by removing its entry from the known volatile registry location described in step STM4(iv) of FIG. 6.

[0170] F2. Un-register the monitored key RegistryKey from the remote computer by removing its entry from the known volatile registry location described in step STM4(iv) of FIG. 6.

[0171] F3. If the monitoring process is currently in progress, (YES) send a shutdown notification to the monitor worker thread (as described in FIG. 4, step STM8).

[0172] F4. Wait for the worker thread to exit.

[0173] F5. Exit the method.

[0174] RECOVERY OF OVERWRITTEN REMOTE KEYS: Any time a monitoring object is about to overwrite an existing remote key, it will create a backup Registry file for that key under the remote machine's system directory before copying the data of the monitored key from the local machine to the remote machine.

[0175] For example, suppose the remote machine's system directory is C:\WINNT\System32 and the monitored key on the local computer is HKLM\Software\Unisys\esProcess. Also suppose that the remote computer already contains a key called HKLM\Software\Unisys\esProcess in its Registry. Before overwriting the key HKLM\SOFTWARE\UNISYS\esProcess on the remote system with data of the same key from the local machine, the monitoring object will create the following disk file to contain the original data of the involved remote key:

[0176] C:\WINNT\System32\UnisysRegMon\HKLM\Software\Unisys\esProcess_<Date>_<Time>

[0177] PROGRAMMATIC RECOVERY: As long as the monitoring object, which creates the backup disk file for the remote destination key, still exists, restoring the original data of the remote destination key is as simple as calling its method RestoreRemoteKey, shown in FIG. 8.

[0178] When it is not possible to restore the original data of the remote destination key (e.g., the monitoring object is no longer around), a manual recovery can be achieved using the system-provided utility called RegEdt32.exe.

[0179] For restoration of the remote key, the following process is involved:

[0180] Run Regedt32.exe on the remote machine

[0181] Select the involved key node (or create it if it doesn't exist and then select it).

[0182] Using the example above, the key node HKLM\SOFTWARE\UNISYS\esProcess should be selected.

[0183] Choose “restore” from the Registry menu.

[0184] Browse and select the appropriate backup Registry file.

[0185] Then click on “open”.

[0186] The warning “Registry editor will restore a key on top of the currently selected key. All value entries and subkeys of this key will be deleted. Do you want to continue the operation? - - - (This appears on the screen).

[0187] Click “OK” to go ahead with the operation. The remote key should now be restored.

[0188] The method for restoration of the original data to a remote key is seen in FIG. 8 and done as follows:

[0189] RS1. Check; if the object had previously created a registry file containing the original data of the backup key RemBackupSubkey on the remote machine RemServer. If (NO), exit with error at Rse. If YES, go to RS2.

[0190] RS2. Check if the monitoring process is currently in progress. If YES, exit with error. If NO, go to RS3.

[0191] RS3. Call a Win32 API to load the saved registry file into the key RemBackupSubkey.

[0192] RS4. Exit the method.

[0193] Suppose a user wanted to monitor a registry key called “HKLM\Software\Unisys\esProcess” on the local computer A and had already specified a remote computer called computer B. By default, when the monitor object starts, it will create an identical key with the same name “HKLM\Software\Unisys\esProcess” on computer B. If computer B happens to already have an existing key called “HKLM\Software\Unisys\esProcess”, the data of this key will be written to a disk file, say, for the sake of discussion, file “SAVEDKEY”, before being overwritten by computer A's “HKLM\Software\Unisys\esProcess” key.

[0194] The method RestoreRemoteKey of FIG. 8 basically describes the process of loading the data in file “SAVEDKEY” back into the key “HKLM\Software\Unisys\esProcess” of computer B, thus, restoring the original data of the said key on B.

[0195] On the other hand, the method RestoreKeyFromBackup of FIG. 9 describes the operation of copying the current data of the key “HKLM\Software\unisys\esProcess” on computer B back onto the key “HKLM\Software\Unisys\esProcess” of computer A.

[0196] Sometimes users may not want the monitoring object to trample over the existing key “HKLM\Software\Unisys\esProcess” on computer B. In that case, they can re-direct the destination (i.e., remote key) to another name by using the property RemBackupSubkey of the monitoring object. Assume that they have specified RemBackupSubkey to “HKLM\Software\MyOwnKey”, when the monitoring object starts, it will create the key “HKLM\Software\MyOwnKey\HKLM\Software\Unisys\esProcess” on computer B by concatenating the values of the properties RemBackupSubkey and RegistryKey. In this particular instance, if computer B has the key called “HKLM\Software\Unisys\esProcess”, it will remain untouched.

[0197] If the method RestoreKeyFromBackup is invoked, the data of the key “HKLM\Software\MyOwnKey\HKLM\Software\Unisys\esProcess” (instead of “HKLM\Software\Unisys\esProcess”) on computer B will get copied onto the key “HKLM\Software\Unisys\esProcess” of computer A.

[0198] The following steps are involved for restoring a local key from Backup files of the remote key:

[0199] RB1. Check if the monitoring process is currently in progress. If NO, exit with error at RBe. If YES, proceed to RB2.

[0200] RB2. Check if the monitored key RegistryKey is valid. If not, exit with error at RBe. If YES, go to RB3.

[0201] RB3. Call the internal method RemConnect (see FIG. 5) to make a connection to the remote server specified by the property RemServer. If RemConnect fails, exit with error at RBe. If the connection succeeds (YES) then proceed to RB4.

[0202] RB4. Ensure the property RemBackupSubkey is valid, (YES) to ensure that it still stores the pre-updated remote key file information.

[0203] RB5. Open the remote registry key RemBackupsubkey on the remote computer RemServer, and proceed to RB6.

[0204] RB6. Delete the monitored local key RegistryKey with all of its sub-keys and values.

[0205] RB7. Recreate the monitored local key RegistryKey with the data of the remote key RemBackupSubkey.

[0206] RB8. Exit the method.

[0207] Described herein has been a system enabling the automatic duplication of registry key data by a remote platform from a local source platform and additionally the provision for restoration of the original registry key data of the remote platform. Additionally, when failure occurs in a local platform and the local registry keys must be restored, then the described method can recover the registry key data from the remote platform for replacement of original registry data back to the local platform.

[0208] It is understood that various types of other embodiments may accomplish similar results to the methodology described herein but which still utilize the concept of the invention described in the attached claims.