Category Archives: Task Sequence

PXE – TFTP Download: smsboot\x64\pxeboot.n12 ……….

This happened in a SCCM 2012 R2 SP1 CU3 environment:

When Deploying an OSD task sequence via PXE, at the PXE boot screen the client was stuck on PXE – TFTP Download: smsboot\x64\pxeboot.n12 ……….

First thing I checked was the smspxe.log on the distribution point. I could see it was in a loop with the line “Looking for bootImage XXX00AA1”


In the ConfigMgr console, I checked Monitoring\Distribution Status\Content Status and verified that the boot image was successfully distributed to the distribution point. It was, but obviously there is an issue.

I went to Administration\Overview\Distribution Points and selected the distribution point having the issue, clicked on Content tab, typed in the boot image name or package ID and clicked Redistribute. Once the boot image had redistributed successfully, I cleared the PXE flag and PXE booted the client again.

It was able to successfully boot and run the Task Sequence.


Task Sequence has failed with the error code (0x00000001) – UEFI/BIOS

When imaging a Dell Venue machine using BIOS firmware (instead of UEFI), the task sequence failed with the below error:

Task Sequence has failed with the error code (0x00000001) – UEFI/BIOS

When viewing the smsts.log I saw:

Marking partitions active is only supported for MBR disks.
Unable to activate partition (0x80004001)
Failed to make volume C:\ bootable. Code 0x80004001.

Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Not implemented (Error: 80004001; Source: Windows)


I checked the Task Sequence, and there was only a step to format the disk as UEFI. The boot mode on the Dell Venue was set to Legacy/BIOS. You can see in the Task Sequence below, the Disk Type is GPT (which is UEFI).


After setting the Dell Venue to UEFI firmware and booting from the NIC, the disk was formatted and the Task Sequence did not fail.

Task Sequence – Failed to make volume C:\ bootable Error: 80004005 – Hyper-V

When imaging a new Generation 1 Hyper-V Server 2008 R2 machine, the task sequence would fail. The smsts.log showed “Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Error: 80004005”


I tried using CMD support (F8) in WinPE and using diskpart to make the partition active/format the disk and run the Task Sequence again, but the same issue.

This fix was an easy one. I just deleted the virtual hard disk (vhdx) and created an other one, cleared the PXE flag and it re-imaged successfully. Not sure what was wrong with the original VHDX file. It still appeared as a C:\ with files in there.

Task Sequence failed 0x87d00269

Task sequence failing with error code: 0x87d00269

I had a remote machine that kept failing its task sequence. I was able to get a copy of the smsts.log from and saw these errors:

Policy Evaluation failed, hr=0x87d00269
MP list missing in WMI after policy evaluation, sending message to location service to refresh client, retriev MP list and try again.
Install Dynamic application action failed to install application: ‘AppName’. Error Code 0x87d00269

When the machine was rebooted it wasn’t joined to the domain. I could login as local admin, then I checked out the C:\Windows\debug\NetSetup.log to see why it failed joining the domain.

The log was filled with these errors:
NetpGetComputerObjectDn: ldap_compare_s failed: 0x20 0x2
NetpCreateComputerObjectInDs: NetpGetComputerObjectDn failed: 0x2
NetpProvisionComputerAccount: LDAP creation failed: 0x2
NetpProvisionComputerAccount: Cannot retry downlevel, specifying OU is not supported
ldap_unbind status: 0x0
NetpJoinDomainOnDs: Function exits with status of: 0x2
NetpJoinDomainOnDs: status of disconnecting from ‘\\ 0x0
NetpDoDomainJoin: status: 0x2

These errors mean that the OU the machine tried to domain is invalid. Double check your task sequence and make sure that it isn’t set to put the machine in the default Computers container in AD. In my case, someone had renamed the OU in AD so of course it was invalid!

Hyper-V Gen 2 Machine – Deploying Windows 10 test

I have a Hyper-V lab set up with a VM running a DC with DHCP, a VM with SCCM Technical Preview 4 and SQL 2012 SP1, and will be testing deploying Windows 10 eval to a Hyper-V Generation 2 VM

Getting Started…

I have made sure that my DP can respond to PXE requests. In my case, I am not using unknown computer support as I will import the MAC address of my hyper-v machine into a collection where I have deployed my task sequence to as required.


I have gone to the Software Library node and made a copy of the install.wim to my machine. (install.wim is from the sources directory on the iso for Windows 10)


After I added my Windows 10 .wim I distributed it to my DP.Now I will be creating my very basic task sequence.


I will be using an existing image package that I created before.




Make note here I haven’t selected a Domain OU. This will put the computer in the default Computers container. If you specify the default Computers container, the Task Sequence will fail.


I left all other options as default. I then right clicked on my Task Sequence and clicked edit, I added the variable below so my installation of Windows 10 will use C:\ rather than X:\ for the drive letter where the OS will be installed.


I then deployed my Task Sequence as required


Creating the Hyper-V Gen 2 machine:

Right click on your Hyper-V host and select New Virtual Machine


Click next at Before you begin screen
Enter the name of your Virtual Machine

I am going to deploy a Windows 10 machine so I selected Generation 2

I am using 2GB for dynamic memory

I have made a Private virtual switch so only my VM’s can communicate (Domain controller, SCCM server and this)

I have left these settings as default

I will be installing the image via PXE so I have ticked the last checkbox
Then click Finish

I then turned on my virtual machine and turned it off. This is because I have a Dynamic MAC Address. If you check the Networking tab you can see it has created the MAC address. We will import this MAC address into SCCM to deploy the image

In the SCCM 2012/Technical Preview console, Select “Import Computer Information” to import the MAC address of the VM created

Select Import single computer

Type in the name of the computer and MAC address and click Next then Next again.


Select to add new computers only to the All Systems collection and keep clicking next until the end of the wizard

In the All Systems collection, I will add the new computer into my collection where I have deployed the task sequence to as Required (Win10Deployment)

Once my collection where I have the task sequence to has updated, I will power on my VM to download the image.