Building a Common Image with Microsoft Windows 7 on HP Pro and Elite Desktop PCs 2012 Commercial Managed IT Models - Techical White Paper

5
Clean Installing the OS, drivers, and enhancements
This section provides guidelines for users performing a clean installation of Windows on a supported
HP business desktop PC.
For more information on installing Windows, refer to the Microsoft website at
http://windows.microsoft.com/help.
IMPORTANT
Follow the installation instructions in the order provided. Failure to
complete these steps in the proper order can result in an unsuccessful
or unstable installation. These instructions are independent of the
operating system currently installed on the PC.
1. Depending on the particular Internet connection(s) being used, download the driver(s) for the
network interface card and/or wireless LAN adapter driver. Save to a USB storage device or
optical media.
Contact your network administrator to properly set up the networking components of Windows.
2. Change the boot order in F10 Setup so the optical drive is the first boot device.
3. Boot with the Windows 7 OS disk; follow the on-screen instructions for installation.
OS recovery media from HP does not require a product ID or key for installation on a supported HP
business desktop PC.
If using Advanced format hard drives (4K sector drives), please refer to the HP white paper
“Preparing Advanced Format hard drives for Microsoft Windows installations on HP Business
Notebook PCs and Desktop PCs.”
4. Install the appropriate communications driver from either the optical media or USB storage device
(Step 1 above) and configure your Internet connection.
5. Install the desired patches from www.microsoft.com/windowsupdate or contact your network
administrator for additional updates. Reboot the system after these patches have been installed.
6. Install the drivers and enhancements listed in Table 1 using HP SoftPaq Download Manager
(available from www.hp.com/go/sdm); alternatively, you can download individual SoftPaqs from
the HP website. Some deliverables may have direct dependencies on other deliverables that may require
.NET.
For more information, refer to