Search the Community

G'day, I followed the guides to set up an MDT Task Sequence in SCCM 2012 and Distributed it to my different DPs which already have WDS and are in production. Currently we do imaging via creating large wim files and network booting however I'd like to move to imaging via SCCM task sequence to apply drivers / applications / os updates. The Task Sequence has been deployed to the Unknown Computers group and a few test groups, but the generally preferred method of imaging is user driven ie technicians booting into windows pe and selecting an image (or, moving forward, a task sequence). The MDT bootable wim that has been setup to lead into the task sequence doesn't show up when booting into winpe, and if I manually import it into the wds server it will show up and launch into the task sequence environment but the computer restarts after sitting at the blank screen for a minute. Is there any way to force a pre-existing wds distribution point to use an mdt created boot sequence? Allow clients to connect anonymously and enable unknown computer support are both enabled on the DP --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- I turned off PXE boot and turned it back on, seems to have changed things for the better. It's not working yet, but it now boots differently. I get a screen that says "Downloaded WDSNBP from IP The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID 4 Message from Administrator: Please Wait. SMS is looking for policy Contacting Server IP TFTP Download smsboot\x64\abortpxe.com PXE boot aborted. Booting to the next device PXE-M0F: Exiting Intel Boot Agent Selected boot device failed. Press any key to reboot the system" Approvals aren't required for the task sequence/pxe boot. The workstation has no agent/is unknown to SCCM, and the task sequence is deployed to the Unknown Systems group ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- DHCP is on a separate server than DP with WDS in smspxe.log I'm getting the following errors: InstallBootFilesForImage failed 0x800040005 Warning: Failed to copy the needed boot binaries from the boot image S:\RemoteInstall\SMSImages\ABC00001.wim\boot.ABD00001.wim The operation completed successfully (Error 00000000; Source: Windows) Failed adding image S:\RemoteInstall\SMSImages\ABC00001.wim\boot.ABD00001.wim. Will retry.. Unspecified Error --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Found part of the problem, the laptop I'm testing with has a different computer name than what's registered with its MAC address in SCCM. SO I added the wrongly named workstation that has the right MAC in SCCM to the group that the task sequence is being deployed to and now my error message returned is slightly different "Downloaded WDSNBP from IP The details below show the information relating to the PXE boot request for this computer. Please provide these details to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID 4 Message from Administrator: Please Wait. SMS is looking for policy Contacting Server IP TFTP Download smsboot\x64\pxeboot.com Press F12 for network service boot PXE-M0F: Exiting Intel Boot Agent Selected boot device failed. Press any key to reboot the system" Rebooted and hit F12 this time before it moved on to PXE-M0F error Now it boots into a blank Microsoft | Solution Accelerators screen for awhile and then reboots without beginning the task sequence Any ideas?