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
Michael
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
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
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 youActually 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.
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