Setting up MDT/WDS for UEFI/Legacy Images & Network Boots
-
Alright guys, I spent about 6 hours this week trying to get my MDT/WDS combo server to load up our Surface 4's with a 1607 Windows 10 image. Reason being is because as many of you know the BIOS for the Surface 4 only allows UEFI booting... I crawled quite a few forums and found nothing that ultimately was able to help me so I figured I'd write it up for Mango.
I have both my DHCP servers configured with the following roles:
60 PXEClient | Value: PXEClient
066 Boot Server Host Name | Value: 10.1.1.10 (Yes, it's static)
067 Bootfile Name | Value: smsboot\x64\wdsmgfw.efiAlso, I did have to add an ip helper on my VLAN in order to get this to work the following command was ran via SSH:
ip helper-address 10.1.1.10 69
The command allows TFTP traffic to be allowed to/from 10.1.1.10. You also need to make sure the following ports are open on your server:
UDP:
67
68 (Only if DHCP authorization is required on the server)
69
4011
Random ports from 64001 through 65000*, to establish a session with the server for TFTP and multicasting
Random ports from 64001 through 65000*, to establish a session with the server for TFTP and multicastingAlso, make sure via WDS>DHCP that you have "Do not listen on DHCP ports" checked.
After this was done I continued to fiddle in frustration with DHCP roles for about 30 minutes until I got the config I stated above.
After you complete these steps WDS will fully support both UEFI booting and imaging.
-
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Alright guys, I spent about 6 hours this week trying to get my MDT/WDS combo server to load up our Surface 4's with a 1607 Windows 10 image. Reason being is because as many of you know the BIOS for the Surface 4 only allows UEFI booting... I crawled quite a few forums and found nothing that ultimately was able to help me so I figured I'd write it up for Mango.
I have both my DHCP servers configured with the following roles:
60 PXEClient | Value: PXEClient
066 Boot Server Host Name | Value: 10.1.1.10 (Yes, it's static)
067 Bootfile Name | Value: smsboot\x64\wdsmgfw.efiTwo questions... why are you using option 060 if you are already using 066 and 067? Second is where did you even find information on the boot file name? I thought it was supposed to be boot\x64\wdsnbp.com
-
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Alright guys, I spent about 6 hours this week trying to get my MDT/WDS combo server to load up our Surface 4's with a 1607 Windows 10 image. Reason being is because as many of you know the BIOS for the Surface 4 only allows UEFI booting... I crawled quite a few forums and found nothing that ultimately was able to help me so I figured I'd write it up for Mango.
I have both my DHCP servers configured with the following roles:
60 PXEClient | Value: PXEClient
066 Boot Server Host Name | Value: 10.1.1.10 (Yes, it's static)
067 Bootfile Name | Value: smsboot\x64\wdsmgfw.efiTwo questions... why are you using option 060 if you are already using 066 and 067? Second is where did you even find information on the boot file name? I thought it was supposed to be boot\x64\wdsnbp.com
Pretty sure boot\x64\wdsnbp.com only supports legacy network boots.
I only have 60 configured because it was stated in quite a few places to support UEFI. -
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Alright guys, I spent about 6 hours this week trying to get my MDT/WDS combo server to load up our Surface 4's with a 1607 Windows 10 image. Reason being is because as many of you know the BIOS for the Surface 4 only allows UEFI booting... I crawled quite a few forums and found nothing that ultimately was able to help me so I figured I'd write it up for Mango.
I have both my DHCP servers configured with the following roles:
60 PXEClient | Value: PXEClient
066 Boot Server Host Name | Value: 10.1.1.10 (Yes, it's static)
067 Bootfile Name | Value: smsboot\x64\wdsmgfw.efiTwo questions... why are you using option 060 if you are already using 066 and 067? Second is where did you even find information on the boot file name? I thought it was supposed to be boot\x64\wdsnbp.com
Pretty sure boot\x64\wdsnbp.com only supports legacy network boots.
I only have 60 configured because it was stated in quite a few places to support UEFI.Weird... ok so the first response I can understand. The second one, 060 has been used for some time. Now if you use WDS-only I see people only use 060 and not 066 or 067, so it's not really a newer concept to use 060. UEFI is a newer concept though, and apparently requires all 3 options... So is 060 an older way to configure DHCP options, but has always worked with UEFI? When I say "older" I really mean 2008 compared to 2012 R2 since UEFI came out around 2005.
-
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Alright guys, I spent about 6 hours this week trying to get my MDT/WDS combo server to load up our Surface 4's with a 1607 Windows 10 image. Reason being is because as many of you know the BIOS for the Surface 4 only allows UEFI booting... I crawled quite a few forums and found nothing that ultimately was able to help me so I figured I'd write it up for Mango.
I have both my DHCP servers configured with the following roles:
60 PXEClient | Value: PXEClient
066 Boot Server Host Name | Value: 10.1.1.10 (Yes, it's static)
067 Bootfile Name | Value: smsboot\x64\wdsmgfw.efiTwo questions... why are you using option 060 if you are already using 066 and 067? Second is where did you even find information on the boot file name? I thought it was supposed to be boot\x64\wdsnbp.com
Pretty sure boot\x64\wdsnbp.com only supports legacy network boots.
I only have 60 configured because it was stated in quite a few places to support UEFI.Weird... ok so the first response I can understand. The second one, 060 has been used for some time. Now if you use WDS-only I see people only use 060 and not 066 or 067, so it's not really a newer concept to use 060. UEFI is a newer concept though, and apparently requires all 3 options... So is 060 an older way to configure DHCP options, but has always worked with UEFI? When I say "older" I really mean 2008 compared to 2012 R2 since UEFI came out around 2005.
I personally don't know the answer. This is the first time I ever touched DHCP role 60.
-
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Alright guys, I spent about 6 hours this week trying to get my MDT/WDS combo server to load up our Surface 4's with a 1607 Windows 10 image. Reason being is because as many of you know the BIOS for the Surface 4 only allows UEFI booting... I crawled quite a few forums and found nothing that ultimately was able to help me so I figured I'd write it up for Mango.
I have both my DHCP servers configured with the following roles:
60 PXEClient | Value: PXEClient
066 Boot Server Host Name | Value: 10.1.1.10 (Yes, it's static)
067 Bootfile Name | Value: smsboot\x64\wdsmgfw.efiTwo questions... why are you using option 060 if you are already using 066 and 067? Second is where did you even find information on the boot file name? I thought it was supposed to be boot\x64\wdsnbp.com
Pretty sure boot\x64\wdsnbp.com only supports legacy network boots.
I only have 60 configured because it was stated in quite a few places to support UEFI.Weird... ok so the first response I can understand. The second one, 060 has been used for some time. Now if you use WDS-only I see people only use 060 and not 066 or 067, so it's not really a newer concept to use 060. UEFI is a newer concept though, and apparently requires all 3 options... So is 060 an older way to configure DHCP options, but has always worked with UEFI? When I say "older" I really mean 2008 compared to 2012 R2 since UEFI came out around 2005.
I personally don't know the answer.
Well you didn't just have an epiphany, provide links! Don't make me be this guy trying to find your articles:
-
Your reply is probably going to be something like this... I can just feel it...
-
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Your reply is probably going to be something like this... I can just feel it...
You already knew that.
Just play this back for yourself:
https://appraw.com/ringtone/police-incoming-message-7zdz6 -
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Your reply is probably going to be something like this... I can just feel it...
You already knew that.
Just play this back for yourself:
https://appraw.com/ringtone/police-incoming-message-7zdz6I can only down vote that once.
-
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@zuphzuph said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
@BBigford said in Setting up MDT/WDS for UEFI/Legacy Images & Network Boots:
Your reply is probably going to be something like this... I can just feel it...
You already knew that.
Just play this back for yourself:
https://appraw.com/ringtone/police-incoming-message-7zdz6I can only down vote that once.
