Build an AD and SQL Server Lab

Build replicated domain controllers and a SQL Server 2019 migration lab.

Introduction

30 Second Summary

Testing server changes on the computer you use every day can make every click feel risky. A separate practice space gives you room to experiment without disturbing the rest of your setup.

In this project, you will use VMware Workstation Pro to build two Windows Server 2022 Evaluation virtual machines. You will activate each server before placing both on a private network with stable names and addresses.

What You'll Build

Two live server consoles show DC01 at 10.50.0.10/24 and DC02 at 10.50.0.11/24, with successful replies proving the private connection.

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

An isolated host-only network that lets DC01 and DC02 communicate on VMnet2 without exposure to your physical LAN.
Two activated Windows Server 2022 consoles installed from one ISO image. Each server boots as an independent machine with its own growable virtual disk.
Predictable server identities using 10.50.0.10/24 and 10.50.0.11/24. You can prove the connection with replies in both directions.
Secret Mission: Create and test Pre-ADDS-Baseline snapshots. Prove a reversion removes a later file while preserving DC02 and its address.

Are there any prerequisites?

You need a Windows host with hardware virtualization enabled, 40 GB of RAM, 250 GB of free storage, and administrator access.

You also need a Broadcom Support Portal account plus a Microsoft account or registration details for the Evaluation Center.

Before We Start

Before the hands-on work begins, this is your moment to commit to building a reusable two-server Windows Server 2022 lab foundation. You will use this foundation for later Active Directory work.

Prepare VMware and the Server ISO

Your Windows host needs a hypervisor before it can run two isolated servers. VMware Workstation Pro provides the virtual machine layer that the rest of this lab depends on.

Each server also needs installation media. One official Windows Server 2022 Evaluation ISO can install both independent servers.

A fixed resource plan keeps the host responsive once both virtual machines are running. This step locks in the RAM budget plus the growable disk capacity.

In this step, get ready to:

Confirm or install VMware Workstation Pro 26H1u1.
Download one official Windows Server 2022 Evaluation ISO.
Lock in the resource plan for both virtual machines.

Confirm VMware Workstation Pro

VMware Workstation Pro is the desktop hypervisor that runs your two servers. The lab uses release 26H1u1 so the later interface labels match this walkthrough.

Workstation Pro is free for commercial use. It is also free for educational use or personal use.

Why Workstation Pro for this lab?

The next step creates a custom network named VMnet2. Workstation Pro includes a purpose-built Virtual Network Editor for creating that host-only network.

Press the Windows key to open Windows search.
Type VMware Workstation Pro into the search field.
Select VMware Workstation Pro if it appears in the results.
Select Help from the menu if the application opens.
Select About to view the installed release.
Choose the tab below that matches your result.

✔️ I see version 26H1u1

Your installed release matches the project. That is the hypervisor ready for both server builds.

Close the About dialog.
Select the Home tab.

You should see the Workstation Pro Home screen without an error.

ⓧ I see an older version

An older release can use interface labels that differ from this project. Upgrade it before creating the lab network.

Close VMware Workstation Pro.
Open Broadcom's official Workstation Pro download guide.
Register a Broadcom Support Portal account if you do not have one.
Sign in to the Broadcom Support Portal.
Download VMware Workstation Pro 26H1u1 for Windows.
In File Explorer, right-click the downloaded Windows installer.
Select Run as administrator.
Accept the installer defaults on each screen.

The installer may request a host restart. Save any other work before approving that restart.

Restart the Windows host if the installer prompts you.
Press the Windows key after installation finishes.
Type VMware Workstation Pro into the search field.
Select VMware Workstation Pro.
Select Help from the menu.
Select About.

You should see release 26H1u1 in the dialog. The Home screen should load after you close it.

ⓧ Command not found

VMware Workstation Pro is not installed yet. The Broadcom download workflow requires a Support Portal account.

Open Broadcom's official Workstation Pro download guide.
Register a Broadcom Support Portal account.
Sign in to the Broadcom Support Portal.
Download VMware Workstation Pro 26H1u1 for Windows.
In File Explorer, right-click the downloaded Windows installer.
Select Run as administrator.
Accept the installer defaults on each screen.

The installer may request a host restart. Save any other work before approving that restart.

Restart the Windows host if the installer prompts you.
Press the Windows key after installation finishes.
Type VMware Workstation Pro into the search field.
Select VMware Workstation Pro.
Select Help from the menu.
Select About.

You should see release 26H1u1 in the dialog. The Home screen should load after you close it.

Workstation Pro will not install?

Confirm that your Windows account has local administrator access.
Restart the host if the installer requested a restart.
Close any older Workstation Pro window before running the 26H1u1 installer again.

Ask for help with a VMware Workstation Pro installation error. You can also check the VMware Workstation Community.

Download the Windows Server ISO

The Evaluation ISO is a reusable installation image. You only need one copy because both virtual machines install independently from the same image.

This download is usually the slowest part of the step. A long progress bar is normal because the duration depends on your internet connection.

Open the official Microsoft Evaluation Center.
Sign in with your Microsoft account if requested.
Complete the registration form if requested.
Select ISO downloads 64-bit edition.
Save one ISO in a stable host folder that you do not plan to rename or move.
Record this location as your stable ISO folder.

Press the Windows key after the download finishes.
Type File Explorer into the search field.
Select File Explorer.
Navigate to your stable ISO folder.

You should see one Windows Server 2022 Evaluation ISO in that folder. Good work. That single image is ready to install both servers.

Cannot find the ISO?

Check whether your browser still shows the download in progress.
Search File Explorer for the Windows Server download if the browser used a different folder.
Restart the download from the Evaluation Center if the first download did not finish.

Ask for help with finding or completing the Windows Server Evaluation ISO download.

Lock in the host resource plan

Both servers run at the same time in later work. A shared resource plan prevents either guest from consuming the capacity reserved for the Windows host.

Reserve 8 GB of host RAM for the two running guests.
Allocate 2 vCPUs to each future virtual machine.
Allocate 4 GB of RAM to each future virtual machine.
Plan one 60 GB growable virtual disk for each future virtual machine.

What does growable mean?

Each virtual disk has a maximum capacity of 60 GB. Its host file grows as the guest writes data.

The disk does not consume its full maximum immediately. The chosen capacity also leaves room above Windows Server's 32 GB absolute minimum.

Before the final check, do you expect the hypervisor plus the server image to be ready for virtual machine creation?

Return to VMware Workstation Pro from earlier.
Select the Home tab.

You should see the Workstation Pro Home screen load successfully.

Select Help from the menu.
Select About.

You should see VMware Workstation Pro release 26H1u1.

Return to File Explorer from earlier.
Navigate to your stable ISO folder.

You should see one official Windows Server 2022 Evaluation ISO ready for VMware Workstation Pro.

Your host now has the exact hypervisor release plus one reusable server image. Next, you will build the isolated VMnet2 network that connects both future servers.

Build the Isolated VMnet2 Network

VMware Workstation Pro is ready on your host. Your Windows Server 2022 ISO is waiting in its stable folder.

The two future domain controllers need a private Ethernet segment before they receive addresses or names. In this step, you will create that isolated segment as VMnet2.

In this step, get ready to:

Create VMnet2 through an administrator session in Virtual Network Editor.
Configure a host-only network on the 10.50.0.0/24 subnet.
Verify the saved network with VMware DHCP disabled.

Add VMnet2 as an administrator

Virtual Network Editor controls the virtual networks shared by your host. Administrator privileges unlock the controls that create or change those networks.

Press the Windows key to open Windows search.
Type Virtual Network Editor.

You will see Virtual Network Editor in the search results.

Right-click the Virtual Network Editor result.
Choose the option that launches the editor with administrator privileges.

Windows now asks for permission to make host-wide network changes.

Approve the Windows permission prompt.

The editor opens with its network controls available.

Select Add Network.

You will see a dialog containing the available custom network names.

Select VMnet2 from the available network names.
Confirm your selection to create the network.

You will see VMnet2 in the network list. The new entry is now ready for its lab settings.

Cannot add VMnet2?

Close Virtual Network Editor if Add Network is unavailable.
Return through Windows search using the administrator option.
Select the existing VMnet2 entry if it already appears in the network list.

help me troubleshoot unavailable network controls in VMware Virtual Network Editor.

Configure the private subnet

The subnet defines the address range that belongs to this private segment. A fixed network boundary gives both future servers one shared address plan.

Select VMnet2 in the network list.
Select the host-only network mode for VMnet2.

The network summary now identifies VMnet2 as host-only. This keeps the future server traffic on the private virtual segment.

Select the Subnet IP field.
Enter 10.50.0.0.

The network address now matches the lab plan.

Select the Subnet mask field.
Enter 255.255.255.0.

The editor now shows the complete 10.50.0.0/24 network boundary.

Why These Two Values?

The address 10.50.0.0 identifies this lab network. The mask 255.255.255.0 defines it as a /24 subnet.

Both servers will receive addresses inside this same boundary in a later step. That shared boundary lets them communicate directly through VMnet2.

Disable DHCP and verify the saved network

DHCP can automatically lease addresses to connected virtual machines. This lab keeps that service off so the server address plan remains under your control.

Locate the Use local DHCP service to distribute IP addresses to VMs checkbox.
Clear the Use local DHCP service to distribute IP addresses to VMs checkbox.

The cleared checkbox shows that VMware will not lease addresses on VMnet2.

Select OK to save the network settings.

Virtual Network Editor closes after saving the custom network configuration.

Before you return, ask yourself whether the DHCP setting stays cleared after the save.

Return to Virtual Network Editor with administrator privileges by using the same Windows search route.

The editor opens with the saved virtual network list.

Select VMnet2 from the network list.

What Should I See?

The selected network remains VMnet2. Its network mode remains host-only.

The Subnet IP field shows 10.50.0.0. The Subnet mask field shows 255.255.255.0.

The Use local DHCP service to distribute IP addresses to VMs checkbox remains cleared. This confirms the isolated network is saved with VMware local DHCP disabled.

That is the network foundation locked in. VMnet2 now matches the lab's private address plan.

VMnet2 now gives your lab a private network boundary. Next, you will install both servers before seeing how they behave on this isolated segment.

Install Two Servers

Your private VMnet2 segment is ready. This step turns that empty segment into a two-server lab using VMware Workstation Pro.

Fresh Windows Server 2022 Evaluation guests request network settings automatically. You will activate both guests over temporary NAT access before testing what happens on your DHCP-free lab network.

In this step, get ready to:

Create two independent virtual machines from one evaluation ISO.
Install activated Server with Desktop Experience guests over NAT.
Move both guests to VMnet2 to inspect their network state.

Create both virtual machines

A virtual machine packages processor capacity, memory, storage, and network hardware in software. Two independent VMs give each server its own Windows installation while allowing both to use the same ISO.

Switch back to VMware Workstation Pro from the Virtual Network Editor.
Click File in the top menu.
Select New Virtual Machine.

The New Virtual Machine wizard opens. You will use its hardware controls to match the lab resource plan.

Select Custom as the configuration type.
Continue to the guest installation source screen.
Select Install the guest operating system later.

Why install the operating system later?

This option creates the virtual hardware before Windows Setup begins. You can attach the same ISO to each VM while keeping both guest installations independent.

Select Windows Server 2022 as the guest operating system.
Enter DC01 as the first virtual machine name.
Keep the VM files in the stable location shown by the wizard.

The wizard now identifies this VM as DC01. This label helps you find the guest in the VMware library.

Set the processor allocation to a total of 2 virtual CPUs.
Set the memory allocation to 4 GB.
Keep one network adapter attached to NAT.

The hardware summary should now show two virtual CPUs, 4 GB of memory, and one NAT adapter.

Set the maximum virtual disk size to 60 GB.
Keep the disk configured to grow as data is written.
Click Finish to create DC01.

You should now see DC01 in the VMware library. Its growable disk can expand to 60 GB without immediately consuming that full amount on the host.

Select DC01 in the VMware library.
Click VM in the top menu.
Select Settings.
Select Hardware.
Select the virtual CD or DVD device.
Choose Use an ISO image.
Select the Windows Server 2022 Evaluation ISO from its stable host folder.

The virtual CD or DVD device should now show the path to your evaluation ISO.

Enable the option that connects the virtual CD or DVD device when the VM starts.
Save the DC01 settings.
Repeat the same creation workflow for a second independent VM.
Enter DC02 as the second virtual machine name.
Apply the same two-virtual-CPU allocation to DC02.
Apply the same 4 GB memory allocation to DC02.
Create one 60 GB growable disk for DC02.
Keep its single network adapter attached to NAT.

You should now see DC01 and DC02 in the VMware library.

Attach the same Windows Server 2022 Evaluation ISO to DC02.
Enable the option that connects its virtual CD or DVD device when the VM starts.
Save the DC02 settings.

VM Names and Server Names

The labels DC01 and DC02 currently identify the VMs inside VMware Workstation Pro. Windows still assigns generated host names during installation.

You will give the operating systems their permanent server names after the addressing gap is resolved.

Install and activate Windows Server

Each evaluation guest needs internet access for activation. The temporary NAT connection provides that route without exposing your final lab network.

Select DC01 in the VMware library.
Start DC01.
Select DC02 in the VMware library.
Start DC02.

Both installations can run in parallel. This is the longest wait in the step, so a quiet console during file copying does not mean the VM has stalled.

Continue each Windows Setup wizard to the edition selection screen.
Select Windows Server Standard with Desktop Experience in each VM.
Select the custom installation option for each new guest.
Select the available 60 GB virtual disk in each guest.
Start both Windows Server installations.

Windows Setup copies the files before restarting each guest. Leave both VMs running through their automatic restarts.

Password handling is the fiddly part here. A password manager keeps the two local Administrator credentials from becoming guesswork.

Create a strong local Administrator password for DC01.
Store the DC01 password in your password manager.
Sign in to DC01.
Create a strong local Administrator password for DC02.
Store the DC02 password in your password manager.
Sign in to DC02.

That is the longest part complete. Both independent Windows desktops are now ready for activation.

Activation runs from an elevated Windows PowerShell session. Administrator elevation gives the licensing script permission to update the guest's activation state.

Press the Windows key inside DC01.
Search for Windows PowerShell.
Select Run as administrator.
Approve the administrator permission prompt.
Repeat the elevated PowerShell workflow inside DC02.

Activate each evaluation installation by running this command in both elevated PowerShell windows:

slmgr.vbs /ato

What Does This Command Do?

The slmgr.vbs /ato command asks Windows to attempt online activation. NAT gives each guest the internet route needed for that request.

Read the activation result shown by DC01.
Dismiss the DC01 activation result.
Read the activation result shown by DC02.
Dismiss the DC02 activation result.

Activation Request Failed?

Confirm that each VM still has one network adapter attached to NAT. Check that the Windows desktop can reach the internet before retrying the activation command.

If the request still fails, help me diagnose Windows Server Evaluation activation over VMware NAT.

Before you inspect the license details, do you expect both guests to report an activated evaluation?

Check the license information by running this command in both elevated PowerShell windows:

slmgr.vbs /dli

What Does This Command Show?

The slmgr.vbs /dli command displays license information for the installed Windows edition. It gives you a separate check after the activation attempt.

Each VM should show Windows Server 2022 Standard Evaluation license information with an activated status. This confirms both evaluation installations completed activation while NAT was available.

Activation Is Not Confirmed?

Run the activation command again while the adapter still uses NAT. Check the guest clock if activation remains unavailable because an incorrect date can interrupt online licensing checks.

For a result you cannot identify, help me interpret my Windows Server license information.

Move both guests to VMnet2

Activation is complete, so the guests no longer need their temporary NAT path. A clean shutdown protects each guest file system before you change its virtual network hardware.

Use the Windows power menu inside DC01 to shut down the guest.
Use the Windows power menu inside DC02 to shut down the guest.

Wait until VMware Workstation Pro shows that neither guest is running.

Select DC01 in the VMware library.
Click VM in the top menu.
Select Settings.
Select Hardware.
Select Network Adapter.
Choose Custom.
Select VMnet2 from the VMnet list.
Save the DC01 settings.

The DC01 hardware summary should now show one Custom network adapter attached to VMnet2.

Select DC02 in the VMware library.
Return to VM in the top menu.
Select Settings.
Select Hardware.
Select Network Adapter.
Choose Custom.
Select VMnet2 from the VMnet list.
Save the DC02 settings.

Both guests are now wired to the same host-only network. The physical LAN has no direct connection to this segment.

Start DC01.
Start DC02.
Sign in to DC01 with its local Administrator password.
Sign in to DC02 with its local Administrator password.
Open Windows PowerShell inside each guest.

Before you inspect the addresses, do you think either guest can receive its planned 10.50.0.x address from VMnet2 on its own?

Inspect the network configuration by running this command in both PowerShell windows:

ipconfig

What Does This Command Show?

The ipconfig command displays each guest's current IP addresses, subnet masks, and default gateways. Running it in both VMs lets you compare their network state.

Each guest should show an automatic 169.254.x.x IPv4 address. Windows uses this APIPA range because no DHCP service answered its request.

That result is the intended addressing gap. VMnet2 is isolated correctly, but these temporary addresses cannot support dependable DNS or directory services.

The labels DC01 and DC02 still identify the VMware entries only. The Windows guest host names remain generated values.

Neither guest has a static address, default gateway, or DNS configuration at this point.

Still Seeing a NAT Address?

Shut down the affected guest. Confirm its only network adapter uses Custom VMnet2 before starting it again.

If the adapter is already correct, help me find why my Windows Server VM still has its previous NAT address.

Both activated guests now run on the isolated VMnet2 segment. Next, you will replace their temporary addresses with stable server identities.

Assign Stable Server Identities

Your two activated Windows Server 2022 guests now share the isolated VMnet2 network. With VMware DHCP disabled, each guest has an APIPA address.

APIPA addresses are unsuitable for DNS or directory services. This step replaces them with stable IPv4 addresses.

You will also give each server its planned name. A focused firewall rule then lets the two nodes prove they can communicate.

In this step, get ready to:

Assign the planned static IPv4 address to each server.
Rename the servers to DC01 and DC02.
Enable two-way ICMP checks through Windows Firewall.

Assign static IPv4 addresses

A static IPv4 address stays predictable across restarts. An elevated Windows PowerShell session gives you permission to replace each temporary address.

Press the Windows key inside DC01 to open search.
Type Windows PowerShell into the search box.
Right-click the Windows PowerShell result.
Select the option that runs Windows PowerShell with administrator privileges.
Approve the permission request.
Repeat the same search steps inside DC02.

Each elevated session can now inspect the network adapter attached to VMnet2.

Display the network interfaces in each elevated session by running this command:

Get-NetIPInterface

What does this command show?

The output separates the IPv4 interface from any IPv6 interface.
The IfIndex value identifies the adapter that receives the static address.
The connected IPv4 row points to the adapter attached to VMnet2.

Find the connected IPv4 row in DC01.
Record its IfIndex here: DC01 IPv4 IfIndex.
Find the connected IPv4 row in DC02.
Record its IfIndex here: DC02 IPv4 IfIndex.

Assign 10.50.0.10 to the connected IPv4 interface in DC01 by running this command:

New-NetIPAddress -InterfaceIndex [[DC01_IFINDEX="DC01 IPv4 IfIndex"]] -IPAddress 10.50.0.10 -PrefixLength 24

How does the address command work?

The -InterfaceIndex parameter targets the connected adapter you identified.
The -IPAddress parameter assigns 10.50.0.10 to DC01.
The -PrefixLength parameter places the address on the planned 10.50.0.0/24 network.
Adding the address with New-NetIPAddress automatically disables DHCP on that interface.

PowerShell returns the new address details. You should see 10.50.0.10 with prefix length 24.

Address command rejected on DC01?

Confirm the PowerShell window is running with administrator privileges. Check that the recorded interface index still matches the connected IPv4 row from Get-NetIPInterface.

If the index still looks correct, help me troubleshoot the DC01 static address command.

Assign 10.50.0.11 to the connected IPv4 interface in DC02 by running this command:

New-NetIPAddress -InterfaceIndex [[DC02_IFINDEX="DC02 IPv4 IfIndex"]] -IPAddress 10.50.0.11 -PrefixLength 24

Why does DC02 need a separate command?

Each virtual machine owns a separate network adapter. DC02 therefore needs its own interface index.

The address 10.50.0.11 keeps the server on the same subnet as DC01 without creating an address conflict.

PowerShell returns the new address details. You should see 10.50.0.11 with prefix length 24.

Address command rejected on DC02?

Confirm the command uses the interface index recorded from DC02. An index copied from DC01 may point to a different interface.

For another check, help me troubleshoot the DC02 static address command.

Why leave the gateway and DNS blank?

This lab currently proves isolated connectivity within VMnet2. It has no router that could serve as a default gateway.

The follow-on project introduces DNS when the first domain controller is ready to host the directory namespace. Leaving both values unset keeps this foundation accurate.

Rename both servers

A stable address tells traffic where to go. A stable server name gives administrators a predictable identity to manage.

SConfig opens an interactive menu for the rename. It prompts for a restart after you enter the new computer name.

Start SConfig in the elevated DC01 session by running the command below.
Start SConfig in the elevated DC02 session by running the same command:

SConfig

What does SConfig change?

SConfig provides a numbered administration menu for Windows Server. Menu option 2 opens the computer name settings.

Restarting each guest applies only its new computer name. The static network settings remain in place.

Enter 2 in the DC01 SConfig menu.
Enter DC01 as the new computer name.
Approve the restart when SConfig prompts you.
Enter 2 in the DC02 SConfig menu.
Enter DC02 as the new computer name.
Approve the restart when SConfig prompts you.

Expect each restart to take a few minutes. The Windows loading screen can remain visible while the new identity is applied.

Sign in to DC01 with its recorded local Administrator password after the restart.
Sign in to DC02 with its recorded local Administrator password after the restart.
Check the active computer name inside each guest by running this command in Windows PowerShell:

hostname

What does hostname prove?

The hostname command reads the computer name currently active in Windows. It confirms that the restart applied the SConfig change.

You should see DC01 on the first server. You should see DC02 on the second server.

Still seeing the old server name?

Confirm that the guest completed its restart after the SConfig rename. A session opened before the restart cannot show the newly applied identity.

If the restart completed, help me check why the SConfig rename did not apply.

Enable two-way connectivity checks

The servers now have stable identities on the same subnet. ICMP echo requests provide a direct test of their isolated network path.

An inbound rule in Windows Firewall with Advanced Security allows each server to answer the other server's echo requests.

Create a new elevated Windows PowerShell session inside DC01 using the search steps from earlier.
Create a new elevated Windows PowerShell session inside DC02 using the same search steps.
Add the inbound IPv4 echo-request rule in both elevated sessions by running this command:

netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow

What does this firewall rule allow?

The rule is named ICMP Allow incoming V4 echo request so you can identify its purpose later.
The protocol setting limits the rule to inbound IPv4 echo requests.
The rule allows each server to answer a connectivity check from the other node.

The command should complete without an error on both servers. Each firewall now contains the enabled inbound echo-request rule.

Firewall rule command failed?

Confirm that you ran the command in an elevated Windows PowerShell session on the server reporting the failure. Administrator privileges are required to change firewall rules.

If the session is elevated, help me troubleshoot the ICMP firewall rule.

Display the full network configuration in each server by running this command:

ipconfig /all

What should the full configuration confirm?

The output shows the complete TCP/IP configuration for each adapter. Use the connected adapter to confirm the address that survived the restart.

The configuration should contain no default gateway or DNS server. Those settings remain intentionally unset for this isolated foundation.

On DC01, you should see 10.50.0.10 with a 255.255.255.0 subnet mask. On DC02, you should see 10.50.0.11 with the same subnet mask.

Before you test both directions, do you expect the two static addresses to reach each other without a gateway?

Send four echo requests from DC01 to DC02 by running:

ping 10.50.0.11

What does this first ping test?

This check sends ICMP echo requests from 10.50.0.10 to 10.50.0.11. A reply proves that DC02 can receive traffic from DC01 across VMnet2.

Send four echo requests from DC02 to DC01 by running:

ping 10.50.0.10

Why test the reverse direction?

The reverse check proves that DC01 also accepts inbound echo requests. Both directions must work before the nodes can support later directory services.

You should receive four replies in each direction. This proves that both static identities communicate across the isolated host-only network.

Seeing timed-out ping requests?

Confirm both virtual machines remain connected to VMnet2. Check that ipconfig /all shows the planned address on each connected adapter.

Run the firewall rule command again on the server that does not answer. If the requests still time out, help me troubleshoot the two-way VMnet2 ping test.

That is the identity layer locked in. Both servers now reach each other through their planned static addresses.

Secret mission

Prove Your Rollback Point Works

Create a clean pre-promotion snapshot for both servers. Then test DC02 by adding a desktop file and proving that reversion removes it while preserving the server identity.

Clean Up Your Resources

Your VMware Workstation Pro lab has no cloud charges. Decide whether to keep the lab available, pause it, or delete it entirely.

Remember the evaluation window

The Windows Server 2022 Evaluation period expires after 180 days. Retaining the lab preserves your setup within that time-limited window.

Resources you used:

A host-only network named VMnet2 with subnet 10.50.0.0/24.
A virtual machine named DC01 with a 60 GB growable virtual disk.
A virtual machine named DC02 with a 60 GB growable virtual disk.
Two snapshots named Pre-ADDS-Baseline.
One Windows Server 2022 Evaluation ISO stored on the Windows host.

Keep everything running

No action needed. Choose this if you are moving directly into Project 2.

Keep DC02 running for the follow-on project.
Power on DC01 when you begin Project 2.
Retain the VMnet2 network.
Retain both VM folders.
Retain both Pre-ADDS-Baseline snapshots.
Retain the Windows Server 2022 Evaluation ISO.

Pause - I'll come back to this later

Shut down the running guest to release its 4 GB memory allocation. Your network files, VM files, ISO, and snapshots remain available.

Switch back to DC02.
Shut down DC02 cleanly from inside Windows Server.
Confirm Workstation Pro shows DC02 powered off.
Keep DC01 powered off.
Retain the VMnet2 network.
Retain both VM folders.
Retain both Pre-ADDS-Baseline snapshots.
Retain the Windows Server 2022 Evaluation ISO.

Delete - I don't want to use this again

Deletion permanently removes the lab. That includes both rollback points.

Switch back to DC02.
Shut down DC02 cleanly from inside Windows Server.
Confirm Workstation Pro shows both guests powered off.
Select DC01 in the Workstation Pro library.
Remove DC01 from disk.
Select DC02 in the Workstation Pro library.
Remove DC02 from disk.
Confirm neither VM remains in the Workstation Pro library.

That clears the largest local resources. Their Pre-ADDS-Baseline snapshots are removed with the VM files.

Return to the Virtual Network Editor from earlier.
Select VMnet2.
Remove VMnet2.
Confirm VMnet2 no longer appears in Virtual Network Editor.

The isolated network is now gone. The downloaded ISO is the final local artifact.

Return to the stable host folder in File Explorer.
Delete the Windows Server 2022 Evaluation ISO.
Confirm the ISO no longer appears in the folder.

Nice Work!

Excellent work! You built two activated Windows Server 2022 Evaluation virtual machines in VMware Workstation Pro. Your isolated lab is ready for the Active Directory follow-on project.

You've learned how to:

Configure an isolated host-only network named VMnet2 on 10.50.0.0/24. Disable VMware DHCP to control server addressing.
Install two independent servers from one ISO. Activate both servers through temporary NAT access before isolation.
Replace APIPA addresses with static IPv4 addresses. Assign 10.50.0.10/24 to DC01. Assign 10.50.0.11/24 to DC02. Permit echo requests through Windows Firewall. Prove two-way ICMP connectivity between the servers.
Secret Mission: Create pre-AD DS snapshots named Pre-ADDS-Baseline. Revert DC02 to prove the rollback removes snapshot-test.txt while preserving the server's name and static address.

Ready to quiz yourself?