PXE boot now requires F12 intervention
I have been using SCCM in testing for about a month.
Everything has been going fine up until the other day.
When i send Images to machines via Task Sequence the machine bootsinto PXE, but before it goes in itrequires users to press F12 to enter thenetwork service boot.

I haven't changed anything for this to start appearing
Is there anything that has happened, or something i can do to change this, as it defeats the whole remote deployment concept.

Cheers
February 6th, 2009 4:36am

Advertisements must be mandatory for PXE to auto F12.. If you just advertise the TS F12 will be necessary... If you use WDS without PSP you must point to the n12 boot file to disable the need to press F12

Michael
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2009 5:45am

Here's a link to managing the netwrk boot program (NBP) in WDS that Michael mentions above:http://technet.microsoft.com/en-us/library/cc732351.aspx.
February 6th, 2009 2:44pm

If you rename the "pxeboot.n12" to "pxeboot.com", this stops the "press F12" request.

Check your smsboot\x86, smsboot\x64 and smsboot\ia64 for the "pxeboot.com" files. Each share contains both a pxeboot.com and pxeboot.n12 file. Swapping the file extensions, like i said, negates the need to press F12. No idea if this is a supported switch, though.
  • Proposed as answer by Derek Gary Thursday, May 09, 2013 6:34 PM
Free Windows Admin Tool Kit Click here and download it now
February 9th, 2009 2:34am

Excellent

I check the task sequence i had created in SCCM and it wasn't mandatory.
I was getting lazy and going straight to completion without selecting the mandatory assignment.

Cheers
February 10th, 2009 4:15am

I marked Michael's response as the answer to your question.
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2009 9:52am

Actually Michaels response is not the only way to bypass pressing F12 twice during SCCM PXE boot.

One way to bypass it is to set your OSD task sequence Advertisement to Mandatory which can be very very dangerous if you have inexperienced SCCM admins working in your environment, so I would definitely advise against it.

Better option in my opinion is as follows:

1) If you installed your SCCM Site server on C:\ drive then go to C:\RemoteInstall\SmsBoot. If your SCCM Site is installed on some other drive than go to the root of that drive and locate "RemoteInstall\SmsBoot" folder.

2) Once you located your folder in there you will find 3 folders and some files, and we are only interested in two of those folders, and that is X64 and X86.

3) Go to "RemoteInstall\SmsBoot\X64" and Rename pxeboot.com to pxeboot.com.old

4) In the same folder rename pxeboot.n12 to pxeboot.com

5) In the same folder rename pxeboot.com.old back to pxeboot.n12

6) now go to "RemoteInstall\SmsBoot\x86 and repeat the same rename operation that you did in two previous steps.

Once you are done, you can test your PXE boot and you should find that now after pressing F12 once and choosing your NIC boot you will not be prompted to press F12 for the second time.


  • Edited by Hooba Wednesday, October 30, 2013 7:46 PM
  • Proposed as answer by UKHC Tuesday, November 12, 2013 6:23 PM
October 30th, 2013 7:44pm

Actually Michaels response is not the only way to bypass pressing F12 twice during SCCM PXE boot.

One way to bypass it is to set your OSD task sequence Advertisement to Mandatory which can be very very dangerous if you have inexperienced SCCM admins working in your environment, so I would definitely advise against it.

Better option in my opinion is as follows:

1) If you installed your SCCM Site server on C:\ drive then go to C:\RemoteInstall\SmsBoot. If your SCCM Site is installed on some other drive than go to the root of that drive and locate "RemoteInstall\SmsBoot" folder.

2) Once you located your folder in there you will find 3 folders and some files, and we are only interested in two of those folders, and that is X64 and X86.

3) Go to "RemoteInstall\SmsBoot\X64" and Rename pxeboot.com to pxeboot.com.old

4) In the same folder rename pxeboot.n12 to pxeboot.com

5) In the same folder rename pxeboot.com.old back to pxeboot.n12

6) now go to "RemoteInstall\SmsBoot\x86 and repeat the same rename operation that you did in two previous steps.

Once you are done, you can test your PXE boot and you should find that now after pressing F12 once and choosing your NIC boot you will not be prompted to press F12 for the second time.


This works perfectly. Thank you
Free Windows Admin Tool Kit Click here and download it now
November 12th, 2013 6:24pm

Hello
I have the following issue :
I 'm testing a zti installation
all is ok but when I clear requirement pxe deployxement
when i boot my windows machine each time he try ro tun
the n12 file. but he keep asking me to press on f12 ...
( i have renamed the file in the boot /x64 folder
my pc are x64 and i change the dhcp option to point to x64 folder
tks

tks for your help
July 21st, 2015 9:47am

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

Other recent topics Other recent topics