Chuck replied to David
24-Dec-09 08:34 PM

There is, although it gets involved.
The first obvious issue is the windows serial number/Key. Next has to do
with a unique machine ID that is generated during the install process, and
the name of each P/C.
Some of these issues also exist with the Applications software, such as
Office and some retail applications.
Finally, you need to decide if a user accounts are "global" to all P/Cs, or
local, tied to each users P/C. It sounds like you want globals, but having
more than one instance of the same global user active can be a problem.
A last, but not least issue has to do with the windows version. OEM,
Corporate, Retail, etc. and the fact that you are talking about XP Home.
For instance, if you had "unconfigured" OEM packs, utilities are included to
make much of what you want to do easier.
Basically, what you end up doing, is cloning a custom configured version,
changing the Key on install/startup, and then adding the unique user
configuration you want.
it is possible to use computer management to import and export users, at
least on the professional version of XP.
The P/Cs need to be more or less isolated, until they have unique valid
What you want to do is more or less what an OEM does when they produce the
generic "master" for a bunch of the same model P/Cs, and load it into hard
drives.
There is a "slipstream" process that can be modified to generate the
MSDN and TecNet used to contain quite a bit of info on the process.
Unfortunately XP is in the sunset, and it is possible that the info has been
removed.
With 10 P/Cs Imight consider adding a business server.