ris / ghost

  • Thread starter Thread starter Barry
  • Start date Start date
B

Barry

Hello,

Question for you all, I need to create a disk image of 2k with various
applications on, and I need it to not work fine on equipment that is not
100% exactly the same as the original image. Having tried this just using
ghost, I get the old faveoutite bsod "inaccessable boot device", which is
sort of what I expected...

Anyway, is there a way of using RIS and Ghost to get round this somehow? I
was thinking of rissing 2k down, installing everything, riprepping it up,
then rissing new image down. At somepoint, I assume I can ghost that final
ris image before it finalises the install??

Reason being, it needs to be on a CD image in the end, not on the network.

Anyone any bright ideas?

Thanks!

Barry
 
Barry said:
Hello,

Question for you all, I need to create a disk image of 2k with various
applications on, and I need it to not work fine on equipment that is not
100% exactly the same as the original image. Having tried this just using
ghost, I get the old faveoutite bsod "inaccessable boot device", which is
sort of what I expected...
Click to expand...

obviously that should be "I need it to work fine" it already 'not works
fine' ;)
 
Barry said:
Hello,

Question for you all, I need to create a disk image of 2k with various
applications on, and I need it to not work fine on equipment that is not
100% exactly the same as the original image. Having tried this just using
ghost, I get the old faveoutite bsod "inaccessable boot device", which is
sort of what I expected...

Anyway, is there a way of using RIS and Ghost to get round this somehow? I
was thinking of rissing 2k down, installing everything, riprepping it up,
then rissing new image down. At somepoint, I assume I can ghost that final
ris image before it finalises the install??

Reason being, it needs to be on a CD image in the end, not on the network.
Click to expand...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Are you sure RIS can help to do image on CD? You can help to install some
application using WINNT.SIF but not prepare image...

Ghost is bad solution - Ghost doesn't clean SID and your computers will have
a trouble in the network environment.

It looks like RIS is your winner, but you diffenetely should have a network
connection...

Regards,
Gennadi
 
Gena said:
network.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Are you sure RIS can help to do image on CD? You can help to install some
application using WINNT.SIF but not prepare image...

Ghost is bad solution - Ghost doesn't clean SID and your computers will have
a trouble in the network environment.

It looks like RIS is your winner, but you diffenetely should have a network
connection...

Regards,
Gennadi
Click to expand...

nope, I'm not sure it can do this :)

Thing is, this is going to our third party for installs out to remote sites,
so it can't be done over the network after the initial image has been
created. I need a way of getting an image on a cd, that will still be able
to detect any hardware changes and create a unique sid etc, kinda like what
ris does when you copy a riprepped image over the network to a client, but
on a cd. If that makes sense?
 
Barry said:
Thing is, this is going to our third party for installs out to remote sites,
so it can't be done over the network after the initial image has been
created. I need a way of getting an image on a cd, that will still be able
to detect any hardware changes and create a unique sid etc, kinda like what
ris does when you copy a riprepped image over the network to a client, but
on a cd. If that makes sense?
Click to expand...

I see. It looks like you need to read about $OEM$ and *.sif files... Put all
your stuff on CD and maybe you can achieve your target.

Please pay attention to these articles:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314479
http://support.microsoft.com/default.aspx?scid=kb;en-us;249694

I hope this helps...

Regards
 
Hi Barry

It's actually SysPrep that you want here. Riprep is for RIS and, since this
is going on a CD, is not applicable. SysPrep does for Ghost what Riprep
does for RIS, if you see what I mean.

Make sure you use the latest version and you should be fine. The rough
procedure is that you run SysPrep, the machine shuts down, at which point
you take an image of the machine.

Hope this helps

Oli
 
Barry said:
Hello,

Question for you all, I need to create a disk image of 2k with various
applications on, and I need it to not work fine on equipment that is not
100% exactly the same as the original image. Having tried this just using
ghost, I get the old faveoutite bsod "inaccessable boot device", which is
sort of what I expected...

Anyway, is there a way of using RIS and Ghost to get round this somehow? I
was thinking of rissing 2k down, installing everything, riprepping it up,
then rissing new image down. At somepoint, I assume I can ghost that final
ris image before it finalises the install??

Reason being, it needs to be on a CD image in the end, not on the network.

Anyone any bright ideas?

Thanks!

Barry
Click to expand...
Shouldn't you be using Sysprep with Ghost?
 
We have gone away from the RIS and went with Ghost because it's more
flexible than the RIS. For myself I prefer to just get an old hard drive and
use that instead of burning the image to 3 or 4 CD(s) obviously if your
cloning laptops you with have to use CDs (or Ghostcast server). If you elect
to use the HD method just make sure you send an IMAGE to the HD. create
your image and run sysprep,, on the new high-end systems I could restore a
system from a HD in about 5 minutes vs 20 minutes (+or-) using the CDs or
the Ghostcast server. if you do this and you still need CD(s) later on make
sure you split your image so off load the image to CDs later
 
Ah gotcha, just read the faq, and it says "The mass-storage controllers (IDE
or SCSI) must be identical between the reference and destination computers."
Seeing as the orignal problem I had when simply ghosting it was "inaccesbile
boot device" (i think) BSOD, is this likely to just happen again after I
sysprep it?

Cheers for your help
 
Barry said:
Ah gotcha, just read the faq, and it says "The mass-storage controllers (IDE
or SCSI) must be identical between the reference and destination computers."
Seeing as the orignal problem I had when simply ghosting it was "inaccesbile
boot device" (i think) BSOD, is this likely to just happen again after I
sysprep it?
Click to expand...

All followed stuff is applying to risprep (it is almost the same as sysprep)

From my experience - nope :)

I mean setup pissed off sections like

[MassStorageDrivers]

in *.sif file

You just have to properly populate $OEM$ folder and txtsetup.oem file.

That is all

Regards,
Gennadi
 
Gena said:
Barry said:
Ah gotcha, just read the faq, and it says "The mass-storage controllers (IDE
or SCSI) must be identical between the reference and destination computers."
Seeing as the orignal problem I had when simply ghosting it was "inaccesbile
boot device" (i think) BSOD, is this likely to just happen again after I
sysprep it?
Click to expand...

All followed stuff is applying to risprep (it is almost the same as sysprep)

From my experience - nope :)

I mean setup pissed off sections like

[MassStorageDrivers]

in *.sif file

You just have to properly populate $OEM$ folder and txtsetup.oem file.

That is all

Regards,
Gennadi
Click to expand...

cool, well, I'll give it a go.

Expect to see me back here in a few days :)

Cheers,
Barry
 
Back
Top