PXE booting with new UEFI thin clients - Revision history

Pburns at 17:34, 3 December 2019

2019-12-03T17:34:47Z

← Older revision		Revision as of 17:34, 3 December 2019
Line 1:		Line 1:
			[[Category:ThinManager]]
			[[Category:PXE]]

	Many new thin clients use the new '''Unified Extensible Firmware Interface''' (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.		Many new thin clients use the new '''Unified Extensible Firmware Interface''' (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.

Pburns at 17:30, 3 December 2019

2019-12-03T17:30:40Z

← Older revision		Revision as of 17:30, 3 December 2019
Line 1:		Line 1:
	Many new thin clients use the new '''Unified Extensible Firmware Interface''' (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.		Many new thin clients use the new '''Unified Extensible Firmware Interface''' (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.

	Using UEFI for PXE boot:		'''Using UEFI for PXE boot:'''
	* The UEFI boot requires ThinManager 11 or later.		* The UEFI boot requires ThinManager 11 or later.
	* The UEFI boot requires Firmware Package 8.1.10 or later.		* The UEFI boot requires Firmware Package 8.1.10 or later.

Pburns at 17:30, 3 December 2019

2019-12-03T17:30:08Z

← Older revision		Revision as of 17:30, 3 December 2019
Line 10:		Line 10:
	=== Mixing PXE Boot with UEFI Boot ===		=== Mixing PXE Boot with UEFI Boot ===

	If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.		If you are using the ''Use standard DHCP server with Boot Options (PXE Disabled)'' then the ''Option 67'' in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.

	See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.		See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.

Pburns at 17:27, 3 December 2019

2019-12-03T17:27:22Z

← Older revision		Revision as of 17:27, 3 December 2019
Line 12:		Line 12:
	If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.		If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.

	~~1 See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.~~		See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.

	2 See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.

	~~3 https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf~~

	~~4 ===<font color="green">For details on setting up Vendor Classes for UEFI boot see [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf]</font>===~~

	~~5 https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf~~

Pburns at 17:26, 3 December 2019

2019-12-03T17:26:56Z

← Older revision		Revision as of 17:26, 3 December 2019
Line 12:		Line 12:
	If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.		If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.

	See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.		1 See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.

	See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.		2 See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.

	https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf		3 https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf

	===<font color="green">For details on setting up Vendor Classes for UEFI boot see [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf]</font>===		4 ===<font color="green">For details on setting up Vendor Classes for UEFI boot see [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf]</font>===

	https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf		5 https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf

Pburns at 17:26, 3 December 2019

2019-12-03T17:26:20Z

← Older revision		Revision as of 17:26, 3 December 2019
Line 14:		Line 14:
	See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.		See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.

	See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf] for details on setting up Vendor Classes for UEFI boot.		See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf Configuring Windows DHCP for UEFI] for details on setting up Vendor Classes for UEFI boot.

	https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf		https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf

Pburns at 17:24, 3 December 2019

2019-12-03T17:24:44Z

← Older revision		Revision as of 17:24, 3 December 2019
Line 11:		Line 11:

	If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.		If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.

	See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.		See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.

			See the attachment [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf] for details on setting up Vendor Classes for UEFI boot.

			https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf

	===<font color="green">For details on setting up Vendor Classes for UEFI boot see [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf]</font>===		===<font color="green">For details on setting up Vendor Classes for UEFI boot see [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf]</font>===

	https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf		https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf

Pburns at 17:23, 3 December 2019

2019-12-03T17:23:27Z

← Older revision		Revision as of 17:23, 3 December 2019
Line 1:		Line 1:
	Many new thin clients use the new Unified Extensible Firmware Interface (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.		Many new thin clients use the new '''Unified Extensible Firmware Interface''' (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.

	Using UEFI for PXE boot:		Using UEFI for PXE boot:
	The UEFI boot requires ThinManager 11 or later.		* The UEFI boot requires ThinManager 11 or later.
	The UEFI boot requires Firmware Package 8.1.10 or later.		* The UEFI boot requires Firmware Package 8.1.10 or later.
	Port UDP-4011 needs to be opened on the ThinManager Server		* Port UDP-4011 needs to be opened on the ThinManager Server
	The thin client Boot options in the BIOS of the thin client need to be set to Boot from LAN or PXE Boot		* The thin client Boot options in the BIOS of the thin client need to be set to Boot from LAN or PXE Boot
	The Secure Boot needs turned off in the thin client BIOS.		* The ''Secure Boot'' needs turned off in the thin client BIOS.

	Mixing PXE Boot with UEFI Boot		=== Mixing PXE Boot with UEFI Boot ===

	If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.		If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.
	See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.		See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.

			===<font color="green">For details on setting up Vendor Classes for UEFI boot see [https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf]</font>===

			https://kb.thinmanager.com/images/2/2f/ConfiguringWindowsDHCPServerForUEFI_02.pdf

Pburns: Created page with "Many new thin clients use the new Unified Extensible Firmware Interface (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardwa..."

2019-12-03T17:18:11Z

Created page with "Many new thin clients use the new Unified Extensible Firmware Interface (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardwa..."

New page

Many new thin clients use the new Unified Extensible Firmware Interface (UEFI) instead of the older Basic Input/Output System (BIOS). ThinManager 11 will handle the new hardware.

Using UEFI for PXE boot:
The UEFI boot requires ThinManager 11 or later.
The UEFI boot requires Firmware Package 8.1.10 or later.
Port UDP-4011 needs to be opened on the ThinManager Server
The thin client Boot options in the BIOS of the thin client need to be set to Boot from LAN or PXE Boot
The Secure Boot needs turned off in the thin client BIOS.

Mixing PXE Boot with UEFI Boot

If you are using the Use standard DHCP server with Boot Options (PXE Disabled) the Option 67 in the DHCP server requires different filenames. This requires configuration of the DHCP Server with different Vendor Classes to handle the different filenames. The options where ThinManager provides the PXE information do not require this extra configuration step.
See the attachment ConfiguringWindowsDHCPServerForUEFI_02.pdf for details on setting up Vendor Classes for UEFI boot.