Fred Hubbard
09-30-2002, 05:32 PM
I know that with verion 1.1 of the Sysprep tool the hard
disk controllers can be different. I recall reading that
if the controllers differ on the master and target
systems, then the controller must be specified in the
Sysprep.inf file before the master image is created and
deployed onto the target machine. I was also given the
impression from an MS KB article that the controller
drivers are loaded "on the fly" when using version 1.1 of
the tool, which I interpet as meaning I don't need to
specify the controller(s) in the Sysprep.inf file. Am I
missing something here, can anyone please tell me that if
in fact the disk controllers are different on the master
and target machine will I need to specify the correct
controller(s)in the Sysprep.inf file. My objective is
simple, I want to be able to image the entire drive on my
notebook onto my server because the notebook is starting
to show signs of wear (hardware wise) and I want to be
able to apply the image to a new notebook with minimal
down time if in fact the unit does eventually fail.
Thanks for the info...
Fred Hubbard
disk controllers can be different. I recall reading that
if the controllers differ on the master and target
systems, then the controller must be specified in the
Sysprep.inf file before the master image is created and
deployed onto the target machine. I was also given the
impression from an MS KB article that the controller
drivers are loaded "on the fly" when using version 1.1 of
the tool, which I interpet as meaning I don't need to
specify the controller(s) in the Sysprep.inf file. Am I
missing something here, can anyone please tell me that if
in fact the disk controllers are different on the master
and target machine will I need to specify the correct
controller(s)in the Sysprep.inf file. My objective is
simple, I want to be able to image the entire drive on my
notebook onto my server because the notebook is starting
to show signs of wear (hardware wise) and I want to be
able to apply the image to a new notebook with minimal
down time if in fact the unit does eventually fail.
Thanks for the info...
Fred Hubbard