Page Comparison

...

1. On your Windows server, go to DHCP and right-click on IPv4.
   

2. Define each vendor class as follows:

   1. In the DHCP Vendor Classes dialog, click Add.

   2. Enter the data according to the vendor class you are creating:

      1. Vendor class for UEFI on an x86 architecture:
         

         • Display name: PXEClient (UEFI x86)

         • Description: PXEClient:Arch:00006

      2. Vendor class for UEFI on an x64 architecture:

         • Display name: PXEClient (UEFI x64)

         • Description: PXEClient:Arch:00007

      3. Vendor class for BIOS on x86 and x64 architectures:

         • Display name: PXEClient (BIOS x86 & x64)

         • Description: PXEClient:Arch:00000
           

           

3. Perform the following steps for each vendor class you have created:

   1. Right-click Scope ([IP address]) DHCP range > Policies and select New Policy from the context menu.

   2. At Policy Name, enter the name exactly as you did for the vendor classes, i.e, once PXEClient (UEFI x86), once, PXEClient (UEFI x64), and once PXEClient (x86 & x64).

   3. Click Next.

   4. In the Configure Conditions for the policy screen, click Add.

   5. In the Add/Edit Condition dialog, click the drop-down menu Value:.

   6. Select the appropriate vendor class.

   7. Activate Append wildcard. click Add and then OK.

   8. Click Next,

   9. Answer the question Do you want to configure an IP address range for the policy? with No and click Next.

   10. Activate option 060 and edit it, according to the policy you are at:

       • For PXEClient (UEFI x86), enter PXEClient.

       • For PXEClient (UEFI x64), enter PXEClient.

       • For PXEClient (BIOS x86 & x64), leave the option empty.

   11. Activate option 066 and enter the Fully Qualified Domain Name (FQDN) or the IP address of your TFTP server.

   12. Activate option 067 and enter the path to the appropriate .efi file on your TFTP server. For example, this might be grub/bootx64.efi for the PXEClient (UEFI x64) vendor class if you are using GRUB as the bootloader.
        

4. Review your Scope Options; they should be similar to this:

   

5. Go to Server Options, add option 066, and enter the Fully Qualified Domain Name (FQDN) or the IP address of your TFTP server.

   

Deploying the TFTP Server

...

1. If IIS is not already available on your Windows server, install it.
   

2. Add the file name extensions and the corresponding MIME types for all file types that are present in the webserver/ directory of the OSC ZIP file. In our example:

   • File name extension .bspl; MIME type application/octet stream

   • File name extension: .sys; MIME type application/octet stream

   • File name extension: .nvgfx; MIME type application/octet stream
     

     

3. Specify a directory in which the required files will be stored, in our example C:\HTTP-Root
   

4. Copy all files from the webserver/ directory of the OSC ZIP file into the directory on the web server that has been defined in the section "osc"/"partitions" of your pxe-config.json (see Editing the "pxe-config.json" File). In our example, the directory is C:\HTTP-Root and the files are osc.bspl, osc.nvgfx, and osc.sys. The files may vary depending on the version of your OSC ZIP file.

   Tip
   title Web Server Check
   We recommend checking the URLs for these files in a web browser to ensure the download is functional.

...