SCCM Client Stuck in Unprovisioned State After OSD

[Andrew Wells]

So I have an odd scenario that recently popped up where some clients are not provisioning after moving to Windows 10, build 1607 via a wipe and install Task Sequence. The clients will have the correct site code and assigned management point in the Control Panel applet, but if you check under the Actions tab, only Machine Policy Retrieval & Evaluation Cycle and User Policy Retrieval & Evaluation Cycle are listed. This doesn't happen on all computers, but seems to be isolated to computers that had previously been on Windows 7 and were active SCCM clients before the update to Windows 10. ClientLocation.log shows the correct AD site for the computer and the AD site is in the proper boundary group. Also, LocationServices.log shows the correct info. To further confound the issue, the PolicyAgent.log shows that the client is successfully is requesting a policy assignment. Where I do see problems is in the attached DataTransferService.log, where it tries to download the policy files from the MP. The BITS job looks like it's timed out, and if I run Get-BitsTransfer -AllUsers on one of these devices, it shows a few BITS jobs in an error state. Any suggestions?

DataTransferService.log

Edited July 24, 2017 by Andrew Wells