Deployment Solution

My question carries over from this topic which never got a concrete answer:

https://www-secure.symantec.com/connect/forums/disable-remove-boot-media-prompt

We build our machines via WinPE boot CD (not going to use PXE for various reasons that aren't applicable). The WinPE CD is that provided by Symantec. Deployment server version is 6.9 SP3.

We have 3 jobs that run in the pre-bootable environment, all using "Run Script" tasks:
1) Create Partitions (using diskpart)
2) Deploy image (a *.WIM file using imagex command line)
3) Update BCD (bcdboot.exe C:\Windows)

Every time the image has finished applying, the "Remove Boot Media" prompt appears and consequently cuts the connection to the deployment server, stopping the final job from running. Ultimately, this means when i reboot i get the "BOOTMGR is missing" (obviously, I never got to run the bcdboot command...) and when I launch back into WinPE to correct this, i get the prompt again (because it is already in deployment server) and will cut the connection again.

Is this a known bug in deployment server? I can't think of any time a *.IMG file had this issue, is it just *.WIM files? Is there anyway I can stop it doing this? Manually inputting the bcdboot command works fine but we don't want to do that for 4000+ devices!

Screenshot of prompt:

Any help would be appreciated as this is very annoying!

have u check the last task and see it didnt fail? is it set to execute in automation?

--Nelo

Yes, the job ran fine and the status code is 0. The job is set to run in automation mode. I know the job works as it applies the image fine and i can see all the windows system files if i open the admin command prompt and run a "dir" command.

Seriously baffling me now...

I really dont think it is the remove disk message.  I have imaged several computers with a WinPE boot disk and did not have issues.  Granted, I was using Rdeploy.  In my case, I added a power control task to reboot the computer after re-imaging.  If the computer was not set to boot from the CD-Rom, it worked correctly.  What is the ImageX command line(s) you are using?