Re: Cloning XP on hard drives
From: Some other guy (Some_at_other.guy.com)
Date: 04/03/04
- Next message: dglock: "Changing name of *.exe files"
- Previous message: dglock: "Autolaunch of Explorer at WinXP startup"
- Next in thread: Some other guy: "Re: Cloning XP on hard drives"
- Reply: Some other guy: "Re: Cloning XP on hard drives"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 03 Apr 2004 13:26:53 -0500
"R. McCarty" wrote:
> Depending on how many "Clones" you need there are several
> options. Microsoft makes an OEM tool called SysPrep. It is
> designed so a common image can be applied and then a short
> setup is done on each machine when it is first booted.
> (This can include entering each system's unique Key)
>
> It is very important that the hardware of each PC is almost
> identical. Different CPU's, motherboards and Chipsets make
> using SysPrep more difficult.
> > We are a small company and we sell an instrument which has
> > a built in computer board, running WinXP. We will buy WinXP
> > for each system, but to simplify making these can we clone
> > the hard drive, with all the software on
Ok, I'm in the same situation as the original poster.
With Windows-98, I've had a "master" computer with Win-98, customized
spash-screen, a few system tweeks, IE 6.what-ever, Fully Updated and
patched via Windows Update, Adobe reader, Win-Zip, Easy CD-creator,
Norton AV, etc. Basically a fully functional (and updated) computer
with the usual list of basic third-party accessories. Once in a while
I will fire up the master computer and update the virus def's.
Used either Drive-Copy (or Ghost) to duplicate the drive. Cloned
drive is then installed on clone system (un-opened OEM copy of Windows
98 goes with it).
Recently (yes, recently) started to explore this process with XP.
Here's what I did:
Took in-house (educational version) retail box XP-pro "upgrade" and
did a virgin install on new "master" computer. During install I
connected to the internet and did the registration thing (gave it the
serial number inside the box). This copy was registered once already
on another machine maybe a year ago. The registration worked (no
indication that the serial number I gave had been used previously),
and this master system was (and continues to be) fully functional.
Went to Windows Update and got it all patched. Installed same set of
3'rd party software (adobe, norton, CD creator, Winzip, etc).
Everything is cool.
Used ghost and made 2 (two) drive-to-drive copies (each cloned from
the same master). They worked fine when installed in PC's with
identical hardware as the master (same type mother-board, video card,
CD-RW, etc).
Made third clone. Installed it into third computer. Fired it up (not
connected to internet). It gave me a message saying something like
the hardware had changed significantly and it would only function for
3 days unless I somehow registered (or re-registered) it. Plugged in
network cable, clicked along the registration process, gave it the
original serial number, and it wouldn't take it. Gave it a serial
number for a new OEM version of XP-pro. Wouldn't take that either.
Ok, fine.
Started the system up, threw in OEM XP cd, did not see any "repair"
function, so I told it to "install" XP on the system from the CD. It
asked for serial number - I gave it OEM serial number. It installed.
After all this, it started up just fine, with all previously installed
software and (I think) most settings as they should be.
Questions:
1) How (or why) did the first 2 clones work, and how did the third
clone know it was a clone? (I will re-clone the master and see if it
will work IN the master).
2) After registration, does an XP system ever communicate back with
the "mother ship" (assuming it's got a network connect) and check to
see if it's still "kosher" ?
3) Are Intel P-4 (and C-4 ie Celeron) "serialized" the way that P3's
were? (and if so, is this how XP registers itself on any given
system) ?
4) How can I install XP on a "master" system, and UPDATE/PATCH the
master, and configure it the way I want, and keep this clone system
"living" for months (a year or longer), and STILL be able to clone it
to production systems and then some-how activate the production
systems with the serial numbers of the OEM-XP CD that will be shipped
with them?
- Next message: dglock: "Changing name of *.exe files"
- Previous message: dglock: "Autolaunch of Explorer at WinXP startup"
- Next in thread: Some other guy: "Re: Cloning XP on hard drives"
- Reply: Some other guy: "Re: Cloning XP on hard drives"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
