Sccm ошибка 80004005

Let’s see how you can FIX SCCM Task Sequence Error 0x80004005. You might encounter a prompt message An error occurred while retrieving policy for this computer during Operating System Deployment with SCCM Task Sequence.

The Task Sequence Error 0x80004005 is generic, and the solution could be different based on the details you get into logs.

We onboarded a new hardware model directly to the Configuration Manager with a MAC address in this scenario. We added a newly imported computer to a collection for deploying operating systems to the computer. After initiating the deployment, at the initial stage, it gets failed with the task sequence Error 0x80004005.

It’s always recommended to examine the SMSTS log for task sequence failure issues to help you get the inside about the failure prompt to troubleshoot the task sequence error 0x80004005. We have a lot of coverage related to OSD troubleshooting within HTMD community posts.

• FIX: SCCM Task sequence has failed with the error code 0x80070057
• Easily FIX SCCM Task Sequence Unable to find a volume Error Code 0x80070490
• Deploy Microsoft Edge WebView2 Using SCCM ConfigMgr

Issue Summary

This error appears at the initial stage when you have started the deployment. Task Sequence fails with the following error message –

An error occurred while retrieving policy for this computer (0x80004005). For more information, contact your system administrator or helpdesk operator.

In this scenario, Task Sequence terminated at the beginning. You will collect the logs at WinPE x:windowstempsmstslogsmsts.log. To get the command prompt window, you have to press F8 key.

More you can explore SCCM OSD Task Sequence Troubleshooting Steps by Step Ultimate Guide SMSTS.log. Here’s the highlight from the SMSTS.log –

• Error. Status code 404 – (Not Found)
• Decoding failed (0x8009310b). Assuming not encoded.
• BOM not found on policy reply
• Failed to download policy AP32080B-AP300A0E-6F6BCC28 (Code 0x80004005).

<![LOG[Error. Status code 404 - (Not Found) returned]LOG]!><time="16:19:15.950-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="libsmsmessaging.cpp:10121">
<![LOG[Found a secure policy.]LOG]!><time="16:19:15.950-480" date="08-24-2021" component="TSMBootstrap" context="" type="1" thread="1612" file="libsmsmessaging.cpp:5186">
<![LOG[Trying to decode policy.]LOG]!><time="16:19:15.950-480" date="08-24-2021" component="TSMBootstrap" context="" type="1" thread="1612" file="libsmsmessaging.cpp:5188">
<![LOG[CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=8009310b (..windes.cpp,451)]LOG]!><time="16:19:15.950-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="windes.cpp:451">
<![LOG[Decoding failed (0x8009310b). Assuming not encoded.]LOG]!><time="16:19:15.950-480" date="08-24-2021" component="TSMBootstrap" context="" type="1" thread="1612" file="libsmsmessaging.cpp:5208">
<![LOG[BOM not found on policy reply]LOG]!><time="16:19:15.950-480" date="08-24-2021" component="TSMBootstrap" context="" type="2" thread="1612" file="libsmsmessaging.cpp:5351">
<![LOG[hr, HRESULT=80004005 (..libsmsmessaging.cpp,5373)]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="libsmsmessaging.cpp:5373">
<![LOG[oPolicy.RequestPolicy((GetPolicyFlags() & POLICY_SECURE) != 0, (GetPolicyFlags() & POLICY_COMPRESS) != 0), HRESULT=80004005 (..tspolicy.cpp,2577)]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="tspolicy.cpp:2577">
<![LOG[Failed to download policy AP32080B-AP300A0E-6F6BCC28 (Code 0x80004005).]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="3" thread="1612" file="tspolicy.cpp:2577">
<![LOG[(*iTSPolicyAssignment)->GetObjects(pszClassName, aTSPolicyObjectArray ), HRESULT=80004005 (..tspolicy.cpp,1574)]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="tspolicy.cpp:1574">
<![LOG[m_pPolicyManager->GetObjects( TS::Policy::TaskSequence::GetClassName(), TS::Policy::TaskSequence::GetPolicyCategory(), TS::Policy::TSPolicyAssignment::POLICY_TS_FOR_CD_AND_PXE, aTSPolicyObjectArray ), HRESULT=80004005 (tsmediawizardcontrol.cpp,1196)]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="tsmediawizardcontrol.cpp:1196">
<![LOG[Failed to get all CCM_TaskSequence objects]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="3" thread="1612" file="tsmediawizardcontrol.cpp:1196">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="tsmediawizardcontrol.cpp:1455">
<![LOG[pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (tsmediawelcomepage.cpp,304)]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1612" file="tsmediawelcomepage.cpp:304">
<![LOG[Setting wizard error: An error occurred while retrieving policy for this computer  (0x80004005). For more information, contact your system administrator or helpdesk operator.]LOG]!><time="16:19:26.970-480" date="08-24-2021" component="TSMBootstrap" context="" type="0" thread="1432" file="tsmediawizardcontrol.cpp:1646">

FIX – SCCM Task Sequence Error 0x80004005 Failed to run while retrieving policy

Let’s check the solution to fix this task sequence error 0x80004005 –

• Launch SCCM Console, Navigate to Assets and Compliance > Devices.
• Look for the device, Remove the device entry from the SCCM Console.

Note – Collect the SMBIOS GUID for a device under the Summary tab in SCCM Console. To get SMBIOS GUID in a machine, Open the command prompt, Run command: wmic csproduct get uuid

SMBIOS is the GUID stored in the device BIOS or UEFI. It’s unique to the device, and SCCM uses it to recognize imported computers. Collect the information as stated above. This time add a computer with the SMBIOS GUID information, import the computer with SMSBIOS GUID, and complete the wizard.

You should add a newly imported computer to a collection. This allows you to create advertisements for deploying operating systems to the computer immediately.

Once you are done with the above steps, Please wait to advertise the computer information. Restart the target machine and reinitiate the task sequence deployment. It should continue without any errors.

For PCs that do not successfully boot from PXE, the SMSPXE.log on the server hosting the PXE Service Point can be examined for the PC’s SMBIOS GUID. The line that contains this information will be something as follows:

MAC=<Mac_Address> SMBIOS GUID=<SMBIOS_GUID> > Device found in the database. MacCount=x GuidCount=y

To obtain the SMBIOS GUID from a PC having the problem, use one of the below methods:

At a command prompt, run the command:
wmic
When the promptwmic:rootcli>appears, type in the command:
csproduct get uuid

The SMBIOS GUID for the PC should be displayed. For Example – 4C4C4544-0032-5610-8037-C8C04P604A63

Let us know your experience with the error code and how you were able to fix it in the comment section.

About Author -> Jitesh has over 5 years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10/11 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.

Resources

• OSD Known Issues Troubleshooting Guide |SCCM |ConfigMgr
• ConfigMgr OSD Troubleshooting Known Issues Guide Part 2 | SCCM
• FIX: SCCM Task Sequence Failed to load class properties 0x80041002 (2147749890)
• FIX: SCCM Task sequence has failed with the error code 0x800700A1

Back to top button

• 1) Check your Distribution Point self-signed certificate hasn’t expired:

  Text

  Administration > Distribution Points > Properties of DP
  

  Check the expiration date. If it’s expired, simply create a new certificate and update all of your boot images to the DP.

  2) BIOS date/time on the client. Ensure it’s correct.

  If points 1 and 2 are OK, I’d try recreating the boot media just in case.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Make sure you do not have an existing record of this computer in AD or already in SCCM. If so delete it and retry.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Pastebin is blocked at my work. Can you attach the log as a .txt file?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Looks like this line is the culprit:

  Text

  line 1063: <![LOG[Process completed with exit code 2147500037]LOG]!><time="20:55:03.324+480" date="03-17-2017" component="TSManager" context="" type="1" thread="1436" file="commandline.cpp:1124">
  

  A quick google of that exit code: https://ardamis.com/2015/11/07/troubleshooting-sccm-2012-task-sequence-failures/ Opens a new window

  What is this task sequence supposed to do?

  My task sequences are limited to clean installs of Windows 10; and one that I got from TechNet to upgrade Win7 to Win10 when it first came out.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• First rule of SCCM: use CMTrace.exe to review your logs.

  Second rule of SCCM: use CMTrace.exe to review your logs.

  

  0x80004005 is the worst generic error code because it doesn’t actually mean anything.  Whenever that pops up, you have to roll up your sleeves and prepare for a long day of investigating and testing.

  First place I would look is to verify your disk partitioning task sequences.

  EDIT: I didn’t realize that screen cap would be so awful.  Here are the two lines that caught my eye that should start your investigation:

  • System partition not set
  • Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned. Unspecified error (Error: 80004005; Source: Windows)

  All the other errors that follow cascade from that initial failure.

  
  2 found this helpful
  thumb_up
  thumb_down
  

• 

  Thank you all for your suggestions, In digging through them, I found that my VM that I used to build and capture the image was set to Legacy instead of EFI. I am going to rebuild the image capture VM with this setting corrected. I will report back with my findings.

  Thank you again.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Make sure you select the correct Image Index as well. That has burned me before.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Jeremy9642 wrote:

  Thank you all for your suggestions, In digging through them, I found that my VM that I used to build and capture the image was set to Legacy instead of EFI. I am going to rebuild the image capture VM with this setting corrected. I will report back with my findings.

  Thank you again.

  Boom.  Disk partition type conflict in the TS.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  After rebuilding the image on a EFI VM the issue has been resolved.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I changed the secure boot option to disabled, then change UEFI only to both and that resolved my issue.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• The fix for me was creating a default TS to «Deploy and existing image»… I then manually recreated all the partition settings in my custom TS, copying the default, and it worked like a charm!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

Below are the locations the log file will be in depending on what stage the TS is at:

During OS Deployment

Before your hard drive is formatted and partitioned

X:windowstempsmstslog

After your hard drive is partitioned formatted

X:smstslog and then is in C:_SMSTaskSequencelogssmstslog

Within Windows

Within Windows before the SCCM agent is installed:

C:_SMSTaskSequencelogssmstslog

Within Windows after the SCCM agent installed:

C:windowssystem32ccmlogssmstslog

When the Task Sequence completes on a x86

C:windowssystem32ccmlogs

For x64 Systems

C:windowsSysWOW64ccmlogs

You will need to enable your boot.wim with f8 support to retrieve the log if it bombs out before apply OS stage so that you can bring up the command prompt and copy the log to a share on the network.

Skip to content