Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Windows Server 2016

You're reading from   Mastering Windows Server 2016 A comprehensive and practical guide to Windows Server 2016

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781785888908
Length 416 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jordan Krause Jordan Krause
Author Profile Icon Jordan Krause
Jordan Krause
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Getting Started with Windows Server 2016 2. Installing and Managing Windows Server 2016 FREE CHAPTER 3. Core Infrastructure Services 4. Certificates in Windows Server 2016 5. Networking with Windows Server 2016 6. Enabling Your Mobile Workforce 7. Hardening and Security 8. Tiny Servers 9. Redundancy in Windows Server 2016 10. Learning PowerShell 5.0 11. Application Containers and Docker 12. Virtualizing Your Datacenter with Hyper-V Index

What is the purpose of Windows Server?

Silly question? I don't think so. A good question to ponder, especially now that the definition for servers and server workloads is changing on a regular basis. The answer to this question for Windows clients is simpler. A Windows client machine is a requestor, consumer, and contributor of data.

From where is this data being pushed and pulled? What enables the mechanisms and applications running on the client operating systems to interface with this data? What secures these users and their data? This is the purpose of servers in general. They are housing, protecting, and serving up the data to be consumed by clients. Everything revolves around data in business today. Our e-mail, documents, databases, customer lists, everything that we need to do business well, is data. Data that is critical to us. Servers are what we use to build the fabric upon which we trust our data to reside.

We traditionally think about servers in a client-server interface mentality. A user opens a program on their client computer, this program reaches out to a server in order to retrieve something, and the server responds as needed. This idea can be correctly applied to just about every transaction you may have with a server. When your domain-joined computer needs to authenticate you as a user, it reaches out to Active Directory on the server to validate your credentials and get an authentication token. When you need to contact a resource by name, your computer asks a DNS server how to get there. If you need to open a file, you ask the file server to send it your way. Servers are designed to be the brains of our operation, and often by doing so transparently. Especially, in recent years, large strides have been taken to ensure resources are always available and accessible in ways that don't require training or large effort on the part of our employees.

In most organizations, many different servers are needed in order to provide your workforce with the capabilities they require. Each service inside Windows Server is provided as, or as part of, a Role. When you talk about needing new servers or configuring a new server for any particular task, what you are really referring to is the individual role or roles that are going to be configured on that server in order to get the work done. A server without any roles installed is useless, though depending on the chassis can make an excellent paperweight.

If you think of roles as the meat and potatoes of a server, then the next bit we will discuss is sort of like adding salt and pepper. Beyond the overhead roles you will install and configure on your servers, Windows also contains many Features that can be installed, which sometimes stand alone, but more often complement specific roles in the operating system. Features may be something that complements and adds functionality to the base operating system such as Telnet Client, or a feature may be added to a server in order to enhance an existing role, such as adding the Network Load Balancing feature to an already-equipped remote access server. The combination of roles and features inside Windows Server is what equips that piece of metal to do work.

This book will, quite obviously, focus on a Microsoft-centric infrastructure. In these environments, the Windows Server operating system is king, and is prevalent across all facets of technology. There are alternatives to Windows Server, and different products which can provide some of the same functions to an organization, but it is quite rare to find a business environment anywhere that is running without some semblance of a Microsoft infrastructure. Windows Server contains an incredible amount of technology, all wrapped up in one small installation disk. With Windows Server 2016, Microsoft has gotten us thinking out of the box for what it means to be a server in the first place, and comes with some exciting new capabilities that we will spend some time covering in these pages. Things like PowerShell and Nano Server are changing the way that we manage and size our computing environments; these are exciting times to be or to become a server administrator!

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image