In this article, we will look at the basic settings of Windows Server 2016, which are configured immediately after the system installation and are usually mandatory for use. You can read about how to install Windows Server 2016 in our previous article.
So, let’s get started. First, you need to set a name for our server. To do this, go to system properties => change settings => change. Set the “Computer Name” and, if necessary, the workgroup name. After changing the settings, you need to reboot.
Next, we need to configure network settings. If your server is connected to a router, set the gateway IP, enter a static address, which is mandatory for the server, and the subnet mask. You can find information about IP addresses in your local network using the “ipconfig” command in the command prompt. Examples are shown in the screenshots below; your IP addresses will differ.
Go to the network connection settings:
Go to the properties of the IPv4 item.
And enter the static IP addresses here. Then check “Validate settings upon exit” to save the settings.
Finally, let’s move on to the most important settings, Active Directory. Start menu => Server Manager.
In the dashboard => Add roles and features.
In the installation type, select “Role-based or feature-based installation.”
Select the desired server in the poo, it will have the name you assigned earlier.
In the server roles, select the following standard roles. You can select additional roles as needed for your tasks.
In the features, leave the following items by default. We recommend that you additionally install the “Wireless LAN Service” since without this service you cannot install a Wi-Fi adapter and configure a wireless network on the server.
In the role services, select the following items. Later in the instructions, we will license the terminal server.
Next, leave everything as default (if you do not need to install anything additionally). Proceed to the “Confirmation” step and install.
After the services are installed, you need to reboot.
Let’s proceed with DNS settings. In Active Directory, click on the flag at the top right and then go to the settings to promote this server to a domain controller.
Select “Add a new forest” and create a name for your domain. In our example, it will be “softcomputers”.
Leave the settings by default. You only need to create a password for your domain.
Run the check. If you did everything correctly, everything should install properly.
After installation and reboot, go to the “Tools” menu => DNS.
Expand the DNS tree => “Your server name” => Forward Lookup Zones => Reverse Lookup Zones => Right-click on this item and “New zone”.
Select “Primary zone” and follow the screenshots below.
At this point, choose the range of your local network. In our example, it will be 192.168.0. Your range may differ (see cmd => ipconfig).
DNS settings are now complete. Let’s proceed with DHCP settings. Go to Active Directory, and in the flag at the top right, select the appropriate setting.
After creating DHCP, go to the tools menu => DHCP to configure it.
In the DHCP tree => Your server => IPv4 => Right-click => Create a scope.
Set the name of the new scope. My will be “basic”.
Next, create a new IP address range that the server will distribute to the local network. In our example, it is the new range 192.168.1. You can create any other range as you see fit.
Next, there will be a menu for excluding ranges. If you need to exclude something, you can do it in this menu; if not, skip it.
Next, in the DHCP tree => Server name => Scope => Address Pool – a new range will be created.
Next, move on to creating and licensing the terminal server. This is necessary for users to connect via RDP to the server with their account. (We will consider user accounts in this instruction below).
Go to “Control Panel” => Administrative Tools => Remote Desktop Services => Remote Desktop Licensing Manager.
Select “All Servers”, then find your server name in the list => right-click on this item => Activate Server.
Go to the “Activation Wizard”.
Select “Automatic”.
Then optionally enter your first and last name, the name of your organization, and the country where the server is located.
Let’s proceed with the licensing itself after registration above. You need a product key to license the terminal server – CAL (Client Access License) in our case. It allows 50 users (clients) to connect via RDP to the server. You can purchase the product key for this function in our online store on the next page.
Select “License pack (Retail Purchase)” => Next.
Enter the product key you purchased.
Next, depending on the license, it may be automatically set for 50 users, or you may need to specify it manually as shown in the screenshot below. (specifying more users than the license allows will simply not activate this setting). Select “Per User” as the license type.
Next, go to the local group policy editor search => gpedit.msc => Computer Configuration => Administrative Templates => Windows Components => Remote Desktop Services => Remote Desktop Session Host => Licensing.
Go to “Use the specified Remote Desktop license servers” and enter the name of your server or its IP in the field.
Then go to “Set the Remote Desktop licensing mode” and select “Per User” from the drop-down menu.
After that, return to the Remote Desktop Licensing Manager and check if the server is activated. If so, everything is fine. However, you may still see a “yellow warning” on the server icon. To troubleshoot issues, go to “Review”. In this “Review” menu, there may be items to mark, click the appropriate buttons if you have them.
The RDP settings are now complete. Now need to create the first user who will connect via RDP to this server.
Active Directory => Tools => Active Directory Users and Computers.
In the right list, select your server => Right-click => New => Organizational Unit. In this menu, we will create a pool containing the list of our users.
Assign it an appropriate name. For safety, check the box to protect from accidental deletion.
Then, in the newly created folder on the left list => Right-click => New => User.
Optionally enter the user’s full name and mandatory login name, preferably in Latin script.
In the next window, set the user’s password with the appropriate checkboxes.
In the “Users” menu, you can manage users, delete them, change their passwords, etc. Now our new user “Jack Jackson” can log in via the server’s IP or its name in RDP while being on the same local network with the server or if added to the server’s domain.
This concludes the settings. We have covered the most important aspects of setting up and licensing Windows Server 2016. Follow our blog SoftComputers for more useful content! 🙂
