/build/static/layout/Breadcrumb_cap_w.png

ghost does not boot to the correct startup device

We are looking into using both Ghost and/or RIS for our deployment of WinXP.

I wondered if someone could help me with how to enforce ghost to boot into the correct bios setting at the correct time.

For instance, if I kick off a clone task and my 1st startup device is the hard disk, it boots into the hard disk and ignores the pxe boot.
If i choose a temporary startup device of the network, it then starts the pxe boot and installs the image correctly, reboots and carries out all of the sysprep commands and then completes. Ghost for some reason sais the job has failed, though it has completed successfully.

However, if I make the network the 1st startup device, and kick off a clone task, it then boots the machine and starts the image, however every reboot after this it continues to boot into pxe.

How can I set it, so that it only boots to the network card to kick off the image but then uses the hard disk for each subsequent reboot?

Also, on a seperate note we are using IBM S50's and S51's. Ghost does not detect the S50's at all, even though the network adapter (Intel pro 100) is available through ghost. We think this maybe a bios issue as it is different to that of the S51, but does anyone have any other ideas?

Thank you for your time,

Gareth.

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ