Tag Archives: SCCM 2012

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)

uefi2

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).

uefi3

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”

notbootablepartition

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.

PXE – PXE-E52: ProxyDHCP offers were received

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”

DHCP

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 DHCP 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.

LocationServices: Failed to retrieve Default Management Points from lookup MP(s)

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.

Task Sequence Failed – Failed to get client identity (80004005)

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.

Error: PXE-E53: No boot filename received

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:
DHCP….

Then

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.

SMSPXE.log:
MAC_ADDRESS: device is in the database.
MAC_ADDRESS: using advertisement ZZZZZZZZ

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 ‘\\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!

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.

ts1

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)

ts2ts3

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

ts4

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

ts5

ts6

ts7

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.

ts8

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.

ts10

I then deployed my Task Sequence as required

ts9

Creating the Hyper-V Gen 2 machine:

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

hyperv1

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

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

I am using 2GB for dynamic memory
hyperv4

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

I have left these settings as default
hyperv6

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

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
hyperv8

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

Select Import single computer
hyperv10

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

hyperv11

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)
hyperv12

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

hyperv14

hyperv15

Software updates not synchronizing – Sync failed: WSUS update source not found on site

I installed a trial of Configuration Manager 2016 Technical Preview 4 and set up and configured the Software Update point. I wasn’t able to synchronize any updates.

I checked wsyncmgr.log and saw Sync failed: WSUS update source not found on site
wsussource1

The workaround was to configure the Software Update Point and disable/remove all Classifications and Products and then to schedule another sync.

wsussource2
wsussource3
wsussource4

After this, I scheduled another sync, and the sync completed.

wsussource5

I then went back and re-configued the Software Update Point for the Classifications and Products I wanted, then scheduled another sync and it worked fine.

wsussource6

Software Update Compliance Issues – SCCM 2012

I had quite a few servers that were reporting incorrect compliance for Software Updates to our SCCM 2012 server. After doing Software Updates Scan Cycle on the client, the WUAHandler.log would always say successful. When doing a Software Updates Deployment Evaluation Cycle the log UpdatesDeployment.log said:

EnumerateUpdates for action (UpdateActionInstall) – Total actionable updates = 0

So if there were no updates available to be installed, why were my Software Update compliance reports showing the client as non-compliant and the Deployments in the Monitoring node in the console saying the client In Progress for a Software Update group deployment?

This blog post saved me http://blogs.technet.com/b/scotts-it-blog/archive/2015/02/23/refreshing-state-messages-in-system-center-configuration-manager-2012.aspx

This PowerShell script in the blog above forced my client to re-send its compliance to the SCCM 2012 server:

$SCCMUpdatesStore = New-Object -ComObject Microsoft.CCM.UpdatesStore
$SCCMUpdatesStore.RefreshServerComplianceState()

Then when checking UpdatesStore.log on the client:
Successfully raised Resync state message.
Resend status completed successfully.

I then checked the SCCM 2012 console in 15 minutes and the Deployments section in the Monitoring node showed the client as Successful instead of In Progress, and the SCCM 2012 update compliance reports showed the client as Compliant.