Electrical computers and digital processing systems: support – Digital data processing system initialization or configuration – Loading initialization program
Reexamination Certificate
1999-09-30
2003-03-18
Lee, Thomas (Department: 2182)
Electrical computers and digital processing systems: support
Digital data processing system initialization or configuration
Loading initialization program
C717S168000
Reexamination Certificate
active
06535977
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates generally to the duplication of a computer system, and more particularly, to duplicating a computer system where each duplicate has a unique identifier.
BACKGROUND OF THE INVENTION
In the computer industry, security is becoming more and more of an important issue. Uniquely identifying individual computer systems in a network provides a strategic advantage when addressing the issue of security. Many corporate entities select their computer platform based principally on the security features provided. Windows NT is one example of a computer operating system having superior security features. At the heart of most security features is a Security IDentification code (SID) embedded within the operating system. In the Windows NT operating system, the SID is generated when the operating system is first installed. The SID uniquely identifies the computer system on which the operating system is installed and allows network accessibility to be securely administered for that computer system. Other operating systems may make use of a similar unique identifier for a similar purpose.
One disadvantage of employing a unique identifier for each computer system is that it creates a problem for manufacturers of computer systems. To compete most effectively, manufacturers must be able to mass produce the computer systems that they sell. Manufacturers are at a serious disadvantage if they must individually install an operating system on each computer system they sell. Manufacturers prefer to configure a master computer system, including an installed operating system, and then duplicate or “clone” the master computer system. Most often, the hard disk drive of the master computer system is duplicated and those duplicates are installed in other computer systems which are then sold. In this way, manufacturers can produce a large number of computer systems without having to individually install the operating system on every one. However, as noted above, unique identifiers are typically generated when the operating system is installed. If the hard disk drive from the master computer system is duplicated, the unique identifier generated when the master computer system was configured is also duplicated. In the past, this situation has made it difficult for computer system manufacturers to generate many similarly configured computer systems without having to individually install the operating system on each computer system.
Other attempts to address that problem have not provided an ideal solution. For example. one attempted solution is to deliver the computer systems with the operating system uninstalled. However, installing an operating system on a new computer is a very complex task, and most consumers dislike having to perform complex installation procedures. Moreover, the manufacturer loses some control over the installed state of the operating system if the installation is performed by the consumer rather than the manufacturer. For those reasons, this solution is undesirable.
Accordingly, a need exists for a mechanism that allows a master computer system, having a unique identifier embedded within the master computer system, to be duplicated or cloned and which provides for the generation of new unique identifiers on each clone or duplicated computer system.
SUMMARY OF THE INVENTION
The present invention addresses the above identified needs by providing a mechanism that enables a master computer system having a unique identifier to be more easily duplicated. The mechanism first prepares the master computer system for duplication. Embedded on the master computer system is a unique identifier created when the operating system was installed. Preparing the master computer system for duplication involves configuring the master computer system to execute a startup program on the next boot-up sequence. The startup program is resident on the master computer system, and may have two components, as discussed below. The master computer system is then shut down.
The master computer system may now be duplicated. For example, the hard disk drive of the master computer system may be removed and installed in a machine designed to create many identical copies of the hard disk drive. Those identical copies are then installed in other computer systems similar to the master computer system. In this manner, many computer systems may be easily created that mirror the configuration of the master computer system. For this discussion, those computer systems are termed “clones” of the master computer system.
Each of the clones may then be sold and delivered to a customer. Because the clones include copies of the master computer hard disk drive, each of the clones is also configured to execute the startup program during the first boot-up sequence. Consequently, the first time a clone computer system is powered up by the consumer, the startup program is executed.
In accordance with one aspect of the invention, the startup program includes an ID changer component. When the clone computer system is first powered up, the ID changer component executes first and very early in the boot-up sequence. The ID changer component searches a registration database contained within the operating system for the unique identifier created when the operating system was installed. It should be apparent that when the operating system was initially installed on the master computer system a unique identifier was created and stored. When the master computer system was cloned, each of the clones included the same unique identifier. Accordingly, the ID changer reads the unique identifier that already exists on the clone computer system. The ID changer also creates a new unique identifier, and then replaces the old unique identifier with the new unique identifier.
In accordance with another aspect of the invention, replacing the old unique identifier includes locating all instances of the old unique identifier stored in the registration database and replacing them with the new unique identifier.
In accordance with yet another aspect of the invention, replacing the old unique identifier also includes identifying any computer files stored on the hard disk drive that have information related to the old unique identifier, such as access permissions, and modifying that information in accordance with the new unique identifier.
In accordance with yet still other aspects of the invention, the startup program includes a setup wizard component that is executed to finish configuring the clone computer system in accordance with the customer's personal information. A wizard is an interactive utility that guides a user through a potentially complex task, typically through a series of question and answer dialog boxes. The setup wizard may be the same setup routine used to install the operating system in the first instance, but, by using a particular switch, only performs a limited subset of the installation functions, such as prompting the user for personal login information, company information, and the like.
After the setup wizard is finished, setup of the clone computer system is complete. The clone computer system reflects its own unique identifier, and the customer was spared the burden of having to perform a complete installation of the operating system.
REFERENCES:
patent: 5758165 (1998-05-01), Shuff
patent: 5828834 (1998-10-01), Choi
patent: 6108697 (2000-08-01), Raymond et al.
Mark Russinovich and Bryce Cogswell, “NTSID 1.1”, Dec. 9, 1997.*
Mark Russinovich and Bryce Cogswell, “NewSID”, May 27, 1999.*
Sean Daly, “10 Steps to Prepare to NT 5.0 Now”, Windows & .NET Magazine, Feb. 1998.*
“Free Newsletter—Networking Professionals, Consultants etc”, Newsgroup: comp.os.ms-windows.nt.admin.misc, Apr. 3, 1998.*
Microsoft Knowledge Base Article Q137367, “Definition of the RunOnce Keys in the Registry”, Reviewed Nov. 21, 1996.*
Microsoft Knowledge Base Article Q158477, “How to Run a Program Only Once After Unattended Setup of NT 4.0”, Reviewed May 22, 1997.
Holle Matthew H.
Miller Edward S.
Christensen O'Connor Johnson & Kindness PLLC
Lee Thomas
Microsoft Corporation
Wang Albert
LandOfFree
Replacing a unique identifier in a cloned computer system... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Replacing a unique identifier in a cloned computer system..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Replacing a unique identifier in a cloned computer system... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3054477