HP Compaq 8100 Elite PC Family, the HP Z200 Workstation Family

Developing a common software image between the HP Compaq 8100 Elite PC Family, the HP Z200 Workstation Family, and the HP Z400 Workstation

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Definition of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Things you need before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Common image creation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Step 1: Choose a base image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Step 2: Collect required drivers for the Z400 Workstation . . . . . . . . . . . . . . . . . . . . . . . 4 Step 3: Create a drivers directory on the Reference Machine . . . . . . . . . . . . . . . . . . . . 5 Step 4: Setting up the drivers on the Reference Machine . . . . . . . . . . . . . . . . . . . . . . . . 5 Step 5: Customizing the Base Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Extend the process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Support for non-bundled hardware devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Step 6: Obtaining sysprep .exe and setting up the C:\Sysprep . . . . . . . . . . . . . . . . . . . . . . . 7Step 7: Creating and customizing sysprep .inf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Optional customization of the sysprep .inf settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Step 8: Create Batch Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Step 9: Create and customize cmdlines .txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Step 10: Run sysprep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Step 11: Capture the common image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 General Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Specific topics for the Z200, Z200 SFF, Z400, and 8100 Elite: . . . . . . . . . . . . . . . . . . 11

Thank You . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Appendix A: Reference sysprep .inf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Appendix B: Reference oobeinfo .ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Appendix C: Additional HP Support URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Appendix D: Driver SoftPaq Matrix for Microsoft Windows XP Professional (32-bit) . . . . . . . . 14Appendix E: [GuiRunOnce] Creative X-Fi Audio, HP Wireless NIC, and Intel AMT installation batch files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Appendix F: Creating an F6 Mass Storage Drivers Floppy Disk . . . . . . . . . . . . . . . . . . . . . 15Appendix G: Capturing and deploying the common image . . . . . . . . . . . . . . . . . . . . . . . . 16Appendix H: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Workstations

Windows® . Life without Walls™ . HP recommends Windows 7 .

HP’s family of personal workstationsWorkstations have a variety of characteristics that can give an organization a competitive advantage, increase business productivity, and allow users to work with confidence and peace of mind . HP offers a full range of workstations (including workstation blades, not discussed here) that are exclusively designed and engineered to give customers an edge up on their competitors . HP personal workstations feature:

System reliability—Features such as error checking and correcting (ECC) memory and more sophisticated cooling mechanisms help ensure expandability while maintaining high reliability .

ISV application certification—ISV certification means application and workstation combinations have been thoroughly tested together, giving predictable and reliable results from one application run to the next .

Superior return on investment—Features that increase ROI include a large number of I/O slots, toolless chassis design, and the additional performance possibilities from dual- and quad-core processors1 .

Professional graphics—Workstations are designed to support the most powerful graphics cards, a requirement for high-end applications where multiple 2D or 3D monitors are required .

Choosing the right workstationGiven the wide range of price and performance covered by the HP family of personal workstations, choosing the right workstation can be a challenge .

The enclosed tables help a prospective buyer determine the optimal workstation solution . The table on the following page has the following columns:

“Application segment”—A general description of the kind of application into which the workstation will be deployed . It is generally sorted by decreasing need of performance and other features, and contains a brief description of the market .

“You generally need . . .”—A generalization of the top two or three most important requirements for this market segment (in priority order) . This list assumes that a purchaser has to make some priority decisions based on budget .

“Choose the right workstation”—A visual indication of the first choice of workstation model to choose .

“ . . .Choose your add-ons”—Answers the question “If I have a small amount (5-10% of the purchase price) of budget left, how is it best spent?” These items are in priority order, and generally describe the most effective add-ons to purchase given the primary workstation model and application segment .

IntroductionPurposeThe goal of this document is to guide the IT professional through the process of creating a Microsoft® Windows® XP Professional 32-bit common image that can be deployed across the HP Compaq 8100 Elite Convertible Minitower PC, HP Compaq 8100 Elite Small Form Factor PC, HP Z200 Workstation, HP Z200 Small Form Factor Workstation, and HP Z400 Workstation .

Before you beginBefore starting this process, note the following:

• While the use of a common image can be extremely advantageous, it causes a shift in the support liability from HP back to the organization creating the common image . It is the responsibility of the organization to qualify the image before deployment .

• It is very important to be aware of the Microsoft Windows operating system licensing requirements . Contact your Microsoft licensing representative for the proper licensing requirements .

• It is very important to be aware of the licensed applications that are part of the common image . Royalty-based applications typically have strict guidelines surrounding deployment and usage .


2

Some examples of royalty-based applications are: Microsoft Office, HP ProtectTools, Roxio Easy Media Creator, InterVideo WinDVD, and antiVirus software . Contact your applications providers for the proper application royalties and licensing requirements and restrictions .

• It is assumed that your IT organization has done the necessary research and planning for the creation and deployment of a common image . This document serves as a guideline to facilitate the creation of a common image .

• This document provides a proven step-by-step process for creating a common image, but other approaches exist .

• This document does not include comprehensive instructions for image capture, deployment, or management . Due to the number and complexity of infrastructures available, it is the customer’s responsibility to decide, research, and implement these steps in the imaging process .

• The Web URLs listed in this document are for additional reference . URLs are subject to change or termination . HP makes no attempt to assure that these URLs are current .

• By providing this document, HP is not liable to provide any additional consulting services . Contact your HP Sales Representative or Channel Partner to arrange for additional HP Consulting Services .

• This document is not meant to be comprehensive in supporting all the possible configurations of the HP Compaq 8100 Elite Desktop PC, the HP Z200 Workstation Family, or the HP Z400 Workstation, but provides sufficient information to enable key hardware devices .

Definition of termsThis document uses the following terms .

Product familyDefined as a set of form-factor types within a numerically-defined series . For example, the HP Z200 product family consists of the HP Z200 Workstation and the HP Z200 Small Form Factor (SFF) Workstation .

Common imageFor the purposes of this paper, a “Microsoft Windows XP 32-bit Common Image” is defined as an operating system image that works across multiple hardware platforms, such as the HP Compaq 8100 Elite PC Family, the HP Z200 Workstation Family, and the HP Z400 Workstation, as outlined in this document . For details on extending your image beyond a product family, see the section entitled, “Extend the process… .”

Reference machineDefined as the system that is being used to create the common image . This machine contains the hard drive image that will eventually be captured as the common image .

NOTE: This document uses the HP Z400 Workstation as a reference machine for image development .

Target machineThe system to which the common image will be deployed .

NOTE: For this document, the target machine refers to an HP Z200 Workstation . The common image, however, can also be deployed to an HP Compaq 8100 Elite convertible minitower (CMT) or small form factor (SFF) PC, and an HP Z200 or HP Z200 SFF Workstation .

Sysprep (SYStem PREParation tool)A Microsoft tool that prepares the operating system for imaging . This tool must be run before imaging a system and deploying that image . Sysprep .exe is located on the operating system installation media obtained either from HP or Microsoft . Sysprep .exe, as well as other useful documentation and tools, is located in the support\tools\deploy.cab directory .

Things you need before you beginMake sure you have the following items before you begin:

• This document .

• External media (CD/DVD or Plug-n-Play USB external drive recommended) to store the HP Z400 drivers that will be needed following the installation of Windows XP 32-bit .

• If performing a “clean” OS installation, you will need to create a floppy disk containing the Mass Storage drivers that will need to be installed during the OS installation process . See Appendix F for more details .


3

Common image creation processThis section will detail the steps to create the common image .

Step 1: Choose a base imageUse one of the following approaches to establish the base image:

• The factory-preinstalled image can be used as a “base” for the common image — even if the file system type or the partition structure is not desirable . File system and partitioning can typically be customized during the image apply phase of the deployment process using an appropriate image deployment tool .

This document assumes the use of an HP factory-preinstalled Microsoft Windows XP Professional image of an HP Z400 Workstation PC as the base image .

NOTE: HP recommends using an imaging tool to create a backup copy of your factory preinstalled image to keep as a “fresh copy” so it is always available in case something goes wrong during the common image development process . Appendix G contains instructions on using ImageX with an external hard drive to create a disc image .

IMPORTANT: HP Backup and Recovery Manager (HPBRM) software is not supported in a common image . If HPBRM is installed, please see FAQ for more specific instructions on how to remove the HPBRM application and the Recovery Partition .

MICROSOFT ACTIVATION: In general, the common image created using the HP factory pre-installed image can only be deployed to HP Workstations and HP Business Desktop PCs due to the Microsoft OEM Activation . The image may work on other HP products but will not work on other vendors’ hardware .

• Use an existing HP Z400 common image that your organization has already developed .

• A clean installation directly from the operating system media can be used . This is particularly useful when building an image from the Microsoft Volume License media if your company is a licensed for that product . Reference the Microsoft Corporate Deployment documentation to build the base image . Then continue with the next section of this document to build a common image .

If you choose to perform a clean installation, see Appendix F for instructions on creating a floppy disk containing the necessary Mass Storage drivers . This must be done prior to the OS installation process .

NOTE: The Windows base image should only be applied to systems with a valid Microsoft OS license . Please consult your Microsoft Licensing Representative to assure that the common image deployment meet the Microsoft licensing requirements .

Step 2: Collect required drivers for the HP Z400 WorkstationGo to the HP support website, http://www .hp .com, and choose the “Software and Driver Downloads” link . Type the product name for which you want to download drivers, then select the appropriate operating system . Drivers are contained in self-extracting packages that HP calls SoftPaqs . Choose to “Save” the appropriate SoftPaqs from the matrix (see the Driver SoftPaq Matrix in Appendix D) .

NOTE: The online SoftPaqs are updated periodically . In order to ensure correct functionality, check that the PnP Driver Paths in the sysprep .inf file are still accurate (see Step 4 for more information) . It is especially important to check the graphics drivers, as their paths include the current driver version number .


4

Step 3: Create a drivers directory on the reference machineOnce the driver packages or SoftPaqs have been saved, there are several ways to handle them .

• You can extract the contents of the SoftPaq to put the driver files in the driver directory .

Unzip the SoftPaqs from Step 2 onto the Reference Machine .

o Open the .exe file with a utility such as WinZip and extract the files (may not work with all SoftPaqs) .

o If the SoftPaq is an InstallShield “PackageForTheWeb” file, it will have this icon:

If this is the case, the contents can be extracted by running the following command line:

SPXXXXX .exe /f <path> /e /s

/f – Specifies the directory in which to land the files .

/e – Specifies the command to run . Most SoftPaqs will automatically launch a setup or other executable . Passing in a blank value to the /e will disable this auto-launch functionality and allow for simply extracting the files .

/s – Specifies “silent” operations . No user interaction is required .

<path> - Indicates the location to store the files . If the directory doesn’t exist, it will be created .

For the recommended paths and resulting directory structure, see “Example directory structure” below . In our example, the HP Z400 chipset SoftPaq would be extracted by running:

Sp47233 .exe /f C:\Drivers\Chipset\ /e /s

NOTE: Mass storage drivers must be extracted manually . After using the above command line extraction, navigate to C:\Drivers\MSD . Extract the contents of f6flpy-x86 .zip into the C:\Drivers\MSD directory .

Example directory structure

Here is an example of <path> values that collect all the drivers under a primary directory, C:\Drivers, with individual categories .

C:\Drivers\Chipset; C:\Drivers\MSD\; C:\Drivers\LSI3041E;C:\Drivers\Audio\Creative; C:\Drivers\Audio\Realtek; C:\Drivers\Video\Intel; C:\Drivers\Video\ATI; C:\Drivers\Video\Nvidia; C:\Drivers\NIC\Intel; C:\Drivers\NIC\Broadcom; C:\Drivers\NIC\HP

• Or, you may choose to simply execute the SoftPaq to extract and/or install the software . (Only use this method if the driver is common to all target machines)

Step 4: Setting up the drivers on the reference machineAfter you have obtained the necessary drivers using one of the methods mentioned in Step 3, you need to copy the INF files of the drivers in a flat file format at the root of the reference machine . These drivers are placed in the following directory structure so that the operating system knows where to find them during the Plug-and-Play detection phase when the common image is deployed on the target machine, as instructed by the sysprep .inf file . This is known as the Plug-and-Play path and it is stored in the [Unattended] section of sysprep .inf, under OemPnPDriversPath .

The example path provided below assumes the drivers were extracted into the directory structure listed in Step 3 . If the drivers are placed in any other folder, the following key in the sysprep .inf file will need to be updated . Refer to Appendix A for the full sample sysprep .inf file .

[Unattended]OemPnPDriversPath = “Drivers\MSD;Drivers\Chipset\All;Drivers\LSI3041E;Drivers\Audio\Realtek\WDM;Drivers\Video\Nvidia\Drivers\WinXP(198 .01)\Display;Drivers\Video\Nvidia\Drivers\WinXP(198 .01)\HDAudio;Drivers\NIC\Intel\PRO1000\Win32\NDIS5x;Drivers\NIC\Broadcom\WinXP\IA32;Drivers\Video\Intel\Graphics;Drivers\Video\ATI\DRIVERS\XP32(8 .701 .1 .3)\Packages\Drivers\Display\XP_INF;Drivers\Video\ATI\DRIVERS\XP32(8 .701 .1 .3)\Packages\Drivers\WDM\HDMI\XP”

5

Step 5: Customizing the base imageThere are several optional steps that can be taken to customize an operating system image before capturing and deploying that image . These optional steps include:

Optional Step 1 – Uninstall preinstalled software .

The HP factory preinstalled image contains several applications and software packages that provide additional value to customers . If these are not desired, they can be removed .

NOTE: You may be required to install applications individually on each target machine due to licensing or functionality requirements .

NOTE: You may notice that software marked as a Hotfix or QFE (Quick Fix Engineering) in the factory preinstalled image cannot be removed . This is by design and is intended to ensure that the system has the latest fixes and security updates from Microsoft at the time the system was shipped . HP recommends these as well as any operating system Service Packs preinstalled by HP not be removed .

Optional Step 2 - Add software applications .

Software applications can be added before proceeding . Be sure to follow all applicable software licenses for software being installed .

NOTE: Refer to the documentation provided by the software vendor on a case-by-case basis for installing additional, non-HP provided software on the image .

Optional Step 3 - Add additional Microsoft patches or updates called “Hotfixes.”

Additional Hotfixes may be added to the base image as required by the IT policies of your organization .

Optional Step 4 – Operating system customization

At this time, any additional customization as required by your organization should be applied . Typical examples

include applying wallpaper or desktop theme, changing the profile settings, and setting device options .

Extend the processSupport for storage devicesThis document describes the process of creating a common image that is intended for the HP Z200 Workstation family, HP Z400 Workstation, and the HP Compaq 8100 Elite Family . The HP Workstations support both SATA and SAS storage devices . The reference sysprep .inf (Appendix A) describes how you can create an image that:

• Supports the SATA Mass Storage for both the HP Compaq 8100 Elite and the HP Z200/HP Z400 Workstations

• Supports the LSI Logic 3041e SAS Mass Storage for the HP Z400 Workstation

Adding support for other mass storage products is possible using the process described in this document by using the respective drivers for each product .

NOTE: One caveat to this approach is potential file collision (duplicated driver names but actual different drivers) in the Plug-and-Play driver directory structure . To prevent this, create unique folder names for each driver . If using this technique, be sure to update the OEMPnPDriversPath setting in the sysprep .inf . This approach assumes there is no device ID conflict . See Appendix A for more examples .

NOTE: Another potential issue can be device ID conflict with two different driver versions . This happens frequently when hardware vendors add support for new devices to existing drivers . An example is the Intel SATA RAID device ID PCI\VEN&8086_DEV&2822 which is used for the ICH8R, ICH9R, ICH10R and other controllers . The new driver has the device ID for old and new devices . Obviously the new device requires the new driver, but it may not be desirable to have the new driver used on an older device . If the new driver is in the pnp path, then it will always be used for any device with matching device ids . The best solution is to have both platforms use the new, common driver .

OPTIONAL STEP: Run “C:\Sysprep\sysprep –bmsd” to populate the [SysprepMassStorage] section of sysprep .inf with the PnP IDs and paths of all the default Windows mass storage drivers . This will add about 10-15 minutes to the time required to run Sysprep . However, this document does not provide specific guidance on additional mass storage device support other than those supported by the HP Z200 Workstation family and the HP Z400 Workstation .


6

Support for non-bundled hardware devices

If support is required for devices not included as part of your HP system (such as video cards, bio-metric devices, etc .) you can include those as part of your common image as well . Obtain the driver for all devices through the hardware vendor and place those drivers in a Plug-and-Play driver directory of your choice . The .inf file for the driver should be at the root of the PnP driver directory (for example, the .inf file for an NVIDIA video card display driver is located in C:\Drivers\Video\Nvidia\Drivers\WinXP(198 .01)\Display) . Be sure to update the OEMPnpDriversPath setting in the sysprep .inf with any directories you add .

NOTE: For more information on building the Plug-and-Play driver directory structure, see the documentation included in the deploy .cab in the support\tools directory on the operating system CD .

NOTE: This document does not provide specific guidance on non-bundled hardware devices, though the same approach can be used for other hardware devices .

Step 6: Obtaining sysprep .exe and setting up the C:\SysprepAfter all operating system customizations have been made and the HP Z400 drivers have been pooled in the correct directory structure, the system is ready to be prepared for imaging . This is accomplished by running the Microsoft Sysprep tool .

To begin:

1 . Create a C:\Sysprep directory on the system drive .

2 . Insert the operating system installation media (obtained earlier from HP or Microsoft) into the CD-ROM drive and browse to the Support\Tools directory .

3 . Double-click on deploy .cab and view the files .

4 . Copy the files sysprep .exe and setupcl .exe to the C:\Sysprep directory .

NOTE: Be sure to use the deploy .cab that matches your OS and service pack . For example, use the deploy .cab from Windows XP 32-bit Service Pack 2 for Windows XP 32-bit Service Pack 2 images .

NOTE: The deploy .cab file also contains other useful files such as a reference guide for unattended setups named unattend .doc . For Windows XP, it contains deploy .chm, a useful guide for creating corporate deployment images and an answer-file reference guide named ref .chm .

Additional resource: http://support .microsoft .com/kb/838080

Step 7: Creating and customizing sysprep .infA base sysprep .inf can be generated by setupmgr .exe, a tool located in the deploy .cab . An example sysprep .inf has been provided in Appendix A of this paper as a baseline .

The end-user experience of the Microsoft Windows XP Professional image can be tailored by customizing sysprep .inf . The screens that a user will or will not see can be controlled, as well as the ability to pre-populate image settings such as region, input language, time zone, etc . To customize the Out-Of-Box-Experience (screens that will be presented to the user after the operating system installation) for Windows XP Professional, see the deploy .chm file included in the deploy .cab file .

After sysprep .inf has been created, place it in the C:\Sysprep directory and customize the sysprep .inf for the HP Z200 and HP Compaq 8100 Elite, if needed .

Optional customization of the sysprep.inf settings

If you would like to have a more compact set of binaries in your common image, there are several optional steps that can be taken to customize the sysprep .inf settings and remove un-needed software . These optional steps include:

NOTE: Before customizing the sysprep .inf, plan or take inventory of the hardware configurations of the target machines . This information can then be used to determine what drivers need to be added or removed .

Two different approaches to install drivers are illustrated in this reference implementation . The first approach is the use of Plug-and-Play drivers as in the case of the LSI Logic 3041e SAS controller driver . The second approach is the use of setup via the [GuiRunOnce] as in the case of the Creative X-Fi Audio driver . SoftPaqs and applications can also be installed by using the second approach .

7

Optional Step 1 – Remove a boot controllerDo you plan to use the LSI 3041e SAS Controller as the boot controller in any target machines? If not,

• Remove the “Drivers\LSI3041E;” string in the OEMPnPDriversPath .

[Unattended]OemPnPDriversPath = “Drivers\MSD;Drivers\Chipset\All;Drivers\LSI3041E;Drivers\Audio\Realtek\WDM; . . .”

• Remove all the lines containing “… c:\drivers LSI3041E\symmpi .inf” from the [SysprepMassStorage] section of the reference sysprep .inf file

• Remove the C:\Drivers\LSI3041E subdirectory and its contents .

Optional step 2 – Remove the ATI graphics driverDo you plan to have any HP Z400 Workstation supported by an ATI graphics controller in any target machines? If not,

• Remove the “Drivers\Video\ATI\DRIVERS XP32(8 .701 .1 .3)\Packages\Drivers\Display XP_INF;” and “Drivers\Video\ATI\DRIVERS XP32(8 .701 .1 .3)\Packages\Drivers\WDM\HDMI\XP” strings from the OemPnPDriversPath .

• Remove the C:\Drivers\Video \ATI subdirectory and its contents .

Optional step 3 – Remove the NVIDIA graphics driverDo you plan to have any HP Z400 Workstation supported by an NVIDIA graphics controller in any target machines? If not,

• Remove the “Drivers\Video\Nvidia\Drivers\WinXP(198 .01)\Display;” and “Drivers\Video\Nvidia\Drivers\ WinXP(198 .01)\HDAudio;” strings from the OemPnPDriversPath .

• Remove the C:\Drivers\Video\Nvidia subdirectory and its contents .

Optional step 4 – Remove the Intel graphics driverDo you plan to have any HP Z400 Workstation supported by an Intel graphics controller in any target machines? If not,

• Remove the “Drivers\Video\Intel\Graphics;” string from the OemPnPDriversPath .

• Remove the C:\Drivers\Video\Intel subdirectory and its contents .

Optional step 5 – Creative X-Fi audio driver

Do you plan to have any HP Z400 or HP Z200 Workstation supported by a Creative X-Fi audio controller in any target machines? If not,

• Remove the line “C:\Drivers\Audio\xfi .cmd” from the [GuiRunOnce] section from the reference sysprep .inf file

• Remove the C:\Drivers\Audio\Creative subdirectory and its contents

Optional step 6 – HP wireless NIC driver

Do you plan to have any HP Compaq 8100 Elite PC or HP Z200 SFF Workstation supported by an HP NIC in any target machines? If not,

• Remove the line “C:\Drivers\NIC\hp .cmd” from the [GuiRunOnce] section from the reference sysprep .inf file

• Remove the C:\Drivers\NIC\HP subdirectory and its contents

Step 8: Create batch command filesOperating system-controlled driver installation in a common image includes the functionality that can be obtained via an .inf file-based installation of the driver by the operating system . The Plug-and-Play drivers include device recognition and basic functionality; however, any functionality that is normally achieved by running a setup program is not available . Some hardware vendors recommend their drivers to be installed via SETUP only . Setup application processing can be added via GUIRunOnce .

In order to ensure proper installation of the Intel Management Engine and HP provided add-on devices, HP recommends using the AMT .cmd, xfi .cmd, and HP .cmd provided in Appendix E of this paper as a baseline . These files are called at the initial login after the image has been successfully installed via the [GuiRunOnce] section of the sysprep .inf .


8

NOTE: If you do not plan on using either the Creative X-Fi audio controller or the HP wireless NIC, you should not create the associated .cmd file and you may remove the relevant lines from the [GuiRunOnce] section of sysprep .inf .

AMT .cmd should be placed in the C:\Drivers\AMT directory, Xfi .cmd should be placed in the C:\Drivers\Audio directory, and HP .cmd should be placed in the C:\Drivers\NIC directory .

NOTE: This process can be extended to install additional add-on drivers . The .cmd files provided in Appendix E may be useful as a reference .

Step 9: Create and customize cmdlines .txtCreate a folder named $OEM$ and place it in the root folder of your drivers directory (our example uses C:\Drivers) .

Within this directory, place a file named cmdlines .txt containing at least the following lines:

[Commands]

“C:\Sysprep\sysprep -clean”

The cmdlines .txt file contains additional commands that are executed after an image is installed . The “sysprep –clean” line ensures that all services related to non-boot mass storage devices are removed from the system once the image is booted after deployment in the target machines . Other commands may also be added now, depending on the requirements of your organization’s image .

The sysprep .inf includes a line indicating where the cmdlines .txt file is located . In the example implementation, the C:\Drivers\$OEM$\cmdlines .txt is being pointed to by:

[Unattended]

InstallFilesPath=C:\Drivers

Step 10: Run sysprepAfter the previous steps have been completed, the system can be prepared for imaging by running sysprep .exe . See the documentation in the deploy .chm file for sysprep .exe command-line options .

NOTE: Before running Sysprep, you can optionally modify oobeinfo .ini to customize the installation process . If you are using a Volume License version of Windows XP 32-bit, you may enter the Product Key into this file in order to skip the Product Key Validation step on each target machine . Appendix B provides an example oobeinfo .ini file .

On the reference machine,

Run “C:\Sysprep\sysprep –reseal –shutdown”

NOTE: Microsoft limits the number of times a system can be sysprep’ed . Windows XP may present a warning that the reseal limit has been reached, and your WPA grace period will not be reset . If you are using the HP-provided image, then you can disregard this message . The HP base image uses OEM Activation and the grace period reset is not pertinent . If you are not using the HP base image (or Volume License version), then end-users will be required to Activate . For other sysprep options including advanced customization and functionality, check the documentation included in the deploy .cab file .

Additional resource: http://support .microsoft .com/kb/838080

Step 11: Capture the common imageAfter running sysprep .exe the image on the Reference Machine’s hard drive will be ready to be captured, tested, and deployed .

An image capturing tool is required to capture and redeploy the common image . Additional qualification tests are likely required by the IT policies of the target machine’s organization .

9

Frequently asked questionsGeneral topics What is a common image?

A common image is defined as a software image that can be installed on a mixed set of PC hardware devices without modification . The software image contains all of the appropriate operating system and device driver files . The image may be installed and operated on any of the representative hardware configurations that the image supports .

What are the benefits of a common image?The following benefits are realized when using a common image:

• Significantly lowers the number of drivers and utilities to manage

• Fewer changes to software images which reduces qualification costs – test/validate on one platform and deploy on any other platform supported by the common image

• Easier management of standard images

• Lower total cost of ownership

Can a common image be created and shared across both desktop and notebook products?It is possible . There are some technical differences between the architectures that must be taken into consideration before creating a common image across these products . Contact your HP Sales Representative or Channel Partners to find out what HP/Channel Partner services might be available that can meet your organization’s imaging needs .

How can I ensure that I have the proper license to build and deploy a common image?Contact your Microsoft licensing representative .

Can I build an image that works on desktop products in other product families?It is possible . See the “Extend the process…” section of this document for details .

Can I build a common image that works on PCs from different manufactures?When you purchase a product from a hardware vendor such as HP, your license for the operating system is tied to that vendor’s hardware . The OEM Activation is also tied to specific manufacturer’s systems . However, it is possible to obtain a Volume License for an Operating System that will support deployment of common images across platforms from multiple manufacturers . Contact your Microsoft License Representative on how to obtain a Volume End User License and product .

Can I deploy a Microsoft Windows common image on systems that originally contained a non-Windows operating system?Not without the proper licensing obtained from Microsoft . Contact your Microsoft licensing representative to ensure you have the proper license .

10

Specific topics for the HP Z200, HP Z200 SFF, HP Z400, and HP Compaq 8100 Elite: How do I preserve the HP OEM activation? When using the HP base image and deploying to the HP desktops discussed in this paper, you can retain the Microsoft OEM Activation . You must include the Product Key in the appropriate section of either the sysprep .inf or oobeinfo .ini as detailed in http://technet .microsoft .com/en-us/library/bb457078 .aspx .

Sysprep .inf contents: [UserData] FullName= OrgName= ComputerName=* ProductKey = “AAAAA-BBBBB-CCCCC-DDDDD- EEEEE”

Oobeinfo .ini contents: [Version] ProductKey = “AAAAA-BBBBB-CCCCC-DDDDD EEEEE”

Additional resource: If the URL is obsolete, search the Microsoft web site for “Preserving OEM Pre-Activation when Re-installing Windows XP .”

How do I remove the HPBRM software and the Recovery Partition? CAUTION: If you have not created any Recovery CDs, it is strongly recommended that you do so before removing the HPBRM software . After removing the software, you will no longer be able to create recovery CDs or recover to any Recovery Points you have previously created .

To remove the HPBRM software and the Recovery Partition go to Control Panel > Add or Remove Programs, click “HP Backup and Recovery Manager”, select Remove and follow the on-screen instructions .

Thank youThank you for your purchase of and interest in HP Business Desktop PC and Workstation products . It is hoped that this document was useful in helping create a corporate deployment image .

For additional products and services that might meet the needs for your organization, please contact your HP Sales Representative or Channel Partners .


11

Appendix A: Reference sysprep.inf fileLocation: C:\Sysprep\sysprep .inf when sysprep is run .

Contents:[Unattended]OemSkipEula=NoOemPnPDriversPath = “Drivers\MSD;Drivers\Chipset\All;Drivers\LSI3041E;Drivers\Audio\Realtek\WDM;Drivers\Video\Nvidia\Drivers\WinXP(198 .01)\Display;Drivers\Video\Nvidia\Drivers\WinXP(198 .01)\HDAudio;Drivers\NIC\Intel\PRO1000\Win32\NDIS5x;Drivers\NIC\Broadcom\WinXP\IA32;Drivers\Video\Intel\Graphics;Drivers\Video\ATI\DRIVERS\XP32(8 .701 .1 .3)\Packages\Drivers\Display\XP_INF;Drivers\Video\ATI\DRIVERS\XP32(8 .701 .1 .3)\Packages\Drivers\WDM\HDMI\XP”UpdateInstalledDrivers = YesInstallFilesPath = “C:\Drivers”

[UserData]FullName=OrgName=ComputerName=*ProductKey = “AAAAA-BBBBB-CCCCC-DDDDD-EEEEE”

[GUIRunOnce]“C:\Drivers\AMT\amt .cmd”“C:\Drivers\Audio\xfi .cmd”“C:\Drivers\NIC\hp .cmd”

[RegionalSettings]LanguageGroup=1

[Display]XResolution = YResolution =

[Identification]JoinWorkgroup=WORKGROUP

[Networking]InstallDefaultComponents=Yes

[SysprepMassStorage]pci\ven_8086&dev_2682&CC_0104 = c:\drivers\msd\iastor .infpci\ven_8086&dev_27C3&CC_0104 = c:\driversmsd\iastor .infpci\ven_8086&dev_27C6&CC_0104 = c:\driversmsd\iastor .infpci\ven_8086&dev_2822&CC_0104 = c:\driversmsd\iastor .infpci\ven_8086&dev_282A&CC_0104 = c:\driversmsd\iastor .infpci\ven_8086&dev_2681&CC_0106 = c:\driversmsd\iaahci .infpci\ven_8086&dev_27C1&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_27C5&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_2821&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_2829&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_2922&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_2929&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_3A02&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&dev_3A22&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&DEV_3B29&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&DEV_3B2F&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_8086&DEV_3B22&CC_0106 = c:\drivers\msd\iaahci .infpci\ven_1000&DEV_0622 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0624 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0626 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0628 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0030 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0032 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0054 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0056 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0058 = c:\drivers\LSI3041E\symmpi .infpci\ven_1000&DEV_0062 = c:\drivers\LSI3041E\symmpi .inf12

Appendix B: Reference oobeinfo.ini fileLocation: C:\WINDOWS\system32\oobe when sysprep is run .

Contents:[DesktopReminders]DesktopRegRemind=0

[Options]TimeZone=1INTL_Settings=1AdminPw=0JoinDomain=0

[StartupOptions]Offline=1ScreenResolutionCheck=0

[UserInfo]

[Version]ProductKey=AAAAA-BBBBB-CCCCC-DDDDD-EEEEE

Manually add the above [Version] section with the ProductKey as listed in http://technet .microsoft .com/en-us/library/bb457078 .aspx to preserve the OEM pre activation . You must be using the HP pre-install image as base to preserve OEM pre-activation .

Appendix C: Additional HP Support URLs • HP Enterprise Solutions - http://www .hp .com/country/us/eng/solutions/business .html• HP support and drivers - http://welcome .hp .com/country/us/eng/support .html• HP driver subscriptions, alerts and notifications – http://www .hp .com/united-states/subscribe/gateway• HP SoftPaq Download Manager (SDM) - http://www .hp .com/go/easydeploy and search for HP SoftPaq Download Manager (under the HP Client Management Solution -> HP Management Tools)• HP System Software Manager (SSM) - http://www .hp .com/go/easydeploy and search for HP System Software Manager (under the HP Client Management Solution -> HP Management Tools)

13

Integrated Add-on options Version HP Z200 HP Z200 SFF

HP Z400 HP Compaq 8100 Elite

Chipset 9.1.1.1025 • • • •Intel mass storage 9.6.0.1014 • • • •LSI Logic 3041e 1.27.03.00 •

Audio

Realtek ALC262 HD Audio 5.10.0.5973 • • • •Creative Xi-F2 Audio Card 6.0.01.1323 • • •

LAN, wireless

Intel GbE Network Connection 11.5.10.0 • • •Broadcom NetXtreme GbE Ethernet NIC

Card14.0.0.7 • • • •

HP Wireless NIC 802.11b/g/n PCIe 11.03.08 • •Embedded

Intel HD Graphics Graphics 6.14.10.5241 • • •Professional

ATI FirePro V3700 8.633.1.1 • •ATI FirePro V3800 8.701.3 •ATI FirePro V4800 8.701.3 • •ATI FirePro V5700 8.633.1.1 • •ATI FirePro V5800 8.701.3 • •ATI FirePro V7750 8.633.1.1 • •

NVIDIA Quadro NVS 295 198.01 • • • •NVIDIA Quadro NVS 450 198.01 •NVIDIA Quadro FX 380 LP 198.01 • •NVIDIA Quadro FX 380 198.01 • •NVIDIA Quadro FX 580 198.01 • •NVIDIA Quadro FX 1800 198.01 • •NVIDIA Quadro FX 3800 198.01 •

NVIDIA Quadro 4000 198.01 •NVIDIA Quadro 5000 198.01 •

Security/Manageability

Infineon 1.2 TPM 1.90.00.0 • • • •Intel AMT LMS_SOL for AMT 6xx 6.0.0.1179 • • •

1 The Broadcom NetXtreme GbE Ethernet NIC Card is also available as an integrated card on the Z400 only

Appendix D: Driver SoftPaq matrix for Microsoft Windows XP Professional (32-bit)

14

Appendix E: [GuiRunOnce] Creative X-Fi Audio, HP Wireless NIC, and Intel AMT installation batch files Location: C:\Drivers\Audio\xfi .cmd, C:\Drivers\NIC\HP .cmd, and C:\Drivers\AMT\amt .cmd . These reference batch file can be invoked by sysprep .inf via the [GuiRunOnce] section . The batch file uses existing Windows XP tools to determine if the system is using non-PnP add-on devices and runs the relevant setup .exe accordingly .

Sysprep.Inf Contents:[GuiRunOnce]“C:\Drivers\Audio\xfi .cmd”“C:\Drivers\NIC\HP .cmd”“C:\Drivers\AMT\amt .cmd”

C:\DRIVERS\Audio\xfi.cmd Contents:“C:\Program Files\Common Files\Microsoft Shared\MSInfo\msinfo32 .exe” /categories SystemSummary /report c:\Drivers\2 .txt type C:\Drivers\2 .txt | findstr “8100 Z400”if errorlevel 1 goto SKIPINSTALLREM *** execute the setup command ***cd “c:\Drivers\Audio\Creative\”setup .exe /sgoto DONE:SKIPINSTALLREM *** do nothing ****:DONE

C:\DRIVERS\NIC\HP.cmd Contents:“C:\Program Files\Common Files\Microsoft Shared\MSInfo\msinfo32 .exe” /categories SystemSummary /report c:\Drivers\2 .txt type C:\Drivers\2 .txt | findstr “8100 Z200”if errorlevel 1 goto SKIPINSTALLREM *** execute the setup command ***cd “c:\Drivers\NIC\HP\”setup .exe /sgoto DONE:SKIPINSTALLREM *** do nothing ****:DONE

C:\DRIVERS\AMT\amt.cmd Contents:“C:\Program Files\Common Files\Microsoft Shared\MSInfo\msinfo32 .exe” /categories SystemSummary /report c:\Drivers\4 .txttype C:\Drivers\4 .txt | findstr “8100 Z200”if errorlevel 1 goto SKIPINSTALLREM *** execute the setup command ***cd “c:\Drivers\AMT”setup .exe /sgoto DONE:SKIPINSTALLREM *** do nothing ****:DONE

Appendix F: Creating an F6 mass storage drivers floppy disk If performing a “clean” OS installation and you are using SATA HDDs, it is essential that you prepare the mass storage system drivers prior to beginning the OS installation process . Follow these steps to ensure that the installation files are correctly copied to the target hard drive .• Download the Intel Rapid Storage Technology Utility and Driver for Microsoft Windows from the HP support site (See Step 2 for instructions on finding the correct file)• Run the .exe and extract the files• Insert a floppy disk into your floppy drive• Open f6flpy-x86 .zip

15

• Extract the following files into the root of the floppy drive o iaAhci .inf o iaAhci .cat o iaStor .inf o iaStor .cat o iaStor .sys o TxtSetup .oem• When this is done, eject the floppy and proceed with the OS installation . • At the start of the OS installation, follow the prompt to press F6 to install a third party SCSI or RAID driver .• When prompted, select ‘S’ to Specify Additional Device .• Insert the floppy and select the appropriate mass storage device drivers .From this point on, you may proceed with the installation normally .

Appendix G: Capturing and deploying the common image After running sysprep .exe the image on the Reference Machine’s hard drive will be ready to be captured, tested, and deployed . One way to do capture and deploy the Common Image is through Microsoft’s WinPE tools . We will illustrate the steps needed to save the common image onto an external hard drive then apply that image onto a Target HDD . For more information on the imaging process and using ImageX, visit http://technet .microsoft .com/en-us/library/cc748966%28WS .10%29 .aspxNOTE: In order to image your hard drive, you must have a version of WinPE that supports your Target Machine . In this example, we used WinPE 3 .0 for Windows 7 . For information on creating a bootable WinPE CD using the Windows OEM Preinstallation Kit (OPK) or Windows Automated Installation Kit (WAIK), visit http://technet .microsoft .com/en-us/library/cc749311%28WS .10%29 .aspxCapturing the Common Image onto an External USB Hard Drive1 . After Sysprep has completed, use your WinPE bootable CD to start your computer in WinPE mode . Note that you may need to set the startup volume to the optical drive in your BIOS .2 . Use ImageX to capture the image onto an external drive when the command line appears: Imagex .exe /compress fast /capture C: E:\<name> .wim <alt name> o C: is the Windows OS partition that we want to clone o E: is the external USB drive o <name> is the name of the image file, and <alt name> is the “human readable” name of the image file . Imagex requires that both names are specified . For example, this could be: Imagex .exe /compress fast /capture C: E:\image .wim “XP Pro”3 . Prepare an internal HD for installation . In our example, we will be applying the image to a primary hard disk (disk 0) . For a list of available disk destinations, enter the command “list disk” after starting diskpart . At the WinPE command line enter: • diskpart • select disk 0 (0 can be replaced with the number of the disk to image) • clean • create partition primary (You can optionally set a size with the size=<n> flag, where <n> is the size of the partition in Megabytes) • assign letter=c: • active • exit • format c: /q /y (Does a quick ntfs format . Remove the /q flag for a full format .)

For a full list of DiskPart commands, please visit http://technet .microsoft .com/en-us/library/cc770877%28WS .10%29 .aspx

Applying the Common Image from an External USB Hard Drive (E:) onto an Internal Hard Drive (C:) • At the WinPE command line enter: imagex /apply E:\<name> .wim 1 C:\

You can now remove the WinPE media and restart your computer to run through the OS setup and installation .

16

© 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. ATI is a trademark of Advanced Micro Devices, Inc.

4AA3-1531ENW, September 2010

Appendix H: Troubleshooting • 0x7B error during OS installation o This likely occurred because the wrong mass storage drivers, or none at all, were loaded during the OS installation process . If you are not using an HP-provided image, you must load the mass storage drivers during the initial OS installation . See Appendix F for more details .• Sysprep fails to complete or fails to load the PnP drivers o Double check your PnP Driver Paths with your driver directory . Each path must lead to an .inf file that Windows uses for installing device drivers . If a device path is spelled incorrectly, sysprep will crash and you will get an error message . o Make sure you have the drivers for the right operating system . For example, if you are installing Windows XP Pro 32-bit, you cannot use the 64-bit driver versions or Windows 7 drivers . o Make sure you are using WHQL certified drivers (All drivers listed on HP .com are WHQL certified) . Drivers that are not WHQL certified or signed will not install without user interaction .• SoftPaqs do not unpack to the right location o If you are unpacking the SoftPaqs using the command line, run it without the /s switch . Some driver packages unpack to the %temp% directory by default, and you will need to specify the new location by hand .• 0x7B error after a Sysprep o Make sure you include all the necessary Mass Storage Driver paths in your Sysprep .inf file .• Initial OS setup after deploying an image is wrong o If you are going through the OS setup and you are not getting the option screens that you specified in your Sysprep .inf answer file, this is likely caused by a syntax error in Sysprep .inf . Make sure your section headers and values are spelled correctly and you have formatted your sections correctly . o Make sure that your Sysprep directory is in the correct location . It must be placed in %SystemDrive%\Sysprep, where %SystemDrive% is the partition that contains the original Windows OS . Typically this is the C: drive, but that is not always the case . o Make sure you are using the correct version of Sysprep .exe for your machine . Different versions contain different features .• Common images require activation immediately after installation o If you are asked for an OS activation upon installation, you are not using the HP-provided base image or a volume-licensed version of the OS . Retail versions of Windows must be activated within 30 days, while volume licensed versions are exempt .

Documents

HP Compaq 8100 Elite PC Family, the HP Z200 Workstation Family