Correcting for changed client machine hardware using a server-based operating system

• US 6,209,089 B1
• Filed: 08/12/1998
• Issued: 03/27/2001
• Est. Priority Date: 08/12/1998
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Selitrennikoff, Sean, Lenzmeier, Charles T., Barr, Adam D.
• Primary Examiner(s): Beausoleil, Robert
• Assistant Examiner(s): ZIEMER, RITA A
• Application Number:
  US09/133,312
• Time in Patent Office: 958 Days
• Field of Search: 713/2, 713/1, 714/6, 714/35, 380/4
• US Class Current: 713/2
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]

Abstract

Methods and systems for adjusting an operating system configuration according to changes in hardware components of a client computer. The adjusted operating system can boot on the client computer regardless of changes in the hardware configuration of the client computer since it was last connected to a network server. Before the operating system boots, a preliminary connection is established between the client computer and the server. During the preliminary connection, the system identifies hardware components that are new and that must be supported by the operating system for bootup to occur. In particular, the server sends information relating to the previous client hardware configuration to the client computer. The client computer compares its current hardware configuration to the previous hardware configuration information, thereby identifying its new hardware components. Information identifying the new hardware components is sent to the server. The server locates operating system components or device drivers that support the new hardware components and stores them in a specified repository at the server. The operating system, which is now reconfigured to support the current client hardware components, is downloaded to the client computer and boots thereon.

Claims

1. In a system including a client computer, a server computer, and a network infrastructure, in which the server computer provides operating system components to the client computer via the network infrastructure, a method of using the server computer for adjusting the operating system components in a client computer hardware configuration in response to replacement or other change of a hardware component and booting the operating system components on the client computer, the method comprising the following steps:

establishing a connection between the client computer and the server computer over the network infrastructure before booting the operating system components on the client computer, and transmitting from the server computer to the client computer the number of times the client computer has booted its operating system while connected to the server;

transmitting information identifying the replacement hardware component from the client computer to the server computer;

modifying the operating system components in response to the transmitted information before booting the operating system components;

transmitting the operating system components from the server computer to the client computer; and

booting the operating system components on the client computer.

2. A method as defined in claim 1, wherein the replacement hardware component is such that the operating system components could not boot on the second client computer in the absence of the step of modifying the operating system components.

3. A method as defined in claim 1, further comprising, before the step of transmitting information identifying the replacement hardware component, the step of sending from the server computer to the client computer previous hardware information identifying the previous hardware component.

4. A method as defined in claim 3, further comprising the step of determining that the replacement hardware component has replaced the previous hardware component by comparing the previous hardware information to replacement hardware information identifying the replacement hardware component.

5. A method as defined in claim 1, wherein the step of transmitting the number of times the client computer has booted the operating system components while being connected to the server computer is comprised of transmitting a server-side boot serial number from the server computer to the client computer, the server-side boot serial number representing the number of times the client computer has booted the operating system components while being connected to the server computer.

6. A method as defined in claim 5, further comprising the steps of:

comparing the server-side boot serial number to a client-side boot serial number, wherein the server-side boot serial number is greater than the client-side boot serial number if the client computer last booted without access to a hard disk at the client computer; and

if the server-side boot serial number is greater than the client-side boot serial number, then disabling a local cache stored on the hard disk before the step of booting the operating system components.

7. A method as defined in claim 1, further comprising the step of transmitting a previous hard disk serial number from the server computer to the client computer the previous hard disk serial number identifying a previous hard disk included in the client computer when the client computer was last connected to the server computer.

8. A method as defined in claim 7, further comprising the steps of:

comparing the previous hard disk serial number to a current hard disk serial number identifying a current hard disk included in the client computer; and

if the previous hard disk serial number is different from the current hard disk serial number, then disabling a local cache stored on the current hard disk before the step of booting the operating system components.

9. A method as defined in claim 1, wherein the step of transmitting information identifying the replacement hardware component comprises the step of transmitting data identifying a replacement motherboard included in the client computer.

10. A method as defined in claim 9, further comprising, before the step of transmitting data identifying the replacement motherboard, the step of comparing the data identifying the replacement motherboard with previous motherboard information identifying a previous motherboard included in the client computer when the client computer was last connected to the server computer, the previous motherboard information having been sent from the server computer to the client computer.

11. A method as defined in claim 1, wherein the step of transmitting information identifying the replacement hardware component comprises the step of transmitting data identifying a replacement network interface card included in the client computer.

12. A method as defined in claim 11, further comprising, before the step of transmitting data identifying the replacement network interface card, the step of comparing the data identifying the replacement network interface card with previous network interface card information identifying a previous network interface card included in the client computer when the client computer was last connected to the server computer, the previous network interface card information having been sent from the server computer to the client computer.

13. In a networked system including a server computer and a network infrastructure over which the server computer can download operating system components to client computers, a method of using the server computer for adjusting the operating system components in response to a change in the hardware configuration that results from a replacement of a first client computer with a second client computer and booting the operating system components on the second client computer, the first client computer having a first hardware component and the second client computer having a corresponding second hardware component that is of a different type than the first hardware component, the method comprising the following steps:

establishing a connection over the network infrastructure between the second client computer and the server computer prior to booting the operating system components on the second client computer, and transmitting a server-side boot serial number from the server computer to the second client computer, the server-side boot serial number representing the number of times the first client computer has booted the operating system components while being connected to the server computer;

determining, by the second client computer, that the second hardware component is of a different type than the first hardware component;

transmitting information identifying the second hardware component from the second client computer to the server computer;

modifying the operating system components in response to the transmitted information before booting the operating system components, the modified operating system components being compatible with the second hardware component;

transmitting the operating system components from the server computer to the second client computer; and

booting the operating system components on the second client computer.

14. A method as defined in claim 13, wherein the second hardware component is such that the operating system components could not boot on the second client computer in the absence of the step of modifying the operating system components.

15. A method as defined in claim 13, wherein the step of modifying the operating system components comprises the steps of:

identifying, by the server computer, software that supports the second hardware component; and

installing the software in an operating system directory located at the server computer and associated with the second client computer.

16. A method as defined in claim 13, further comprising the step of maintaining a local cache at the second client computer, including a copy of the operating system components provided by the server computer.

17. A method as defined in claim 13, further comprising, after the step of booting the operating system components, the step of further modifying the operating system components to support changed hardware components of the second client computer other than the second hardware component.

18. In a system including a client computer, a server computer, and a network infrastructure, in which the server computer provides operating system components to the client computer via the network infrastructure, a method for limiting access to a hard disk on the client computer before the operating system components are booted on the client computer, the method comprising the following steps:

establishing a connection between the client computer and the server computer over the network infrastructure before booting the operating system components on the client computer, the server computer having a repository wherein client information associated with the client computer is stored, the client information including operating system components compatible with the client computer;

transmitting from the server computer to the client computer a server-side boot serial number from the server computer to the client computer, the server-side boot serial number representing the number of times the client computer has booted the operating system components while being connected to the server computer;

recognizing that a hard disk at the client computer does not have a complete copy of the client information;

disabling the hard disk;

downloading the operating system components over the network infrastructure from the server computer to the client computer; and

booting the operating system components on the client computer without the assistance of the hard disk.

19. A method as defined in claim 18, wherein the step of recognizing that the hard disk does not have a complete copy of the client information comprises the step of comparing a hard disk serial number associated with the hard disk to a previous hard disk serial number associated with a previous hard disk included in the client computer when the client computer was last connected to the server computer.

20. A method as defined in claim 18, wherein the step of recognizing that the hard disk does not have a complete copy of the client information comprises the step of recognizing that the client computer has not previously been connected to the server.

21. A method as defined in claim 18, wherein the step of recognizing that the hard disk does not have a complete copy of the client information comprises the step of comparing a server-side boot serial number to a client-side boot serial number, wherein the server-side boot serial number represents the number of times the client computer has booted the operating system components while being connected to the server computer, and wherein the client-side boot serial number is less than the server-side boot serial number if the client computer last booted without access to the hard disk.

22. A method as defined in claim 18, further comprising, after the step of booting the operating system, the steps of:

enabling the hard disk; and

storing a complete copy of the client information on the hard disk.

23. In a system including a client computer, a server computer, and a network infrastructure, in which the server computer provides operating system components to the client computer via the network infrastructure, a method for adjusting the operating system components in response to a change in a client computer hardware configuration and booting the operating system components on the client computer, the method comprising the following steps:

establishing a connection between the client computer and the server computer prior to booting the operating system components on the client computer;

transmitting from the server computer to the client computer the number of times the client computer has booted its operating system while connected to the server;

transferring information between the client computer and the server computer via the connection, wherein the information identifies either current hardware components of the client computer or previous hardware components of the client;

comparing the information identifying the current hardware components with the information identifying the previous hardware components so as to identify any of the current hardware components that have changed since the client computer was last connected to the server computer;

if any of the current hardware components has changed, and if at least one changed hardware component requires a modification of the operating system components before the operating system components can be booted on the client computer, then placing, by the server computer, software components that support the modification in an operating system directory accessible to the client computer; and

booting the operating system components, including any software components, on the client computer.

24. In a server computer interconnected with a client computer via a network infrastructure, a computer program product for implementing a method for adjusting operating system components in response to a change in a client computer hardware configuration and providing the operating system components to the client computer, the computer program product comprising:

a computer-readable medium for carrying computer-executable instructions, wherein said computer-executable instructions comprise;

code means for establishing a connection between the client computer and the server computer, the connection being established prior to booting the operating system components on the client computer;

code means for transmitting from the server computer to the client computer the number of times the client computer has booted its operating system while connected to the server;

code means for transmitting to the client previous hardware information identifying a previous hardware component of the client computer;

code means for receiving from the client computer, prior to booting the operating system components on the client computer, notification that a replacement hardware component of the client computer has replaced the previous hardware component;

code means for modifying operating system components stored in the server computer so as to be compatible with the replacement hardware component; and

code means for initiating transmission of the modified operating system components to the client computer over the network infrastructure so that the modified operating system components can be booted on the client computer.

25. A computer program product as defined in claim 24, wherein the computer-readable medium further carries computer-readable data comprising the previous hardware information.

26. A computer program product as defined in claim 24, wherein the code means for modifying operating system components comprise code means for identifying software that supports the replacement hardware component.

27. A computer program product as defined in claim 26, wherein the code means for modifying operating system components further comprise code means for installing the software in an operating system directory on the computer-readable medium and associated with the client computer.

28. A computer program product as defined in claim 24, wherein the computer-executable instructions further comprise code means for initiating transmission of information stored in a client directory on the computer-readable medium to the client computer, such that a copy of the information can also be stored at the client computer.