BIOS and UEFI Co-Existence - Revision history

Necros: /* Using Linux DHCP */ left brace missing

2020-02-08T10:25:15Z

‎Using Linux DHCP: left brace missing

Wayne-workman.28155: /* Step 3 */

2017-04-18T00:41:51Z

‎Step 3

Wayne-workman.28155: /* Step 3 */

2016-11-24T18:02:48Z

‎Step 3

Wayne-workman.28155: /* Using Windows Server 2012 (R1 and later) DHCP Policy */

2016-11-23T18:22:29Z

‎Using Windows Server 2012 (R1 and later) DHCP Policy

Wayne-workman.28155: /* Using Windows Server 2012 (R1 and later) DHCP Policy */

2016-11-23T18:22:02Z

‎Using Windows Server 2012 (R1 and later) DHCP Policy

Wayne-workman.28155: /* Step 3 */

2016-11-23T17:41:43Z

‎Step 3

Wayne-workman.28155: /* Step 3 */

2016-11-23T17:41:00Z

‎Step 3

Wayne-workman.28155: /* Step 3 */

2016-11-23T17:40:36Z

‎Step 3

Wayne-workman.28155: /* Using ProxyDHCP (dnsmasq) */

2016-10-12T17:06:21Z

‎Using ProxyDHCP (dnsmasq)

Wayne-workman.28155: /* Using Windows Server 2012 (r1 and later) DHCP Policy */

2016-10-02T16:11:33Z

‎Using Windows Server 2012 (r1 and later) DHCP Policy

@@ Line 40: / Line 40: @@
           filename   "ipxe32.efi";
+      }
-      else
+      else {
           # default to EFI 64 bit
           filename   "ipxe.efi";

← Older revision		Revision as of 00:41, 18 April 2017
Line 256:		Line 256:

	"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.		"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.
		+
		+	"PXEClient:Arch:00007:UNDI:003016" should get "ipxe7156.efi" this file is specific to the Surface Pro 4.

	In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.		In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.

← Older revision		Revision as of 18:02, 24 November 2016
Line 256:		Line 256:

	"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.		"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.
−
−	~~"PXEClient:Arch:00000" should be given "undionly.kkpxe" or some other legacy boot file that works for most of your computers.~~

	In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.		In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.

@@ Line 225: / Line 225: @@
 = Using Windows Server 2012 (R1 and later) DHCP Policy =
-The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting (without these already set, these steps will not result in success). The below DHCP policy will only apply to UEFI based network booting. Regular BIOS based network booting will still use the default scope options set in the scope.
+The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting (without these already set, the below steps will not result in success). The below DHCP policy will only apply to UEFI based network booting. Regular BIOS based network booting will still use the default scope options set in the scope.
 You may substitute whatever Vendor Class Identifier you need in the ASCII field on step 3.

@@ Line 225: / Line 225: @@
 = Using Windows Server 2012 (R1 and later) DHCP Policy =
-The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting. The below DHCP policy will only apply to UEFI based network booting. Regular BIOS based network booting will still use the default scope options set in the scope.
+The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting (without these already set, these steps will not result in success). The below DHCP policy will only apply to UEFI based network booting. Regular BIOS based network booting will still use the default scope options set in the scope.
 You may substitute whatever Vendor Class Identifier you need in the ASCII field on step 3.

← Older revision		Revision as of 17:41, 23 November 2016
Line 257:		Line 257:
	"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.		"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.

−	"PXEClient:Arch:00000" should be given "undionly.kkpxe" or some other legacy boot file that works for most of your computers. In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.	+	"PXEClient:Arch:00000" should be given "undionly.kkpxe" or some other legacy boot file that works for most of your computers.
		+
		+	In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.

← Older revision		Revision as of 17:41, 23 November 2016
Line 258:		Line 258:

	"PXEClient:Arch:00000" should be given "undionly.kkpxe" or some other legacy boot file that works for most of your computers. In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.		"PXEClient:Arch:00000" should be given "undionly.kkpxe" or some other legacy boot file that works for most of your computers. In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.
−
−	~~<font color="red">'''END NOTE'''</font>~~

@@ Line 252: / Line 252: @@
 <font color="red">'''NOTE:'''</font>
 There are many other UEFI architectures besides just "PXEClient:Arch:00007".
 "PXEClient:Arch:00002" and "PXEClient:Arch:00006" both should get "i386-efi/ipxe.efi" as their option 067 boot file.
 "PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.
 "PXEClient:Arch:00000" should be given "undionly.kkpxe" or some other legacy boot file that works for most of your computers. In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.
 <font color="red">'''END NOTE'''</font>

← Older revision		Revision as of 17:06, 12 October 2016
Line 206:		Line 206:

	= Using ProxyDHCP (dnsmasq) =		= Using ProxyDHCP (dnsmasq) =
		+
		+	Related article: [[ProxyDHCP with dnsmasq]]

	There are powerful matching rules in dnsmasq's configuration syntax. Here is an example of how this could be used to distingush between BIOS and UEFI. '''Note: This will NOT work in proxy mode!!'''		There are powerful matching rules in dnsmasq's configuration syntax. Here is an example of how this could be used to distingush between BIOS and UEFI. '''Note: This will NOT work in proxy mode!!'''

@@ Line 221: / Line 221: @@
   dhcp-boot=tag:efi64,ipxe.efi,x.x.x.x,x.x.x.x            # x.x.x.x = TFTP/FOG server IP
-= Using Windows Server 2012 (r1 and later) DHCP Policy =
+= Using Windows Server 2012 (R1 and later) DHCP Policy =
 The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting. The below DHCP policy will only apply to UEFI based network booting. Regular BIOS based network booting will still use the default scope options set in the scope.