Book Image

Windows Server 2019 Cookbook - Second Edition

By : Mark Henderson, Jordan Krause
Book Image

Windows Server 2019 Cookbook - Second Edition

By: Mark Henderson, Jordan Krause

Overview of this book

Do you want to get up and running with essential administrative tasks in Windows Server 2019? This second edition of the Windows Server 2019 Cookbook is packed with practical recipes that will help you do just that. The book starts by taking you through the basics that you need to know to get a Windows Server operating system working, before teaching you how to navigate through daily tasks using the upgraded graphical user interface (GUI). You'll then learn how to compose an optimal Group Policy and perform task automation with PowerShell scripting. As you advance, you’ll get to grips with faster app innovation, improved Windows security measures, and hybrid cloud environments. After you’ve explored the functions available to provide remote network access to your users, you’ll cover the new Hyper-V enhancements. Finally, this Windows Server book will guide you through practical recipes relating to Azure integration and important tips for how to manage a Windows Server environment seamlessly. By the end of this book, you’ll be well-versed with Windows Server 2019 essentials and have the skills you need to configure Windows services and implement best practices for securing a Windows Server environment.
Table of Contents (18 chapters)

Enabling Distributed File System and creating a Namespace

Distributed File System (DFS) is a technology included with Windows Server 2019 that enables multiple file servers to share a single Namespace, enabling end users to access files and folders from a single network name. DFS has been around as a standard Windows component since Windows 2000 – it's not a new technology. However, early versions had a lot of accessibility and replication issues. As of Server 2019, though, DFS is a very solid technology. It allows those accessing files to not have to worry about which server they are currently in contact with; they simply utilize the Namespace of the DFS environment and let the servers do all the grunt work in making sure that all the files and folders are available to the users, no matter where those files happen to be physically sitting. Another way to think of it is as a collection of network shares, all stuck together under the same umbrella that is the DFS Namespace...