Re: Using sysprep on Win2K to unplanned different hardware
From: Dennis Calhoun (dcalhoun_at_blomand.net)
Date: 08/28/04
- Next message: Kelvin: "Cannot Log on to Windows after PC start up"
- Previous message: Ken Woodard: "Quickest way to rebuild a Win2000 workstation?"
- In reply to: Michael Leone: "Re: Using sysprep on Win2K to unplanned different hardware"
- Next in thread: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 28 Aug 2004 01:22:41 -0500
On Fri, 27 Aug 2004 14:22:52 -0400, "Michael Leone"
<mleone@contributionship.com> wrote:
>
>"Dennis Calhoun" <dcalhoun@blomand.net> wrote in message
>news:bdmti014rg82360evle6odapedv48kd0pg@4ax.com...
>>
[snip]
>The hard disks in the replacement machines will be connected to RAID
>controllers that are (almost certainly) not in that list. That list includes
>no Dell PERC RAID controllers, that I saw, and these machines will
>(probably, altho not defintely) be Dell machines, using Dell RAID
>controllers (altho I can not guarantee ahead of time with model RAID
>controller). So adding those drivers entries you speak of to the sysprep.inf
>wouldn't help me, in that sitution, would it?
Not unless one of the generic drivers that is included with Win2000
would be enough to get the system booted in a minimally usable state.
If so, which I doubt, one could then use the Dell disk to install the
correct driver/s. Not a likely scenario, but not impossible, maybe.
>
>> Also, in your distro you need to add the cmdlines.txt file to your
>> $OEM$ folder and in that file have the *first* command be
>> C:\Sysprep\Sysprep -clean
>> assuming you have Sysprep located in C:\Sysprep [adjust to fit your
>> location]
>
>My sysprep.inf file has all the IDE drivers listed (altho I also had to add
>a registry file with those same drivers, according to an MS KB article I
>found). This works for all machines I've tried, that are on machines with no
>SCSI controllers. Everytime I add the SCSI list to the sysprep.inf file
>(making no other changes), and re-do sysprep, it blue screens with "07B". If
>I remove the SCSI entries from the list, and leave just the IDE, it boots
>fine. Every time, on multiple models of hardware.
>
>Never boots with both IDE and SCSI controllers listed. I even downloaded a
>sysprep.inf from the Net, from the author of the Windows 2000 Deployment
>Guide book ... still blue-screens. Every time, and on multiple models (IDE
>only, IDE and SCSI drives attached).
Hmmm.... that's strange. I've made a syspreped image on a Dell GX100
that I've since cloned to GX150, GX1 and one of the Dimensions too,
with a total of 5 or six different IDE controllers. Not once have I
seen the blue screen with 07B as you have. Maybe just my luck, which
could change unexpectedly.
Back to what you are trying to accomplish.....
You say that you want this "one size fits all" image to use for fast
fix D/R. How about this....
As each new batch of machines come in and you *know* what is in the
box, make a "Ghosted only" clone of each different system type, just
for the short run. Collect the necessary information and drivers/files
from each set and once you have all you need for all of the whole lot,
fire up your original Model System, add the files in the location you
desire, make the necessary Sysprep.inf entries and registry changes
(if needed) then make a new Master image. After some testing and fine
tuning, deed done.
What I've been doing at our school is to make a Ghosted Only image of
the original software package and configuration, an image of the whole
disk, without using sysprep. I use this clean original to restore to
the model computer prior to making any updated master images that are
syspreped, to avoid potential problems, like accumulated duplicate
entries in some registry values.
IN another post of mine I spoke of my inability to get anything that I
enter in the $OEM$ tree to actually be DONE on a target computer. One
thing that I've thought of *might* also interest you, but there is a
glitch in your case that I will mention in a bit.
I am using Ghost 2003 for our cloning, don't have the luxury of the
Corporate edition. I've thought that it might be possible to add
something to a drive immediately after it has been restored from an
image that is held on a mapped network drive in our peer-to-peer
setup. In our case, I think this would be ok, because the things I
want to import would be needed only after the mini-setup has ran its
course (PnP drivers for peripheral devices). I *have* already found
that once Ghost has completed writing the image to the target computer
I can elect to click "continue" rather than "reset computer". It will
then close the GUI of the Ghost executable and return to a command
prompt. At that point the computer is still connected to the source
computer, via the drive-mapping boot disk connection that was first
established when I began the process. I THINK I should be able to use
that command line interface to copy or xcopy additional directories or
files from the source to the target drive, but I have not yet had time
to test this idea.
You could do that too, if it will work, but the glitch I see is in the
registry entries. If you are comfortable with making such edits en
mass, you could release the attributes on the hives and then import
your edited version/s, along with all the necessary files, then reset
the attributes. Seems like a lot of bother to me and I tend to think
it would be easier to just make a new master image once you have
collected everything necessary from the new systems.
-- The universe is so huge and we are so small. There is only one thing that we can truly control. Whether we are good or evil. Dennis C.
- Next message: Kelvin: "Cannot Log on to Windows after PC start up"
- Previous message: Ken Woodard: "Quickest way to rebuild a Win2000 workstation?"
- In reply to: Michael Leone: "Re: Using sysprep on Win2K to unplanned different hardware"
- Next in thread: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
