Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Tech News
  • Contact
  • Toggle search form

How to set up a VM via PXE boot on a Generation 1 VM

Posted on 19/01/202017/08/2026 IT Expert By IT Expert No Comments on How to set up a VM via PXE boot on a Generation 1 VM
  1. Home
  2. Virtualization
  3. How to set up a VM via PXE boot on a Generation 1 VM
VMware, PXE boot

To boot a virtual machine (VM) using PXE boot, the VM has to support an emulated Legacy Network Adapter. Follow the steps below to perform this. Please see “Generation 2 VM deployment of Windows Server 2019, how to set up a Generation 2 VM via PXE boot, how to set up a Generation 1VM via PXE boot, and how to set up a VM via PXE boot on a Generation 2 VM.

Hyper-V specifically provides hardware virtualization. That means each virtual machine runs on virtual hardware. Hyper-V lets you create virtual hard drives, virtual switches, and a number of other virtual devices all of which can be added to virtual machines.

Please see Veeam Enterprise Manager setup and User Role management, Building VIHR: Ransomware-Proof Repository with Veeam JeOS, and how to fix Failed to connect to Deployer Service Error.

VM via PXE boot on a Generation 1 VM

To set up a VM via PXE boot on a Generation 1 VM, please follow the steps below.

  • Shut down or turn off the virtual machine.
  • Edit the settings of the virtual machine.
  • Browse to Add Hardware, select Legacy Network Adapter, and click Add.
  • Click OK to save your changes.

Now the virtual machine is PXE capable, with the lower performing Legacy Network Adapter.

PXE boot

Follow up with other manual steps. Add the legacy network adapter. Click on Add

Generation 1 VM

Click Expand the legacy Network Adapter recently added

Enter the Mac Address (Depending on your environment, you have to set a Static MAC address that will enable the VM search for the WDS server or else it will fail)

setup

Please, see how to deploy images to computers or virtual machines using WDS, and Windows deployment cannot continue, the operating system is missing via MDT deployment“.

Virtual Switch

Click on the Next, click on the legacy Network adapter and under the virtual switch, select the right network adapter

Configuration screen for a Legacy Network Adapter in a virtual machine setup, displaying options for selecting a virtual switch and VLAN ID, along with a recommendation for usage.

Lastly, ensure that the client boots first using the Legacy Network Adapter. Just select the Legacy Network Adapter and move it to the top using the buttons.

Screenshot of a BIOS configuration window showing boot device settings, with 'Legacy Network adapter' highlighted in the startup order.

Start your Virtual Machine, and now PXE boot should function correctly 

Command line interface displaying 'Hyper-V PXE Network Boot' with fields for CLIENT MAC ADDRESS and GUID.

Here is the result below of a successful deployment.

A window titled 'Deployment Summary' displaying a message indicating 'Success' with a computer icon.

I hope you found this blog post on How to set up a VM via PXE boot on a Generation 1 VM very helpful. If you have any questions, please let me know in the comment session.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:configure PXE boot for Hyper-V VM, Generation 1 VM installation via network boot, Hyper-V PXE boot setup, hyperV, Microsoft Windows, PXE boot setup Generation 1 VM, set up a VM via PXE boot on a Generation 1 VM, Windows Deployment Services, Windows Server 2016

Post navigation

Previous Post: Why does the legacy PXE not does work on Generation 2 VM
Next Post: How to fix unable to create a new VM on HyperV

Related Posts

  • hero windowsserver hyperv scaled
    Pass-Through Authentication Authentication and ADFS environment setup on Hyper-V for Hybrid Identity integration Virtualization
  • SCVMM setup Error 10421 e1773750310917
    SCVMM setup Error 10421: Fix VMM Service Account conflict Virtualization
  • image
    How to start HyperV VMs in safe mode Virtualization
  • Docker Guide
    Pull and Deploy Nginx Container Images from Docker Hub AWS/Azure/OpenShift
  • VMware Error Fix
    How to fix “The process cannot access the file because another process has locked a portion of the file” Virtualization
  • Free up filesystem root space
    How to fix the Filesystem root is running low on Disk space Virtualization

More Related Articles

hero windowsserver hyperv scaled Pass-Through Authentication Authentication and ADFS environment setup on Hyper-V for Hybrid Identity integration Virtualization
SCVMM setup Error 10421 e1773750310917 SCVMM setup Error 10421: Fix VMM Service Account conflict Virtualization
image How to start HyperV VMs in safe mode Virtualization
Docker Guide Pull and Deploy Nginx Container Images from Docker Hub AWS/Azure/OpenShift
VMware Error Fix How to fix “The process cannot access the file because another process has locked a portion of the file” Virtualization
Free up filesystem root space How to fix the Filesystem root is running low on Disk space Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • Featured image Win1022H2
    How to get the Windows 10 Version 22H2 Update Windows
  • wds and dns l
    What happens when WDS and DNS are installed on the same Windows Server? DNS issues with WDS Windows Server
  • Update Wampserver
    How to update WampServer to Latest Version Web Server
  • Confluence setup
    How to set up Confluence Site and Spaces in Confluence Cloud JIRA|Confluence|Apps
  • BitLocker removal on Windows Server
    How to correctly disable BitLocker on Windows Server Windows Server
  • image 11
    Setting Up your Amazon S3 Glacier and FastGlacier for Your Online Vault AWS/Azure/OpenShift
  • Allow and Disallow Simultaneous Connection to Domain and Non Domain network
    Allow and Disallow Simultaneous Connection to Domain and Non-Domain network Network | Monitoring
  • backupvssnapshot
    Virtual Machine Snapshot vs Backup Version Control System

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,762 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.