Issues with DOS Ghost Boot Disk

July 16, 2007

This is my first time posting to any community

Here's a situation

Our current laptop models D410 and D620 are reaching end of life and

getting replaced with newer model D630. We have variety of

configurations on these laptops (e.g Laptops with two hard drives,

laptop with external cd writer)

Our normal process to image a machine to into USB DOS bootdisk with

network drivers, pull the image from network and lay it down to

primary hard drive of the machine using the ghost command line DST=2

(Boot disk is DST = 1). Its been working fine for several models with

Dual Hard drive such as D620, P670 and P690

Dell D630 has introduced a new complexity to the process. Bascially,

the second hard drive (Modular Bay attached) takes over the primary so

ghost image gets pulled down to secondary hard drive which inturn

break all our internal imaging script.

Right now, the solution is to disconnected the drive, start imaging

and as soon as ghost starts laying the image down, put the drive back

in for everything to work properly.

This is clugy process and doesn't fly with several supports folks who

frequently image/reimage the machine.

I am basically looking for ideas on how to quickly handle this. I am

in the process of migrating Boot disk to WinPE which will let me

handle this type of stuff using vbscript but I need something in the

interim to handle this issue.

Does anyone know of way to programmaticaly handle this? using some bat

file, internal dos command or some dos utility

Recommended Posts