IT administrator initiated remote hardware independent imaging technology

Abstract
The present invention relates to a method for removing the driver map component from being stored on the service partition and placing it on a server for retrieval at a later time. Only the actual device drivers that are required for that system will be provided. A central repository will be provided for applications and device drivers that would leverage the AMT area. The AMT IDE-R would be used to store the hook to network install, for example an IT administrator initiated network install to an unpowered system. Two situations exist in which this method will be used. The first situation involves supplying ImageUltra content to a system that is connected to the Local Area Network while ImageUltra is running. The second situation involves supplying ImageUltra content to a system that is not connected to the Local Area Network while ImageUltra is running.
Description
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

As mentioned above, the present invention relates to a method for removing the driver map component from being stored on the service partition and instead placing it on a server for retrieval at a later time. Only the actual device drivers that are required for that system will be provided resulting in reduced hard drive waste. A central repository will be provided for applications and device drivers that would leverage the AMT area. The AMT IDE-R would be used to store the hook to network install, for example an IT administrator initiated network install to an unpowered system. There are two main situations in which this method can be used (though of course a variety of other situations are conceivable). The first situation involves supplying ImageUltra content to a system that is connected to the Local Area Network while ImageUltra is running. The second situation involves supplying ImageUltra content to a system that is not connected to the Local Area Network while ImageUltra is running.


The first situation can be manifested by adhering to the following steps. First, a request is sent to the AMT on the client system requesting the PCI inventory data to find out what hardware is installed on the system. The server-based ImageUltra process runs its “PNP” rules to generate an ISO image containing only the device drivers applicable to the system. This is done without having to power up the target system. The ISO image is made available on the network. Another request is sent to the AMT on the client system to request an IDE-R mount of the ISO image. Next, a request is sent to AMT to boot ImageUltra. Power is preferably applied to the system to accomplish booting. When the system boots, it will load the ImageUltra software, and assign a drive letter to the RHIIT. After this, normal ImageUltra activities will take over. When these ImageUltra activities are finished, the RHIIT area can be saved on the server for future reuse.


More specifically, AMT (Intel Active Management Technology) contains 24 k of flash ROM space for applications to store data. When the system is plugged in but powered off, the network space is still active, and maintains a network address, such as an IP address. The system is able to communicate with AMT, with the ability to perform many functions such as the ability to retrieve data, get the system serial number, write data to the storage area, and so forth. AMT also provides a set of boot protocols. The IDE-R (Intel's Remote Integrated Driver Electronics) protocol is utilized during the boot. The BIOS connects to remote network share and enables an emulation of the share as an IDE hard drive. These abilities allow the system to perform a method in accordance with the present invention without needing to power up. IDE-R allows gigabytes of space to be available immediately to boot the system up remotely.


The list of drivers is obtained by a specification called Plug n Play. When the power cord is plugged in, the AMT card polls the system to obtain the inventory data and stores the data on the AMT storage space described above. Every device on the PCI bus has a four part ID. When the AMT queries the PCI, it obtains this list of four part IDs that represents the devices on the system. Through the network cable, a request is initiated to obtain that data. The information is sent through the network to the server, allowing the server to have an inventory of that specific system. The server compares the PCI IDs it has just obtained with the drivers that it stores. From the list of stored drivers it maintains, the server selects those drivers specific to the machine and constructs an ISO image that contains only the drivers and applicable system information for that system. Thus, the server creates a custom boot image for that specific system.


Next, that share/ISO image is made available. The AMT on the client is told on its next boot to do an IDE-R connection and give it the name of the share, the server location, and other necessary information. The wait command is sent and then the system is powered up. At this stage, the system boots, sees that it is booting to IDE-R, connects to the network share, mounts the ISO image, and boots that image. The system then begins to do the ImageUltra activities. It takes the data it has, images the hard drive, copies the specific drivers targeted to that system, and puts those on the HIIT area on the server.


The second situation involves providing an arrangement to supply ImageUltra content to a system that may not be connected to the LAN while ImageUltra is running. In this situation, the AMT is enhanced to have more storage, for example 10 MB or 1 Gig. This process again starts with sending a request to on the client system to request the PCI inventory data. The server based ImageUltra process runs its “PNP” rules to generate an ISO image containing only the device drivers applicable to the system. This is also done without powering the target system. The ISO image is made available on the network and then a request is sent to the AMT on the client system to store the ISO image. Power is then preferably applied to the system to accomplish booting. When the user starts ImageUltra, the ImageUltra software will query the cached data for the drivers and the Operating System components that are automatically installed from AMT. Then, normal ImageUltra activities will take over. Once ImageUltra has completed, it could retrieve all the data from AMT and store on either the hard drive or delete the information. Much of this process is similar to that detailed above with regard to the first situation.


In recapitulation, the present invention broadly relates, in accordance with at least one preferred embodiment, to a method for removing the driver map component from being stored on the service partition and instead placing it on a server for retrieval at a later time. Only the actual device drivers that are required for that system will be provided resulting in reduced hard drive waste. A central repository will be provided for applications and device drivers that would leverage the AMT area. The AMT IDE-R would be used to store the hook to network install, for example an IT administrator initiated network install to an unpowered system. There are two main situations in which this method will be used. The first situation involves supplying ImageUltra content to a system that is connected to the Local Area Network while ImageUltra is running. The second situation involves supplying ImageUltra content to a system that is not connected to the Local Area Network while ImageUltra is running.


The present invention, in accordance with at least one preferred embodiment, can be run on a base system. This system needs only a minimum of two (2) cables to be plugged in: the power cable and the network cable. The system should not be powered on, and does not necessarily have to have an Operating System. The power off state of the system also necessitates that the processor is not running and memory is not accessible. Thus, the present invention, in accordance with at least one preferred embodiment, is more advantageous than traditional network boot systems which require the computer to be fully powered throughout the entire process.


The present invention, in accordance with at least one preferred embodiment, can be thought of as a pre-pre Operating System boot system that runs before the Operating System or a Plug n Play loading or storing of drivers. When shipped from the manufacturer, systems that use the instant invention to load an Operating System do not even necessarily need to have a hard drive installed. A customer would be able to install any hard drive they prefer, run the instant invention, and have a functional computer. To a certain extent, the present invention, in accordance with at least one preferred embodiment, can also be thought of as an alternative way to deliver an Operating System or repair an Operating System.


It is to be understood that the present invention, in accordance with at least one presently preferred embodiment, includes elements which may be implemented on at least one general-purpose computer running suitable software programs. These may also be implemented on at least one Integrated Circuit or part of at least one Integrated Circuit. Thus, it is to be understood that the invention may be implemented in hardware, software, or a combination of both.


If not otherwise stated herein, it is to be assumed that all patents, patent applications, patent publications and other publications mentioned and cited herein are hereby fully incorporated by reference herein as if set forth in their entirety herein.


Although illustrative embodiments of the present invention have been described herein, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be affected therein by one skilled in the art without departing from the scope or spirit of the invention.

Claims
  • 1. An apparatus comprising: an arrangement for accepting a master image at an end-user system;an arrangement for facilitating customization of the master image to an end-user system; andan arrangement for storing a driver map elsewhere than a service partition, the driver map relating to drivers usable by said arrangement for accepting a master image.
  • 2. The apparatus according to claim 1, wherein said storing arrangement comprises a table-based index of drivers usable by said arrangement for accepting a master image.
  • 3. The apparatus according to claim 1, wherein said storing arrangement acts to store the driver map at a server for later retrieval.
  • 4. The apparatus according to claim 1, wherein said arrangement for facilitating customization acts to permit selection of context-specific parameters.
  • 5. The apparatus according to claim 4, wherein said context-specific parameters include at least one of: language and operating system.
  • 6. The apparatus according to claim 1, wherein said storing arrangement acts to store a driver map which relates solely to device drivers pertinent to a given end-user system.
  • 7. The apparatus according to claim 1, wherein said accepting arrangement acts to employ active management technology at an end-user system in accepting a master image.
  • 8. The apparatus according to claim 7, wherein said accepting arrangement acts to variably employ active management technology based on whether an end-user system is connected to or disconnected from a local area network.
  • 9. The apparatus according to claim 1, wherein said arrangement for facilitating customization acts to facilitate the creation of an image with multiple applications for different contexts associated with an end-user system.
  • 10. A method comprising the steps of: accepting a master image at an end-user system;facilitating customization of the master image to an end-user system; andstoring a driver map elsewhere than a service partition, the driver map relating to drivers usable by said step for accepting a master image.
  • 11. The method according to claim 10, wherein said storing step comprises providing a table-based index of drivers usable in said step of accepting a master image.
  • 12. The method according to claim 10, wherein said storing step comprises storing the driver map at a server for later retrieval.
  • 13. The method according to claim 10, wherein said step of facilitating customization comprises permitting selection of context-specific parameters.
  • 14. The method according to claim 13, wherein the context-specific parameters include at least one of: language and operating system.
  • 15. The method according to claim 10, wherein said storing step comprises storing a driver map which relates solely to device drivers pertinent to a given end-user system.
  • 16. The method according to claim 10, wherein said accepting step comprises employing active management technology at an end-user system in accepting a master image.
  • 17. The method according to claim 16, wherein said employing step comprises variably employing active management technology based on whether an end-user system is connected to or disconnected from a local area network.
  • 18. The method according to claim 10, wherein said step of facilitating customization comprises facilitating the creation of an image with multiple applications for different contexts associated with an end-user system.
  • 19. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for facilitating the provision of an image at an end-user system, said method comprising the steps of: accepting a master image at an end-user system;facilitating customization of the master image to an end-user system; andstoring a driver map elsewhere than a service partition, the driver map relating to drivers usable by said step for accepting a master image.