RE: ghost and sid walker

Hi,

Make sure you have all the sysprep files. If you are using XP you need
Sysprep version 2.0 plus the Setup Mananger etc that comes with it to create
the inf. For 2000 you need Sysprep 1.1 The files are located on the XP CD in
Tools. I have a copy of the inf files that I use on my site
http://www.sd61.bc.ca/windows2000/downloads/Sysprepxp.zip
http://www.sd61.bc.ca/windows2000/downloads/Sysprep2000.zip

Duplicate machine names are a problem because even if you change the name it
still thinks they are the same computer (SID). Who ever created the original
machine you used to Image should have known to run sysprep BEFORE imaging
which would have saved you hours of hassle.

If you run setup manager with both the XP or 2000 versions it will create a
folder called C:\sysprep and then you can manually copy the sysprep.exe and
the setupcl.exe as well as the sysprep.inf to this folder. Once the Sysprep
runs on startup it DELETE's this folder automatically so be aware.

Cheers,
Lara

"softtrain" wrote:

Thanks Lara. I'll give it a try. This may help actually because when we
ghosted we got duplicate machine names which I wasn't worried about because I
coudl just change them.

I've starting working with this and sysprep is making me choose either the
CD or an installation point. I'm assuming that I'm referring it to the .inf
file that I created on the local drive. is t hat correct?

Do I proceed with adding all the remaining machine names that I need to
change and run sysprep in the appropriate order so that the machines grabs
the next machines name?

Thanks for your help.
P
--
P Cully


"lforbes" wrote:

Sysprep was probably only looking for sysprep.inf as it doesn't need an CD's,
network shares or installation files unless it is setup to "Plug and Play"
the drivers and the drivers aren't available. Basically all sysprep does is
strip the info from the machine and then uses the sysprep.inf file to put
back the info. You can always build a sysprep.inf file and put it on a floppy
as sysprep will look to the floppy drive for it.

The only sid program I know is ghostwalker (can't remember the exact .exe
name) it is put out by Sympatec Ghost and was included with older versions of
Ghost including 6.5 for ghosting NT. I am not sure if there is a version with
the recent ghost. I don't use Ghost. I use Partimage instead which doesn't
have a sid program. However, as I use XP and 2000 I just use Sysprep.

By the way, you CAN run sysprep after the fact on a machine that has been
imaged already and it will strip the sid information and then on reboot you
will be prompted to add the information again. This is by far the easiest way
to fix your problem. I often use Sysprep to "fix" any name issues or other
issues if I have a box that is a problem.

Create a sysprep.inf using the setup manager and add any specifics. Then say
"yes" to create the sysprep folder. copy the sysprep.exe to the sysprep
folder (this info is deleted automatically after the setup manager runs) and
then run sysprep.exe from the sysprep folder. Say "no to plug and play" and
make sure the SID regeneration is set to yes.

Cheers,
Lara

"softtrain" wrote:

Thanks. I figured that out when I tried to run sysprep. the lab teacher had
already built the reference machine. What threw me off was that sysprep was
looking for a place for the installation files, either the CD or a network
share. I understood that to mean the files for the OS. The reference
machine already had the OS loaded with all the applications so I wasn't sure
how to proceed.

Now that I've dug myself into a big hole, do you know of a sidwalker program
I can run to change the SIDs?

Thanks,
P
--
P Cully


"lforbes" wrote:

Hi,

If you ran Sysprep on the Windows machine BEFORE imaging it then you don't
need to change the SID. Sysprep strips all the "computer specific"
information from the machine including the SID, name, Domain etc. Therefore
you run SYSPREP and when it shuts down, you image the machine. When you boot
the new machine after imaging Sysprep will ask you for the information that
you haven't already provided in the sysprep.inf.

The Sysprep.inf can be created using Setup Manager which is a tool with
Windows 2000 and XP.

Cheers,
Lara

"softtrain" wrote:

Hi

I'm running ghost 7.5 I built a model computer and I've dumped the image.
I had one client "load the image" from ghost. It appears to have worked fine.

My question: I used ghost multicast server to dump the image and load the
file. I did not use the ghost walker program yet when the new machine came
on line it did not report a SID duplication error.

The manual is beyond comprehension and there are no KB articles at symantec
to explain this. I thought after imaging I'd have to run a task and change
the SID.

Question: should I expect an error message re: duplicate SIDs?
If yes, then I should be okay. If not, how can I check?

Thanks in advance,
Patricia
--
P Cully
.

Relevant Pages
Loading