Build a Dual-Network Windows Server VM

Deploy a dual-network Windows Server 2025 VM in Proxmox for an AD lab.

Introduction

30 Second Summary

Experiments at home often share the same network as every phone, television, and work laptop. A separate space keeps your practice environment away from everyday devices.

In this project, you will build a Windows Server 2025 virtual machine named DC01 in Proxmox VE. Its two network adapters give the server home-LAN access while reserving an isolated segment for future Active Directory clients.

What You'll Build

From the Proxmox browser console, you will see DC01 running with one path to your home network plus another path reserved for future domain clients.

By the end of this project, you'll have:

  • A working Windows Server desktop that you can open through Proxmox browser console whenever you want to administer DC01.
  • A dual-network layout with External connected to your home LAN through bridged networking. Internal stays on the isolated Linux bridge vmbr1 at 172.16.0.1/24.
  • The QEMU Guest Agent giving Proxmox visibility into DC01. You can confirm its memory use plus IP information from the host.
  • Secret Mission: Create a tested network-ready snapshot that removes a temporary change while preserving DC01's network baseline.

Are there any prerequisites?

This project starts with Proxmox VE already installed on a bare-metal host. The host must be reachable from your Windows administration laptop, and you need its IP address plus administrator credentials.

The host also needs capacity for 4 virtual CPU cores, 8 GB of RAM, and a 64 GB virtual disk.

Before We Start

This checkpoint defines the two network roles for DC01, the reusable foundation of your home Active Directory lab. Keeping External on the internet-facing home LAN and Internal on the isolated future client network prevents lab traffic from mixing with household devices.

Stage the Installation Media

Download and Upload the Installation ISOs

DC01 needs two installation images before you can create the virtual machine in Proxmox VE. The Windows Server ISO provides the operating system installer.

The VirtIO drivers let Windows use Proxmox virtual storage and networking. You will sign in to your existing host, download both ISO images, and upload them to Proxmox storage.

In this step, get ready to:
  • Sign in to your existing Proxmox VE host.
  • Download the Windows Server and VirtIO ISO images.
  • Upload both ISO images to Proxmox storage.
Sign in to Proxmox VE

Your Proxmox VE host is already installed and reachable. Start by opening its known address and signing in.

  • Open your Proxmox VE address on port 8006 in a browser (eg: 192.168.x.x:8006)
  • Sign in with your existing Proxmox VE administrator credentials.

You should now see the Proxmox VE resource tree and host summary.

Download both installation images

The Windows Server 2025 evaluation ISO starts Windows Setup. The VirtIO ISO carries the Windows software needed for the VM's virtual hardware.

Why do you need two ISO images?

Each ISO has a separate role during installation. Keeping both in Proxmox VE lets the VM access them as virtual discs.

  • The Windows Server evaluation ISO contains the operating system installer.
  • The VirtIO ISO contains the Windows Server 2025 storage driver.
  • The VirtIO ISO contains the Windows Server 2025 network driver.
  • The VirtIO ISO contains the balloon driver plus the QEMU Guest Agent installer.

Both files are large disk images. A several-minute wait is normal on slower connections.

  • Open the Microsoft Evaluation Center in a new browser tab.
  • Complete the registration form for the Windows Server evaluation.
  • Choose Windows Server 2025 | 64-bit ISO.
  • Start the Windows Server evaluation ISO download.

The Windows evaluation image now begins downloading. Keep its browser tab available while you fetch the driver image.

  • Open the Proxmox Windows VirtIO Drivers page in another browser tab.
  • Follow the release archive linked from the Proxmox page.
  • Select the virtio-win 0.1.271 release.
  • Download the ISO file for that release.
  • Wait for both ISO downloads to finish.

Your browser should now show two completed ISO downloads. One is the Windows Server installer.

The other is the pinned VirtIO driver image. You now have everything that Proxmox VE needs for the upload stage.

Upload the ISO images

Proxmox VE stores installer media under ISO Images. Each file becomes available to virtual machines after its upload task completes.

Large ISO uploads can remain in progress for several minutes. Keep the Proxmox VE tab open until each task finishes successfully.

  • In the Proxmox VE resource tree, select the storage that contains ISO Images.
  • Open ISO Images.
  • Click Upload.
  • Select the downloaded Windows Server 2025 evaluation ISO in the file picker.
  • Start the upload.
  • Wait for the Windows Server ISO upload task to finish successfully.

That first upload gives DC01 its operating system installer. The storage list should now include the Windows Server evaluation ISO.

  • Click Upload again.
  • Select the downloaded virtio-win 0.1.271 ISO in the file picker.
  • Start the upload.
  • Wait for the VirtIO ISO upload task to finish successfully.

Before the final check, form a prediction about whether the selected storage now contains one combined installer or two separate ISO images.

  • Review the files listed under ISO Images on the selected storage.

You should see a Windows Server 2025 evaluation ISO. You should also see a virtio-win 0.1.271 ISO.

That's the media staging complete. Both upload tasks should show successful completion.

Missing an ISO after upload?

  • Retry the upload for the missing file.
  • Confirm that the selected storage still exposes ISO Images.
  • Wait for the active upload task to finish before checking the file list again.

Still missing a file? Help me troubleshoot my Proxmox VE ISO upload.

Your installation media is staged in Proxmox VE. Next, you'll build DC01 and boot into Windows Setup.

Build DC01 and Reach Windows Setup

Your two ISO uploads are complete. That careful staging gives Proxmox VE the installation media needed to turn DC01 into a virtual machine.

Windows Server 2025 Setup needs to understand the virtual disk before installation can continue. In this step, you will build DC01 with the intended hardware before using Setup to test what the guest can detect.

In this step, get ready to:
  • Create DC01 with the Windows Server 2025 installer attached.
  • Configure the virtual disk and external network connection.
  • Attach the second ISO and test storage detection in the browser console.
Create the DC01 virtual machine

Every Proxmox guest needs a unique numeric VM ID. Proxmox selects the next free ID automatically, so DC01 does not need a fixed number.

  • Click Create VM in the Proxmox VE toolbar.
  • Keep the automatically selected value in the VM ID field.
  • Enter DC01 as the VM name.

The wizard now identifies the new guest as DC01.

  • Select the uploaded Windows Server 2025 ISO as the installation media.
  • Select Microsoft Windows 11/2022/2025 as the guest OS type.

The selected installer now matches the guest type that Proxmox uses for current Windows Server releases.

  • Open the System stage of the wizard.
  • Enable Qemu Agent for later communication with the QEMU Guest Agent inside Windows.

DC01 is now prepared to report guest information back to Proxmox after the agent is installed in Windows.

Configure the DC01 hardware

A Linux bridge acts like a virtual network switch. The existing wired LAN bridge gives DC01 a path to your home network.

VirtIO presents storage and network devices in a form designed for virtual machines. This project uses the documented Proxmox Windows guest path for both devices.

Why VirtIO for DC01?

The VirtIO SCSI controller provides the storage path for the server disk. The paravirtualized VirtIO NIC provides the external network path.

Using both keeps DC01 aligned with Proxmox's Windows Server guest guidance.

  • Continue to the disk configuration stage.
  • Set the disk bus to SCSI.
  • Set the disk size to 64 GB.

The wizard now shows a 64 GB disk on the SCSI bus.

  • Select VirtIO SCSI single as the SCSI controller.
  • Keep the cache setting at No cache.

DC01 now uses the intended controller with the safer default cache setting.

  • Enable Discard for the disk.
  • Enable IO Thread for the disk.

The disk configuration now matches the target storage design for DC01.

  • Continue to the processor configuration stage.
  • Set the total CPU cores to 4.

The wizard now allocates four total CPU cores to DC01.

  • Continue to the memory configuration stage.
  • Set the memory to 8192 MiB.

DC01 now has 8192 MiB of memory for a more responsive Desktop Experience.

  • Continue to the network configuration stage.
  • Select VirtIO (paravirtualized) as the network device model.
  • Select the existing wired LAN bridge as the network bridge.

The wired LAN bridge is normally vmbr0. Use the bridge connected to your laptop's built-in Ethernet if your environment uses a different name.

  • Create DC01 from the wizard's confirmation page.

Good work. DC01 now appears in the Proxmox resource list with its first set of virtual hardware.

DC01 needs both uploaded ISOs attached before its first boot. The virtio-win image belongs in a second virtual CD drive.

  • Select DC01 in the Proxmox resource list.
  • Open the Hardware view.
  • Click Add.
  • Select CD/DVD drive.

The new drive dialog is ready for the second ISO.

  • Set the bus to IDE.
  • Set the drive number to 0.
  • Select the uploaded virtio-win 0.1.271 ISO.
  • Confirm the new CD/DVD drive.

The Hardware view should show the 64 GB SCSI disk plus one external VirtIO NIC. The virtio-win 0.1.271 ISO should appear on IDE 0.

The Windows Server 2025 ISO should remain attached as the boot media.

DC01 Hardware Does Not Match?

  • Return to the disk settings if the disk is not listed as 64 GB on SCSI.
  • Check that the external NIC uses the existing wired LAN bridge.
  • Check that the virtio-win 0.1.271 ISO is mounted on IDE 0.

Need a second pair of eyes? Help me compare my DC01 hardware with the required configuration.

Boot into Windows Setup

Proxmox gives you a browser console that behaves like a monitor connected directly to DC01. This lets you follow the installer without remote access inside Windows.

  • Select DC01 in the Proxmox resource list.
  • Use the start control to power on DC01.

DC01's status changes to running.

  • Click Console in DC01's left menu.
  • Select noVNC if Proxmox asks which console viewer to use.
  • Respond to the boot prompt so the attached Windows ISO starts.
  • Continue through the initial Windows Setup pages until you reach the installation-type page.

Before you choose Custom (advanced), what do you expect the disk list to show? This is your prediction point.

  • Select Custom (advanced) as the installation type.

You will reach the disk-selection screen. The 64 GB disk does not appear in the installable disk list.

The Empty Disk List Is Intentional

Proxmox has created the virtual disk. Windows Setup has not loaded support for the VirtIO SCSI device.

The empty list proves that DC01 has reached the planned driver gap.

  • Keep noVNC open at the empty disk-selection screen.

DC01 remains powered on at the intended stopping point.

Did You Reach a Different Screen?

  • Confirm that the disk bus is SCSI if a disk unexpectedly appears.
  • Confirm that the controller is VirtIO SCSI single if a disk unexpectedly appears.
  • Confirm that the Windows Server 2025 ISO remains attached if the installer does not start.

Still stuck? Help me reach the empty Windows Setup disk-selection screen.

DC01 now boots into Windows Setup, where the empty disk list has exposed the planned driver gap. Next, you will load the VirtIO drivers before installing Windows Server.

Load VirtIO and Install Windows Server

DC01 reached the intended roadblock in the last step. Windows Setup cannot see its 64 GB VirtIO SCSI disk.

The VirtIO storage driver exposes that disk to Windows Server 2025. This paravirtualized path gives DC01 efficient access to its virtual hardware.

In this step, get ready to:
  • Expose the 64 GB disk by loading the three VirtIO drivers.
  • Install Windows Server 2025 Standard with Desktop Experience.
  • Enable guest reporting from DC01.
Load the VirtIO drivers

Windows Setup needs the matching storage driver before it can communicate with the virtual SCSI controller. The mounted virtio-win 0.1.271 CD contains that driver.

  • In the noVNC console from earlier, select Load driver.
  • Browse to the mounted virtio-win driver CD.
  • Choose the vioscsi\2k25\amd64 folder.
  • Select Red Hat VirtIO SCSI pass-through controller from the driver list.
  • Install the selected storage driver.

That is the roadblock cleared. Windows Setup can now see the 64 GB disk through the VirtIO SCSI controller.

  • Select Load driver again.
  • Browse to NetKVM\2k25\amd64 on the driver CD.
  • Select Redhat VirtIO Ethernet Adapter from the driver list.
  • Install the selected network driver.

Windows Setup returns to the disk-selection screen. The network driver is now available for the external VirtIO adapter.

  • Select Load driver once more.
  • Browse to Balloon\2k25\amd64 on the driver CD.
  • Select VirtIO Balloon Driver from the driver list.
  • Install the selected balloon driver.

Windows Setup returns to the disk-selection screen, where you should see only the 64 GB disk. That disk confirms storage access because the network and balloon drivers do not create disk entries.

What did these drivers unlock?

  • The driver in vioscsi\2k25\amd64 lets Windows Setup communicate with the 64 GB SCSI disk.
  • The driver in NetKVM\2k25\amd64 gives Windows access to the external VirtIO network adapter.
  • The driver in Balloon\2k25\amd64 supports memory coordination between DC01 and its host.

🙋‍♀️ Still Missing the 64 GB Disk?

  • Confirm that you selected vioscsi\2k25\amd64 from the mounted virtio-win 0.1.271 CD.
  • Confirm that the selected driver is Red Hat VirtIO SCSI pass-through controller.
  • Reload the storage driver if Windows Setup returned to the disk screen without showing the 64 GB disk.

Still stuck? Help me troubleshoot why Windows Setup cannot see my 64 GB VirtIO SCSI disk.

Install Windows Server

Windows Server Standard with Desktop Experience includes the standard graphical interface. That interface gives this home lab a visual desktop for server administration.

Why Use Desktop Experience?

Desktop Experience provides the familiar Windows interface and graphical tools. This makes DC01 easier to inspect before you add server roles in a later project.

Windows Setup can spend several minutes on its progress screens. Several automatic restarts are normal during this installation.

  • Select the visible 64 GB disk.
  • Click Next to let Windows Setup create the required partitions.
  • Let Windows Setup complete the installation.

After the final automatic restart, you will see the local Administrator password setup. This password controls direct access to DC01.

This credential stays private. You never need to share or screenshot it during this project.

  • Enter a strong password for the Administrator account.
  • Re-enter the same password in the confirmation field.
  • Submit the password setup.
  • Sign in to the Administrator account with the password you created.

That is the biggest installation milestone complete. You can now see the Windows Server desktop running inside DC01.

Installation Did Not Reach the Desktop?

  • Let DC01 boot from its 64 GB virtual disk if the installation media appears again after a restart.
  • Reload vioscsi\2k25\amd64 if the virtual disk disappears before installation begins.
  • Follow the password guidance shown by Windows if the new Administrator password is rejected.

Need help? Help me diagnose where my Windows Server installation stopped.

Install guest integration tools

The QEMU Guest Agent sends guest details from Windows to Proxmox VE. The guest tools installer completes the remaining driver and service setup.

Both installers are on the mounted virtio-win 0.1.271 CD. Windows may show a permission prompt when each installer starts.

  • Select the Search icon on the Windows taskbar.
  • Type File Explorer into Windows Search.
  • Select File Explorer from the search results.
  • Select the mounted virtio-win driver CD in the File Explorer sidebar.
  • Open the guest-agent folder.

You should see the QEMU Guest Agent installer inside the folder. This installer adds the service that communicates with Proxmox.

  • Double-click guest-agent\qemu-ga-x86_64.msi.
  • Approve the Windows permission prompt if it appears.
  • Keep the default choices on each installer screen.
  • Complete the QEMU Guest Agent installation.

The QEMU Guest Agent service is now installed in DC01. The VM still needs the complete guest tools package before the final restart.

  • Return to the top level of the mounted driver CD.
  • Double-click virtio-win-gt-x64.msi.
  • Approve the Windows permission prompt if it appears.
  • Keep the default choices on each installer screen.
  • Complete the VirtIO guest tools installation.

The guest tools package completes missing driver and service installation. A restart activates the finished integration.

  • Open the Windows power menu.
  • Select Restart.
  • Sign back in to the Administrator account after DC01 restarts.

Before you check Proxmox, which new guest details do you think the agent makes visible?

  • Switch back to the Proxmox VE web interface from earlier.
  • Select DC01 in the left resource tree.
  • Select Summary.

You should see guest information in the Summary view. You should also see DC01's RAM usage.

The Summary view should report an external IP address from your home LAN. That is the integration complete: Proxmox can now read useful information from the running Windows guest.

Guest Information Missing From Summary?

  • Give DC01 a short moment after sign-in before checking the Summary view again.
  • Confirm that QEMU Guest Agent remains enabled in DC01's VM settings.
  • Confirm that guest-agent\qemu-ga-x86_64.msi completed before the restart.
  • Confirm that the external VirtIO adapter is connected to the existing wired LAN bridge.

Still missing guest details? Help me troubleshoot QEMU Guest Agent reporting for DC01.

DC01 now runs Windows Server with working storage, networking, and host integration. Next up, you will add the isolated bridge that separates future domain clients from household devices.

Add an Isolated Lab Network

DC01 is running Windows Server 2025 with its VirtIO drivers in place. Its first adapter can already reach your home network.

Future domain clients need a private segment that household devices cannot join. This step adds that separated path without changing DC01's working external connection.

In this step, get ready to:
  • Create an isolated bridge named vmbr1.
  • Attach a second VirtIO network adapter to vmbr1.
  • Use Windows PowerShell to match both adapters by their MAC addresses.
Create the isolated bridge

A Linux bridge is a virtual switch inside Proxmox VE. A bridge without a physical port keeps its traffic inside the host.

Why Use a Standard Linux Bridge?

DC01 needs one isolated segment on one Proxmox host. A standard Linux bridge provides that switch with few moving parts.

Proxmox Software Defined Networking adds features for larger designs. This lab needs only one local bridge.

  • Return to the Proxmox VE web interface from earlier.
  • Select your Proxmox host node in the resource tree.
  • Open the node's network settings.
  • Choose the option to add a Linux bridge.
  • Enter vmbr1 as the bridge name.

The bridge name field should now show vmbr1.

  • Leave the physical bridge port empty.
  • Leave the host IP address unset.

The form should now show no physical bridge port. It should also show no host IP address.

  • Leave the gateway unset.
  • Confirm the bridge creation.

The network settings should now list vmbr1 with no physical port. Its host address and gateway should also be empty.

What Keeps the Bridge Isolated?

  • An empty physical bridge port prevents vmbr1 from reaching your household network through a cable.
  • No host IP keeps the Proxmox host out of this guest network.
  • No gateway keeps the bridge from creating another default route.

Applying host networking can feel risky because the web interface depends on the current LAN bridge. This change adds vmbr1 without editing that existing bridge.

  • Select Apply Configuration.

The Proxmox VE page should remain reachable. The network settings should continue to list vmbr1.

That is the network-side work complete. Your isolated virtual switch now exists without taking Proxmox VE off the home LAN.

Bridge Missing or Web Interface Unreachable?

  • Check for a pending network configuration if vmbr1 does not appear after creation.
  • Return through your existing SSH access if the web interface disconnects.
  • Confirm that the working wired LAN bridge kept its original configuration.

Need help recovering access? Help me troubleshoot my Proxmox bridge configuration.

Attach the second network adapter

Each virtual NIC gets its own MAC address. That address gives you a reliable way to connect a Proxmox hardware entry to a Windows adapter.

The new adapter must join vmbr1. The existing adapter stays on the wired LAN bridge.

  • Return to DC01 through the Proxmox browser console.
  • Use the Windows power menu to shut down DC01 cleanly.

Wait until Proxmox reports that DC01 has stopped. The hardware change is safe to make once the guest is fully off.

  • Select DC01 in the Proxmox resource tree.
  • Open Hardware.

The Hardware view should show the existing network device on your wired LAN bridge. A standard installation normally uses vmbr0 for this bridge.

  • Select the existing network device attached to the wired LAN bridge.
  • Record its MAC address here: external NIC MAC address.

Why Record the MAC Addresses?

Proxmox identifies each virtual NIC by its bridge and MAC address. Windows shows the same MAC address beside the guest adapter.

Matching those values tells you which Windows adapter reaches the home LAN. It also identifies the adapter connected to the isolated lab.

  • Select Add in the Hardware toolbar.
  • Choose Network Device.

The network-device dialog should now show settings for the model and bridge.

  • Set the model to VirtIO (paravirtualized).
  • Set the bridge to vmbr1.

The dialog should now show a VirtIO device connected to vmbr1.

  • Confirm the network-device addition.

Hardware should now list two network devices. The new device should show vmbr1 as its bridge.

  • Record the new device's MAC address here: internal NIC MAC address.

Don't See Two Network Devices?

  • Confirm that DC01 is fully stopped before changing its virtual hardware.
  • Check that the new device uses VirtIO (paravirtualized).
  • Check that the new device connects to vmbr1.

Still stuck? Help me find the missing second network device.

Match the adapters by MAC address

Windows adapter names can be generic. Their MAC addresses stay aligned with the virtual NIC entries you recorded in Proxmox.

An elevated Windows PowerShell session can list every visible adapter. You will use its output to map the external and internal paths.

  • Start DC01 from the Proxmox VE web interface.

Proxmox should report that DC01 is running.

  • Open DC01 through Proxmox browser console.
  • Sign in with the configured local Administrator account.

You should see the Windows Server desktop.

  • Press the Windows key to open search.
  • Type Windows PowerShell.

The search results should show Windows PowerShell.

  • Use the search result's administrator option to open an elevated session.
  • Approve the elevation prompt.

You should now see an elevated Windows PowerShell window.

Before you run the check, how many adapters do you expect Windows to report?

  • List every visible adapter by running this command:
Get-NetAdapter -Name *

What Does This Command Show?

  • The Get-NetAdapter command asks Windows for its network adapters.
  • The -Name * part includes every visible adapter name.
  • The output includes each adapter's current name and MAC address.

You should see two visible adapter rows. Each row should include a MAC address that matches one of the values recorded in Proxmox.

  • Match the row containing external NIC MAC address to the wired LAN bridge.
  • Match the row containing internal NIC MAC address to vmbr1.
  • Switch back to the Proxmox VE web interface from earlier.
  • Select DC01.
  • Open Hardware.

You should see two VirtIO network devices. The existing device attaches to the wired LAN bridge.

The new device attaches to vmbr1.

Second Adapter Missing in Windows?

  • Confirm that Proxmox Hardware still lists the second device on vmbr1.
  • Confirm that the second device uses VirtIO (paravirtualized).
  • Restart DC01 if the adapter was added before Windows completed its previous shutdown.

Need help with the missing adapter? Help me troubleshoot why Get-NetAdapter shows only one NIC.

You have now proved that DC01 can see both sides of its network design. The MAC matches give you a dependable map between Proxmox hardware and Windows.

Your Network Baseline

  • The vmbr1 bridge has no physical port.
  • The vmbr1 bridge has no host IP address or gateway.
  • DC01 has one VirtIO NIC on the wired LAN bridge.
  • DC01 has one VirtIO NIC on vmbr1.
  • Windows sees both NICs through the installed Red Hat VirtIO Ethernet Adapter driver.
  • Both Proxmox MAC addresses match visible Windows adapters.

DC01 now has a working external path plus an isolated internal path. Next, you will turn this hardware map into a stable network configuration.

Name and Address Both Adapters

Name DC01 and Address Both Adapters

You matched each VirtIO adapter to its Proxmox VE NIC by MAC address in the previous step. Windows still uses generic names that hide each connection's purpose.

Now you'll use Windows PowerShell to replace those names with External and Internal. The role-based names make the network design clear whenever you inspect DC01.

External keeps its home-router DHCP address as the only adapter with a default gateway. Internal receives 172.16.0.1 with subnet mask 255.255.255.0, no gateway, and loopback DNS. You will then give Windows the computer name DC01.

In this step, get ready to:
  • Turn the MAC-verified adapters into clear External and Internal roles.
  • Configure Internal with its static IPv4 address, subnet mask, gateway behavior, and loopback DNS.
  • Rename the Windows computer to DC01.
Turn the MAC matches into clear roles

The MAC addresses you matched earlier are the source of truth. They prevent the wired-LAN adapter from being confused with the isolated vmbr1 adapter.

  • Return to the elevated Windows PowerShell session inside DC01.
  • Use your MAC-address notes to identify the current Windows name of the wired-LAN adapter.
  • Use your MAC-address notes to identify the current Windows name of the vmbr1 adapter.
  • Replace <current external adapter name> with the current name of the wired-LAN adapter.
  • Replace <current internal adapter name> with the current name of the vmbr1 adapter.
  • Rename both matched adapters by running your completed commands:
Rename-NetAdapter -Name "<current external adapter name>" -NewName "External"
Rename-NetAdapter -Name "<current internal adapter name>" -NewName "Internal"

What Do These Commands Do?

  • The -Name parameter selects the existing adapter alias that you identified through its MAC address.
  • The -NewName parameter assigns the adapter's role-based alias.
  • The new names keep the server's routing intent visible during later configuration.

Before you check, which role-based name should match each recorded MAC address?

  • Display the renamed adapters by running this command:
Get-NetAdapter -Name *

What Should You See?

You should see adapters named External and Internal. Each adapter's MAC address should still match the corresponding NIC recorded in Proxmox VE.

🙋‍♀️ Do the Names Match the Wrong MAC Addresses?

  • Compare the MAC address shown for each Windows adapter with your notes from DC01's Hardware view.
  • Rerun the corresponding rename command with the correct current adapter name.

Need help checking the mapping? Help me match my Windows network adapters to my Proxmox NICs by MAC address.

That careful MAC matching has paid off. Windows now shows the purpose of each connection at a glance.

Configure Internal and name DC01

The isolated adapter needs a dependable address for future lab clients. It does not need a route to the internet.

  • Configure Internal's IPv4 address, subnet mask, gateway behavior, and DNS server by running these commands:
New-NetIPAddress -InterfaceAlias "Internal" -IPAddress 172.16.0.1 -PrefixLength 24
Set-DnsClientServerAddress -InterfaceAlias "Internal" -ServerAddresses 127.0.0.1

What Do These Commands Do?

  • -IPAddress assigns 172.16.0.1 to Internal.
  • -PrefixLength 24 applies subnet mask 255.255.255.0.
  • Omitting -DefaultGateway leaves the gateway blank on Internal.
  • Set-DnsClientServerAddress sets the preferred DNS server to loopback address 127.0.0.1.

The loopback address points DC01 to its own future DNS service. External keeps its router-supplied DNS settings while the DNS Server role is not installed.

The Internal adapter now has its complete lab configuration. The next command restarts Windows immediately so the new computer name can take effect.

  • Save any open work before the restart.
  • Rename the computer to DC01 and restart Windows by running this command:
Rename-Computer -NewName "DC01" -Restart
Verify DC01 and the routed path

The restart applies the computer name without changing the saved network settings. Your final checks now cover identity, addressing, DNS, and routing.

Before you run these checks, which adapter should show the only default gateway? What computer name should the first command return?

  • Reconnect to DC01's noVNC console after the restart.
  • Sign in with the Administrator password you created.
  • Verify the computer name, Internal IPv4 settings, DNS server, and both adapters by running these commands:
hostname
Get-NetIPAddress -InterfaceAlias "Internal" -AddressFamily IPv4 | Select-Object IPAddress, PrefixLength
Get-DnsClientServerAddress -InterfaceAlias "Internal" -AddressFamily IPv4
Get-NetIPConfiguration

What Should You See?

  • hostname returns DC01.
  • Get-NetIPAddress shows 172.16.0.1 on Internal.
  • Internal shows prefix length 24, which equals subnet mask 255.255.255.0.
  • Get-DnsClientServerAddress shows 127.0.0.1 for Internal.
  • Internal shows no default gateway.
  • External shows a router-supplied IPv4 address and the only default gateway.

🙋‍♀️ Seeing an Unexpected Result?

  • Confirm that Windows PowerShell is running as Administrator before you rerun a configuration command.
  • Rerun the rename command from the elevated session if hostname still shows the old computer name.
  • Compare the adapter MAC addresses with your Proxmox VE notes if the Internal and External results appear reversed.

Still seeing a different result? Help me troubleshoot DC01's name and network settings.

  • Minimize Windows PowerShell in the DC01 noVNC console.
  • Press the Windows key to open search.
  • Type Microsoft Edge into search.
  • Press Enter to open Microsoft Edge.
  • Enter https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2025 in the address bar.
  • Press Enter to load the page.

You should see the Microsoft Evaluation Center page load. This proves that External still carries DC01's internet traffic.

That's the dual-network baseline locked in. DC01 now has the stable Internal address, subnet mask, and loopback DNS setting that the lab can build on.

External remains DC01's only path to the home network and the internet.

Secret mission

Prove Your Baseline Can Roll Back

Your clean DC01 baseline is about to become a domain controller in the next project. Create a rollback artifact, make a visible change, and prove you can recover the completed dual-network configuration.

Clean Up Your Resources

Clean Up Your Resources

Your Proxmox VE lab has no cloud charges. Choose whether to keep DC01 running, shut it down for later, or remove its local resources.

Cost warning

A powered-on DC01 uses host RAM. It also increases the Proxmox host's electricity use.

The Windows Server 2025 evaluation expires after 180 days. It must be activated over the internet within the first 10 days to avoid automatic shutdown.

Resources you used:

  • The virtual machine named DC01 with its 64 GB VirtIO SCSI disk.
  • The External virtual NIC attached to the wired LAN bridge.
  • The Internal virtual NIC attached to vmbr1.
  • The Windows Server 2025 evaluation ISO image uploaded to your selected Proxmox storage.
  • The virtio-win 0.1.271 ISO uploaded to the same storage.
  • The isolated Linux bridge named vmbr1.
  • The tested network-ready rollback artifact stored as a snapshot or full backup.

Keep everything running

No action is needed. Choose this option if you are continuing directly to Active Directory installation.

  • Leave DC01 powered on for your next lab session.
  • Retain both uploaded ISO files for future Windows guests.
  • Keep vmbr1 available for future domain clients.
  • Preserve the network-ready rollback artifact as your clean baseline.

Pause - I'll come back to this later

Shut down the guest to release its assigned RAM. Your VM files remain available for the next project.

  • Return to the DC01 noVNC console.
  • Use the Windows Server power menu to shut down DC01 cleanly.
  • Select DC01 in the Proxmox resource tree.
  • Open Summary.
  • Confirm that the VM status is stopped.
  • Retain the VM, uploaded ISO files, vmbr1, and the rollback artifact.

Your baseline is safely parked. It keeps its disk space while releasing the VM's assigned memory.

Delete - I don't want to use this again

Deleting this lab is permanent. Choose the pause option if you expect to continue with Active Directory.

  • Return to the DC01 noVNC console.
  • Use the Windows Server power menu to shut down DC01 cleanly.
  • Select DC01 in the Proxmox resource tree.
  • Open Summary.
  • Confirm that the VM status is stopped.

The rollback artifact exists in one of two locations. Its location depends on whether your VM storage supports snapshots.

  • Open Snapshots if you created a snapshot.
  • Select network-ready if it appears in the snapshot list.
  • Use the snapshot toolbar's removal action to delete the selected snapshot.
  • Select the storage holding your full backup if you used the backup fallback.
  • Select the full DC01 backup used as the rollback artifact.
  • Use the storage toolbar's deletion action to delete the selected backup.

The rollback artifact is now removed. The VM can be deleted with its attached storage.

  • Return to DC01 in the Proxmox resource tree.
  • Use the VM toolbar's removal action.
  • Include the attached 64 GB disk in the removal confirmation.
  • Confirm that DC01 no longer appears in the resource tree.

Removing DC01 also removes its External and Internal virtual NIC definitions. The uploaded installation media remains in Proxmox storage.

  • Select the Proxmox storage that contains ISO Images.
  • Open ISO Images.
  • Select the Windows Server 2025 evaluation ISO you uploaded.
  • Use the storage toolbar's deletion action to delete the selected ISO.
  • Select the virtio-win 0.1.271 ISO.
  • Use the storage toolbar's deletion action to delete the selected ISO.
  • Confirm that neither ISO remains listed under ISO Images.

Only the isolated bridge remains. It is safe to remove after every remaining guest has stopped using it.

  • Check each remaining VM's Hardware view for a network device attached to vmbr1.
  • Return to the Proxmox node's network settings.
  • Select vmbr1.
  • Use the network settings deletion action.
  • Select Apply Configuration.
  • Refresh the Proxmox web interface.

That clears the whole lab. The bridge list no longer includes vmbr1, while the Proxmox web interface remains reachable.

Nice Work!

Nice Work!

You did it! Your finished DC01 is a Windows Server 2025 VM in Proxmox VE with a dual-network baseline ready for the next Active Directory project.

What you learned:

  • Install Windows Server 2025 through the VirtIO storage path after resolving the missing-disk driver gap.
  • Install the QEMU Guest Agent so the Proxmox Summary shows DC01's guest information.
  • Configure a dual-network design where External uses home-router DHCP. Internal stays isolated on vmbr1 at 172.16.0.1/24.
  • Complete the optional Secret Mission by creating a tested network-ready rollback artifact. Prove it removes Desktop\rollback-test while preserving the completed network configuration.

Ready to quiz yourself?