Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Tuesday, March 1, 2016 2:16 PM
A few months back I tried to ready our SCCM 2012 R2 server for Windows 10 Deployment. Long story short, OSD broke completely. I was hoping that installing the new Current Branch version of Configuration Manager would fix things. No dice. I have the new, default boot images. Both X86 & X64 deployed and checked the box to deploy from PXE DP. Created and deployed new image from Win 10 WIM. Edited task sequence to use the new Boot Image. Still getting the following error.
File: \tmp\x86x64{randomcharactors}.bcd
Status: 0xc0000098
Info: The Windows boot configuration data (BCD) file from the PXE server does not contain a valid operating system entry. Ensure that the server has boot images installed for this architecture.
I've also tried disabling PXE on the DP, rebooting and re-enabling. No go. Also noticed the SMSPXE.log on the DP has not been updating in a long time.
Hope I've listed enough information that someone can point me in the right direction. THANKS!
Mike Pietrorazio
Thursday, March 31, 2016 2:39 PM ✅Answered
I've resolved this issue. In my case I had WDS installed on my SCCM server (Which is not a DP). When I uninstalled it, immediately PXE from the DP's began to work.
Mike Pietrorazio
Tuesday, March 1, 2016 2:34 PM
Hello
untick the enable PXE checkbox on the distribution point,that you want to remove the Windows Deployment service.
Remove boot images from your distribution point, then delete %windir%\temp
check with server manager. If WDS is done uninstalling there is a reboot pending. Reboot.
check if the remoteinstall folder is located on your system.
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.
reboot
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.
Also check the below link for related KB Articles
http://social.technet.microsoft.com/wiki/contents/articles/9539.sccm-2012-list-of-public-microsoft-support-knowledge-base-articles.aspx
Regards, Regin Ravi
Thursday, March 3, 2016 6:29 PM
I've done the following:
1. Removed PXE
2. Deleted the content of %windir%\temp
3. Deleted the remoteinstall folder
4. Rebooted
5 Added PXE again
6. Rebooted
I see the remoteinstall folder has been added again, but the WDS service won't start. Below is the event log.
Event ID: 513
Task Category: WDSServer
An error occurred while trying to initialize provider WDSMDMGR from C:\Windows\system32\wdsmdmgr.dll. Windows Deployment Services server will be shutdown.
Error Information: 0x3
Mike Pietrorazio
Thursday, March 3, 2016 10:03 PM
Just have a look at this post for more information: http://www.gerryhampsoncm.blogspot.nl/2013/02/sccm-2012-task-sequence-fails-with-bcd.html
-Go to the Properties of the DP and uncheck the box "Enable PXE support for clients"
-Wait for a short time while Windows Deployment Services uninstalls
-Reboot the DP
-Re-enable PXE support and wait while WDS re-installs
-WDS usually requires a reboot so you should reboot again
-Verify that the RemoteInstall folders have been populated
My blogs: Henk's blog | Follow Me on: Twitter | View My Profile on: LinkedIn
Friday, March 4, 2016 1:13 PM
As noted above, I've just done those steps but it has not worked. The WDS service still fails to start.
Mike Pietrorazio
Saturday, March 5, 2016 10:43 PM
1. Removed PXE
2. Wait for Windows Deployment Services uninstalls
3. Deleted the remoteinstall folder
4. Check if Windows Deployent Service uninstalled, and check if you have Windows Deployment Services Tools installed, if there is, uninstall it.
5. Rebooted
6. Added PXE again
7. Rebooted
Sandy
Saturday, March 5, 2016 10:46 PM
and this https://support.microsoft.com/en-us/kb/2712387
Sandy
Tuesday, March 8, 2016 12:40 PM
i had a similar type of problem, but it was related to my version of sccm. have a look at the following post if you have not solved your problem already:
Tuesday, March 8, 2016 12:45 PM
I finally got WDS running, but OSD is still not working. I've done the following.
Removed PXE
Manually uninstalled WDS
Rebooted
Renamed RemoteInstall folder
Manually installed WDS
Enabled PXE
Distributed Boot Images
Same problem
I've opened a case with Microsoft. Will report back.
Mike Pietrorazio
Wednesday, March 9, 2016 7:54 PM
Did you check the box "Enable PXE support for clients" again on boot images?
Why OSD isn't working? What's the message you are seeing?
My blogs: Henk's blog | Follow Me on: Twitter | View My Profile on: LinkedIn
Wednesday, March 16, 2016 2:06 AM
Dear Sir,
Have your issue been resolved now?
Best regards,
Jimmy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Wednesday, March 16, 2016 11:20 AM
No resolution yet. 1st level Microsoft support couldn't fix the problem. I'm being escalated to senior support now...
Mike Pietrorazio
Monday, March 21, 2016 6:22 PM
That BCD file is not from SCCM. The SCCM-generated BCD file path looks like SMSTemp\Date-Time{GUID}.boot.bcd.
You have another PXE server on your network that is responding to your clients. You need to disable or remove that other PXE server, or configure that other PXE server to allow the SCCM PXE server to respond first.
Thursday, January 12, 2017 6:51 PM
Just for future posterity...
In my case, I simply had all of my Boot Images disabled in WDS. Make sure you have at least one Boot Image Enabled (duh).