Windows Server 1.1 : Post installation tasks

Once Windows Server 2019 has finished installing, there are several post-install tasks to take care of. Most of them can be done directly through Server Manager, which opens automatically at every logon. If you have closed it, just type "Server Manager" in the search bar to relaunch it. From the left pane, click Local Server — that is where almost everything happens.

Tasks to perform

  • Check activation — open the activation entry to confirm Windows is activated. Activation may take a few moments after installation, so do not worry if it has not turned green right away.
  • Set a static IP address — click the Ethernet link, then the IPv4 address. Double-click the network adapter, open Properties, select Internet Protocol Version 4, click Properties, then Use the following IP address. Enter 192.168.1.250 with the subnet mask 255.255.255.0. Leave the default gateway empty for now. For the preferred DNS server, use the same address as the IP: 192.168.1.250. The reason is that this machine will become its own DNS server (we will install the DNS role shortly), so it points to itself for name resolution.
  • Rename the machine — the VM was created as RTS-DC1, but the inner computer name is a random string. Rename the computer to RTS-DC1 as well so the OS name matches the VM name, and accept the restart prompt.

While the VM is restarting, switch the Hyper-V virtual switch from External to Private: open Virtual Switch Manager and toggle the network type. From this point on the VM no longer reaches the Internet, but can still talk to other VMs we will spin up later. This isolation is important: anything you break on the upcoming Active Directory services will not disturb your real network. After the reboot, open Server Manager → Local Server and confirm that the computer name is RTS-DC1 and the IP is the static one — all post-install settings are now in place.

Summary

This lesson covers the essential post-installation configuration tasks for Windows Server. The instructor demonstrates how to verify system activation, configure a static IP address (192.168.1.250) and DNS settings using Server Manager, rename the computer to match intended naming conventions, and isolate the server network by changing the virtual network adapter to private mode. These foundational tasks are performed through the Server Manager interface, which opens automatically upon login to the server.

Key points

  • Windows Server Manager is the primary tool for post-installation configuration and opens automatically upon each server login
  • Verify Windows activation status early—the operating system will begin shutting down hourly after 10 days if not activated
  • Configure a static IP address (e.g., 192.168.1.250) with subnet mask 255.255.255.0 through the network adapter properties
  • Set DNS server to the same IP address as the server itself, since DNS will be installed and hosted on this server
  • Rename the computer from its randomly generated console name to the intended name (e.g., RTS-DC1) and restart the system
  • Change the virtual network adapter from external to private mode to isolate the server from the host network and prevent service disruption

FAQ

What should I do if Windows Server Manager doesn't open automatically?

You can open it manually by clicking on the search bar, typing 'Server Manager', and launching it from the search results list.

Why do we set the DNS server IP address to the same address as the server itself?

Because DNS will be installed and configured directly on this server, making it its own DNS server. Setting the DNS to point to itself allows the server to resolve domain names to its own IP address.

Why is it important to change the network adapter to private mode?

Private mode isolates the virtual machine from the host network and external networks, preventing any services running on the server from disrupting host connectivity and limiting connections to only other virtual machines on the same private network.