Windows server 2019

Windows server 2019 – About 10 years ago, Microsoft adjusted its operating system release ideology so that the latest Windows Server operating system would always be structurally similar to its latest Windows client operating system. This trend continued until recently with Server 2008 R2, which closely mirrored Windows 7, Server 2012, and many of the same features that were used with Windows 8.1 updates were also included in Server 2012 R2. This, of course, was also migrated to Server 2016 – which made it feel similar to the way that you registered on a Windows 10 workstation.

Now that you’re all familiar with and comfortable with the Windows 10 interface, we usually have no problem jumping to the Server 2016 interface when taking a test drive in it. Windows Server 2019 is again no exception to this rule, except that the release of client side operating systems has been slightly moved. Now, instead of releasing new versions of Windows (11, 12, 13, etc.) we give it release dates. For example, version 1703 for Windows 10 was released around March 2017. The 1709 version for Windows 10 was released in September 2017. Then we had 1803 and 1809 – although there was a slight delay with the 1809 version and it was released somewhere closer to November, but it was not part of the original plans. The current plan is to release Windows every six months or so, but to expect IT departments to move all their servers up and down just for the purpose of migrating to an operating system that is six months new is crazy; sometimes it takes longer than planning some kind of migration.

Anyway, I am getting a little ahead of myself because we will be discussing the design of Windows Server versions in this chapter later in our section on Windows Server Versions and Licensing. The fact is that Windows Server 2019 looks and feels like the latest version of the client operating system that was released around the same time – and it was Windows 10 1809. Before we begin discussing Windows Server features, it is important to establish some basis for applicability and familiarity with the operating system itself before going deeper into the technology that works under the hood.

About 10 years ago, Microsoft adjusted its operating system release ideology so that the latest Windows Server operating system would always be structurally similar to its latest Windows client operating system. This trend continued until recently with Server 2008 R2, which closely mirrored Windows 7, Server 2012, and many of the same features that were used with Windows 8.1 updates were also included in Server 2012 R2. This, of course, was also migrated to Server 2016 – which made it feel similar to the way that you registered on a Windows 10 workstation.

Now that you’re all familiar with and comfortable with the Windows 10 interface, we usually have no problem jumping to the Server 2016 interface when taking a test drive in it. Windows Server 2019 is again no exception to this rule, except that the release of client side operating systems has been slightly moved. Now, instead of releasing new versions of Windows (11, 12, 13, etc.) we give it release dates. For example, version 1703 for Windows 10 was released around March 2017. The 1709 version for Windows 10 was released in September 2017. Then we had 1803 and 1809 – although there was a slight delay with the 1809 version and it was released somewhere closer to November, but it was not part of the original plans. The current plan is to release Windows every six months or so, but to expect IT departments to move all their servers up and down just for the purpose of migrating to an operating system that is six months new is crazy; sometimes it takes longer than planning some kind of migration.

Anyway, I am getting a little ahead of myself because we will be discussing the design of Windows Server versions in this chapter later in our section on Windows Server Versions and Licensing. The fact is that Windows Server 2019 looks and feels like the latest version of the client operating system that was released around the same time – and it was Windows 10 1809. Before we begin discussing Windows Server features, it is important to establish some basis for applicability and familiarity with the operating system itself before going deeper into the technology that works under the hood.

What is the purpose of Windows Server?

Is someone asking a stupid question about the main purpose of Windows Server? I don’t think so. This is a good issue to discuss, especially now that the definition for servers and server workloads is constantly changing. The answer to this question is easier for Windows client machines. The Windows client computer performs queries, is a consumer and producer of data.

Where are these data delivered and retrieved from? What allows mechanisms and applications running in client operating systems to interact with this data? What protects these users and their data? Answers to these questions and reveal the main purpose of servers in general. They host, protect and maintain the data that customers will consume.

In today’s business, everything revolves around data. Our email messages, databases, user lists – all that is required for business is data. This data is critical to us. Servers are what we use to build the factory that we trust to host our data.

We traditionally imagine servers using the worldview of client-server interaction. A user opens a program in his client computer, this program reaches a server to find something, and the server responds as it should. This idea can be applied fairly fairly to almost any transaction that you may have with a particular server. When your domain-joined server (computer) needs to authenticate you as a server, it turns to the Active Directory on its server to authenticate you and obtain token authentication. When you need to communicate with a resource by its name, your computer asks a DNS server how to get it. If you need to open a file, you ask it to be sent in your own way.

Servers are designed to be the core consciousness of your actions and often do so in a transparent manner. In recent years, extensive research has been done to ensure that resources are always available and achieved in a way that does not require training and effort for the majority of our employees.

Most organizations require many different servers to represent your workspace with the features you need. Every service within Windows Server is provided as part of a role. When you are discussing the need for new servers, or configuring a new server for a specific task, what you are actually referring to is a specific personal role, or roles that you are going to configure on that server to get the work done. A server that is installed without any role is useless, although depending on its chassis can be a great press papier. The 3U SAN can weigh over 45 kilos and keep your table in place even in the middle of a storm!

If you imagined the roles as meat and potatoes from a certain server, then the next small step is to add salt and pepper. In addition to the service roles that you will install and configure on your servers, Windows also contains many features available for installation that are sometimes self-contained, but more often complement specific roles in the operating system itself. Functionality can be something that complements and adds functionality to an existing base operating system, such as a Telnet client, or a property can be added to a server to extend an existing role, such as adding Network Load Balancing (NLB) functionality to an already equipped remote access or IIS server. This combination of roles and properties within Windows Server is what makes this piece of hardware work.

It is only natural that this book will focus on the Microsoft infrastructure. In these environments, the Windows Server operating system is the king and is common on all sides of the technology. There are some alternatives for Windows Server and various products that can provide the same functionality to an organization, but it is rare to find a business environment that works somehow differently from the Microsoft infrastructure.

Windows Server contains an unimaginable number of technologies, all contained in one small installation disk. With Windows Server 2019, Microsoft makes us think about what it means to be a server immediately after installation and also offers some interesting new features that we will spend some time on these pages. Things like PowerShell, Windows Admin Center and Storage Spaces Direct change the very way we manage and size our computing environments; and these are breathtaking times to become a server administrator!

Technical Requirements

When planning a build of a new server, many of the tolerances of the type of licensing that are required for a decision to be made. What roles do you intend to install on this server? Can Server 2019 Standard handle this or will we need Datacenter Edition for these guys? Do we intend to take advantage of the security benefits from the Kernel Server or do we really need a full Desktop Practice? These days, Hyper-V servers with the ability to be deployed on the first whim of virtual machines, we often continue to leave the hardware of some server unattended, but there will certainly still be options when the physical hardware will run on Windows Server 2019. In such cases you need to be aware of the requirements of this new platform, so let’s take a moment to list these features. This information is available in an advanced form on the Microsoft Docs website if you need to double-check some features, but here we will summarize the minimum system requirements:

• THE CPU: 1.4 GHz with 64 bits which supports a number of things: NX, DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW and SLAT.
• RAM: a minimum of 512 MB of memory with ECC, or a recommended minimum of 2 GB for a server with Desktop Practices running. I can let you know that it is possible to install and run a Practice with a desktop that is much smaller than 2GB (e.g. inside some lab for testing), but you realize that the performance will be far from what we could expect.
• Drive: Server 2019 requires a PCI Express (PCIe) storage adapter. Not suitable for boot devices ATA/PATA/IDE. The minimum required storage space is 32 GB, but the Desktop Practices consume 4 GB more space than a Core Server, so take this into account.

Download Windows Server 2019

First, you need to download the distribution of Windows Server 2019. You can download it on the next page.

www.microsoft.com/en-us/windows-server

After downloading the distribution kit – it should be written to a flash drive, making it bootable. Instructions how to write the distribution on a flash drive.

Next you need to boot from a flash drive under the bios to start the installation itself.

Now that you have booted from the flash drive, let’s get started with the installation.

Installing Windows Server 2019

Step 1. Run the Windows Server installation.

Run the Windows Server installation

Step 2. Waiting for the installer to boot.

Installing Windows Server 2019

Step 3. Choose your language. English is offered by default.

Choose your language. English is offered by default

Step 4. Press the set button now.

Press the set button now

Step 5. Then we need to specify the license key. Microsoft has long been offering license keys for six months, getting to know its product.

Then we need to specify the license key

Step 6. Next, choose the version we’re going to install. Since the command line is not the most enjoyable part of Windows, I will choose the GUI version.

choose the GUI version

Step 7. We accept the license agreement.

We accept the license agreement

Step 8. Choose a manual installation (Custom: Install Windows).

Choose a manual installation

Step 9. Then we create a new partition on the specified disc.

new partition on the specified disc

Step 10. Windows will create all of the necessary partitions itself. Let’s continue with the installation.

Windows will create all of the necessary partitions itself

Step 11. We wait for the files to be copied and the operating system installed. Windows Server 2019 will then be rebooted.

Windows Server 2019 will then be rebooted

Step 12: After that, Windows Server will configure some services.

Windows Server will configure some services

Step 13. Next, we will need to specify the Administrator password. Password must be at least 8 characters.

Administrator password

Step 14. After that we need to authenticate and the Windows desktop will appear before us. And we’ll see the Server Manager.

Server Manager

Windows Server 2019 Quick Overview