Replacing a unique identifier in a cloned computer system using program module that runs only once during the next boot sequence

• US 6,535,977 B1
• Filed: 09/30/1999
• Issued: 03/18/2003
• Est. Priority Date: 09/30/1999
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Holle, Matthew H., Miller, Edward S.
• Primary Examiner(s): Lee, Thomas
• Assistant Examiner(s): WANG, ALBERT C
• Application Number:
  US09/410,197
• Time in Patent Office: 1,265 Days
• Field of Search: 717/173, 717/178, 717/168, 713/2, 713/1
• US Class Current: 713/2
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method for generating a unique identifier for a computer system is disclosed. A master computer system is prepared for duplication and configured to execute a startup program on the next boot-up sequence. The master computer system is then shut down and duplicated. On the first boot-up of the copy or “clone” computer system, a new unique identifier is created and used to replace all instances of the old unique identifier that was associated with the master computer system. Finally, a setup wizard component is executed to finish configuring the clone computer system in accordance with the customer'"'"'s personal information making the system ready for commercial use.

Claims

1. A computer-readable medium having computer-executable instructions for replacing an old unique identifier with a new unique identifier, which, when executed, comprise:

(a) preparing a computer system to execute a program module only during the next initialization of the computer system'"'"'s operating system; and

(b) in response to the execution of the program module;

(i) reading the old unique identifier;

(ii) generating a new unique identifier; and

(iii) replacing all occurrences of the old unique identifier with the new unique identifier.

2. The computer-readable medium of claim 1, wherein preparing a computer system to execute a program module further comprises:

configuring the computer system;

writing an instruction in a storage location that executes during the initialization of the computer system'"'"'s operating system; and

shutting down the computer system.

3. The computer-readable medium of claim 2, wherein writing the instruction is performed by a preparation program.

4. The computer-readable medium of claim 1, wherein the program module includes an ID changer.

5. The computer-readable medium of claim 4, wherein the program module further includes a mini-setup routine.

6. The computer-readable medium of claim 5, wherein the mini-setup routine is a subset of the functions of a setup routine generally used in setting up a computer system.

7. The computer-readable medium of claim 1, wherein the program module includes a mini-setup routine.

8. The computer-readable medium of claim 7, wherein the mini-setup routine is a subset of the functions of a setup routine generally used in setting up a computer system.

9. The computer-readable medium of claim 1, wherein reading the old unique identifier includes:

accessing a system registry that stores the old unique identifier; and

retrieving from the system registry the old unique identifier.

10. The computer-readable medium of claim 1, wherein each unique identifier is a 96-bit pseudo-random security identification code.

11. The computer-readable medium of claim 10, wherein the new unique identifier is generated using the same algorithm used to generate the old unique identifier.

12. The computer-readable medium of claim 1, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for all instances of the old unique identifier; and

replacing each instance of the old unique identifier with the new unique identifier.

13. The computer-readable medium of claim 12, wherein the instances of the old unique identifier are stored in a system registry.

14. The computer-readable medium of claim 13, wherein the old unique identifier is stored as part of a registry key value.

15. The computer-readable medium of claim 13, wherein the old unique identifier is stored in a registry key.

16. The computer-readable medium of claim 1, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for a computer file stored on the computer system and that reflects the old unique identifier; and

modifying the computer file to reflect the new unique identifier.

17. The computer-readable medium of claim 16, wherein the computer file that reflects the old unique identifier includes a permission based on the old unique identifier.

18. The computer-readable medium of claim 17, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for the permission based on the old unique identifier; and

modifying the permission to reflect the new unique identifier.

19. The computer-readable medium of claim 16, wherein the computer file that reflects the old unique identifier includes a setting based on the old unique identifier.

20. The computer-readable medium of claim 19, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for settings which reflect the old unique identifier; and

modifying those settings to reflect the new unique identifier.

21. The computer-readable medium of claim 1, wherein the program module is configured to interface directly with an application programming interface native to the computer system'"'"'s operating system.

22. A method for preparing a master computer system for duplication, comprising:

(a) setting an entry associated with an operating system of the master computer system to launch a program module only during the next initialization of the operating system, the program module having computer-executable instructions, which, when executed, comprise;

(i) reading an old unique identifier associated with the master computer system;

(ii) generating a new unique identifier;

(iii) replacing all occurrences of the old unique identifier with the new unique identifier; and

(iv) if a computer file accessible by the program module exists that reflect the old unique identifier, modifying the computer file to reflect the new unique identifier; and

(b) duplicating the operating system of the master computer system for installation in a second computer system.

23. The method of claim 22, wherein the entry associated with the operating system is a system registry key within a system registry associated with the operating system.

24. The method of claim 22, wherein the program module includes an ID changer.

25. The method of claim 24, wherein the program module also includes a mini-setup routine.

26. The method of claim 25, wherein the mini-setup routine comprises computer-executable instructions, which, when executed, perform a subset of functions associated with a general setup routine for setting up the master computer system.

27. The method of claim 22, wherein the startup program comprises a mini-setup routine comprising computer-executable instructions, which, when executed, perform a subset of functions associated with a general setup routine for setting up the master computer system.

28. The method of claim 22, wherein reading the old unique identifier includes:

accessing a system registry key that stores the old unique identifier; and

retrieving from the system registry key the old identifier.

29. The method of claim 22, wherein each unique identifier is a 96-bit pseudo-random security identification code.

30. The method of claim 22, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for all instances of the old unique identifier in a system registry; and

replacing each instance of the old unique identifier with the new unique identifier.

31. The method of claim 30, wherein the old unique identifier is stored as part of a registry key value.

32. The method of claim 30, wherein the old unique identifier is stored in a registry key.

33. The method of claim 22, wherein the computer files that reflect the old unique identifier include a permission that reflects the old unique identifier.

34. The method of claim 33, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for permissions which reflect the old unique identifier; and

modifying those permissions to reflect the new unique identifier.

35. The method of claim 22, wherein the computer files that reflect the old unique identifier includes a security having the old unique identifier embedded.

36. The method of claim 35, wherein replacing all occurrences of the old unique identifier with the new unique identifier includes:

searching for securities which reflect the old unique identifier; and

modifying those securities to reflect the new unique identifier.