WDS Strangeness - Error 0xc0000023 and Server IP: 0.0.0.0

%3CLINGO-SUB%20id%3D%22lingo-sub-90379%22%20slang%3D%22en-US%22%3EWDS%20Strangeness%20-%20Error%200xc0000023%20and%20Server%20IP%3A%200.0.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90379%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20have%26nbsp%3B%20the%20following%20infrastructure.%20WDS%20Server%20for%20UEFI%20and%20one%20for%20BIOS%20Images.%20Both%20have%20MDT%206.3.8443.1000%20and%20ADK%2010.1.15063.0%20installed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20BIOS%20WDS%20Server%20works%20just%20fine.%20The%20UEFI%20one%20however%20does%20not%20seems%20to%20respond%20correctly%2C%20but%20I%20do%20not%20really%20understand%20what%20is%20happening%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17732i9055208296738118%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20what%20I%20see%20after%20the%20TFTP%20Download%20succeeded.%20This%20much%20I%20was%20able%20to%20check%20in%20the%20wireshark%20dump.%20But%20after%20that%20there%20seems%20to%20be%20no%20further%20communication%20between%20the%20host%20that%20I%20want%20to%20deploy%20and%20the%20WDS%20server.%20The%20WDS%20Event%20Viewer%20logs%20show%20that%20the%20appropriate%20TFTP%20File%20was%20successfully%20downloaded%20and%20then%20everything%20stops%20and%20the%20above%20screen%20is%20shown.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20last%20log%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Following%20Client%20completed%20TFTP%20Download%3A%3C%2FP%3E%3CP%3EClient%20IP%3A%20xxx.xxx.xxx.xxx%3CBR%20%2F%3EFilename%3A%20Boot%5C%5Cx64%5C%5Cwdsmgfw.efi%3CBR%20%2F%3EFile%20Size%3A%201029536%3CBR%20%2F%3EClient%20Port%3A%201191%3CBR%20%2F%3EServer%20Port%3A%2061459%3CBR%20%2F%3EVariable%20Window%3A%20false%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20lost%20atm%20as%20to%20where%20even%20look%20for%20the%20error.%20Do%20you%20have%20any%20ideas%20how%20to%20proceed%3F%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3CP%3EChristian%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdate%3A%3C%2FP%3E%3CP%3EWhile%20trying%20to%20further%20debug%20the%20issue%20I%20hit%20another%20problem%20that%20the%20event%20viewer%20config%20does%20not%20work%20as%20expected%2C%20as%20it%20only%20shows%20the%20log%20messages%20from%203%20hours%20before%2C%20but%20not%20the%20current%20ones%3A%3C%2FP%3E%3CP%3E%3CMAYBE%20there%3D%22%22%20is%3D%22%22%20also%3D%22%22%20someone%3D%22%22%20with%3D%22%22%20enough%3D%22%22%20wisdom%3D%22%22%20here%3D%22%22%20to%3D%22%22%20enlighten%3D%22%22%20me%3D%22%22%3E%3C%2FMAYBE%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17746i0839710E13C797E0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92000%22%20slang%3D%22en-US%22%3ERe%3A%20WDS%20Strangeness%20-%20Error%200xc0000023%20and%20Server%20IP%3A%200.0.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92000%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%26gt%3B%20First%20of%20all%20you%20don't%20need%202%20wds%20servers.%20I%20expect%20you%20are%20configuring%20DHCP%20options%20to%20point%20to%20each.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhich%20we%20do%20and%20it%20used%20to%20work.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26gt%3B%20Remove%20DHCP%20options%20and%20add%20an%20IP%20helper%20on%20the%20switch%20to%20look%20t%20to%20one%20server%20and%20bios%20or%20uefi%20will%20be%20selected%20on%20capabilities%20of%20system%20being%20booted.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20I%20can%20not%20do%20in%20our%20infrastructure.%20Network%20is%20not%20under%20my%20control%20and%20network%20will%20not%20allow%20changes%20to%20the%20network%20if%20we%20can%20not%20show%20that%20it%20is%20absolutely%20necessary.%20In%20this%20case%20it%20is%20not%2C%20because%20this%20used%20to%20work%20and%20it%20stopped%20working%20a%20couple%20of%20days%20ago%2C%20I%20am%20still%20hunting%20for%20the%20reason.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%3E%26gt%3B%20Additionally%20if%20you're%20really%20must%20use%202%20wds%20servers%20make%20sure%20you%20have%20both%20x86%20and%20x64%20boot%20images%20on%20wds%20server%20otherwise%20even%20x64%20won't%20work%20with%20x86%20components%20there.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20part%20sounds%20interesting%2C%20but%20I%20do%20not%20understand%20it.%20Could%20you%20please%20amplify.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%20Chris.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EKind%20regards.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EChristian%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91844%22%20slang%3D%22en-US%22%3ERe%3A%20WDS%20Strangeness%20-%20Error%200xc0000023%20and%20Server%20IP%3A%200.0.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91844%22%20slang%3D%22en-US%22%3EHi%3CBR%20%2F%3EFirst%20of%20all%20you%20don't%20need%202%20wds%20servers.%20I%20expect%20you%20are%20configuring%20DHCP%20options%20to%20point%20to%20each.%20Remove%20DHCP%20options%20and%20add%20an%20IP%20helper%20on%20the%20switch%20to%20look%20t%20to%20one%20server%20and%20bios%20or%20uefi%20will%20be%20selected%20on%20capabilities%20of%20system%20being%20booted.%3CBR%20%2F%3E%3CBR%20%2F%3EAdditionally%20if%20you're%20really%20must%20use%202%20wds%20servers%20make%20sure%20you%20have%20both%20x86%20and%20x64%20boot%20images%20on%20wds%20server%20otherwise%20even%20x64%20won't%20work%20with%20x86%20components%20there.%3CBR%20%2F%3E%3CBR%20%2F%3EChris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1160522%22%20slang%3D%22en-US%22%3ERe%3A%20WDS%20Strangeness%20-%20Error%200xc0000023%20and%20Server%20IP%3A%200.0.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1160522%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51908%22%20target%3D%22_blank%22%3E%40Christian%20Bernardt%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20ever%20find%20a%20solution%20to%20this%3F%20I%20know%20it's%20been%20years....but%20I%20am%20just%20now%20running%20into%20this%20problem%20myself.%20Here%20is%20the%20situation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20use%20WDS%20to%20deploy%20Windows%2010%20images%20over%203%20different%20subnets.%20All%203%20used%20to%20work%20just%20fine%20regardless%20of%20BIOS%20or%20UEFI.%20Now%2C%202%20out%20of%203%20subnets%20work%20with%20both%20normally%2C%20but%20one%20of%20the%20subnets%20only%20works%20using%20BIOS%2C%20UEFI%20booting%20gives%20the%20same%20error%20that%20you%20were%20experiencing.%20I%20asked%20our%20Network%20Admins%20if%20any%20changes%20had%20been%20made%20and%20they%20claim%20nothing%20changed.%20I%20didn't%20touch%20the%20WDS%20server%20during%20the%20time%20it%20worked%20and%20stopped%20working%2C%20so%20I'm%20at%20a%20point%20where%20I%20just%20can't%20get%20by%20this%20error%20when%20trying%20to%20PxE%20boot%20using%20UEFI.%20I%20can't%20even%20find%201%20solution%20online%20for%20this%20either...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20figured%20out%20the%20problem%2C%20I'd%20appreciate%20it%20if%20you%20could%20share%20what%20you%20did%20to%20resolve%20it.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1949065%22%20slang%3D%22en-US%22%3ERe%3A%20WDS%20Strangeness%20-%20Error%200xc0000023%20and%20Server%20IP%3A%200.0.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1949065%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F549244%22%20target%3D%22_blank%22%3E%40Zephyrius%3C%2FA%3E%26nbsp%3B%20Your%20problem%20is%20solved%3F%20I%20have%20the%20same....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1950384%22%20slang%3D%22en-US%22%3ERe%3A%20WDS%20Strangeness%20-%20Error%200xc0000023%20and%20Server%20IP%3A%200.0.0.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1950384%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3Efirst%20of%20I%20want%20to%20apologize%20that%20I%20never%20replied%20with%20a%20solution%20to%20my%20own%20thread%2C%20I%20hate%20such%20people%20who%20just%20ask%2C%20but%20never%20give%20back.%20Now%20I%20am%20one%20of%20them.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20our%20case%20it%20was%20about%20DNS%20options%20if%20I%20remember%20correctly.%20I%20am%20very%20sorry%20I%20can%20not%20be%20of%20great%20help%2C%20because%20this%20was%20such%20a%20long%20time%20ago.%20I%20think%20it%20came%20down%20to%20two%20major%20problems.%20We%20had%20a%20spelling%20problem%20in%20the%20DNS%20options%2C%20we%20used%20a%20none%20microsoft%20DNS%2C%20I%20believe%20Nokia%20or%20something%20like%20this.%20I%20searched%20around%20a%20bit%20and%20I%20think%20option%2060%20was%20our%20problem%2Csee%20below.%20The%20Arch%20values%20on%20the%20server%20were%20important%20as%20well.%20And%20last%20but%20not%20least%20the%20firmware%20of%20the%20network.interfaces%20and%20docking%20stations.%20Especially%20with%20Microsoft%20Docking%20Stations%20for%20Surface%20Books%20it%20was%20a.desaster.%20There%20are%20different%20generations%20of%20the%20docking%20stations%20each%20working%20under%20different%20conditions%2C%20with%20or%20without%20firmware%20update.%20Also%20almost%20every%20DELL%20we%20got%20had%20some%20different%20network%20card%20gen.%3CBR%20%2F%3E%3CBR%20%2F%3EAgain%20I%20know%2C%20this%20is%20no%20real%20help%20that%20I%20give%20here%2C%20but%20sometimes%20pointing%20in%20the%20direction%20helps%20as%20well%2C%20however%20unspecific%20it%20might%20be.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20one%20more%20advice%2C%20do%20not%20waste%20your%20precious%20support%20hours%20of%20your%20microsoft%20contract%20if%20you%20have%20one.%20They%20were%20a%20complete%20waste%20of%20time.%20I%20think%20what%20I%20did%20at%20the%20time%20for%20debugging%2C.I%20created%20VMs%20one%20for%20UEFI%20and%20one%20for%20legacy%20boot%20and%20hooked%20up%20Wireshark%20to%20follow%20how%20far%20communication%20between%20client%20and%20server%20got%2C%20that%20helped%20a%20lot%20in%20solving%20the%20issue.%20Also%20ask%20your%20network%20guys%2C%20the%20can%20mirror%20traffic%2C%20this%20way%20you%20can%20Wireshark%20your%20physical%20machine%20while%20you%20try%20UEFI%20PXE%20one%20of%20your%20machines.%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20I%20think%20I%20was%20too%20stupid%2C%20because%20it%20took%20me%20a%20month%20or%20more%20with%20maybe%2030%20hours%20Microsoft%20Support%20wasted%2C%20really%20no%20help%20from%20there%2C%20a%20shrug%20of%20shoulder%20by%20two%20Microsoft%20MVPs%20or%20however%20they%20name%20themselves.%3CBR%20%2F%3E%3CBR%20%2F%3EOne%20more%20advice%2C%20your%20network%20people%20say%20they%20have%20not%20changed%20anything.%20Never%20trust%20that%2C%20backup%20your%20network%20settings%20yourself%20and%20double%20check%2C%20at%20the%20time%20I%20had%20subnet%20config%20privileges%20to%20play%20around%20with%20different%20network%20options.%20I%20more%20than%20once%20observed%20that%20one%20of%20my%20settings%20was%20not%20there%20the%20next%20day.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20found%20this%20in%20a%20quick%20search%20and%20this%20looks%2C%20from%20memory%2C%20what%20we%20had%20at%20the%20time.%3CBR%20%2F%3E%3CBR%20%2F%3EServeroptionen%20f%C3%BCr%20Bios%20und%20UEFI%20sind%20folgend%20gesetzt.%3CBR%20%2F%3E%3CBR%20%2F%3E64bit%20UEFI%3CBR%20%2F%3EDisplay%20Name%20%3D%20PXEClient%20(UEFI%20x64)%3CBR%20%2F%3EDescription%20%3D%20PXE%3AArch%3A00007%3CBR%20%2F%3EASCII%20%3D%20PXE%3AArch%3A00007%3CBR%20%2F%3E32bit%20UEFI%3CBR%20%2F%3EDisplay%20Name%20%3D%20PXEClient%20(UEFI%20x86)%3CBR%20%2F%3EDescription%20%3D%20PXE%3AArch%3A00006%3CBR%20%2F%3EASCII%20%3D%20PXE%3AArch%3A00006%3CBR%20%2F%3E%3CBR%20%2F%3ELegacy%20BIOS%3CBR%20%2F%3EDisplay%20Name%20%3D%20PXEClient%20(BIOS%20x86%20%26amp%3B%20x64)%3CBR%20%2F%3EDescription%20%3D%20PXE%3AArch%3A00000%3CBR%20%2F%3EASCII%20%3D%20PXE%3AArch%3A00000%3CBR%20%2F%3EDanach%20folgend%20die%20entprechenden%20Bootfiles%20angegeben%20wie%20folgt%3A%3CBR%20%2F%3E%3CBR%20%2F%3EOption%2060%3A%20PXEClient%3CBR%20%2F%3E%3CBR%20%2F%3EOption%2066%3A%20Name%20des%20Servers%20eben%20oder%20die%20IP%3CBR%20%2F%3E%3CBR%20%2F%3EOption%2067%3A%20Pfadangabe%20zum%20File%20(Beispiel%3A%20smsboot%5Cx64%5Cwdsmgfw.efi)%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi community,

 

we have  the following infrastructure. WDS Server for UEFI and one for BIOS Images. Both have MDT 6.3.8443.1000 and ADK 10.1.15063.0 installed.

 

 

The BIOS WDS Server works just fine. The UEFI one however does not seems to respond correctly, but I do not really understand what is happening here.

 

image.png

 

This is what I see after the TFTP Download succeeded. This much I was able to check in the wireshark dump. But after that there seems to be no further communication between the host that I want to deploy and the WDS server. The WDS Event Viewer logs show that the appropriate TFTP File was successfully downloaded and then everything stops and the above screen is shown.

 

This is the last log:

 

The Following Client completed TFTP Download:

Client IP: xxx.xxx.xxx.xxx
Filename: Boot\\x64\\wdsmgfw.efi
File Size: 1029536
Client Port: 1191
Server Port: 61459
Variable Window: false

 

I am lost atm as to where even look for the error. Do you have any ideas how to proceed?

Thank you.

Christian

 

Update:

While trying to further debug the issue I hit another problem that the event viewer config does not work as expected, as it only shows the log messages from 3 hours before, but not the current ones:

<maybe there is also someone with enough wisdom here to enlighten me>

image.png

 

5 Replies
Hi
First of all you don't need 2 wds servers. I expect you are configuring DHCP options to point to each. Remove DHCP options and add an IP helper on the switch to look t to one server and bios or uefi will be selected on capabilities of system being booted.

Additionally if you're really must use 2 wds servers make sure you have both x86 and x64 boot images on wds server otherwise even x64 won't work with x86 components there.

Chris

> First of all you don't need 2 wds servers. I expect you are configuring DHCP options to point to each.

 

Which we do and it used to work.

 

> Remove DHCP options and add an IP helper on the switch to look t to one server and bios or uefi will be selected on capabilities of system being booted.

 

This I can not do in our infrastructure. Network is not under my control and network will not allow changes to the network if we can not show that it is absolutely necessary. In this case it is not, because this used to work and it stopped working a couple of days ago, I am still hunting for the reason.


> Additionally if you're really must use 2 wds servers make sure you have both x86 and x64 boot images on wds server otherwise even x64 won't work with x86 components there.

 

This part sounds interesting, but I do not understand it. Could you please amplify.

 

Thank you Chris.

Kind regards.

Christian

@Christian Bernardt 

 

Did you ever find a solution to this? I know it's been years....but I am just now running into this problem myself. Here is the situation.

 

I use WDS to deploy Windows 10 images over 3 different subnets. All 3 used to work just fine regardless of BIOS or UEFI. Now, 2 out of 3 subnets work with both normally, but one of the subnets only works using BIOS, UEFI booting gives the same error that you were experiencing. I asked our Network Admins if any changes had been made and they claim nothing changed. I didn't touch the WDS server during the time it worked and stopped working, so I'm at a point where I just can't get by this error when trying to PxE boot using UEFI. I can't even find 1 solution online for this either...

 

If you figured out the problem, I'd appreciate it if you could share what you did to resolve it. Thanks.

@Zephyrius  Your problem is solved? I have the same....

Hi,
first of I want to apologize that I never replied with a solution to my own thread, I hate such people who just ask, but never give back. Now I am one of them.

In our case it was about DNS options if I remember correctly. I am very sorry I can not be of great help, because this was such a long time ago. I think it came down to two major problems. We had a spelling problem in the DNS options, we used a none microsoft DNS, I believe Nokia or something like this. I searched around a bit and I think option 60 was our problem,see below. The Arch values on the server were important as well. And last but not least the firmware of the network.interfaces and docking stations. Especially with Microsoft Docking Stations for Surface Books it was a.desaster. There are different generations of the docking stations each working under different conditions, with or without firmware update. Also almost every DELL we got had some different network card gen.

Again I know, this is no real help that I give here, but sometimes pointing in the direction helps as well, however unspecific it might be.

And one more advice, do not waste your precious support hours of your microsoft contract if you have one. They were a complete waste of time. I think what I did at the time for debugging,.I created VMs one for UEFI and one for legacy boot and hooked up Wireshark to follow how far communication between client and server got, that helped a lot in solving the issue. Also ask your network guys, the can mirror traffic, this way you can Wireshark your physical machine while you try UEFI PXE one of your machines.

But I think I was too stupid, because it took me a month or more with maybe 30 hours Microsoft Support wasted, really no help from there, a shrug of shoulder by two Microsoft MVPs or however they name themselves.

One more advice, your network people say they have not changed anything. Never trust that, backup your network settings yourself and double check, at the time I had subnet config privileges to play around with different network options. I more than once observed that one of my settings was not there the next day.

I found this in a quick search and this looks, from memory, what we had at the time.

Serveroptionen für Bios und UEFI sind folgend gesetzt.

64bit UEFI
Display Name = PXEClient (UEFI x64)
Description = PXE:Arch:00007
ASCII = PXE:Arch:00007
32bit UEFI
Display Name = PXEClient (UEFI x86)
Description = PXE:Arch:00006
ASCII = PXE:Arch:00006

Legacy BIOS
Display Name = PXEClient (BIOS x86 & x64)
Description = PXE:Arch:00000
ASCII = PXE:Arch:00000
Danach folgend die entprechenden Bootfiles angegeben wie folgt:

Option 60: PXEClient

Option 66: Name des Servers eben oder die IP

Option 67: Pfadangabe zum File (Beispiel: smsboot\x64\wdsmgfw.efi)