What a great event it was, ExpertsLive 2019 NL. A great location, great speakers, nice people from all over the world!! Thanks to the organization again!! Up to next year!!
In this blogpost I’m going to show you the steps to install Microsoft Exchange Server 2019 on Windows Server 2019 Core Edition. When you’re working with Windows Server Core the first time, it’s a little different then managing Windows with a GUI (Graphical User Interface).
Windows Server Core is just a command line interface, that’s all. There’re many advantages of using Windows Server Core edition, for example:
* Small footprint
* Less Windows Updates to install
* Less reboots needed after Windows Updates
* Reduced attack surface
* Less disk space required
* Reduced management
With the release of Exchange Server 2019, Windows Server Core is also supported!! YEAH!!!
Install Windows Server 2019 Core Edition
This step is really easy. Just hit next, next, next and finish!
Hit CTRL+ALT+DELETE, type the local administrator password and login to your server. After this, you can start configuring the server using SCONFIG.
Configure the network configuration using SCONFIG or Powershell.
Assign a static IP:
New-NetIPAddress -InterfaceIndex 6 -IPAddress 172.16.1.100 -PrefixLength 16 -DefaultGateway 172.16.1.101
Configure a DNS Server:
Set-DNSClientServerAddress -InterfaceIndex 6 -ServerAddress "172.16.1.100"
Enable Remote Desktop:
cscript C:\Windows\System32\Scregedit.wsf /ar 0
Use the following PowerShell command to install the OS component required for Microsoft UCMA 4.0 and the OS component required for Active Directory Preparation.
Don’t forget to switch to powershell
Install-WindowsFeature Server-Media-Foundation, RSAT-ADDS
Download necessary software
From an admin workstation, download the following software and copy it over to the Server Core we are preparing for the Exchange installation (for example C:\_Install)
Install UCMA (Microsoft Unified Communications Managed API 4.0)
The UCMA installable is present on the Exchange Server 2019 media itself. Use the following PowerShell command to mount the Exchange Server media:
The UCMA installable is located under the “UCMARedist” folder on the Exchange Server 2019 .ISO. Start the UCMA installation:
Do not reboot the server just yet; join the computer to an AD domain and then reboot it.
Joining the computer to AD domain
* Rename the computer to 2019-EX01
* Add the computer to domain homelab.local
Add-Computer -DomainName homelab.local -NewName 2019-EX01 -DomainCredential homelab\administrator
Restart the server
Use the following PowerShell command to restart the computer:
After rebooting the server mount the Exchange .ISO image.
Use the following command to start Exchange Server installation. The PowerShell command will also install the required OS components for Exchange:
.\Setup.exe /m:install /roles:m /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents
Once Exchange is installed, you can launch the Exchange Management Shell using LaunchEMS command from the command line.
You can also start the Exchange Management Console from a different server using the URL below:
Windows Server 2016 and 2019 Storage Sapces Direct (S2D) allows building HA storage systems using storage nodes with local storage, such as SATA or SSD disks.
In this blogpost, I’ll deploy a two node S2D cluster based on Windows Server 2019 build 17744. The main machine is a HP ProBook 450 G5 with Windows 10, 16 GB memory, 512 GB SSD disk, and Hyper-V enabled.
First of all, I’ve deployed the following virtual machines:
- S2D-W2019-DC01 (Domain Controller, DNS, Group Policies)
IP address: 172.16.0.100
- S2D-W2019-HV01 (Hyper-V host, S2D node)
IP address: 172.16.0.101 (LAN)
IP address: 10.10.0.101 (Live Migration)
- S2D-W2019-HV02 (Hyper-V host, S2D node)
- IP address: 172.16.0.102 (LAN)
IP address: 10.10.0.102 (Live Migration)
All the servers are installed with Windows Server 2019 build 17744. The first server I’ve configured is the domain controller. My internal domain is s2dlab.local.
For both S2D nodes (S2D-W2019-HV01 and S2D-W2019-HV02), you’ve to configure some additional settings, because this servers are virtual. So we’re going to run Hyper-V in Hyper-V and on that Hyper-V host there’re some guest virtual machines (nested virtualization) 😀 Cool stuff!!!
$S2DHOST1 = 'S2D-W2019-HV01' $S2DHOST2 = 'S2D-W2019-HV02' # List all virtual machines Get-VM # Enable nested virtualization on virtual machines Set-VMProcessor -VMName $S2DHOST1 -ExposeVirtualizationExtensions $true Set-VMProcessor -VMName $S2DHOST2 -ExposeVirtualizationExtensions $true
Next, you’ve to Configure the following settings within the VM configuration:
- Disable dynamic memory;
- Set the number of virtual processors to 2 or 4;
- Turn on MAC address spoofing on your network interface(s);
Now the domain controller is up and running and both S2D nodes are installed and configured with Windows Server 2019, it’s time to add some storage. Both servers have 3 x 50 GB virtual disks attached! Note!! this is only for testing and demo!!
So we’ve 300 GB storage available for our S2D cluster. After this is done, you can install the following roles and features within Windows Server:
- (Role) File and Storage Services;
- (Role) Hyper-V;
- (Feature) Failover Clustering;
Now all the components are ready to build the cluster. It’s recommended to run the cluster validation before building your cluster! The name of my cluster is ‘S2D-CL01’ with IP address 172.16.0.200/16. Note!! Uncheck the option ‘Add all eligible storage to the cluster’!!
The cluster is up and running. As you can see within your Active Directory and DNS configuration, there’re three computer objects (two cluster nodes and one Failover Cluster object).
The last step before enabling ‘S2D’ on our cluster is checking the disk configuration.
# List all available disks within the cluster nodes Get-PhysicalDisk # Enable Storage Spaces Direct on the cluster Enable-ClusterS2D # List all Storage Pools within the S2D cluster Get-Storagepool S2D*
Now our cluster is Storage Spaces Direct (S2D) enabled. The last step is to create a virtual disk within our Storage Pool and add it as a Cluster Shared Volume (CSV) to the cluster, wo we can store workloads on it! Bacause we’ve a two node cluster, the only Resiliency type is Two-Way Mirror.
In this blogpost we’ve builded a two nodes virtual Storage Spaces Direct cluster in Hyper-V (Windows 10). The S2D nodes are running Windows Server 2019. It’s really a nice opportunity to run this configuration virtual on your laptop or desktop, while nested virtualization is supported and it works great!!
In the next blogpost I’ll show you to install and configure a virtual machine within our S2D cluster. Also performing some live migrations to show the high availability and resiliency of our setup!
Windows Server 2019 Webinar
With Microsoft Ignite just around the corner, Windows Server 2019 is set to get its full release and the signs look good. Very good.
Unless you’re part of the Windows Server insider program – which grants you access to the latest Windows Server Preview builds – you probably haven’t had a hands-on experience yet
with Windows Server 2019 but the guys over at Altaro have and are preparing to host a webinar on the 3rd of October to tell you all about it.
The webinar will be held a week after Microsoft Ignite so it will cover the complete feature set included in the full release as well as a more in-depth look at the most important
features in Windows Server 2019.
Whenever a new version of Windows Server gets released there’s always a lot of attention and media coverage so it’s nice to have an hour-long session where you can sit back and let
a panel of Microsoft experts cut through the noise and give you all the information you need.
It’s also a great chance to ask your questions direct to those with the inside knowledge and receive answers live on air.
Over 2000 people have now registered for this webinar and I’m going to be joining too. It’s free to register – what are you waiting for?