SCCM: Failed to Get Client Identity (80004005)

2

This morning, one of my customers called me and told me that they bought some new Lenovo laptops (Lenovo ThinkPad S540), but they was unable start OS Deployment using SCCM/PXE.

Normally when I see this behaivor, it’s caused by a missing driver in the boot image, so I told them to verify that the driver was loaded correct.

Here is a guide to verify the network driver in a SCCM Boot Image:
https://www.ronnipedersen.com/2009/04/importing-network-drivers-into-the-windows-pe-boot-image/

But the driver was loaded correct, so I requested the SMSTS.log and found another common issue.

The SMSTS.log file can be found here:
https://www.ronnipedersen.com/2014/08/sccm-2012-r2-smsts-log-located/

In the SMSTS.log we got the following message:
Failed to get client identity (80004005)” and “Failed to request for client

image

Resolution

Normaly this problem is caused by the incorrect time on the client, and in this case the BIOS time on the client was 1 hour ahead of the SCCM Site server.

After changing the BIOS time on the client, it could be deployed successfully.

Update!

Normally this is a rare situation, but if you experience this on many client in your environment, you might want to automate this completely. A fellow MVP Niall Brady has a great blog post that explains how this can be done by adding a prestart command to your boot image :

http://www.windows-noob.com/forums/index.php?%2Ftopic%2F11016-how-can-i-sync-the-bios-date-in-winpe-to-avoid-pxe-boot-failure-with-system-center-2012-r2-configuration-manager%2F

 

/Enjoy.

+Ronni Pedersen


About Author

My name is Ronni Pedersen and I'm currently working as a Cloud Solution Architect at EG A/S in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

2 Comments

Leave A Reply