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
While in the middle of doing an SCCM 2007 to SCCM 2012 migration, my SCCM 2012 PXE Task Sequences would fail after the image had applied and the client was downloading and installing additional applications.
First thing I did before the image failed was to press F8 to load up a command prompt, then type in CMTrace so I could view the logs easily.
The log of interest was the cas.log which told me that the machine was unable to find any distribution points when locating the software. I knew the boundary was correct and that the boundary group was correct also.
The number of discovered DPs(including Branch DP and Multicast) is 0
Anyway, I double checked the boundary groups in SCCM 2012 and noticed that the SCCM 2007 running migration jobs automatically created a boundary group for the SCCM 2007 distribution point and assigned the boundaries I was using to it. This caused my clients unable to locate software to download and install additional programs.
I had migrated everything I needed from 2007 to 2012, so I simply stopped the 2007 migration job and deleted the automatically created 2007 boundary groups.
I then reimaged the machine and the cas.log looked good and could find the distribution point it needed to download the additional software for the Task Sequence.
I have had a few issues with the WDS service not starting on some of my distribution points.
One server was easily fixed by checking and fixing the permissions for the SYSTEM account for the C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 folder.
It needed to have Full Permissions to start. For some reason the permission was removed which caused the service to fail each time I started to fix it.
Another time I had this issue, it turned out to be a corrupt SQL computer account in the SCCM SQL database.
Each time I tried to start the WDS service under the System Account it would generate Failure Audit alerts in the Application Log:
Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Time: 1:00:00 PM
Login failed for user ‘Domain\ComputerAccount$’. [CLIENT: x.x.x.x]
I removed the login for ComputerAccount$ from the SQL Management Studio and re-created it with the same permissions and the WDS service can now start.
Disclaimer: This is what worked in my environment. It may not work in yours. Run at your own risk. I am not responsible for any issues it may cause. Modifying the database is not supported by Microsoft.
This was a strange issue which caused me a massive headache. I was unable to successfully PXE image any machine at my site. When trying to image, it would get the abortpxe message and not pick up the advertised Task Sequence.
In my environment, I do not have Unknown Computer support enabled. I have a collection and task sequences deployed to the collection as Required.
I could not clear the PXE flag on the machine in SCCM 2012 because the machine had not run the advertisement.
I confirmed the machines had a task sequence deployed to it. I tried different computers with different MAC addresses but it was the same issue.
I checked out smspxe.log on the site server and it said:
There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer.
Unspecified error (Error: 80004005; Source: Windows) TSPxe 7/04/2015 2:14:26 PM 872 (0x0368)
Again, I confirmed that the machines did in fact have a task sequence deployed to it as required. The machine was not picking up the policy from the management server. After a lot of research, I found there was a SQL query I could run on the site database which could find a Null entry (if it exists), which was blocking the machines from getting the policy. The query to run was:
SELECT * FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)
This returned a null entry. To remove it:
Delete FROM ResPolicyMap WHERE machineid = 0 and PADBID IN (SELECT PADBID FROM PolicyAssignment WHERE BodyHash IS NULL)
After this was removed, I restarted my Management Point I could now image again. What a lifesaver this script was!