Using bood disk creator

Where does it stall?  Make sure the system has more then 256 mg of ram.

Hi,

After the first job runs it trys to boot again using DHCP, how do I tell it to either use the iso again.

Also does setting it to ramdisk solve the issue of reusing the iso?

If I understand correctly.

1. You created a WinPE automation boot disk with a static IP address

2. A job was assigned to a client, the client booted the iso created in step 1.  The job was executed.

3. A second job did not work because the boot disk (ISO) did not use the static IP address

right?

Any chances you are pointing to a different ISO? 

This could also happen if you have an embedded partition because the client goes into aumation again.

So when booting up change  the boot up sequance and have the CD/DVD to be the first boot. This way u make sure the right ISO booted.

Nelo

Exactly however it seems that it is picking dhcp even when the cd is before it.  It happens after the first job runs. The altiris client tells it to boot (bios) into automation which then it uses dhcp and pxe.  I want to tell it to boot into ramdisk or iso. Does that make sense?

So,

Change the boot order in the BIOS. Make CD/DVD be the first option, Hark Disk, an finally PXE boot last because it is not an option for u. Or press F12(dell) F9 (HP) when booting to pick the boot device?

Yeah I checked all that bios a stuff lready

Now it loads winpe then after it connects to altiris it stated to remove the boot media and reboot, then can not boot into anything, unless I mount the iso again.

Do you know how to create and load a boot disk on a local partition on the remote server? That may fix the issue