Part 1: Exchange Server 2019 Hyper V Install – Prepare VMs

This post is the first part of a series where I share my experience on how to prepare an Exchange Server 2019 Hyper V install and install an AD Server and an Exchange 2019 Server on Hyper V.  The first part covers the Virtual Machines.

Microsoft recommends min. 128 GB of RAM for an Exchange 2019 Install in a production environment. Curious about how Exchange 2019 behaves and for testing purpose I will set up a test environment on my test lab before we start to build our real test environment at work.

Before we begin some information on the available resources :

You see it’s just a home lab, so much more curious am I if Exchange 2019 is able to run with these specifications.

Exchange Server 2019 Hyper V Install

Target is to prepare 2 VMs

• Server 2019 as Domain Controller running Active Director with Desktop Experience ( GUI )
• Server 2019 Core where we will install Exchange 2019

Ok let’s get to it :

Create a new Virtual Machine for the Domain Controller ( AD2019 ) running on Server 2019 with Desktop Experience ( GUI )

Specify Name and Location:

> Choose 2nd generation > Next

Assign Memory:

I do not use Dynamic Memory in hope of a better Performance.
When we later prepare the VM for an Exchange Server 2019 Hyper V Install a fixed memory is mandatory. Exchange 2019 does not support Dynamic Memory.

Configure Networking:

Set it to fit your needs but make sure that Exchange and the Domain Controller can communicate with each other. I will choose the default switch for both VMs. This makes sure that they NAT to the NIC of the host machine ( Win 10 ) and have internet access. You can block internet access if needed through the firewall of the host machine by blocking all inbound and outbound connections from and to the Hyper-V default IP ( 174.24.96.129 ). When blocked both guests still can communicate with each other.

Connect Virtual Hard Disk:

Under Create a virtual hard disk specify the location and size of the Virtual Disk ( .vhdx ). In this case, 45GB will be more than enough for my needs.
If you already have a Domain Controller prepared on an existing virtual hard disk choose that option.

Installations Option:

Choose the location where you have stored the Server 2019 installation media.

Check the Summary and confirm with Finish.

Go to the Settings of the newly created Virtual Machine to check the hardware :

Install Windows Server 2019 with Desktop Experience

First, connect to the newly created Virtual Machine ( Ad2019 ). It is easier to hit a key straight away after the VM starts when you connect first. You will need to hit a key to boot from DVD.

Set the language to install, Time and currency format and the keyboard or input method.

This VM ( AD2019 ) will run Windows Server 2019 Datacenter Edition with Desktop Experience.

Since this scenario covers a new install on a new VM choose Custom

Wait until Windows Setup finishes. Depending on your chosen hardware specs this can take some time.

Create the 2nd Virtual Machine for Exchange 2019 running on Server 2019 core.

In Hyper V Manager create a new virtual machine and repeat the steps listed under Point 1.

I gave this VM 60 GB disk space. This should fit all needs for this Exchange Server 2019 Hyper V Install.

Don’t forget to adjust the hardware in the settings of the VM.

Install Windows Server 2019 core on the 2nd Virtual Machine

Again first connect to the newly created Virtual Machine ( Exchange2019 )

Set the language to install, Time and currency format and the keyboard or input method.

This VM ( Exchange2019 ) will run Windows Server 2019 Datacenter Core named just Windows Server 2019.

Since this scenario covers a new install on a new VM choose Custom

Again wait until Windows Setup finishes. Depending on your chosen hardware specs this can take some time. The install to the SSD is really fast and takes only a couple of minutes.

After the install has finished you need to change the password of the built-in Administrator

Now we need to make sure that both servers can communicate with each other:
Disable IPV6 on the Domain Controller ( AD2019). Otherwise, the server responds with its IPV6 IP. For me, it is more transparent this way since my config is based on IPV4.

You can disable IPV6 on Server Core ( Exchange 2019 ) as well if needed.
After  I have disabled IPV6 on Server 2019 Core I was not able to open Network Settings under Network Adapter Settings: Invalid Index.

Find more information here :
Disable IPv6 on Server Core through Powershell and deal with the Invalid Index state

Next, disable the appropriate Firewall to make sure both servers can see each other:

Note: Since it is a test lab I have disabled the firewall on all three networks > Domain, Public and Private. Adjust this according to your environment.

Disable Firewall on Exchange2019 Server Core and enable Remote Management:

Check the status with:

Disable the firewall:

The core server Exchange2019 will be pingable now.

Enable Remote Management: Powershell

Configure a network interface to communicate with the Domain Controller:

Type sconfig > the Server Configuration shows up.

I have already assigned a fix IP address to this server.
You can configure the IP address and Default Gateway through the following options:
Set Network Adapter Address :

Enter the Default Gateway:

Set DNS Server:

Now that both servers can ping each other the next step in our Exchange Server 2019 Hyper V Install will be to prepare and install the AD Server Role on  Server 2019 Desktop Experience.

This is covered in Part 2 : Install the Active Directory Role on Server 2019

The post Exchange Server 2019 Hyper V Install appeared first on Webbanshee.