Hi, i have a client workstation that is encrypted using bitlocker. Suppose i send a WOL package to wake up this client and let it try to boot into PXE. While there is no OSD assignment the PXE server normally replies with "boot to next device in order". However because the client is bitlockered the booting OS is displaying a warning that the client is not booting in a normal way and that on site presence is nessecary to hit the enter key to proceed the boot process. The warning will not show up when the client first will reboot instead of trying to boot to next device. So my question is: Is it possible to configure the WDS/PXE server (or boot image) to let a client reboot instead of "boot to next device in order" when no assignment is available? regards

Hi Not a perfect answer but you could set up a "dummy task sequence" for the computer to boot into.Kind regards Tim Nilimaa IT Consultant at Mindgrape (Sweden) Please remember to mark this answer as helpful if it helped you.

hmm, so that would be a TS with a reboot command. That will require the client to download the complete WinPE boot image through TFTP. That will take a lot of time. However that could possible, but whenever i do want the client to boot to a OS deployment TS assignment the client would have two mandatory task sequences assigned to it. Then again i could create a dynamic collection for it that contain all resource records that are not assigned to a OS deployment. In that way all clients that will boot into PXE that are not targetted for any OS deployment. On the other hand, it would be much faster when WDS sends the reboot command instead of boot-to-next-device. Can i edit this behaviour in WDS? Where should i start? regards

Update.... So far i found a boot program that i took out of Windows Embedded 2009. This boot program, Reboot.com, let the device reboot when executed. I copied this file to the folder where abortpxe.com resides, renamed abortpxe.com to abortpxe.old and Reboot.com to abortpxe.com. Result is that the client will reboot instead of boot to next device. It works like a charm but it's not out of the box. Next problem will be that virtual pc configuration by default have PXE boot as the first option in BIOS and will result in infinite reboots when i implement Reboot.com. For this, i'm planning to let the virtual pc's PXE boot to a PXE server that contain the original abortpxe.com. We also considered changing BIOS settings to put PXE on top of the boot order. Unfortunatly it's not possible to change production pc's due to the lack of proper tooling (i.e. Dell CCTK) to do this. I would like to hear some opinions about this configuration. Regards