Build Your Home Lab Foundation

Set up an Ubuntu Server VM and connect to it via SSH from Windows.

Introduction

30 Second Summary

Every IT professional, sysadmin, and security analyst needs a safe place to practice. A home lab gives you a personal sandbox to break things, fix them, and build real skills without risking anyone's production systems.

In this project, you will set up a virtual machine running Ubuntu Server on your Windows PC, configure a private network between them, and connect remotely via SSH.

What You'll Build

A fully functional virtual home lab with an Ubuntu Server VM that you can SSH into from your Windows machine over a private network.

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

  • A configured Oracle VirtualBox installation with a Host-Only network connecting your Windows host to your VM.
  • An Ubuntu Server 26.04 LTS virtual machine with 2GB RAM and 20GB of disk space.
  • A working SSH connection from your Windows terminal into your Ubuntu server over the private network.
  • Secret Mission: Write a bash script that collects system information and outputs a formatted report.

Are there any prerequisites?

None. You just need a Windows PC with at least 16GB of RAM. This guide walks you through installing every tool from scratch.

Install VirtualBox and Download Ubuntu Server

Every IT professional needs a safe environment to practice in. A virtual machine gives you an isolated computer running inside your real computer, so you can experiment without risking your actual system.

In this step, you will install the software that creates virtual machines, download the operating system you will run inside one, and set up a private network so your Windows PC can talk to the VM directly.

In this step, get ready to:
  • Install Oracle VirtualBox 7.2 on your Windows PC.
  • Download the Ubuntu Server 26.04 LTS ISO file.
  • Create a Host-Only network in VirtualBox for private communication between your PC and the VM.
Download and install Oracle VirtualBox

Oracle VirtualBox is a free, open-source application that lets you run entire operating systems inside virtual machines on your existing PC. It is classified as a Type-2 hypervisor because it runs on top of your normal Windows operating system.

  • Press the Windows key to open your search bar.
  • Type VirtualBox and look at the results.

✔️ I see VirtualBox 7.0 or higher

VirtualBox is already installed on your machine. Open it and check the version number.

  • Open VirtualBox Manager from the search results.
  • Click Help in the top menu bar, then click About VirtualBox.
  • Confirm the version starts with 7.0 or higher. If so, close the About dialog and proceed to the next substep.

What if I have version 7.0 or 7.1?

VirtualBox 7.0 and 7.1 are compatible with everything in this project. You can continue without upgrading. If you want the latest 7.2 release, follow the instructions in the next tab to download and install over your current version.

ⓧ I see an older version (6.x or below)

You have an outdated version of VirtualBox that may not support all features used in this project. You need to upgrade to 7.2.

  • Close VirtualBox completely. Make sure no VMs are running.
  • Open your browser and navigate to the VirtualBox downloads page:
  • https://www.virtualbox.org/wiki/Downloads
  • Click the Windows hosts link to download the installer.
  • Right-click the downloaded installer file and select Run as administrator.
  • The installer will detect your existing version and offer to upgrade it. Click Yes to proceed.
  • Accept all defaults and click Next through each screen.
  • When you see warnings about unsigned drivers or network interfaces being temporarily disconnected, click Yes to allow them. These are VirtualBox's networking drivers being installed.
  • Click Install, then click Finish when the installation completes.

VirtualBox Manager should open automatically after the upgrade finishes.

ⓧ I don't have VirtualBox installed

No problem. You will download and install VirtualBox from scratch.

  • Open your browser and navigate to the VirtualBox downloads page:
  • https://www.virtualbox.org/wiki/Downloads
  • Click the Windows hosts link to download the installer.
  • Once the download completes, double-click the installer file to run it.
  • The installer opens a Welcome dialog. Click Next.
  • On the component selection screen, leave all options checked (including USB support and Networking). Click Next.
  • Accept the default install location and click Next.
  • You may see a warning that installing the networking feature will temporarily disconnect your network. Click Yes to proceed.
  • Click Install to begin the installation.
  • During installation, you may see prompts about unsigned drivers. Click Install on each of these prompts. These are VirtualBox's kernel and network drivers that allow VMs to run.
  • When finished, leave Start Oracle VirtualBox after installation checked and click Finish.

VirtualBox Manager opens. You are ready to continue.

Why VirtualBox over other options?

VirtualBox is free, open-source (GPL licensed), and does not require creating a vendor account to download. Its Host-Only networking model is explicit and educational, making it ideal for learning networking concepts.

VMware Workstation is also free now, but requires a Broadcom account and has a more complex download process. For a learning lab focused on understanding, VirtualBox is the simpler starting point.

Installer failed or VirtualBox won't open?

If the installer fails with a rollback error, try right-clicking the installer and selecting Run as administrator. Third-party antivirus software can also block the network driver installation. Temporarily disable it and retry.

If you see an error about Hyper-V or hypervisor conflicts, you may need to disable Hyper-V in Windows Features. Search for Turn Windows features on or off in your Start menu, uncheck Hyper-V, and restart your PC.

Help me troubleshoot VirtualBox installation on Windows

Download the Ubuntu Server 26.04 LTS ISO

An ISO file is a digital copy of an installation disc. You will use this file to install Ubuntu Server inside your virtual machine, just like you would insert a DVD into a physical computer.

  • Open your browser and navigate to the Ubuntu Server 26.04 release page:
  • https://releases.ubuntu.com/26.04/
  • Find and click the download link for ubuntu-26.04-live-server-amd64.iso.
  • Save the file to a location you can easily find later, such as your Downloads folder.

Why Ubuntu Server instead of Desktop?

Ubuntu Server has no graphical interface. This forces you to learn the command line, which is the actual skill needed for IT, sysadmin, and cybersecurity careers.

It also uses less RAM because there is no desktop environment running. This leaves room for additional VMs if you expand your lab later.

  • Wait for the download to complete. The file is approximately 2.7 GB, so it may take several minutes depending on your internet connection.
  • Confirm the file exists in your download location. You should see ubuntu-26.04-live-server-amd64.iso listed.

Download interrupted or file seems too small?

If the download fails partway through, delete the partial file and try again. The final file should be approximately 2.7 GB. A significantly smaller file means the download was incomplete.

Help me download the Ubuntu Server ISO

Create the Host-Only network in VirtualBox

A Host-Only network creates a private connection between your Windows PC and your virtual machines. No traffic leaves your computer. This is the network you will use to SSH into your server from Windows later in the project.

  • In VirtualBox Manager, click File in the top menu bar.
  • Click Tools.
  • Click Network Manager.
  • Click the Host-Only Networks tab.
  • Click Create.
  • A new adapter appears in the list. It is typically named VirtualBox Host-Only Ethernet Adapter.
  • Select the new adapter. Confirm the IPv4 Address shows 192.168.56.1.
  • Confirm the DHCP Server is enabled. This is on by default. It automatically assigns IP addresses to VMs that connect to this network.
  • Click Apply, then close the Network Manager window.

What is a Host-Only network?

A Host-Only network is a virtual network that only exists between your Windows host (your real PC) and your VMs. It cannot reach the internet. VMs on this network get IP addresses in the 192.168.56.x range.

Your Windows host always gets 192.168.56.1 on this network. The DHCP server hands out addresses like 192.168.56.101 to VMs that connect. This gives you a predictable, private address to SSH into later.

Don't see the Host-Only Networks tab?

Make sure you are using VirtualBox 7.0 or higher. In older versions, the Network Manager may be in a different location. Also confirm you navigated to File then Tools then Network Manager (not the Settings menu for a specific VM).

If the Create button is grayed out, close VirtualBox, right-click its icon, and reopen it with Run as administrator.

Help me create a Host-Only network in VirtualBox

Your tools are ready. VirtualBox is installed, the Ubuntu Server ISO is downloaded, and your private network is configured. Next up, you will create the virtual machine itself and install Ubuntu Server inside it.

Create and Install Your Ubuntu Server VM

Your VirtualBox installation is ready and your private Host-Only network is in place. Now it's time to create the virtual machine itself and install an operating system on it.

In this step, you'll build an Ubuntu Server VM from scratch, walk through the text-based installer, and bring the system up to date. By the end, you'll have a fully working Linux server running inside your Windows PC.

In this step, get ready to:
  • Create and configure a virtual machine in VirtualBox with networking and storage.
  • Install Ubuntu Server 26.04 LTS using the text-based installer.
  • Log in and fully update the system.
Create and configure the virtual machine

A virtual machine needs a name, an operating system type, memory, and a hard disk. You'll also attach your downloaded ISO and set up two network adapters so the VM can reach the internet and your private network.

  • In VirtualBox Manager, click New in the toolbar to start the Create Virtual Machine workflow.
  • Enter Ubuntu-Server-Lab in the Name field.
  • Set Type to Linux.
  • Set Version to Ubuntu (64-bit).
  • In the hardware section, set Base Memory to 2048 MB.
  • In the hard disk section, select Create a Virtual Hard Disk Now.
  • Set the disk size to 20 GB. Leave the format as VDI and allocation as Dynamically Allocated.
  • Click Finish to create the VM.

What does dynamically allocated mean?

A dynamically allocated disk file starts small and grows as you add data, up to the 20 GB maximum. It does not immediately consume 20 GB on your actual hard drive.

Your VM now appears in the Machines list. Before starting it, you need to configure its network adapters and attach the Ubuntu ISO.

  • Select Ubuntu-Server-Lab in the Machines list, then click Settings.
  • Click Network in the left sidebar.
  • On the Adapter 1 tab, confirm Attached to is set to NAT. This is the default and gives your VM internet access.
  • Click the Adapter 2 tab.
  • Check the Enable Network Adapter box.
  • Set Attached to to Host-Only Adapter. Select the adapter you created in Step 1 (VirtualBox Host-Only Ethernet Adapter).

Why two network adapters?

Adapter 1 (NAT) lets the VM reach the internet for downloading updates. Adapter 2 (Host-Only) creates a private link between your Windows PC and the VM.

Later, you'll use the Host-Only network to SSH into the VM from Windows. The two adapters work side by side without interfering.

  • Still in Settings, click Storage in the left sidebar.
  • Under Controller: IDE, click the empty disk icon (it shows Empty).
  • On the right side, click the small disk icon next to Optical Drive.
  • Select Choose a disk file and browse to your downloaded ubuntu-26.04-live-server-amd64.iso file.
  • Click OK to close Settings.

Your VM is now configured with two network adapters and the Ubuntu installer ISO attached.

Don't see your Host-Only adapter in the dropdown?

Go back to File then Tools then Network Manager and confirm a Host-Only network exists with IP 192.168.56.1. If it's missing, click Create to add one.

help me troubleshoot my VirtualBox Host-Only network adapter not showing up

Install Ubuntu Server with the text-based installer

The Ubuntu Server installer is entirely text-based. You'll navigate it using your arrow keys, Tab, Spacebar, and Enter. The process takes about 5-10 minutes depending on your hardware.

  • Select Ubuntu-Server-Lab in VirtualBox Manager and click Start.
  • The VM window opens and boots from the ISO. Wait for the installer to load.
  • Select your language (English) and press Enter.
  • If offered an installer update, select Continue without updating.
  • Accept the default keyboard layout and select Done.
  • On the network screen, let it auto-configure via DHCP and select Done.
  • Skip the proxy screen by selecting Done.
  • Accept the default mirror and select Done.
  • On the storage screen, leave Use an entire disk checked and select Done.
  • Review the storage summary and select Done.
  • Confirm the destructive action by selecting Continue.

The installer now asks you to set up your profile. This is where you create your login credentials.

  • Enter your real name in the Your name field.
  • Enter lab-server in the Your server's name field. This is the hostname.
  • Enter a username you'll remember in the Pick a username field.
  • Enter a strong password and confirm it.
  • Select Done.

Next comes the SSH setup screen. This is critical for connecting remotely later.

  • On the SSH Setup screen, use Spacebar to check the Install OpenSSH server box.
  • Select Done.
  • On the Featured Server Snaps screen, do not select anything. Select Done.

What is OpenSSH?

OpenSSH is the tool that lets you connect to your server remotely from another computer. Installing it now means you won't need to configure it manually later.

In Step 4, you'll use SSH from your Windows machine to control this server without touching the VirtualBox window.

The installer will now download and install packages. This may take several minutes depending on your internet speed.

  • When installation completes, select Reboot Now.
  • If prompted to remove the installation medium, press Enter. VirtualBox handles this automatically.

VM stuck on a black screen after reboot?

Wait 30-60 seconds. The first boot after installation can be slow. If you still see nothing, press Enter once to trigger the login prompt.

If the installer loops back to the beginning, power off the VM (Machine then Close then Power Off), go to Settings then Storage, remove the ISO from the IDE controller, and start the VM again.

help me fix my Ubuntu Server VM not booting after installation

Log in and update the system

After reboot, your VM boots into Ubuntu Server. You'll see a text login prompt asking for your username and password.

  • At the login: prompt, type your username and press Enter.
  • Type your password and press Enter. The password won't appear as you type. This is normal.

You're now logged into your Ubuntu Server. The first thing to do on any fresh install is update all packages to their latest versions.

  • Update your system packages by running this command:
sudo apt update && sudo apt upgrade -y

What does this command do?

This is actually two commands chained together. sudo apt update refreshes the list of available packages from Ubuntu's servers. sudo apt upgrade -y downloads and installs any newer versions of your installed packages.

The -y flag automatically says "yes" to all prompts so you don't have to confirm each package manually.

This process may take a few minutes. You'll see package names scrolling by as they download and install.

  • Once it finishes, verify your Ubuntu version by running:
lsb_release -a

You should see output confirming Ubuntu 26.04 LTS. The Description line shows Ubuntu 26.04 LTS.

Seeing 'Unable to locate package' or network errors?

This means your VM can't reach the internet. Check that Adapter 1 in your VM's network settings is set to NAT. Power off the VM, fix the setting, and start it again.

If you see a dpkg lock error, wait a minute and try again. Ubuntu sometimes runs automatic updates in the background on first boot.

help me fix network connectivity issues in my Ubuntu Server VirtualBox VM

Your Ubuntu Server is installed, up to date, and ready to go. Next up, you'll explore Linux command line fundamentals and discover how to navigate the file system, manage permissions, and install packages.

Explore Linux Command Line Fundamentals

Your Ubuntu Server is installed, updated, and ready for action. Now you need to learn how to control it.

Unlike Windows, Linux servers have no graphical interface. Everything you do happens through text commands typed into a terminal. In this step, you will practice the most essential commands for navigating files, managing permissions, and inspecting your system.

In this step, get ready to:
  • Navigate the file system and create directories and files.
  • Manage user identity and file permissions.
  • Inspect system resources and install a package from the command line.
Navigate the file system and create files

Every Linux system organizes files into a tree of directories starting from / (the root). You will use a handful of commands to move around this tree, inspect what is inside, and create your own files.

  • In your VM console, check your current location and list the files around you by running these commands one at a time:
pwd
ls -la

What do these commands do?

  • pwd prints the full path of the directory you are currently in (your "working directory").
  • ls -la lists every file in the current directory, including hidden files (those starting with a dot) and details like permissions, owner, and size.
  • Navigate into the system configuration directory and view your server's hostname by running:
cd /etc
cat /etc/hostname

What do these commands do?

  • cd /etc changes your current directory to /etc, where Linux stores system configuration files.
  • cat /etc/hostname prints the contents of the hostname file. You should see lab-server (the hostname you chose during installation).
  • Create a directory for your lab notes and an empty file inside it by running:
mkdir ~/lab-notes
touch ~/lab-notes/day1.txt

What do these commands do?

  • mkdir ~/lab-notes creates a new directory called lab-notes inside your home folder. The ~ symbol is a shortcut that always points to your home directory.
  • touch ~/lab-notes/day1.txt creates an empty file called day1.txt inside that new directory.
  • Confirm the directory and file were created by running:
ls ~/lab-notes

You should see day1.txt in the output.

Don't see day1.txt?

  • Check for typos in the mkdir and touch commands. Linux is case-sensitive, so Lab-Notes and lab-notes are different directories.
  • Make sure you included the ~ before /lab-notes. Without it, the command tries to create the folder at the root of the file system, which requires root permissions.
  • help me troubleshoot why my lab-notes directory was not created

What is the Linux directory structure?

Linux organizes everything into a few key top-level directories:

  • /home contains personal folders for each user.
  • /etc stores system-wide configuration files.
  • /var/log holds log files that record what the system is doing.
  • /tmp is for temporary files that get cleared on reboot.
Check users and manage permissions

Linux is a multi-user system. Every file has an owner, a group, and a set of permissions that control who can read, write, or execute it.

  • Check your identity on the system by running these commands one at a time:
whoami
id
sudo whoami

What do these commands do?

  • whoami prints the username you are logged in as.
  • id shows your numeric user ID (uid), group ID (gid), and all groups you belong to.
  • sudo whoami temporarily elevates your privileges to the root (administrator) account, then prints root. This proves your user has sudo access.
  • Change the permissions on your lab-notes directory by running:
chmod 755 ~/lab-notes
  • Verify the permissions were applied by running:
ls -la ~/lab-notes

In the output, look at the first line (the . entry representing the directory itself). You should see drwxr-xr-x at the beginning.

What does 755 mean?

Linux permissions use three numbers, one each for the owner, the group, and everyone else. Each number is the sum of: read (r=4), write (w=2), and execute (x=1).

  • 7 (owner) = read + write + execute (4+2+1). Full control.
  • 5 (group) = read + execute (4+1). Can view and enter, but not modify.
  • 5 (others) = read + execute (4+1). Same as group.

Permissions look different than expected?

  • Make sure you ran chmod 755 ~/lab-notes with the ~ symbol. Without it, the command targets a different path.
  • If you see a permission denied error, try adding sudo before the command. Your user should own the directory, but sudo overrides any ownership issue.
  • help me understand why my chmod command did not work as expected
Inspect system info and install a package

Sysadmins constantly check what resources a server has available. These commands give you a quick health snapshot of your machine.

  • View your system's hardware and resource information by running these commands one at a time:
uname -a
df -h
free -h
ip addr show

What do these commands do?

  • uname -a prints kernel and OS information (version, architecture, hostname).
  • df -h shows disk usage in human-readable format. You will see your 20 GB virtual disk.
  • free -h shows RAM usage. You will see approximately 2 GB total (the RAM you allocated to this VM).
  • ip addr show lists all network interfaces and their IP addresses.
  • Install the net-tools package (which provides the classic ifconfig command) by running:
sudo apt install net-tools -y

What does this command do?

apt is Ubuntu's package manager. It downloads and installs software from Ubuntu's online repositories. The -y flag automatically answers "yes" to the confirmation prompt so the install proceeds without waiting for input.

  • Use the newly installed ifconfig command to view your network interfaces by running:
ifconfig

Look for the enp0s8 interface in the output. It should show an IP address in the 192.168.56.x range. This is the Host-Only network adapter that connects your VM to your Windows host.

Don't see an IP on enp0s8?

  • If enp0s8 does not appear at all, your VM's second adapter may not be configured as Host-Only. Power off the VM, go to Settings, then Network, and confirm Adapter 2 is enabled and set to Host-Only Adapter.
  • If enp0s8 appears but has no IP, run sudo dhclient enp0s8 to request an address from the DHCP server.
  • help me troubleshoot why my enp0s8 interface has no IP address
  • Confirm your Host-Only IP directly by running:
ip addr show enp0s8

You should see an inet line with an address like 192.168.56.101 (your exact number may differ). This is the address your Windows host will use to reach this VM over SSH in the next step.

You now have a solid foundation in Linux command line basics. Next up, you will use that 192.168.56.x IP address to connect to your server remotely from Windows using SSH.

Connect via SSH from Windows

You can navigate the Linux file system, manage files, and install packages. All of that happened directly at the VM console, like sitting in front of a physical server.

In the real world, servers live in data centers or the cloud. Administrators rarely sit at a physical console. Instead, they connect remotely using SSH (Secure Shell), a protocol that gives you an encrypted command-line session over a network. In this step, you will connect from your Windows machine to your Ubuntu VM over the private Host-Only network.

In this step, get ready to:
  • Verify that the SSH service is running inside your VM.
  • Ping your VM from Windows to confirm network connectivity.
  • Establish an SSH connection from Windows Terminal into your Ubuntu server.
Verify SSH is running and note your VM's IP

Before you can connect remotely, you need to confirm that the SSH service is accepting connections inside your VM. You also need to know the VM's IP address on the Host-Only network.

  • In your Ubuntu VM console, check that SSH is active by running this command:
sudo systemctl status ssh

What should I see?

Look for the line that says Active: active (running). This confirms that the SSH daemon is listening for incoming connections on port 22.

Ubuntu 26.04 uses socket activation for SSH, so you may also see a reference to ssh.socket in the output. This is normal and means SSH is ready to accept connections.

  • Press q to exit the status view.
  • Now find your VM's Host-Only IP address by running:
ip addr show enp0s8

What am I looking for?

Find the line that starts with inet (not inet6). It shows your VM's IPv4 address on the Host-Only network, for example 192.168.56.101. Write this IP address down. You will need it in the next substep.

  • Note the IP address shown after inet on the enp0s8 interface. It will be in the 192.168.56.x range.

Don't see an IP on enp0s8?

Make sure Adapter 2 is set to Host-Only Adapter in your VM's network settings. Power off the VM, check Settings then Network then Adapter 2, and confirm it is enabled and attached to your Host-Only adapter.

help me figure out why my VM's enp0s8 interface has no IP address

Ping and connect from Windows Terminal

Now that you know SSH is running and you have the VM's IP, switch over to your Windows machine. You will test network connectivity first, then establish the SSH connection.

  • Press the Windows key on your keyboard to open the search bar.
  • Type Windows Terminal and press Enter to open it.
  • Test that your Windows machine can reach the VM by running this command:
ping [[VM_IP="your VM's IP, e.g. 192.168.56.101"]]
  • You should see replies coming back from your VM's IP address. Press Ctrl+C to stop the ping.

What does this prove?

A successful ping confirms that the Host-Only network is working. Your Windows host (192.168.56.1) and your Ubuntu VM (192.168.56.x) can communicate over this private virtual network.

  • Now connect to your VM via SSH by running:
ssh [[VM_USERNAME="your Ubuntu username"]]@[[VM_IP="your VM's IP, e.g. 192.168.56.101"]]

What happens on first connection?

The first time you connect, SSH will show a host key fingerprint and ask you to verify it. This is a security feature that lets you confirm you are connecting to the correct server.

Type yes and press Enter to accept the fingerprint. Then enter your Ubuntu password when prompted. The password will not show any characters as you type. This is normal.

  • Type yes when asked about the host key fingerprint, then press Enter.
  • Enter your Ubuntu password and press Enter.

Your terminal prompt changes to show your Ubuntu username and hostname. You are now remotely controlling your server from Windows.

Connection timed out or refused?

  • If the ping failed, check that the VM is running and that Adapter 2 is set to Host-Only in VirtualBox.
  • If the ping works but SSH is refused, go back to your VM console and run sudo systemctl status ssh to confirm the service is active.
  • Double-check that you are using the correct IP address and username.

help me troubleshoot my SSH connection from Windows to my Ubuntu VM

Run commands remotely and disconnect

You are now doing exactly what sysadmins do every day. The commands you run in this Windows Terminal window execute on your Ubuntu server, not on your Windows machine.

  • Confirm you are on the remote server by running these commands:
hostname
uptime
last
who

What do these commands show?

  • hostname prints the server's name. It should show lab-server, proving you are on the VM and not your Windows machine.
  • uptime shows how long the server has been running since its last boot.
  • last displays a history of recent logins, including your new SSH session.
  • who shows currently logged-in users. You should see your username with a pts/ prefix, indicating a remote terminal session.
  • When you are done, disconnect from the SSH session by typing:
exit

Your terminal prompt returns to your Windows machine. You have just connected to a remote server over SSH, the single most important skill in Linux system administration.

Hostname shows your Windows PC name?

If hostname does not show lab-server, your SSH connection may not have succeeded. Check that your terminal prompt shows your Ubuntu username and lab-server (for example, youruser@lab-server). If it still shows your Windows machine name, run the ssh command again.

help me verify that my SSH session is connected to my Ubuntu VM and not running locally on Windows

Secret mission

Write a System Info Script

You have proven you can set up a VM and connect remotely. Now prove you can automate a common sysadmin task: writing a bash script that collects system information into a formatted report.

Clean Up Your Resources

Clean Up Your Resources

Decide whether to keep your resources running, pause them to come back later, or delete them entirely. This project runs entirely locally, so there are no ongoing costs.

Resources you used:

  • Oracle VirtualBox 7.2 installed on your Windows PC.
  • Ubuntu-Server-Lab VM (Ubuntu Server 26.04 LTS, 2 GB RAM, 20 GB virtual disk).
  • Host-Only network (VirtualBox Host-Only Ethernet Adapter, IP 192.168.56.1).
  • Ubuntu Server ISO file (ubuntu-26.04-live-server-amd64.iso, approximately 2.7 GB) saved on your PC.

Keep everything running

No action needed. Choose this if you are still actively building or plan to continue learning Linux administration in your next session.

  • Your VM will remain in VirtualBox Manager, ready to start anytime.
  • The Host-Only network stays configured for future VMs.
  • The ISO file stays on disk in case you need to reinstall or create a new VM.
  • VirtualBox stays installed and ready for your next project.

Pause - I'll come back to this later

Shut down your VM to free up RAM and CPU resources while keeping everything intact for later.

  • If you are still SSH'd into the VM, type exit to disconnect.
  • In VirtualBox Manager, right-click Ubuntu-Server-Lab and select Close, then Power Off.
  • Your VM, network settings, and all files inside the VM are preserved on disk.
  • To resume, open VirtualBox Manager, select your VM, and click Start.

Delete - I don't want to use this again

Remove all project resources completely. This frees up disk space and removes the virtual network adapter.

  • If you are still SSH'd into the VM, type exit to disconnect.
  • In VirtualBox Manager, right-click Ubuntu-Server-Lab and select Remove.
  • Choose Delete all files to remove the virtual hard disk and all VM data.
  • Go to File, then Tools, then Network Manager. Click the Host-Only Networks tab, select your adapter, and click Remove.
  • Delete the Ubuntu Server ISO from your PC. Open File Explorer, navigate to where you saved ubuntu-26.04-live-server-amd64.iso, right-click it, and select Delete.
  • To uninstall VirtualBox, press the Windows key and type Add or remove programs. Find Oracle VirtualBox in the list, click it, and select Uninstall.

Nice Work!

Nice Work!

Nice work! You just built a fully functional virtual home lab from scratch. You have an Ubuntu Server running inside VirtualBox that you can connect to remotely from your Windows machine over a private network.

You've learned how to:

  • Installed Oracle VirtualBox and created a Host-Only virtual network on your Windows PC.
  • Built an Ubuntu Server 26.04 LTS virtual machine from scratch and navigated the Linux command line to manage files, permissions, and packages.
  • Configured and used SSH to remotely connect from Windows to your Ubuntu server over a private network.
  • Secret Mission: Wrote a bash script that automates system information collection into a formatted report.

Ready to quiz yourself?