Windows Lab 2 - Creating Server02
In this lab we'll be creating our second virtual machine which will be named Server02. We're going to create this server the same way we created Server01. In this lab you won't have screenshots to help guide you. You'll want Server01 running during this lab.
Create a Virtual Machine named Server02 using VirtualBox
Open VirtualBox and create a new virtual server. If you need assistance with the steps please refer to Windows Lab 01 for more detailed instructions. Use the following settings when creating the server.
Version: Windows 2019 (64-bit)
RAM: 2048MB (This can be less if you don't have a lot of RAM in your computer)
Hard disk file type: VDI; Dynamically allocated
Hard disk size: 100.00 GB
After creating the virtual server change the following settings.
Display: Enable 3d Acceleration (Adjust scale factor if needed)
Network: Internal Network; Promiscuous Mode - Allow All
Storage: Insert the Windows Server disk into the disk drive
Once the machine is created it should look like the one in the image below. Power on both virtual machines.
Installing Windows Server 2022
Server01 can sit at the logon screen while we work on Server02. Server02 should boot to the Windows Installation screen. This time we're not going to install the version with the desktop experience. This will be a command line only version of Windows Server. Choose the default options for the first two screens to start the install.
When selecting the operating system choose Windows Server 2022 Datacenter, then follow all the same steps from lab 1 to complete the install.
Applicable notices and license terms: I Accept
Type of installation: Custom
Where do you want to install: Drive 0 Unallocated Space
After the install completes you'll be asked to set the password just like when you installed Server01, this time the prompt will be in a command line interface. Press enter with Ok selected.
Set the password to P@ssw0rd and hit tab to move to the confirm prompt, type the password again and hit enter.
Press enter to acknowledge the password change.
Install Guest Additions for VirtualBox
Even though this is a command line only version of Windows we still want the Guest Additions installed.
Insert the Guest Additions CD into the virtual machine. After doing that type in 15 and hit enter to exit to PowerShell.
In PowerShell type in d: and hit enter to switch to the CD drive. Then type dir and hit enter to get a directory listing of the root of the CD. In there you'll see the install program for the Guest Additions. Start typing the name vbox then hit tab until .\VBoxWindowsAdditions.exe is displayed, then hit enter.
The installer for the Guest Additions will start, follow the prompts the same way you did on Server01.
Once complete hit Finish to restart Server02.
After the server restarts send a CTRL-ALT-DEL to the server to login.
Login to Server02
After the guest additions are installed we're going to change settings on Server02 like we did on Server01.
The first thing we're going to do is rename the server. Type in 2 and hit enter.
Type in Server02 for the name of the server and hit enter. When it asks if we want to restart hit y and hit enter.
Now that the server has the correct name we're going to configure the network settings, press 8 and hit enter.
We only have one network card in our virtual server. That's the card we're going to configure, select it by typing in 1 and hitting enter.
Hit 1 to set the network adapter address. Then enter the following settings. If this is successful you can skip the next two steps.
s for static
IP address: 192.168.10.2
Subnet mask: 255.255.255.0
If you get an error message during this process then you may need to set the IP information manually using PowerShell. When you're returned to the menu hit 15 to exit to PowerShell. Type in Get-NetAdapter to find the interface index. On my system that was 6. They type the following command to set the IP address. Change out the InterfaceIndex with yours from the Get-NetAdapter cmdlet.
New-NetIPAddress - InterfaceIndex 6 -IPAddress 192.168.10.2 -PrefixLength 24 -DefaultGateway 192.168.10.254
Optionally you can set the DNS settings in PowerShell as well. Type in the command below. If you do this you can skip the next step.
Set-DnsClientServerAddress -InterfaceIndex 6 -ServerAddress 192.168.10.1
If everything went well with setting the IP you'll be returned to the main menu, enter 8 to return to network settings, the press 1 to select the network card. At the network adapter settings screen type 2 to set the DNS servers, enter 192.168.10.1 for the preferred DNS server and nothing for the alternate.
Next we're going to set the time zone, choose 9 from the main menu.
The familiar Date and Time window will appear, click the Change time zone button.
Change the time zone to Eastern Time and click Ok on the two windows to close them.
Server02 has now been configures and we can move to the next step to make sure the two server can talk to each other.
Verify Connectivity Between Servers
Now we're going to verify that the server can talk to each other over the network by pinging them. Connectivity will be necessary moving forward so we need to make sure they can communicate. Server01 should still be running in the back ground. If it's not, turn it on now and leave it on at the login screen.
On Server02 open PowerShell by typing 15 and pressing enter.
In PowerShell type ping 192.168.10.1 and hit enter. You'll notice the ping fails. Don't worry, by default ICMP is blocked by the built in firewall. We need to modify the firewall rules on Server01 before it will work. Switch to Server01 now.
After logging into Server01 Server Manager will open automatically. If it doesn't, open it from the Windows menu. Select the Tools dropdown and click Windows Defender Firewall with Advanced Security.
In the Firewall window select the Inbound Rules section. Scroll down a little until you see the four Core Networking Diagnostics items. Select all four and click Enable Rule.
After clicking Enable Rule their should be green check marks next to the four rules indicating they're on.
Switch back to Server02 and try that ping command again. You can press the up arrow within PowerShell active to retype the previous command. Now that those rules on the firewall have been enabled you can ping the server.
While you're on Server02 we want the same firewall rule so we can do a test ping from Server01 to Server02. In PowerShell type in netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow
This will create a firewall rule that will allow incoming IPv4 ICMP code 8 (echo) packets in from anywhere.
On Server01 close the firewall screen which will return you to Server Manager. Click Tools - Windows PowerShell.
Type in ping 192.168.10.2 and hit enter. If the changes to the firewall were properly made on Server02 you should receive replies.
To shutdown Server02 choose option 14 and hit y for yes. If you're in PowerShell instead of the welcome screen you can type in sconfig to return to the welcome screen.
Once you've verified connectivity between the two servers shut them both down and take snapshots of both machines called Lab 2 Complete.