Imaging HDD using BartPE/Ghost

[_Bat_]

Hi everyone,

 

How are the "holidays" going?

 

Over the past couple of days I have been creating an image for about seven/eight identical laptops... I have just completed it this morning and before running sysprep I decided to do a backup image just in case. So I loaded up BartPE to use ghost and attemped to connect to a share on the server only to be told "cannot connect to "\\server\ghost$". Tried again after reboot to see the same message. I guess bartPE has trouble with the network card, because it works fine in windows.

 

I think the only option I have is to create a partition on the HDD and put the ghost image there, boot into windows and move the image across to the server. Then i'll attempt to put the image on the remaining laptops via CD if needs be...

 

I have never used ghost in any way before other then the way that just failed, so i'm not sure if the above process has flaws, can anyone help me out or think of a better way?

 

Thanks

[CyberNerd]

you could try G4U. G4U is a boot disk that will allow you to upload an entire disk image to an ftp server, then image from that server. (no compression though - ouch!)

 

http://www.feyrer.de/g4u/

[NetworkGeezer]

@_BAT_

Does your BartPE DHCP ok? Can you ping the server?

What network card are using. You don't have have a Dell with a Broadcom NIC by any chance?

Which version of Ghost are you using?

 

@CyberNerd

Would've thought you would've suggested Knoppix with dd to do it like real men

[_Bat_]

@_BAT_

Does your BartPE DHCP ok? Can you ping the server?

What network card are using. You don't have have a Dell with a Broadcom NIC by any chance?

Which version of Ghost are you using?

 

Strangely enough it goes through the entire process of DHCP without any errors and also pings the server without packet loss.

 

Network card is "Intel Pro/100 M Mobile", so no, not the above.

 

The version of ghost I am using is V8

 

I have never had this problem before... it surprised me lol.

[_Bat_]

I tried to map the drive via CMD and I got the following error message: "system error 1450 has occurred - insufficent system resources exist to complete the requested service"

 

Tried googling to no avail.

[beeswax]

What network card are using. You don't have have a Dell with a Broadcom NIC by any chance?

 

I've just been imaging 15 Stone laptops with broadcom nics, and when it came to creating the boot disk the protocol.ini file was incorrect, in that it had a blank space where the drivername should be, i.e.

 

"[protman]

drivername=PROTMAN$

 

[pktdrv]

drivername=PKTDRV$

bindings=nic

intvec=0x60

chainvec=0x66

 

[nic]

drivername = [this space was blank]"

 

it should have had B44$, without the brackets, for the Broadcom 440X 10/100. worked fine after that. I've never had this problem before creating a boot disk.

[NetworkGeezer]

@_BAT_

Try CD to the C: drive or RAM disk. Complete stab in the dark but I don't know whether it just requires a r/w filesystem.

 

You computers all have 256MB+ I take it?

 

Have you authenicated against the server before you try to map to the share or do you use

 net use E: \\server\share$ /user:domain\username

[_Bat_]

@_BAT_

Try CD to the C: drive or RAM disk. Complete stab in the dark but I don't know whether it just requires a r/w filesystem.

 

You computers all have 256MB+ I take it?

 

Have you authenicated against the server before you try to map to the share or do you use

 net use E: \\server\share$\ /user:domain\username

 

I have gone ahead with my plan B now... no matter what I did, I could not get the drive to map or get access to any shares at all. I tried mapping it from within bartPE and simply trying to access the share from the run command. It asks me for username and password which I entered and it comes back with an error... doing the latter says "error during installation".

[NetworkGeezer]

@Beeswax

Looks like Broadcom is just geared to producing drivers for a full Windows installation.

 

They probably had to explain a few times what DOS was to the trainee the dumped the job of cobbling together the driver package

[_Bat_]

I hate computers (for the remainer of this day anyway). Does that make me an outcast here?

[petectid]

I've had similar results when there are time differences between the server and the workstation, though I cannot remember the error number I was getting it may be worth checking the time settings on the server and workstation. A stab in the dark but what is happening here also happens when there is a time difference. Bye the way Bart PE is a 32bit environment and does not use Dos drivers, so NICs are not usualy a problem when booting.