SOLVED SCCM 2012 R2 OSD PXE fails with 0xc0000001

[Sarnizzzle]

Hi, I am a fairly new SysAdmin and was tasked with image deployment through SCCM 2012 I have been trying to learn and absorb as much as i can. until i ran into the below issue.

Presently i have an issue deploying a Win 7 X64 image via PXE through SCCM. I had an issue previously where i had to inject LAN drivers for the workstation PXE booting to download the Boot image but now its not even doing that. when the workstation PXE boots it gets hung at loading files...

IP: x.x.x.x, File: \SMSImages\AUR00061\winpe.AUR00061.wim

Then Errors out stating "windows Failed to start" with "Status:0xc0000001" never getting to the WINPE environment or the Task Sequence.

when i looked up the SMSPXE log i see the below:

Prioritizing local MP http://116216-xxxxx.xxxxx.xxxxx.com. SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
00:23:24:B1:21:4E, 2E751A84-0D3C-11E6-8C0E-0D21DA901E00: device is not in the database. SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Prioritizing local MP http://116216-xxxxx.xxxxx.xxxxx.com. SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Prioritizing local MP http://116216-xxxxx.xxxxx.xxxxx.com. SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>cd22fa5c-6864-4611-840c-0055252b8df5</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="AUR2004A" OfferIDTime="6/3/2016 12:18:00 PM" PkgID="AUR00065" PackageVersion="" PackagePath="http://116216-xxxxx.xxxxx.xxxxx.com/SMS_DP_SMSPKG$/AUR00061" BootImageID="AUR00061" Mandatory="1"/></ClientIDReply>
SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
00:23:24:B1:21:4E, 2E751A84-0D3C-11E6-8C0E-0D21DA901E00: using advertisement AUR2004A SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Looking for bootImage AUR00061 SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Prioritizing local MP http://116216-xxxxx.xxxxx.xxxxx.com. SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Prioritizing local MP http://116216-xxxxx.xxxxx.xxxxx.com. SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
Report Body: <ReportBody><ClientID>cd22fa5c-6864-4611-840c-0055252b8df5</ClientID><StateMessage MessageTime="20160603191153.000000+000" SerialNumber="1"><ClientID>cd22fa5c-6864-4611-840c-0055252b8df5</ClientID><Topic ID="PXE Boot Adv Status" Type="600" IDType="600"/><State ID="100" Criticality="0"/><UserParameters Flags="32" Count="4"><Param>00:23:24:B1:21:4E</Param><Param>2E751A84-0D3C-11E6-8C0E-0D21DA901E00</Param><Param>AUR2004A</Param><Param>AUR</Param></UserParameters></StateMessage></ReportBody>
SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)
00:23:24:B1:21:4E, 2E751A84-0D3C-11E6-8C0E-0D21DA901E00: Updating Device Cached LastAdv Time. Time=03/06/2016 19:11:53 LastAdvID=AUR2004A SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)File E:\RemoteInstall\SMSTemp\2016.06.03.13.20.49.08.{EEE560B6-578F-4CB2-81CB-CAC645BC6A40}.boot.bcd deleted. SMSPXE 6/3/2016 2:13:24 PM 4728 (0x1278)
File E:\RemoteInstall\SMSTemp\2016.06.03.13.20.49.08.{EEE560B6-578F-4CB2-81CB-CAC645BC6A40}.boot.bcd.log deleted. SMSPXE 6/3/2016 2:13:24 PM 4728 (0x1278)
File E:\RemoteInstall\SMSTemp\2016.06.03.13.20.49.0002.{EEE560B6-578F-4CB2-81CB-CAC645BC6A40}.boot.var deleted. SMSPXE 6/3/2016 2:13:24 PM 4728 (0x1278)

I think it has something to do with:

"Looking for bootImage AUR00061 SMSPXE 6/3/2016 2:11:53 PM 2128 (0x0850)"

but i couldn't find anything relating to that error other than a thread where a guy said after mounting a background image to his boot image it worked (tried that too and it didnt work for me)

Ive tried the below

1) Uncheck the enable PXE option on the distribution point. Answer yes that you want to remove the Windows Deployment service.
2) Remove boot images from your distribution point
3) After few minutes delete %windir%\temp
4) If WDS is uninstalled correctly, reboot the server.
5) Check if the remoteinstall folder is located on your system. If it is delete it. If it fails to delete due to permission issues with the SMSTempBootFiles path, delete all folders except that one and then rename the remoteinstall folder something else.
6) Reboot the server.
7) Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remoteinstall folder reappears..
Replicate the boot image to the DP again. After they land you can try running an F12 and it should roll smoothly.

after no success i tried

removing Boot images from DP
Re-adding them
Rebuilding Boot images
injecting drivers to boot images
making sure all content is distributed to the DP
creating new Task Sequences

and still no luck. i have about 60 new workstations that need to get imaged within a week and would appreciate any help anyone can provide. thank you in advance!

 

[Nem]

These issues are almost always permission issues or about missing files because of permissions.
1) I'd check to see if your network access account is working.
2) Verify that your PXE image is actually in the DPs. Did you add the SCCM sever computer account to the DP admin accounts?
3) Test the PXE on the same subnet as the server. Make sure your IP helpers are working on other vlans if they are not on the same subnet.
4) Create a PXE bootable media and put it on a usb drive. Use it to get an F8 command prompt. Then ping your DPs to verify the image can see and talk to the servers.
5) Firewall issues? Might want to turn them off while trouble shooting.
6) You can also check site status under the monitoring for site role issues.
Upgrading your SCCM server to 1511 or 1602 can fix a lot of issues.

 

[Prajwal Desai]

Unchecking PXE, multicast > rebooting the server > enabling PXE and multicast on DP fixed the issue for me.