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.
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.
I was recently trying to PXE build a machine and was getting the error “PXE-E52: proxyDHCP offers were received. No DHCP offers were received”
I checked the SMSPXE.log on my SCCM 2012 R2 Distribution point and I could see that the machine MAC address was in the log, but it wasn’t getting an IP. I checked the DHCP Scope in my DHCP Console for this particular VLAN and noticed this icon which meant “DHCP server alert. No addresses are available from server scopes because the maximum (100 percent) of the addresses allocated for use are currently leased. This represents a failure of the DHCP server on the network because it is not able to lease or service clients.” https://technet.microsoft.com/en-us/library/gg722802(v=ws.10).aspx
I increased the scope and now the machine could PXE boot successfully.
I was working on a server trying to install Windows Updates from Software Center. When installing anything in Software Center the status would change to failed.
I checked CAS.log in C:\Windows\CCM\CAS.log to see if it could find a distribution point and it had an error of “Failed to send Location Request Message”
I checked Configuration Manager client in Control Panel and there was no Assigned management point under the General tab.
I went back into C:\Windows\Logs and checked Locationservices.log and noticed “Failed to retrieve Default Management Points from lookup MP(s)”. Clientlocation.log showed “Unable to retrieve AD forest + domain membership”
When checking the network settings I realised there was an old DNS server set on this server. The old DNS server had been decomissioned. Once changing it to the new DNS server, I restarted “SMS Agent Host” service and after 5 minutes I could see the logs updating and everything looked ok. I could now install updates/software from the Software Center.
In my case it was DNS issues, but take a look into your network settings.
SCCM 2012 R2:
I had an issue today where a task sequence was failing on a particular machine with the error “Failed to get client identity (80004005)”. Other machines were building today with the same task sequence and PXE point.
First thing I checked before the machine restarted during the task sequence was the SMSTS.log by pressing F8. I loaded up CMtrace.exe in the cmd window and browsed to X:\Windows\Temp\SMSTS.log and the error in interest was Failed to get client identity (80004005)
After finding out a bit more information about the machine, I had heard that a Dell technician came out to replace the motherboard. Previously to that it was working. When checking out the BIOS settings I noticed that the date and time was incorrect. The date was set to 08/08/15 (MM/DD/YY) and time was set to 09:32:48PM. It is currently 03/08/2016 and 01:58PM. After setting the correct date and time in the BIOS and clearing the PXE flag the machine imaged successfully.
In my environment I import machines MAC address and machine name into a collection and have the task sequence advertised to that collection. I am not using unknown computer support.
I was trying to PXE boot a client and it kept failing. It would hang on:
Error: PXE-E53: No boot filename received
I initially thought it was a network problem and checked the network configuration on the switches and it was OK. I tested a few other machines and they were able to get an IP from DHCP then contact the PXE service point. So it had to be something linked to this particular client.
On my PXE service point I opened up the SMSPXE.log and searched for the MAC address of the problem client noticed this error:
MAC_ADDRESS: device is not in the database. SMSPXE
MAC_ADDRESS: Not serviced.
I deleted the client and re-imported the client into the collection and it could now PXE boot.
MAC_ADDRESS: device is in the database.
MAC_ADDRESS: using advertisement ZZZZZZZZ
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 ‘\\computername.domain.com: 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!