Building a Common Image

<Path>net user administrator /active:yes</Path>

</RunSynchronousCommand>

</RunSynchronous>

</component>

</settings>

<component name="Microsoft-Windows-Security-Licensing-SLC"

processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"

language="neutral" versionScope="nonSxS"

xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

</component>

</settings>

<cpi:offlineImage

cpi:source="wim://arbors01/installs/vistaos/install.wim#Windows

Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

Frequently asked questions

Q: What is a common image?

A: A common image is 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 run on “any” of the representative hardware configurations that

the image supports.

Q: What are the benefits of a common image?

A: The benefits of a common image are as follows:

 Single image can be developed for multiple HP Business Desktop models

 Significantly lowers 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

Q: What are the types of Common Images?

A: The following are types of Common Images:

 Common, “shared” hardware—this type of common image starts with the

hardware design process using similar product components. PC systems

that use a single supplier for certain components (for example, NIC, audio,

etc) can reduce the image complexity by reducing the number of driver

and image components. HP believes customers value the ability to scale

hardware solutions across their entire environment, and thus this approach