Compaq dc7100 HP Compaq Business Desktop PCs - Developing a Common Windows XP - Page 3

Advantages of a common image, Limitations of a common image, Choosing a base image - hard drive removal

Page 3 highlights

Reference Machine-The reference machine is defined as the system that is being used to perform work to pool drivers, customize software and set OS options and parameters. This will be the machine from which the image is captured. Sysprep (System preparation tool)-This is a Microsoft tool that prepares the operating system for imaging. This tool must be run before imaging a system and then deploying that image. Sysprep.exe can be found on your operating system CD obtained either from HP or Microsoft. Sysprep, as well as other useful documentation and tools, is contained in the named deploy.cab, located in the support\tools directory. Advantages of a common image Creating a common image has several advantages. • Image reduction - By creating a product family-based common image, image management becomes easier because the number of images that require management is reduced. • Image validation - By using the image preinstalled by HP, you will start with an image that has already undergone extensive testing and validation with the hardware on which it will be deployed. This will save considerable testing resources in your environment. In addition, using the HP image as a base will bypass the Microsoft Windows Activation process that requires each user to activate their copy of Windows (activation is required in Windows XP). • Operating System-controlled driver installation - By implementing the .inf file-based driver installation method outlined in this white paper, it is assured that hardware will be installed in the most optimal manner. Limitations of a common image While the use of a common image can be extremely advantageous, it is not without caveats. Creating a common image causes a shift in the support liability from the PC OEM back to the organization creating the common image. It is very important to be aware of the operating system license as well as licensed applications that are part of the common image. Royalty-based applications typically have strict guidelines surrounding deployment and usage. For example, devices such as DVD drives have strict distribution restrictions regarding how DVD software is distributed. Please contact your Microsoft licensing representative for the proper operating system license. Choosing a base image As mentioned previously, it is recommended by HP to begin with the factory preinstalled image as a base for the common image. If the file system type or the partition structure is not desirable, HP recommends that you still use the factory preinstalled image to build the common image. File system and partitioning can be customized during the image load phase of the deployment process. If the factory preinstalled image has already been removed from the hard drive, you may restore that image using the Restore Plus! CD recovery media using the associated Restore Plus! documentation included with the computer. Finally, you may choose to forgo both of these options in favor of a clean installation directly from operating system media. You should reference Microsoft Corporate Deployment documentation in order to build the base image, and then continue with the next section of this document to build a common image. 3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15

3
Reference Machine
—The
reference machine
is defined as the system that is being used to perform work to
pool drivers, customize software and set OS options and parameters. This will be the machine from which the
image is captured.
Sysprep
(System preparation tool)—This is a Microsoft tool that prepares the operating system for imaging.
This
tool must be run before imaging a system and then deploying that image. Sysprep.exe can be found on your
operating system CD obtained either from HP or Microsoft.
Sysprep, as well as other useful documentation and
tools, is contained in the named
deploy.cab
, located in the
support\tools
directory.
Advantages of a common image
Creating a common image has several advantages.
Image reduction – By creating a product family-based common image, image management becomes easier
because the
number
of images that require management is reduced.
Image validation – By using the image preinstalled by HP, you will start with an image that has already
undergone extensive testing and validation with the hardware on which it will be deployed. This will save
considerable testing resources in your environment. In addition, using the HP image as a base will bypass
the Microsoft Windows Activation process that requires each user to activate their copy of Windows
(activation is required in Windows XP).
Operating System-controlled driver installation – By implementing the .inf file-based driver installation
method outlined in this white paper, it is assured that hardware will be installed in the most optimal
manner.
Limitations of a common image
While the use of a common image can be extremely advantageous, it is not without caveats.
Creating a common image causes a shift in the support liability from the PC OEM back to the organization creating
the common image.
It is very important to be aware of the operating system license as well as licensed applications that are part of the
common image.
Royalty-based applications typically have strict guidelines surrounding deployment and usage. For
example, devices such as DVD drives have strict distribution restrictions regarding how DVD software is distributed.
Please contact your Microsoft licensing representative for the proper operating system license.
Choosing a base image
As mentioned previously, it is recommended by HP to begin with the factory preinstalled image as a base for the
common image.
If the file system type or the partition structure is not desirable, HP recommends that you still use
the factory preinstalled image to build the common image. File system and partitioning can be customized during
the image load phase of the deployment process.
If the factory preinstalled image has already been removed from the hard drive, you may restore that image using
the
Restore Plus!
CD recovery media using the associated
Restore Plus!
documentation included with the computer.
Finally, you may choose to forgo both of these options in favor of a clean installation directly from operating system
media.
You should reference Microsoft Corporate Deployment documentation in order to build the base image,
and then continue with the next section of this document to build a common image.