Week 1 - Intro to Server Roles and Features WEEK1.pdf

Week 1: Course Introductions and What to Expect NTWK-8071: Windows Server Roles and Features  Welcome to the Course! This week we are going to start slow, so strap in and enjoy the course! After this lecture you should be able to… Understand the course overview, g...

Week 1: Course Introductions and What to Expect NTWK-8071: Windows Server Roles and Features  Welcome to the Course! This week we are going to start slow, so strap in and enjoy the course! After this lecture you should be able to… Understand the course overview, grading, assignments, and student/professor responsibilities Discuss course format and “Value-Added-Learning” Explain what Windows Server is, the benefits of Windows Server in an Enterprise, and why you would want to use it Describe the basic Roles and Features, and some basic use cases of Windows Server An introduction!  The Quick Summary This course will give you the basic skills to identify the business and technical needs to implement Windows Server in an enterprise environment. We will be discussing various roles and services, as well as how to get the most of your server by making your deployments secure and scalable.  How you are evaluated 3 quizzes (covering weekly topics throughout the course) 2 Practical Assignments (Tests your understanding of applying concepts) 1 midterm (covering content up-to week 6) 1 final exam (covering content from weeks 9 through 14)  Adding value through external resources This course introduces the concepts of Value Added Learning by adding additional links (where appropriate). The links in this course are designed to supplement your understanding of the concepts discussed. Visiting these links to consume the content is entirely optional (and won’t be tested on) – however is highly encouraged. Links for this course will focus on the theoretical use and understanding of basic concepts. Introducing Windows Server  What is Windows Server Windows Server is an operating system, that has been developed and released by Microsoft since 2003. The Windows Server operating system typically installed on a high-power computer (“server”), in order to provide a specific service (or “serve”) a specific task or role.  How does Windows Server compare to Microsoft Windows Windows Server is built on the same platform as Microsoft Windows (such as Windows 10 and 11). Unlike Windows 10/11, Windows Sever (WS hereafter) is not intended to serve as a user-centric interface. WS is typically run in as headless (“without user input, or monitor connected”) configuration. Users typically only log into WS systems to perform administrative tasks.  How does Windows Server compare to Microsoft Windows - Continued Many applications (such as web browsers, games, or office software) should never be installed on WS devices. Most properly-configured WS environments implement rigid security policies, limiting who can access and what those accessing can perform. WS environments are typically purpose-built to deliver a solution to a required task. WS environments should never be configured as an all- purpose device (segregation of services)  Typical Examples of Servers A File Server – Typically made to A Web Server – Typically made to host files (such as making them host websites (both internal and available to a broad audience), while external), using a properly configured ensuring that only those that need or WS environment can ensure that your are authorized, can access them. website stays active regardless of spikes in demand. Examples of Server Hardware What makes a Server a Server? Before we understand what sort of devices Servers are, we have to understand what hardware a server is typically installed on. Servers are purpose-built high performance devices. They typically have vast amounts of RAM to handle large sums of synchronous data processing. They are robustly built with multiple redundant power supplies, high airflow, and almost always mounted in racks in datacenters. What makes a Server a Server - Continued Robust networking capabilities – having the ability to move a lot of data throughout the network or provide network redundancy. Large storage capacity – for storing massive amounts of data, or providing data resiliency. High compute capability (CPUs) – for processing data in real-time.  What makes a Server a Server - Summary In short, Servers are optimized for doing intensive or important workloads in a reliable and scalable fashion. The differ from traditional computers by providing higher capabilities for data processing, either by the sheer scope, or volume. Servers are typically installed in datacenters which provide centralized storage, network, power, cooling and are also typically in access-controlled environments.  Installing – Virtual vs Physical There are two primary methods of installing WS. Physical – or the more “traditional” method of installation, revolves around installing WS on a physical computer. This is known as a “bare metal” install. Virtual or Hypervisor – the more common method of installing in present times. This involves installing the WS onto an existing server running a hypervisor. This enables a much more flexible approach to server management and enables better resource allocation, scalability and resiliency.  Why chose a Virtual Install? A virtualized installation of WS enables a few key benefits: Ensuring that compute resources are used wisely by allowing more than one instance of WS is installed on a physical node or server. Typically, a node or server has more resources than WS will use. Ensuring that the costs are kept down by installing multiple instances of WS on a physical server. This ensures that the costs of buying physical servers are kept lower, by only investing in physical servers when more capacity is required.  An example of benefits Physical Install Virtual Install Whole server is used up by one WS 4 different WS installations are Installation, not cost effective. It is running on this server, this makes unlikely that all the server resources the installation more cost-effective will be used by one WS installation and compute resources are shared This Photo by Unknown Author is licensed under CC BY-NC  Installation Options / Editions Two primary editions of Windows Server exist: Standard and Datacenter.  So what’s the difference? WS Datacenter is a server edition that builds on the WS Standard Edition. WS Standard and Datacenter share nearly every role and feature except a few, which will be explored on the next slides The key differences between WS Standard and WS Datacenter is that WS Datacenter is geared towards a larger virtual deployment. We’ll discuss the differences in the Roles and Features section  Installation Options When installing WS, you will be presented with a number of options, along with selecting either Standard or Datacenter Server Core (it is selected by default) Desktop Experience  Server Core vs Desktop Experience The Server Core option is a minimal installation and includes most server roles. It lacks a graphical user interface and must be administered using a PowerShell command line or Remote Server Administration Tools (or RSAT for short). The Desktop Experience installation option is the “classic” installation option for WS, pairing a full- fledged WS installation with the traditional Windows Desktop (start menu, control panel, and everything else you are used to) Introducing Roles and Features  What is a Role? A WS Role is a role that your server is indented to do in your environment. This can be thought of as a job. There are many roles that WS ships with Some roles require extra features Roles determine what a servers’ purpose is Some roles do not exist and must be added via software (3rd or 1st party software, but not though the “console”) Examples of some built-in Roles Microsoft Active Directory (Active Directory Domain Services) and IIS (Internet Information Services) are a few common built-in WS roles. Built-in roles are bundled with the WS Operating system and do not need additional software to function. We will be going over these and other roles in the coming weeks.  Installing Roles and Features Installing Roles and Features is a simple task that is either completed through a command console (PowerShell) or through the Roles and Features Wizard You will be installing roles in your lab class (NTWK8060)  Other frequently-used Roles Active Directory and IIS aren’t the only two roles in WS. Below are some examples of other roles. DNS – Domain Name Services DHCP – Dynamic Host Configuration Protocol File and Storage Services Hyper-V We will be covering some of these, and a few other roles in detail in the coming weeks.  Hyper-V Hyper-V is Microsoft’s virtualization product. It is Microsoft’s answer to VMWare/VirtualBox/Parallels for being able to run a virtual machine(s). Hyper-V is available as both a WS Role, as well as a standalone “bare metal” hypervisor. Hyper-V is also available as a feature in certain Windows 10/11 versions, but an enhanced enterprise-ready version is only available on WS installations.  Standard vs Datacenter As mentioned, the primary differences between WS Standard and Datacenter lie in Hyper-V. Standard allows a maximum of 2 virtual machines* to be created Datacenter does not limit (unlimited, resources permitting) the number of virtual machines* * License costs (CAL) are also a consideration, however are not covered in this course. For accurate license details, resellers and Microsoft partners are key in order to provide you with accurate quotes based on use cases.  Standard vs Datacenter - Continued WS Datacenter also includes a few more additions (roles) that focus on the Hyper-V product, these are not included in WS Standard: Network Controller – A SDN (Software Defined Networking) solution that allow you to build comprehensive networks without the associated costs of network hardware. Hyper-V Host Guardian – A security feature for enhancing security of virtual machines  What are Features? Unlike Roles (which are what the server does), features are underlying and/or supporting resources that are frequently used/accessed by roles, the users accessing the server, or by the server itself.  Examples of Features Some examples of common WS Features are:.NET Framework – Used by the server itself, in order to run certain applications Role Management Tools – i.e. tools to manage various Roles, such as IIS, Hyper-V, DNS and DHCP consoles, to administer these Roles locally (from the WS) Plugins for web languages for IIS – Such as ASP.NET  Some Roles will add Features It is imperative to understand that some Roles will automatically add features, which are required in order for proper operation of the Roles.  Instructor Led – Demonstration Installing Windows Server with a GUI in vCenter In this demonstration, we will complete the following: – Install Windows Server with a GUI (Desktop Experience) – Set a hostname – Set IP information to get network access End of Lecture, Questions?