{"id":31790,"date":"2019-10-31T21:43:07","date_gmt":"2019-10-31T18:43:07","guid":{"rendered":"https:\/\/prohoster.info\/blog\/rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi\/"},"modified":"2019-10-31T21:43:07","modified_gmt":"2019-10-31T18:43:07","slug":"rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi","title":{"rendered":"Extending WDS functionality: adding UEFI boot capability","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Hello everyone!<\/p>\n<p><\/p>\n<p>This article describes the steps you need to take to add UEFI boot support to your WDS.<\/p>\n<p><\/p>\n<p>That is, the instructions in this article assume you already have a configuration similar to the following:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">1. Windows Server 2012R2 (or newer)\n2. Fully configured DHCP for WDS\n3. The WDS itself\n4. IIS\n5. A virtual machine or PC running Ubuntu<\/code><\/pre>\n<p><\/p>\n<p>Here, I also describe actions that did not yield satisfactory results.<br \/>\n<em>I outlined them to save you time and make your search easier.<\/em><\/p>\n<p><\/p>\n<h2 id=\"predislovie\">Preface<\/h2>\n<p><\/p>\n<p>I used to set up a WDS at work with numerous features, as I was tired of running around with a bunch of flash drives and constantly rewriting them.<\/p>\n<p><\/p>\n<p>By the way, these articles helped me back then:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/171329\/\">Adding WDS versatility<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/175669\/\">PXE Boot Menu with System Center Configuration Manager<\/a><\/noindex><\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<b class=\"spoiler_title\">It looks like this<\/b><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/a7a33a522a91961b7ff24af518e63102.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>Everything was fine; new boot images were added, the winPE image was enhanced with new features, and everything worked.<\/p>\n<p><\/p>\n<p>However, not all devices support BIOS\/Legacy boot mode, and if they do, enabling it can often be found in a very obscure place.<\/p>\n<p><\/p>\n<p>Moreover, installing Windows in legacy mode when there's an option for UEFI is not ideal.<\/p>\n<p><\/p>\n<p>As a result, I decided to add UEFI boot support and went to Google.<\/p>\n<p><\/p>\n<p>However, I couldn't find any structured information on how to get a working WDS + UEFI.<br \/>\nThat's why I decided to write this article.<\/p>\n<p><\/p>\n<p>Before we start, I will describe the issue that took up the most time.<\/p>\n<p>\n<b class=\"spoiler_title\">When adding UEFI support to WDS, the following rather non-obvious situation may arise:<\/b><\/p>\n<p>If you add a boot file to WDS and attempt to boot on the device<br \/>\nin UEFI, you see the following text:<br \/>\n<code>The selected boot device failed. Press  to Continue.<\/code><br \/>\nOr <code>Boot Device Not Found<\/code><br \/>\nBut the legacy boot works fine.<br \/>\nThen one possible reason could be the absence of the file <strong>wdsmgfw.efi<\/strong>,<br \/>\nat the following path: <code>%WDSpath%Bootx64wdsmgfw.efi<\/code><\/p>\n<p><\/p>\n<p>You can find it here: <code>C:\\Windows\\System32\\RemInst\\bootx64wdsmgfw.efi<\/code><br \/>\nAlternatively, if you are missing this file for some reason, I have uploaded it to <noindex><a rel=\"nofollow\" href=\"https:\/\/drive.google.com\/file\/d\/10uNaSnlcDz98pihzPkiOfvP1OsPbYsEg\/view?usp=sharing\">google<\/a><\/noindex>.<br \/>\nThanks to the guys from <noindex><a rel=\"nofollow\" href=\"https:\/\/www.reddit.com\/r\/sysadmin\/comments\/9fj6ct\/cant_get_uefi_pxe_boot_to_wds_working_ive_tried\/\">Reddit<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>I spent the most time on this issue, as I thought the problem lay somewhere in the WDS or DHCP configuration.<\/p>\n<p><\/p>\n<p>I configured policies by adding Vendor Classes for different architectures and setting up DHCP options 060, 066, 067. <noindex><a rel=\"nofollow\" href=\"https:\/\/gal.vin\/2017\/05\/05\/pxe-booting-for-uefi-bios\/\">Instruction<\/a><\/noindex> for setting up DHCP policies.<\/p>\n<p>\n<b class=\"spoiler_title\">Architectures in ASCII for DHCP configuration<\/b><\/p>\n<p>PXEClient:Arch:00000 \u2014 BIOS\/Legacy<br \/>\nPXEClient:Arch:00006 \u2014 UEFI x86<br \/>\nPXEClient:Arch:00007 \u2014 UEFI x64<\/p>\n<p><\/p>\n<p>I also tried various boot file options <code>.efi<\/code><\/p>\n<p><\/p>\n<ul>\n<li>syslinux<\/li>\n<li>grub 2<\/li>\n<\/ul>\n<p><\/p>\n<p>I also tried to find the problem in the Event log.<br \/>\n<code>win + r -&gt; eventvwr -&gt; Application and Service logs -&gt; Microsoft -&gt; Windows -&gt; Deployment-Services-Diagnostics<\/code><\/p>\n<p><\/p>\n<p>But, as I mentioned above, the problem lay in the file <strong>wdsmgfw.efi<\/strong>.<br \/>\nEither I accidentally deleted it myself, or it didn't copy during installation<br \/>\nand setup of WDS.<\/p>\n<p><\/p>\n<p>Well, let's get started!<\/p>\n<p><\/p>\n<h2 id=\"instrukciya\">Instruction<\/h2>\n<p><\/p>\n<h4 id=\"etap-1---proverka-rabotosposobnosti-wds\">Step 1 \u2014 Checking the functionality of WDS<\/h4>\n<p><\/p>\n<p>Take any device or virtual machine that supports UEFI network booting and try to boot.<\/p>\n<p><\/p>\n<p>You should see the following picture:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/d3f793ebd93115f33d931c94194c1b9d.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>If so, great, you can continue.<br \/>\nIf not, then see what I wrote in the preface.<\/p>\n<p><\/p>\n<h4 id=\"etap-2---sborka-zagruzochnogo-fayla-ipxe\">Step 2 \u2014 Building the iPXE boot file<\/h4>\n<p><\/p>\n<p>Launch the prepared Ubuntu, open the terminal, and paste this line:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">git clone https:\/\/git.ipxe.org\/ipxe.git ipxe<\/code><\/pre>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/262686b08916a8e9f866664ef504973d.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p><em>Here I would like to make a small note that you may need to add packages necessary for compiling C and C++ in Ubuntu.<br \/>\nI just already had them installed.<\/em><\/p>\n<p><\/p>\n<p>Downloaded? \u2014 Great!<br \/>\nNow you need to create a configuration file for the build.<br \/>\nIn the terminal, type:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">cd ipxe\/src\ngedit chain.ipxe<\/code><\/pre>\n<p><\/p>\n<p>And paste the following code into this file, then save:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">#!ipxe\n\ndhcp\nchain http:\/\/%IP-address-your-IIS-server%\/install.ipxe<\/code><\/pre>\n<p><\/p>\n<p>Now go back to the terminal and start the compilation:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">make bin-x86_64-efi\/ipxe.efi EMBED=chain.ipxe<\/code><\/pre>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/70f18d8f99760b42cbcd0f475ee6fdb6.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>If everything is okay, you should see the following output in the terminal:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/8a184a840d2400e268df2b9336b61869.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>And the file <strong>ipxe.efi<\/strong>, located at: <code>ipxe\/src\/bin-x86_64-efi\/ipxe.efi<\/code><br \/>\n<em>If for some reason you couldn't compile it yourself,<br \/>\nI have attached my <noindex><a rel=\"nofollow\" href=\"https:\/\/drive.google.com\/file\/d\/189NZhU0hdZSiYvFoLI83AZbfAv3cQCOK\/view?usp=sharing\">file<\/a><\/noindex>.<br \/>\nIt is compiled for booting from <code>http:\/\/192.168.0.100\/install.ipxe<\/code><\/em><\/p>\n<p><\/p>\n<p>That's all from Ubuntu.<\/p>\n<p><\/p>\n<h4 id=\"etap-3---dobavlenie-ipxeefi-k-wds\">Step 3 \u2014 Adding ipxe.efi to WDS<\/h4>\n<p><\/p>\n<p>Take the file we obtained in the second step and copy it to the path:<br \/>\n<code>%WDSpath%Bootx64%your-boot-folderIBOOT<\/code><br \/>\nThen rename it to BOOTX64.EFI.<br \/>\n<em>This is not mandatory, it's just more convenient.<\/em><\/p>\n<p><\/p>\n<p>Then run <strong>cmd<\/strong> as an administrator, and type the following commands:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">wdsutil \/set-server \/bootprogram:Bootx64%your-boot-folderIBOOTBOOTX\n64.EFI \/architecture:x64uefi\nand\nwdsutil \/set-server \/N12bootprogram:Bootx64%your-boot-folderIBOOTBOOTX\n64.EFI \/architecture:x64uefi<\/code><\/pre>\n<p><\/p>\n<p>This will set the obtained file for booting via WDS.<\/p>\n<p><\/p>\n<p>Let's check the configuration:<\/p>\n<p><\/p>\n<pre><code class=\"plaintext\">wdsutil \/get-server \/Show:Config<\/code><\/pre>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/ac98dfac436399d01601004545a34f43.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p><em>I also copied the file ipxe.efi, renamed it to BOOTIA32.EFI, and configured the boot for it, just in case. <code>architecture:x86uefi<\/code><br \/>\nBut ultimately, there is no point in this, as the file Bootmgfw.efi does not support x86.<\/em><\/p>\n<p><\/p>\n<p>Let's check what we got.<br \/>\n<img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/2d04a5af05ae6c67df1729990b6ce64b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nGreat, WDS is sending our file for loading, and it is looking for the configuration at the path: <code>http:\/\/192.168.0.100\/install.ipxe<\/code><\/p>\n<p><\/p>\n<h4 id=\"etap-4---konfiguraciya-menyu\">Step 4 \u2014 Menu Configuration<\/h4>\n<p><\/p>\n<p>Let's go to the root folder of your website.<br \/>\nBy default, this is: <code>C:\\inetpub\\wwwroot<\/code><\/p>\n<p><\/p>\n<p>Create a text file <strong>install.ipxe<\/strong>.<\/p>\n<p><\/p>\n<p>And configure it according to <noindex><a rel=\"nofollow\" href=\"http:\/\/ipxe.org\/docs\">documentation<\/a><\/noindex> and your needs.<br \/>\nThere is also a Russian-language <noindex><a rel=\"nofollow\" href=\"http:\/\/tdkare.ru\/sysadmin\/index.php\/IPXE\">description<\/a><\/noindex> command.<br \/>\nI used <noindex><a rel=\"nofollow\" href=\"https:\/\/doc.rogerwhittaker.org.uk\/ipxe-installation-and-EFI\/\">this<\/a><\/noindex> the guide when configuring my WDS.<\/p>\n<p>\n<b class=\"spoiler_title\">Example configuration for install.ipxe<\/b><\/p>\n<pre><code class=\"plaintext\">#!ipxe\n\n:start\nmenu Please choose an operating system to start\/install\nitem --gap Start Win PE\nitem WinPE-x64 WinPE x64\nitem --gap ipxe shell\nitem shell       Drop to iPXE shell\n\nchoose target &amp;&amp; goto ${target}\n\n:failed\necho Booting failed, dropping to shell\ngoto shell\n\n:shell\necho Type 'exit' to get the back to the menu\nshell\nset menu-timeout 0\nset submenu-timeout 0\ngoto start\n\n:WinPE-x64\nkernel http:\/\/192.168.0.100\/wimboot\ninitrd http:\/\/192.168.0.100\/peSE\/Boot\/bcd\ninitrd http:\/\/192.168.0.100\/peSE\/Boot\/boot.sdi\ninitrd http:\/\/192.168.0.100\/peSE\/Boot\/peSE64.wim\nboot || goto failed<\/code><\/pre>\n<p><\/p>\n<p>You can read about the configuration for loading winPE <noindex><a rel=\"nofollow\" href=\"http:\/\/ipxe.org\/howto\/winpe\">here<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h4 id=\"etap-5---mime-types\">Step 5 \u2014 MIME Types<\/h4>\n<p><\/p>\n<p>After creating the menu and adding all necessary files to the root folder of IIS,<br \/>\nyou need to give access to them.<\/p>\n<p><\/p>\n<p>Because even if you try to download a file via your browser using its address, you will receive an error: <code>HTTP 404.3 - Not Found<\/code>.<br \/>\n<img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/ae8519f75d4ef050fb089f6431c770b5.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>To do this, you need to add MIME types in the IIS management panel according to<br \/>\nthe file extensions that you will be loading via HTTP.<\/p>\n<p><\/p>\n<p>I did not search for which MIME type is best for these purposes and set <code>application\/octet-stream<\/code>, after which everything started working.<\/p>\n<p><\/p>\n<p>For files without an extension, use a dot.<\/p>\n<p><\/p>\n<p>Like this:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/11827e7ed39f20b9dc075ea7a33d5b83.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<h2 id=\"zaklyuchenie\">Conclusion<\/h2>\n<p><\/p>\n<p>In the end, we have the ability to boot over the local network via UEFI.<\/p>\n<p><\/p>\n<p>If we did everything right, we will have a boot selection menu that looks something like this:<\/p>\n<p><\/p>\n<p><img decoding=\"async\" alt=\"Extending WDS functionality: adding UEFI boot capability\" src=\"\/wp-content\/uploads\/2019\/04\/01cb07fd55da153a9c81a1f561b1bd21.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<p>If you have prepared the basic tools and you do not get bogged down in configuration, it takes about 10-20 minutes to implement this capability.<br \/>\nIt took me 2 working days since I had to Google a lot.<\/p>\n<p><\/p>\n<p>Good luck with the implementation!<\/p>\n<p><\/p>\n<p>Thank you for your attention, and a huge thanks to those people whose articles helped me!<br \/>\nOn Habr it's: <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/ingtar\/\" class=\"user_link\">Ingtar<\/a><\/noindex> and <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/deeptown\/\" class=\"user_link\">Deeptown<\/a><\/noindex>.<\/p>\n<p>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/448476\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u043e\u043f\u0438\u0441\u0430\u043d\u044b \u0448\u0430\u0433\u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c, \u0434\u043b\u044f \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a \u0432\u0430\u0448\u0435\u043c\u0443 WDS, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 \u0440\u0435\u0436\u0438\u043c\u0435 UEFI. \u0422.\u0435. \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044f \u0432 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u043f\u0440\u0435\u0434\u043f\u043e\u043b\u0430\u0433\u0430\u0435\u0442, \u0447\u0442\u043e \u0443 \u0432\u0430\u0441 \u0443\u0436\u0435 \u0438\u043c\u0435\u0435\u0442\u0441\u044f, \u043f\u0440\u0438\u043c\u0435\u0440\u043d\u043e \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0430\u044f \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u044f: 1. Windows Server 2012R2 (\u0438\u043b\u0438 \u043d\u043e\u0432\u0435\u0435) 2. \u041f\u043e\u043b\u043d\u043e\u0441\u0442\u044c\u044e \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043d\u043d\u044b\u0439 DHCP \u0434\u043b\u044f \u0440\u0430\u0431\u043e\u0442\u044b \u0441 WDS 3. \u0421\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u043e \u0441\u0430\u043c WDS 4. IIS 5. [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23673,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31790","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u043e\u043f\u0438\u0441\u0430\u043d\u044b \u0448\u0430\u0433\u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c, \u0434\u043b\u044f \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a \u0432\u0430\u0448\u0435\u043c\u0443 WDS, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 \u0440\u0435\u0436\u0438\u043c\u0435 UEFI. \u0422.\u0435.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0420\u0430\u0441\u0448\u0438\u0440\u044f\u0435\u043c \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b WDS: \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 UEFI | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u043e\u043f\u0438\u0441\u0430\u043d\u044b \u0448\u0430\u0433\u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c, \u0434\u043b\u044f \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a \u0432\u0430\u0448\u0435\u043c\u0443 WDS, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 \u0440\u0435\u0436\u0438\u043c\u0435 UEFI. \u0422.\u0435.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:43:07+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:43:07+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Expanding WDS functionality: adding the ability to boot in UEFI | ProHoster","description":"Hello everyone! In this article, the steps that need to be followed to add the ability to boot in UEFI mode to your WDS are described.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0420\u0430\u0441\u0448\u0438\u0440\u044f\u0435\u043c \u0444\u0443\u043d\u043a\u0446\u0438\u043e\u043d\u0430\u043b WDS: \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 UEFI | ProHoster","og:description":"\u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435, \u043e\u043f\u0438\u0441\u0430\u043d\u044b \u0448\u0430\u0433\u0438 \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435\u043e\u0431\u0445\u043e\u0434\u0438\u043c\u043e \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c, \u0434\u043b\u044f \u0434\u043e\u0431\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a \u0432\u0430\u0448\u0435\u043c\u0443 WDS, \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u0432 \u0440\u0435\u0436\u0438\u043c\u0435 UEFI. \u0422.\u0435.","og:url":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/rasshiryaem-funktsional-wds-dobavlenie-vozmozhnosti-zagruzki-v-uefi","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:43:07+00:00","article:modified_time":"2019-10-31T18:43:07+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31790","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 07:51:22","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:59:47","updated":"2026-01-21 07:51:22","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/31790","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=31790"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/31790\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media\/23673"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=31790"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=31790"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=31790"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}