PXE Service Point not working after everytime PXE server restarted
Hi, Everytime the PXE service point/sccm server being restarted, then it wont be working anymore. It has the error as following:- PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389.
November 19th, 2009 9:30am

verify if the Windows Deployment Services service has started, if not, start it, if you are running Server 2008 you can set that service to start with a Delayed start cheers niallmy SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 10:15am

Hi, The WDS is started. Why do I need to start with delayed start? Could you please explain more to me? I see this errors on the smspxe.log, what's the problem? Mutex was not owned. Now have ownership. smspxe 19/11/2009 3:29:08 PM 4640 (0x1220) Unable to delete file C:\Windows\TEMP\PXEBootFiles\Windows\Boot\EFI\bootmgfw.efi (0x80070005). Retry after 1 seconds smspxe 19/11/2009 3:29:19 PM 4640 (0x1220)
November 19th, 2009 11:37am

if the service is started then nothing to worry about, as regards the smspxe.log error does it succeed in deleting the file later in the log ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 12:35pm

But then the SMSboot\x86 & SMSboot\x64 folder doesn't contain any boot files. So in another words, PXE is not working.
November 19th, 2009 2:05pm

Have you added those boot images to the PXE service point? That doesn't happen automatically.
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 2:15pm

Hi, yes, I added the boot images, but after the server restarted, those files no longer there.
November 19th, 2009 3:47pm

Are you saying that, before a restart the SMSboot\x86 folder on you psp server contains 10 files and then after you reboot the server those files are gone?
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2009 4:48pm

Yes. that's what I meant
November 19th, 2009 6:24pm

Hi, I have set the services to delayed start, first time reboot, the pxe service point still responding. second time reboot, the pxe service point not working anymore. Any idea?
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 12:20pm

Hi have you tried removing the PXE service point role and then reinstalling it?
November 23rd, 2009 12:23pm

Hi, Yes, I tried many times. But I dont think this is the solution as it's very troublesome to remove and install again everytime reboot.
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 12:49pm

what errors are you seeing in event viewermy SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
November 23rd, 2009 1:01pm

Hi, These are the error in event viewer. By the way WDS is started after these error message. ======================================================== An error occurred while trying to initialize the Windows Deployment Services image server. Error Information: 0xC1030104 ======================================================== On 23/11/2009 6:13:01 PM, component SMS_PXE_SERVICE_POINT on computer SCCM reported: PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389. Possible cause: PXE service point is not started or not responding. Solution: Manually restart the PXE service point. Possible cause: WDS service is not responding. Solution: Manually restart the WDS service.
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 1:21pm

what type of hardware is this server, its possible that its doing so many things that starting the wds service just takes more time than it has... hence the delayed start my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
November 23rd, 2009 3:21pm

Hi, Intel 2.40GHz, 64 bit OS, 4GB memory and It's on Hyper-V. The server is SCCM Server as well with MP, DP, RP & etc. Will it be better if I put SMS Executive & SMS Site Components Manager service to "delayed start"? and the WDS services configured as "automatic start"?
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 3:33pm

i wouldnt do that, find out what is the bottleneck on the server, is it running SQL as well ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
November 23rd, 2009 3:42pm

No, it's not running SQL, SQL is on remote server.
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 3:49pm

Does that help? http://maijen.nl/index.php?option=com_content&view=article&id=73:sccm-2007-r2-smsboot-files-disappear-after-reboot&catid=31:microsoft-sccm&Itemid=64
November 23rd, 2009 3:57pm

Hi Torsten, Thank you very much. I believe it helps as in my logs it was written, right after I rename the folder, it copy the files to the SMSBoot. But I just couldn't delete the old C:\Windows\TEMP\PXEBootFile-old folder and can't change the permission. Perhaps I need to stop the WDS before I change the permission of the old folder? Mutex was not owned. Now have ownership. smspxe 19/11/2009 3:29:08 PM 4640 (0x1220) Unable to delete file C:\Windows\TEMP\PXEBootFiles\Windows\Boot\EFI\bootmgfw.efi (0x80070005). Retry after 1 seconds smspxe 19/11/2009 3:29:19 PM 4640 (0x1220)
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2009 6:00pm

try it and if it still wont let you uninstall the PSP role, try again, then add them back *wds and psp*my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
November 23rd, 2009 6:12pm

Hi, I stop the WDS services before I restart the server, then I tried to delete the pxebootfile folder, but access denied for bootmgfw.efi file. I renamed the folder and restart the server. Then the WDS and PXE is working fine after reboot as it manage to copy the files to the temp folder. Anyway I couldn't reset the permission as access denied to bootmgfw.efi file. Is there anyway to reset the permission by forcing? Anyway the solution of this is for everytime reboot, we have to do this? Or one time task only?
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2009 3:53pm

Ah yes, 16389... that's a good one. Players: Windows 2008 SP2 Virtual Machine as Central/Primary Site Server hosting the DB Windows 2008 SP2 Virtual Machine as WDS & DHCP to add PSP Rules of Conduct: 1.) When WDS & DHCP are on the SAME SERVER as the PSP, you must configure WDS first you will find much documentation that says you do not need to configure WDS for PSP & this is true. However, this is NOT true when WDS & DHCP are the same box. Why? You need to set certain DHCP & Firewall options to integrate DHCP & WDS on the same box: SCCM is not aware of the DHCP being on the same server as the WDS. Dont worry you CAN configure it first! 2.) With the necessary Windows Server Roles enabled (App, DHCP, IIS, WDS) and a reboot just for good measure, configure the WDS server. Select the defaults & make sure to check both boxes to ensure the 60 PXE setting in DHCP & the firewall port get set correctly. 3.) Now install your PSP roles using the computer account on completion, WDS will not start & youll get a bunch of error logs in your SCCM consoles & in the SMSPXE.log on the target PS system under %ISNTDIR%\SMS_CCM\logs 4.) Per some instructions I read, I changed the PSP DB connection account to the SQL DB service account that failed. However, it started to become clear from SMSPXE.log that the issue was access related i.e.: the database. 5.) For sanity, I created an Ad-Hoc SCCM_WDS_PXE_DB account & copied whatever database roles were associated with PSPs computer account. 6.) With the roles created in the DB, I changed the PSPs run as permissions from SCCM. 7.) On the WDS server, I started the WDS service & opened the SMSPXE.log 8.) Eight is Great Everything Worked Yippy Skippy Why does this happen? When the remote computer attempts to contact the SQL server, it logs on using NETWORK SERVICE\Anonymous account which fails, of course. Since SCCM typically only uses computer accounts, we have to specify an account that has DB access for this service, in this case the AdHoc account that we created. Need to learn more about SCCM, R2, SP2, PXE, DHCP, WDS, MDT, or WMI? Check out our company blog at logisci.com/blogMark West MCSE
December 8th, 2009 12:18am

i like point 1) above. Do you have a Technet reference to confirm it ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2009 12:36am

Hi, Intel 2.40GHz, 64 bit OS, 4GB memory and It's on Hyper-V. The server is SCCM Server as well with MP, DP, RP & etc. Will it be better if I put SMS Executive & SMS Site Components Manager service to "delayed start"? and the WDS services configured as "automatic start"? For me the solution on a Hyper-V configuration was: Assign a physical hard disc to the virtual machine and do not use an .vhd as drive. Reinstall the server. I used: Windows Server 2008 R2 SP1 (Release candidate) SQL 2005 SP3 SCCM 2007 SP2 R3 AIK for Windows 7. Hope this was helpfull. Freek Abels
December 2nd, 2010 9:05am

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

Other recent topics Other recent topics