> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/4.0/troubleshooting/device-compatibility.md). # Device Compatibility ## Will iPXE work with your desktop and laptop computers? Nearly all modern business-class laptops and desktops that support PXE also support iPXE. Only a few configuration changes are needed to convert an existing PXE environment to support iPXE booting. **How do you know whether your machines can support PXE?** Most computers fall into one of three categories: 1. **Known Good Machines:**\ Nearly all modern business-class laptops and desktops, and many consumer laptops and desktops from the major computer manufacturers, support PXE as long as the machine has a built-in wired RJ-45 Ethernet port.\ These include manufacturers such as Dell, Lenovo, and HP. 2. **Known Exceptions List:**\ The following machines have known issues with iPXE: * *Microsoft Surface 2 Go Laptop* – When booting, some of the iPXE drivers can conflict with the attached USB keyboard. The remedy is to attach an external keyboard, or use the on-screen keyboard. (iPXE #975) * *Dell Latitude 3440* – Some users have reported issues when downloading the boot.wim file. This can be mitigated by adjusting some network settings; contact 2Pint support if you are having issues. If you are having issues with a specific device, contact . 3. **Other Machines:** * Some laptops and tablets do not have a wired network connection available, only Wi-Fi or USB.\ Some laptop and tablet manufacturers support PXE/iPXE booting over Wi-Fi. Check with your device manufacturer to see if this is an option. iPXE can use on-board Wi-Fi. * Many laptop and tablet manufacturers support PXE/iPXE booting over USB-to-Ethernet adapters. Check with your device manufacturer to see if they have approved USB-to-Ethernet adapters. This is true for most Microsoft Surface devices. Note that some USB-to-Ethernet adapters may not boot. * Finally, a backup option is to use a USB boot disk with iPXE (see [Boot Media Tools](/2pxe-server/4.0/reference/boot-media-tools.md)), and a USB-to-Ethernet adapter to connect to the network. This works with most devices, and is an ideal backup solution. ## Secure Boot The 2PXE iPXE binaries are signed by Microsoft using the Microsoft third-party UEFI Secure Boot certificate (the "Microsoft UEFI CA", sometimes shown in firmware settings as the "Microsoft 3rd Party UEFI CA"). Because most devices trust this certificate by default, iPXE can boot on them with Secure Boot enabled. Devices that implement Microsoft's Secured-core PC specification do not trust the Microsoft 3rd Party UEFI CA by default, so they will not boot iPXE with Secure Boot enabled. On these devices, you may need to allow or enable the Microsoft 3rd Party UEFI CA manually in the firmware (UEFI) settings. The name and location of this setting vary by manufacturer; check your device manufacturer's documentation. {% hint style="info" %} **Hyper-V virtual machines:** Hyper-V Secure Boot templates only allow one of the two certificates at a time: the **Microsoft Windows** template trusts the Windows certificate, and the **Microsoft UEFI Certificate Authority** template trusts the 3rd Party UEFI CA. Because there is no way to trust both at the same time, turn off Secure Boot on Hyper-V virtual machines that boot with iPXE. {% endhint %} ## Supported network devices A full list of networking devices supported by iPXE can be found at: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.2pintsoftware.com/2pxe-server/4.0/troubleshooting/device-compatibility.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.