Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Virtualization » How to set up a VM via PXE boot on a Generation 1 VM

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

Posted on 19/01/202025/03/2026 IT Expert By IT Expert No Comments on 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

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.

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

Here is the result below of a successful deployment.

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

  • sandboxx
    Use Windows Sandbox as a security feature Virtualization
  • Machine does not support XSAve
    How to disable side-channel mitigations on VMware Workstation Virtualization
  • Domain
    Connectivity to a writable domain controller from a node could not be determined because of an error Virtualization
  • Clone SysPrep
    Clone and Sysprep a Windows Server running on a VMware Workstation Virtualization
  • Add additional Windows drives
    How to Add Another Hard Drive to a Virtual Machine in HyperV  Virtualization
  • FailedRegistration
    DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names Virtualization

More Related Articles

sandboxx Use Windows Sandbox as a security feature Virtualization
Machine does not support XSAve How to disable side-channel mitigations on VMware Workstation Virtualization
Domain Connectivity to a writable domain controller from a node could not be determined because of an error Virtualization
Clone SysPrep Clone and Sysprep a Windows Server running on a VMware Workstation Virtualization
Add additional Windows drives How to Add Another Hard Drive to a Virtual Machine in HyperV  Virtualization
FailedRegistration DNS Bad key 9017: The Cluster Name registration failed of one or more associated DNS names 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

  • featurekube
    How to Install and Use Minikube on a Linux System Containers
  • rdp5
    Change expired RDP Password: How to change a password on a Remote Desktop session Windows Server
  • maxresdefault 2 7
    How to record your screen with PowerPoint and make slide shows Mac
  • sdgfdhx
    MDT Warning: Unable to set working directory, the application returned an unexpected code 2 Windows Server
  • vmwarevinchin
    3 Ways to Convert VMware VMs to Hyper-V Backup
  • macOS
    How to upgrade macOS Big Sur to macOS Monterey Mac
  • FEATURE ZABBIX
    How to Install Zabbix Monitoring Tool on a Linux System Linux
  • Enable a Pre Boot BitLocker PIN on Windows
    How to Enable a Pre-Boot BitLocker PIN on Windows Security | Vulnerability Scans and Assessment

Subscribe to Blog via Email

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

Join 1,805 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

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

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.