If an administrator has to install Windows XP to more than one machine at once, the usual approach (when the systems have similar hardware) is to build a system image and use Norton Ghost or a similar system-imaging tool to deploy it.
However, one possible problem that can arise from this is how to deal with product activation. If you're installing across multiple machines and you have a volume license key, does each computer need to be activated individually?
Generally, the answer is no. But when preparing the image, you need to follow certain steps. An admin will usually employ the Microsoft System Preparation tool Sysprep to create and seal the system image before deployment. However, Sysprep normally erases the activation data from a system when it's sealed, so when dealing with volume license keys, you must take the following steps.
The product key line will contain a placeholder key, supplied by Microsoft, which will instruct the computer to preserve the existing volume license key information. You'll need to supply different keys depending on
To continue reading for free, register below or login
To read more you must become a member of SearchWindowsServer.com
');
// -->

which edition of Windows you're using:
Windows XP Professional 32 bit
MVF4D-W774K-MC4VM-QY6XY- R38TB
Windows XP Tablet PC Edition
XT67V-GY7FW-GR6FR-WDK2C-8T97J
Windows XP Professional x64 bit
FM634-HJ3QK-6QVTY-RJY4R-XCR9J
Note: These product keys are only placeholders, and will not work in a standalone environment.
Also, if the system in question has to be re-activated at any time due to hardware changes, product activation will ask for the volume license key for that particular computer. The substitute key listed above is not an actual working key, so product activation will demand that you supply a real one if it needs to run again. Be sure that the volume license keys you use are associated with the correct computers and products.
About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators. He is also the author of the book Windows Server Undocumented Solutions.
More information on this topic: