Link to home
Start Free TrialLog in
Avatar of RhoSysAdmin
RhoSysAdminFlag for United States of America

asked on

SCCM current branch, Windows 10 OSD MDT 2013 task sequence fails to run - 0x80004005

We've just configured OSD on a new SCCM Current Branch 1706 server, following the steps laid out here -

https://www.windows-noob.com/forums/topic/14057-how-can-i-deploy-windows-10-with-mdt-2013-update-2-integrated-with-system-center-configuration-manager-current-branch/

We're using the Windows 10 LTSB N ISO.
We installed Windows ADK 1703, which is the correct release for SCCM 1706 and Windows 10 deployments.
We created the Windows 10 1703 boot image as described in the windows-noob article.

We testing a deployment of Windows 10 to a VM. The VM does PXE boot, and I confirmed it has an IP address.

I'm prompted to enter the PXE password, and then the TS times out trying to retrieve the "policy". Eventually I get the following error:

An error occurred while retrieving policy for this computer (0x80004005).

When I check the smsts.log file, the first error (red herring or not b/c there are other entries in the log file that seem to succeed) is:

ShellExecute ('raserver.exe') failed. 0x80070002.

I also see the following error later in the smsts.log file:

Error. Received 0x80072ee7 from WinHttpSendRequest

What I've confirmed so far:

- Network access account is setup and has permissions to all images and packages.
- Time on VM is synch'd when compared to SCCM server
- Anonymous Authentication is enabled in IIS on the SCCM server

The VM is using the E1000 network adapter. I was under the impression a Windows 10 ISO would include this rather generic driver. If my assumption is incorrect, any advice on where best to download the drivers?

The TS does not ever get started.  I don't have an easy way to provide the entire smsts.log file off this vm given its current state.

Where do I go from here?
ASKER CERTIFIED SOLUTION
Avatar of RhoSysAdmin
RhoSysAdmin
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of RhoSysAdmin

ASKER

Issue was networking, not SCCM