SCCM2012 R2 System deployment, client reported 0x80004005 error (1)

Error phenomena:

An error occured while retrieving the policy for this computer (0x80004005). For more information,contact your system Administra Tor or helpdesk operator.

through After PXE boot, after you enter the Task Sequence Wizard password, the 0x80004005 error is reported when the task sequence is scanned , and the client is restarted.

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/8C/27/wKiom1hjd5HzeIzgAAEKvdVtruM752.png-wh_500x0-wm_3 -wmp_4-s_1577854428.png "title=" 1.png "alt=" Wkiom1hjd5hzeizgaaekvdvtrum752.png-wh_50 "/>

Troubleshoot this issue from the following starting points:

2. software distribution account permissions.

4. The client NIC driver is properly bound.

6. Check that the client BIOS date time is synchronized with the SCCM site.

8. Check DNS, DHCP service is healthy

10. Check that the task sequence is configured correctly

Solution:

By checking that the first three items are normal, by pressing the F8 command in the PE environment, the discovery is DHCP, the DNS server points to an error. Because the wireless router in the network has DHCP enabled, it causes the bare metal to obtain an IP address from a non-line DHCP server when booting from PEX, rather than obtaining an IP address from the configured DHCP servers. Turn off the no-line by DHCP feature. Reboot bare metal through PEX boot, everything is OK.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M00/8C/27/wKiom1hjeArjOv7FAAQeex9sxys051.png-wh_500x0-wm_3 -wmp_4-s_1127798577.png "style=" Float:none; "title=" 2.png "alt=" Wkiom1hjearjov7faaqeex9sxys051.png-wh_50 "/>

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M01/8C/23/wKioL1hjeAzCTuf5AAOyHDsurms823.png-wh_500x0-wm_3 -wmp_4-s_3571505139.png "style=" Float:none; "title=" 3.png "alt=" Wkiol1hjeazctuf5aaoyhdsurms823.png-wh_50 "/>

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M02/8C/27/wKiom1hjeBfA62wAAAPFEoaN5r8139.png-wh_500x0-wm_3 -wmp_4-s_2993919494.png "style=" Float:none; "title=" 4.png "alt=" Wkiom1hjebfa62waaapfeoan5r8139.png-wh_50 "/>

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/8C/27/wKiom1hjeBrAwi5oAACbBbqgnz4674.png-wh_500x0-wm_3 -wmp_4-s_2040357465.png "style=" Float:none; "title=" 5.png "alt=" Wkiom1hjebrawi5oaacbbbqgnz4674.png-wh_50 "/>

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/8C/23/wKioL1hjeCbCJJFDAACeA3UGV6Q596.png-wh_500x0-wm_3 -wmp_4-s_73080212.png "style=" Float:none; "title=" 6.png "alt=" Wkiol1hjecbcjjfdaacea3ugv6q596.png-wh_50 "/>

This article from "The Light of Asia" blog, declined reprint!

SCCM2012 R2 System deployment, client reported 0x80004005 error (1)