AliG Posted December 19, 2012 Posted December 19, 2012 Our SCCM 2012 PXE is broken again. I had trouble back in April and spent days on it and I have sepnt all this week trying to get it working again. The SMSBOOT folders X86/X64 are not getting poulated either.I have tried reloading the boot disks but get this - failed to copy G:\RemoteInstall\SMSTempBootFiles\0010008E\WINDOWS\Boot\PXE\pxeboot.com to G:\RemoteInstall\SMSBoot\x86\pxeboot.com SMSPXE 19/12/2012 14:37:39 1692 (0x069C) InstallBootFilesForImage failed. 0x80070003 SMSPXE 19/12/2012 14:37:39 1692 (0x069C) Warning: Failed to copy the needed boot binaries from the boot image G:\RemoteInstall\SMSImages\0010008E\winpe.0010008E.wim. The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 19/12/2012 14:37:39 1692 (0x069C) Failed adding image G:\RemoteInstall\SMSImages\0010008E\winpe.0010008E.wim. Will Retry.. The system cannot find the path specified. (Error: 80070003; Source: Windows) SMSPXE 19/12/2012 14:37:39 1692 (0x069C) I have tried all sorts with the help of the goggle and i'm pulling my hair out!
AliG Posted December 19, 2012 Author Posted December 19, 2012 @TheScarfedOne got any ideas for me? being the SCCM expert! I'm almost at the point of thinking of reformating the server and starting over!
bandgeekmafia78 Posted December 19, 2012 Posted December 19, 2012 Should there be a space between 00100008E and .wim?
TheScarfedOne Posted December 19, 2012 Posted December 19, 2012 Hello!! Someone call for me! LOL Ive seen some odd things with PXE before like this in both 2007 and 2012. Each time, Ive unticked the "PXE" support and checked the event log to make sure its removed. Reboot the server, and then check the box again which will trigger the installation of it.
AliG Posted December 20, 2012 Author Posted December 20, 2012 Update- Looks like this update broke my sccm pxe update installed on 13/12/12 Microsoft Update KB2506143 (Windows Management Framework 3.0) that was released by Microsoft on 12/12/2012 Spent many hours trying to fix it and may have to call MS and try and use one of my EES/ Technet Direct calls to hopefully fix it! I'm so angry!!!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now