PXE Boot TFTP error
EVERYTIME I reboot our SCCM server we are unable to image using PXE Boot. We are able to image from an in Windows advertisement however. Why does this continually happen? Below are the steps we take each time this error happens. Any help is appreciated, I am tired of this annoyance whenever we reboot. - Attempting to PXE boot; received the following error message - - - TFTP Download : smsboot\x64\pxeboot.com - Rebooted the server - Completed the following steps - taking the information from the log: Unable to delete folder C:\Windows\TEMP\PXEBootFiles\ (0x80070091) - opened Explorer and tried deleting the folder from Temp, i was unable - Stopped the "Windows Deployment Services Server" (WDSServer) service - tried deleting the folder again and was unable - it said I needed "TrustedInstaller" permissions - Modified the security permissions for the folder - - Changed Ownership to be "Administrators" - - Changed Administrators group to have Full access - - Forced the changes to all subfolders and files overwriting - Deleted the folder - Started the "Windows Deployment Services Server" (WDSServer) service - - the PXEBootFiles directory was recreated when the service started - I am now normally able to PXE Boot into the SCCM system - Sometimes I am stil unable to PXE boot - - - Went to the following folder - D:\RemoteInstall\SMSBoot\x64 - only contained the abortpxe file - - - Advised to copy the following folder from within SCCM "D:\RemoteInstall\Boot\x64" to D:\RemoteInstall\SMSBoot\x64 - Upon completion of copy we were successfully able to image. I am going to look into what this one [ http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/90308be3-81bc-462b-a014-a10e48452354 ] says, but does anyone have any insight for me?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 20th, 2011 9:18am

What version (SP level) are you running? Note that when you run a TS using a direct advert from Windows it doesn't use PXE at all so the two are completely unrelated.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 9:49am

What version (SP level) are you running? Note that when you run a TS using a direct advert from Windows it doesn't use PXE at all so the two are completely unrelated.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
January 20th, 2011 9:49am

I was aware of that they were separate (PXE and advertisement), but I didn't make that clear. Add/Remove Programs shows: Microsoft Configuration Manager 2007 Primary Site Microsoft Configuration Manager 2007 R2 (4.00.6355.1000) Help About System Center Configuration Manager says 4.00.6487.2000 I think that means we are SP2?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 9:55am

I was aware of that they were separate (PXE and advertisement), but I didn't make that clear. Add/Remove Programs shows: Microsoft Configuration Manager 2007 Primary Site Microsoft Configuration Manager 2007 R2 (4.00.6355.1000) Help About System Center Configuration Manager says 4.00.6487.2000 I think that means we are SP2?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 20th, 2011 9:55am

Tried removing the PXE by right clicking the pxe.msi and choosing Uninstall. Didn't seem to do anything, but then I went into SCCM and right clicked the PXE service point and chose Delete. Monitoring the PXESetup.log I got: <01-20-2011 09:50:27> ==================================================================== <01-20-2011 09:50:27> SMSPXE Setup Started.... <01-20-2011 09:50:27> Parameters: C:\PROGRA~2\MICROS~1\bin\i386\ROLESE~1.EXE /deinstall /siteserver:BASD-SCCM SMSPXE <01-20-2011 09:50:27> Deinstalling the SMSPXE <01-20-2011 09:50:27> No versions of SMSPXE are installed. Returning Success. <01-20-2011 09:58:14> Then I attempted to reinstall since it said it was actually already gone. I did so by adding the Role back to the server using the SCCM console. The PXESetup.log results are as follows: ==================================================================== <01-20-2011 09:58:14> SMSPXE Setup Started.... <01-20-2011 09:58:14> Parameters: C:\PROGRA~2\MICROS~1\bin\i386\ROLESE~1.EXE /install /siteserver:BASD-SCCM SMSPXE <01-20-2011 09:58:14> Installing Pre Reqs for SMSPXE <01-20-2011 09:58:14> ======== Installing Pre Reqs for Role SMSPXE ======== <01-20-2011 09:58:14> Found 1 Pre Reqs for Role SMSPXE <01-20-2011 09:58:14> Pre Req MSXML60 found. <01-20-2011 09:58:14> No versions of MSXML60 are installed. Would install new MSXML60. <01-20-2011 09:58:14> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <01-20-2011 09:58:14> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <01-20-2011 09:58:15> msxml6_x64.msi exited with return code: 0 <01-20-2011 09:58:15> msxml6_x64.msi Installation was successful. <01-20-2011 09:58:15> ======== Completed Installion of Pre Reqs for Role SMSPXE ======== <01-20-2011 09:58:15> Installing the SMSPXE <01-20-2011 09:58:15> Machine is running Windows 2003 SP1 or later. (NTVersion=0X601, ServicePack=0) <01-20-2011 09:58:15> WDS Service is installed. <01-20-2011 09:58:15> No versions of SMSPXE are installed. Installing new SMSPXE. <01-20-2011 09:58:15> Enabling MSI logging. pxe.msi will log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\pxeMSI.log <01-20-2011 09:58:15> Installing C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="C:\Program Files (x86)\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1 <01-20-2011 09:58:25> pxe.msi exited with return code: 0 <01-20-2011 09:58:25> Installation was successful. I then rebooted. Attempted PXE and it seems to be going to the WDS pxe instead of SCCM pxe if that makes any sense. How do I resolve that? Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 10:30am

I stopped and restarted the WDSServer service. Monitoring the SMSPXE.LOG I no longer see the Cannot delete C:\Windows\TEMP\PXEBootFiles\ message, but now I get: Failed to read PXE settings. The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 1/20/2011 10:31:06 AM 4436 (0x1154) Failed to read PXE settings. The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 1/20/2011 10:31:06 AM 4436 (0x1154) HELP! We are in the middle of deploying laptops and we are at a stand still... :-(Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 20th, 2011 10:38am

I stopped and restarted the WDSServer service. Monitoring the SMSPXE.LOG I no longer see the Cannot delete C:\Windows\TEMP\PXEBootFiles\ message, but now I get: Failed to read PXE settings. The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 1/20/2011 10:31:06 AM 4436 (0x1154) Failed to read PXE settings. The system cannot find the file specified. (Error: 80070002; Source: Windows) smspxe 1/20/2011 10:31:06 AM 4436 (0x1154) HELP! We are in the middle of deploying laptops and we are at a stand still... :-(Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 10:38am

____ I created this in the Software Distribution!!! Can a Moderator move this to the PXE section!?!Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 20th, 2011 10:39am

____ I created this in the Software Distribution!!! Can a Moderator move this to the PXE section!?!Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 10:39am

____ I created this in the Software Distribution!!! Can a Moderator move this to the PXE section!?! Done. Moved to OSD subforum ...
January 20th, 2011 10:55am

____ I created this in the Software Distribution!!! Can a Moderator move this to the PXE section!?! Done. Moved to OSD subforum ...
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 10:55am

OK, so I completed the following steps laid out here: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/8677d9f3-ea24-4586-94b3-80eda4bb8a18/ Remove the SMS PXE role. Look at the PXESetup.log file to verify that the uninstall is complete and successful. Uninstall the WDS server. Reboot the machine. Re-install the WDS server, but "do not configure it". Do nothing at all other than installing WDS. Add the SMS PXE role. Look at the PXESetup.log file to verify that the installation is complete and successful. Add the boot images to the SMS PXE DP share. Look at the distmgr.log file to verify that the replication of the boot image to the DP is complete and successful. Try booting a PXE client. I am now back to the normal SCCM PXE and not WDS, but I am still getting TFTP error. May need to just do the steps I mentioned to get things working and then continue this... Suggestions for resolving the original issue of the TFTP error everytime we reboot?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 20th, 2011 11:52am

OK, so I completed the following steps laid out here: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/8677d9f3-ea24-4586-94b3-80eda4bb8a18/ Remove the SMS PXE role. Look at the PXESetup.log file to verify that the uninstall is complete and successful. Uninstall the WDS server. Reboot the machine. Re-install the WDS server, but "do not configure it". Do nothing at all other than installing WDS. Add the SMS PXE role. Look at the PXESetup.log file to verify that the installation is complete and successful. Add the boot images to the SMS PXE DP share. Look at the distmgr.log file to verify that the replication of the boot image to the DP is complete and successful. Try booting a PXE client. I am now back to the normal SCCM PXE and not WDS, but I am still getting TFTP error. May need to just do the steps I mentioned to get things working and then continue this... Suggestions for resolving the original issue of the TFTP error everytime we reboot?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 11:52am

Bump! Anyone? This is a very annoying and inconvenient issue. By chance would this be resolved with the R3 release of configuration manager...I think that may have been released... Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 27th, 2011 2:32pm

Bump! Anyone? This is a very annoying and inconvenient issue. By chance would this be resolved with the R3 release of configuration manager...I think that may have been released... Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 2:32pm

checkout: http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspxtesgroup
January 28th, 2011 2:20am

checkout: http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx tesgroup I did the majority of this but I didn't delete the folder RemoteInstall when I reinstalled. I'll try that tomorrow morning. Thanks. I'll get back to you all tomorrow. Weather pending... Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2011 4:54pm

checkout: http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx tesgroup I did the majority of this but I didn't delete the folder RemoteInstall when I reinstalled. I'll try that tomorrow morning. Thanks. I'll get back to you all tomorrow. Weather pending... Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
January 31st, 2011 4:54pm

checkout: http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx tesgroup @tesgroup: This worked! I can now reboot and everything keeps running. From the article: In total there should only be four folders within the RemoteInstall folder as follows: SMSBoot SMSIMAGES SMSTemp Stores If additional folders exist in the RemoteInstall folder, such as: Boot Images Mgmt Templates Tmp WdsClientUnattend Mine contained the extra folders. Last time when I reinstalled I did not delete/rename the RemoteInstall folder. This time I did rename it as the article explains and it worked great. Renaming or deleting the RemoteInstall folder seemed to be the key. Also, on Step 3 of "How To Properly Install And Set Up A New Instance Of WDS And A PXE Service Point" it says, "3. If prompted to do so after WDS has finished installing, reboot the server." I was not prompted, but I ignored this and rebooted anyway. The first time I did not reboot after WDS installed and the RemoteInstall folder was not recreated after adding the PXE Service point back to SCCM. Second try I made sure to reboot anyway and everything worked out great. Thanks so much for your suggestions all! Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2011 11:10am

I have similar issue same above error but this error i am getting intermittent keeping trying 2 or 3 times i get F12 option to boot the network services TFTP PXE-T01 The specified file not found PXE-E3B TFTP Error : File not found Our environment have DHCP configured In Inflobox and the Primary site server and PXE DP server located in Same Subnet and configured 2008 R2 sp1 and configured SCCM2012 in VM environment I tried all the Options uninstall and re-install no luck and i have tried to increase Tramsmiit and recive Buffer size in lan card but the issue is not resolved. Capture smspxe log when it found boot image the pxe working ,when it not found getting TFTP error. SMSPxe log says no errors but getting client Pxe TFTP error file not found (Since its not looking Image throw out TFTP error) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777230" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:49D9F374-7606-4277-8AE9-FEE608FFB01E</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SGP20001" OfferIDTime="6/25/2012 11:09:00 AM" PkgID="SGP00009" PackageVersion="" PackagePath="http://XXX.company.com/SMS_DP_SMSPKG$/SGP00004" BootImageID="SGP00004" Mandatory="0"/></ClientIDReply> Client Identity: 9c7f0d6a-58dd-4cda-a4f0-3f66316067fb PXE::CBootImageManager::FindMatchingArchitectureBootImage Set media certificate in transport Set authenticator in transport SMSPxe log says no errors t i can able to do pxe Log found Boot image Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777230" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:49D9F374-7606-4277-8AE9-FEE608FFB01E</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SGP20001" OfferIDTime="6/25/2012 11:09:00 AM" PkgID="SGP00009" PackageVersion="" PackagePath="http://xxx.company.com/SMS_DP_SMSPKG$/SGP00004" BootImageID="SGP00004" Mandatory="0"/></ClientIDReply> Client Identity: 9c7f0d6a-58dd-4cda-a4f0-3f66316067fb PXE::CBootImageManager::FindMatchingArchitectureBootImage PXE::CBootImageManager::FindBootImage: SGP00004 Looking for bootImage SGP00004 PXE::CBootImageCache::FindImage PXE::CBootImageInfo::UpdateAccessTime Appreciate if you could provide some solution Ksrini
June 27th, 2012 3:50am

I have similar issue same above error but this error i am getting intermittent keeping trying 2 or 3 times i get F12 option to boot the network services TFTP PXE-T01 The specified file not found PXE-E3B TFTP Error : File not found Our environment have DHCP configured In Inflobox and the Primary site server and PXE DP server located in Same Subnet and configured 2008 R2 sp1 and configured SCCM2012 in VM environment I tried all the Options uninstall and re-install no luck and i have tried to increase Tramsmiit and recive Buffer size in lan card but the issue is not resolved. Capture smspxe log when it found boot image the pxe working ,when it not found getting TFTP error. SMSPxe log says no errors but getting client Pxe TFTP error file not found (Since its not looking Image throw out TFTP error) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777230" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:49D9F374-7606-4277-8AE9-FEE608FFB01E</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SGP20001" OfferIDTime="6/25/2012 11:09:00 AM" PkgID="SGP00009" PackageVersion="" PackagePath="http://XXX.company.com/SMS_DP_SMSPKG$/SGP00004" BootImageID="SGP00004" Mandatory="0"/></ClientIDReply> Client Identity: 9c7f0d6a-58dd-4cda-a4f0-3f66316067fb PXE::CBootImageManager::FindMatchingArchitectureBootImage Set media certificate in transport Set authenticator in transport SMSPxe log says no errors t i can able to do pxe Log found Boot image Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777230" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:49D9F374-7606-4277-8AE9-FEE608FFB01E</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="SGP20001" OfferIDTime="6/25/2012 11:09:00 AM" PkgID="SGP00009" PackageVersion="" PackagePath="http://xxx.company.com/SMS_DP_SMSPKG$/SGP00004" BootImageID="SGP00004" Mandatory="0"/></ClientIDReply> Client Identity: 9c7f0d6a-58dd-4cda-a4f0-3f66316067fb PXE::CBootImageManager::FindMatchingArchitectureBootImage PXE::CBootImageManager::FindBootImage: SGP00004 Looking for bootImage SGP00004 PXE::CBootImageCache::FindImage PXE::CBootImageInfo::UpdateAccessTime Appreciate if you could provide some solution Ksrini
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2012 11:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics