02-08-2019 207400 - Instalaton, Storage, and Compute with Windows Server 2016 | Sklpipe Module 1: Installing, upgrading, and migrating servers and workloads Contents: Module overview Lesson 1: Introducing Windows Server 2016 Lesson 2: Preparing and installing Server Core Lesson 3: Preparing for upgrades and migrations Lesson 4: Migrating server roles and workloads Lesson 5: Windows Server activation models Lab: Installing and configuring Server Core Module review and takeaways Module overview For your organization to effectively manage storage and compute functions, you need to understand the new features available in Windows Server 2016. This module introduces you to Windows Server 2016 and describes the various editions and installation options. You will learn how to install Server Core. You will also learn how to plan a server and migration strategy, along with how to perform a migration of server roles and workloads. Finally, you will learn how to choose the most appropriate activation model for your organization. Objectives htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 161coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine After completing this module, you will be able to + Describe the new features of Windows Server 2016. + Prepare for and install Server Core. + Plan a server upgrade and migration strategy. + Perform a migration of server roles and workloads within a domain and across domains. + Choose an appropriate activation model. Lesson 1: Introducing Windows Server 2016 Knowing the capabilities of the Windows Server 2016 operating system enables you to use it effectively and take full advantage of what it can offer your organization Some of the many improvements to Windows Server 2016 include increased scalability and performance; improved virtualization; improved management tools; and additional deployment options. This lesson explores these new features and capabilities in Windows Server 2016, in particular those in the computer and storage space, along with the various installation options available Lesson objectives After completing this lesson, you will be able to: + Select a suitable Windows Server 2016 edition. + Describe the hardware requirements for Windows Server 2016. + Describe installation options for Windows Server 2016. + Describe the tools available for remotely managing Windows Server 2016. + Explain how to use Windows PowerShell 5.0 to manage servers. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 28102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe + Describe the new and improved features of Windows Server 2016. Selecting a suitable Windows Server 2016 e + Windows Server 2016 Essentials «Windows Server 2016 Standard - Windows Server 2016 Datacenter - Microsoft Hyper-V Server 2016 - Windows Storage Server 2016 Workgroup - Windows Storage Server 2016 Standard You can choose one of several editions of Windows Server 2016, These editions allow organizations to select a version of Windows Server 2016 that best meets their needs, rather than pay for features they do not require. When deploying a server for a specific role, system administrators can save substantially by selecting the appropriate edition. The following table describes the Windows Server 2016 editions. Edition Description Windows Server 2016 Windows Server 2016 Essentials edition is designed for small businesses. It Essentials edition corresponds to Windows Small Business Server from earlier versions of ‘Windows Server. This edition allows up to 25 users and 50 devices. It supports two processor cores and up to 64 gigabytes (GB) of random access memory (RAM). It does not support many of the features of Windows Server 2046, including virtualization. Windows Server 2016 Windows Server 2016 Standard edition is designed for physical server Standard edition environments with little or no virtualization, It provides many of the roles and htps:www-sklpipe.comitireaderibook/8035340-c012-4850-8e60-730DI@Sab7I4 36102-09-2019 Windows Server 2016 Datacenter edition Microsoft Hyper-V Server 2016 Windows Storage Server 2016 Workgroup edition Windows Storage Server 2016 Standard edition 20740C- Installation, Storage, and Compute with Windows Server 2016 | Sklpipe features available for the Windows Server 2016 operating system. This ESSERE up to 64 sockets and up to 4 terabytes (TB) of RAM. It includes licenses for up to two virtual machines. Note: You can run two virtual machines on one physical host, using one standard license, as long as the physical host is only used for hosting and managing the virtual machines. If the physical host is used to run other services, such as DNS, you can only run one Virtual machine. For more information about Windows licensing, speak with a Microsoft licensing specialist. Windows Server 2016 Datacenter edition is designed for highly virtualized infrastructures, including private cloud and hybrid cloud environments. It provides all of the roles and features available for the Windows Server 2016 operating system. This edition supports up to 64 sockets, up to 640 processor cores, and up to 4 TB of RAM. It includes unlimited Windows Server-based virlual machine licenses for virtual machines that run on the same hardware. It also includes new features such as Storage Spaces Direct and Storage Replica, along with new Shielded Virtual Machines and features for software-defined datacenter scenarios. ‘Acts as a stand-alone virtualization server for virtual machines, including all the new features around virtualization in Windows Server 2016. The host operating system has no licensing cost, but virtual machines must be licensed separately. This edition supports up to 64 sockets and up to 4 TB of RAM. It supports domain joining. It does not support Windows Server 2016 roles other than limited file service features. This edition has no GUI but does have a UI that displays a menu of configuration tasks. Acts as an entry-level unified storage appliance, This edition allows 50 users, one processor core, and 32 GB of RAM. It supports domain joining, ‘Supports up to 64 sockets but is licensed on a two-socket, incrementing basis. This edition supports up to 4 TB of RAM. It includes two virtual machine licenses. It supports domain joining. It supports some roles, including Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) server roles, but does not support others, including Active Directory Domain Services (AD DS), Active Directory Certificate Services (AD CS), or Active Directory Federation Services (AD FS). htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 48102-09-2019 207: /40C - Installation, Storage, and Compute with Windows Server 2016 | Skilppe Hardware requirements Windows Server 2016 has the following minimum hardware requirements for Server Core installation: Hardware Requirement Processor architecture x64 Processor speed 1.4 GHz RAM 512 MB Hard drive space 32 GB The hardware requireme nts needed to support Windows Server 2016 depend on the services that the server is hosting, the load on the server, and how responsive you want the server to be. Th network, disk /O, proces: absolute minimum requir Component Processor architecture Processor speed RAM Hard drive space Virtualized deployments e Services and features of each role put a unique load on sor, and memory resources. The following table shows the ed for a Server Core installation on a physical machine. Requirement 64-bit 1.4 gigahertz (GHz) 512 MB 32GB of Windows Server 2016 must match the same hardware specifications as those required for physical deployments, However, during installation you will need to allocate extra memory to the VM, which you can then htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 5161coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine deallocate after installation, or you will need to create an installation partition during the boot process Desktop Experience If you want to install Windows Server 2016 with the Desktop Experience installed, the hard drive space requirement is approximately 4 GB greater. Other hardware requirements In addition to the previously referenced requirements, there are a variety of other hardware requirements to keep in mind, depending on your specific organizational needs and installation scenarios: + Greater disk space is required for network installations or for computers with more than 16 GB of RAM. + Storage and network adapters must be PC! Express compliant. + A Trusted Platform Module (TPM) 2.0 chip is required for certain features such as BitLocker Drive Encryption. Overview of installation options htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 66102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe You can choose among the following installation options when deploying Windows Server 2016: - Windows Server 2016 (Desktop Experience)—full server installation - Windows Server 2016—Server Core installation - Windows and Hyper-V containers can run on a Desktop Experience or Server Core of Windows Server 2016, and provide further application isolation When you install Windows Server 2016, you can select one of three installation options: + Windows Server 2016 with Desktop Experience. This is a full server installation and includes a complete graphical management interface. This installation option supports all Windows Server roles. + Windows Server 2016. This is the equivalent of Server Core in earlier versions of Windows Server and provides for a command-line management interface. This installation option has a reduced hardware footprint but does not support all Windows Server roles. Note: Installing Server Core is covered in detail in the next lesson. Managing servers remotely htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 8102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe + Use the following options to remotely manage a computer that is running Windows Server 2016: +» Remote Server Administration Tools (RSAT) + Server Manager + Management consoles for each role/feature - Windows PowerShell remoting and PowerShell Direct + Remote shell » Remote Desktop + Group Policy (not supported on Nano Server) : Firewall exceptions required for remote management Performing the interactive management of Windows Server is not the best practice. With Server Core, your local management options are limited. After you have configured the network and firewall settings of Server Core, you must perform other management tasks remotely or by using the Command Prompt window and the Windows PowerShell command-line interface. When you install a role or feature, you will receive a prompt to install the appropriate administrative tools. The best practice is to manage servers remotely by using the Remote Server Administration Tools (RSAT) available for Windows 10. RSAT includes the full set of administrative tools, including Server Manager, the Active Directory Administrative Center, and management consoles. You can later choose to disable the tools by using Turn Windows features on or off in Control Panel Note: For a full list of all the tools included in RSAT for Windows 10, refer to: “Remote Server Administration Tolls (RSAT) for Windows Client and Windows Server (dsform2wiki)’ at: http://aka.ms/hz53ry To download Remote Server Administration Tools, see http://aka.ms/wzpq0j Server Manager htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 861coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine Server Manager is part of the Windows Server 2016 Desktop Experience, or you can run it from a Windows 10 workstation when installed as part of RSAT. Server Manager is the primary GUI tool to manage computers running Windows Server 2016. The Server Manager console can manage both local and remote servers. You can also manage servers as groups, allowing you to perform the same administrative tasks quickly across multiple servers. You can also use Server Manager to run the Best Practices Analyzer to determine if the roles are functioning properly on the servers in your network. Windows PowerShell remoting and PowerShell Direct You can use Windows PowerShell to run Windows PowerShell commands or scripts against correctly configured remote servers if the script is hosted on the local server. With Windows PowerShell remoting, where necessary, you can also load Windows PowerShell modules locally, such as those that are part of Server Manager, and run the cmdlets available in that module against appropriately configured remote servers. In Windows Server 2016, you also have the option of using PowerShell Direct to run PowerShell scripts or cmdlets on virtual machines from a Hyper-V host. Note: More information about PowerShell Direct is provided in Module 5, “Installing and configuring Hyper-V and virtual machines.” Remote Shell Windows Remote Shell (WinRS) is a command-line tool that allows you to execute remote commands on a target server that supports Windows Remote Management (WinRM). WinRM is a collection of standards-based technologies that enables administrators to manage server hardware when signed in directly or over the network. Server Manager and Windows PowerShell remoting also rely on WinRM in Windows Server 2016. Remote desktop htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 9161coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine You can connect to a remote server computer that is running the Server Core installation or the full installation by using Remote Desktop. On Server Core, you must enable Remote Desktop by using Sconfig.cmd. Group Policy You can use Group Policy to manage Server Core and full installations of Windows Server 2016, just like you can manage any other computer running Windows Firewall settings Microsoft Management Console (MMC) and some other tools used for remote server management rely on the Distributed Component Object Model (DCOM). Even Server Manager, when managing servers running Windows Server 2008 without the Windows Management Framework updates installed, depends on DCOM. DCOM, unlike WinRM, requires Windows Firewall on the computer running the remote management tools to be configured to allow exceptions to multiple rules. These exceptions include: + COM+ Network Access (DCOM-In) + Remote Event Log Management (NP-In) + Remote Event Log Management (RPC) + Remote Event Log Management (RPC-EPMAP) Additional Reading: For more information about configuring firewall settings to support remote management, refer to the procedure: “To configure MMC or other tool remote management over DCOM'” in the topic "Configure Remote Management in Server Manager” at: http://aka.ms/eyxijf Using Windows PowerShell 5.0 to manage servers htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 108102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Windows PowerShell is a scripting language and command-line interface that is designed to assist you in performing day-to-day administrative tasks Windows PowerShell 5.0 is a scripting language and command-line interface that is designed to assist you in performing day-to-day administrative tasks. Windows PowerShell cmdlets execute at a Windows PowerShell command prompt or combine into Windows PowerShell scripts. You can also use Windows PowerShell to manage servers remotely. A headless server has no graphical user interface and there is no capability for local sign-in. Importing modules Some Windows PowerShell cmdlets are not available in the default Windows PowerShell library. When you enable some Windows features or want to administer particular environments, you must obtain additional Windows PowerShell functions. These additional functions are packaged in modules. Windows PowerShell remote management You can use Windows PowerShell to remotely run cmdlets on other Windows systems. This is called remoting. Windows PowerShell remoting depends on the htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 181coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine WinRM service running on the target systems. This service can be enabled manually or by running the Enable-PSRemoting cmdlet on the target. The simplest way to use remoting is one-to-one remoting, which allows you to bring up an interactive Windows PowerShell session on the remote system. After the connection is established, the Windows PowerShell prompt displays the name of the remote computer. PowerShell Direct Many administrators choose to run some or all of their servers running Windows Server in virtualized environments. To enable a simpler administration of Windows Server Hyper-V virtual machines, Windows 10 and Windows Server 2016 both support a new feature called PowerShell Direct. PowerShell Direct enables you to run a Windows PowerShell cmdlet or script inside a virtual machine from the host operating system without regard to network and firewall configurations, and regardless of remote management configuration Note: You must still authenticate to the virtual machine by using guest operating system credentials. To use PowerShell Direct, from your host, run the following Windows PowerShell cmdlet: Enter-PsSession -VMName VMName You can then run the same cmdlets that you normally run in the same way as with any other remote Windows PowerShell situation. Windows PowerShell Desired State Configuration (DSC) htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 v6coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine Windows PowerShell DSC is a set of Windows PowerShell extensions, cmdlets, and resources that support configuring and managing remote computers in a scalable and standardized manner by pushing or pulling declarative configurations. Note: Windows PowerShell DSC is covered in detail in Module 12, “Managing, monitoring, and maintaining virtual machine installations.” What’s new since Windows Server 2008 was released? New features and improvements introduced in Windows Server 2012 or Windows Server 2012 R2: +» Work Folders » Storage Spaces + DHCP failover + Storage tiers * IPAM + Better domain controller + Dynamic Access Control virtualization + Data deduplication + Cloning virtual domain controllers Windows Server 2016 provides many new features and a number of significant improvements over earlier versions of Windows Server. Some of these features and improvements were first introduced in Windows Server 2012 or Windows Server 2012 R2, whereas others are new to Windows Server 2016. New features and improvements introduced in Windows Server 2012 or Windows Server 2012 R2 htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 196102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe The following features and feature improvements in Windows Server 2016 were first introduced in Windows Server 2012 or Windows Server 2012 R2: + Work Folders. Provides a mechanism for both domain joined computers and those that are not domain joined to access and synchronize corporate data files. + DHCP failover. Enables you to deploy two DHCP servers containing overlapping DHCP scopes. If a DHCP server goes offline, DHCP client computers can renew their IP configurations from the failover DHCP server. + IP Address Management (IPAM). Provides administrative and monitoring capabilities for the IP address infrastructure within your organization's networks. With IPAM, you can monitor, audit, and manage servers running DHCP and DNS. + Dynamic Access Control. This claims-based authorization platform enables you to control access to file resources within your organization. This is in addition to any folder or shared folder permissions already protecting the resource. Dynamic Access Control enables you to apply access control permissions based on rules that can include the sensitivity of the resources, the job or role of the user, and the configuration of the device that is used to access these resources. + Data deduplication. Involves finding and removing duplication within data. By segmenting files into small, variable-sized pieces; identifying duplicate pieces; and maintaining a single copy of each piece, data deduplication enables you to store more data in less space + Storage Spaces. Enables cost-effective, highly available, scalable, and flexible storage for critical deployments. Storage Spaces are based on virtual disks that are created from free space in a storage pool. Storage pools are collections of physical disks that enable you to aggregate disks, expand capacity in a flexible manner, and delegate administration + Storage tiers. Automatically moves frequently accessed data to faster storage and less-frequently accessed data to slower storage. + Better support for domain controller virtualization. Although many organizations have virtualized domain controllers for several years, potential issues can affect hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 wiscoon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine the reliability of this configuration. A feature known as GenerationID changes whenever the virtual machine experiences an event that affects its position in time During startup and normal operations, a virtual domain controller compares the current value of Generation|D against the expected value. A mismatch is interpreted as a rollback event, and the domain controller employs safeguards to prevent the virtual domain controller from creating duplicate security principals The ability to clone virtual domain controllers. Enables you to deploy new virtual domain controllers by cloning existing ones. Note: This is not a complete list of all the new or improved features in Windows Server 2012 or Windows Server 2012 R2. New features and improvements introduced in Windows Server 2016 The following features and feature improvements were introduced in Windows Server 2016: + Windows Server containers and Hyper-V containers. Containers enable you to isolate your apps from the operating system environment. This improves security and reliability. Windows containers are isolated from one another but run on the host operating system. Hyper-V containers are further isolated, because they run within a virtual machine. Docker. Docker is a technology for managing containers. Although Docker is usually associated with Linux, Windows Server 2016 provides support for Docker for managing Windows containers and Hyper-V containers. The latest version of Docker, Docker Enterprise Edition for Windows Server 2016, is freely available for all Windows Server 2016 installations, and it enables easier installation of Docker on Windows Server 2016. Rolling upgrades for Hyper-V and storage clusters. These upgrades enable you to add Windows Server 2016 nodes to an existing Windows Server 2012 R2 failover htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 1661coon2019 207400 salation, Storage, and Compute with Windows Server 2018 | Siig cluster. The cluster continues to operate at a Windows Server 2012 R2 functional level until all the nodes are upgraded The ability to hot add and hot remove virtual memory and network adapters from virtual machines. In Hyper-V in Windows Server 2016, you can now add or remove virtual memory and network adapters while the virtual machines are running Nested virtualization. In Hyper-V in Windows Server 2016, you can enable nested virtualization, enabling you to run Hyper-V virtual machines within a virtual machine. Shielded virtual machines. Shielding your virtual machines enables you to help protect the data on them from unauthorized access. PowerShell Direct. This feature enables you to run Windows PowerShell commands against a guest operating system in a virtual machine without handling security policies, host network settings, or firewall settings. + Windows Defender. Windows Defender is provided to help protect your server against malware. Although the Windows Defender interface is not installed by default, the antimalware patterns are automatically kept up-to-date + Storage Spaces Direct. This feature enables you to build highly available storage with directly attached disks on each node in a cluster. The Server Message Block 3 (SMB3) protocol provides resiliency. + Storage Replica. This feature enables you to synchronously or asynchronously replicate volumes at the block level. + Microsoft Passport. This service replaces passwords with two-factor authentication that consists of an enrolled device and a Windows Hello (biometric) or PIN. This helps provide a more secure and convenient sign-in experience + Remote Desktop Services. You can now use an Azure SQL database to create a high availability environment for Remote Desktop Connection Broker. + Active Directory Domain Services (AD DS). AD DS improvements include support hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 16161coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine for privileged access management (PAM), support for Azure AD Join, along with support for Microsoft Passport. Note: Windows Server 2016 includes many other improvements to existing features. For a full list of all the changes in Windows Server 2016, refer to: “What's New in Windows Server 2016” at: http://aka.ms/S4u2tt Windows Server Servicing Channels Windows Server 2016 now uses the Windows-as-a-Service servicing model known as Channels * Semi-Annual Channel « Contains new or updated features released every six months + Only available through a Microsoft SA Agreement ° LTSC « Traditional deployment and versioning « Available in Server Core or Server with Desktop Experience modes + Both channels will release security and driver updates as required as soon as available - Nano Server no longer supported with infrastructure roles; use Server Core or Desktop Experience modes instead Windows 10 introduced a method of delivering new features and functional changes. This method is known as Windows-as-a-Service. This is a major change from the past, when new versions of Windows operating systems released about every three years. Windows-as-a-Service uses the servicing model to introduce updates. The updates were called branches initially, and the three branches were Current Branch, Current Branch for Business, and Long-Term Servicing Branch. Subsequently, Microsoft introduced this servicing model to Microsoft Office 365 and System Center 2016 Configuration Manager. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 viecoon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine Starting in 2017, Windows Server 2016 also started following a similar servicing model. The update servicing model nomenclature has changed from branches to channels. Windows Server 2016 has two channels; the Semi-Annual Channel and the Long-Term Servicing Channel (LTSC). Security and driver updates or design flaws will not change based on these channels; these updates automatically become available for all editions. The distribution and methods for each are as follows: + Semi-Annual Channel. This is acquired with a Software Assurance (SA) agreement with Microsoft. The Semi-Annual Channel releases about every six months, and you can identify it by using a YYMM construct. For example, the first Windows Server 2016 Semi-Annual Channel release was version 1709, for ‘September of 2017. The Semi-Annual Channel for Windows Server 2016 only comes in Server Core or a Nano Server that is running in a Windows container. This channel offers new or updated features that are not available on LTSC. + LTSC. Windows Server 2016, as released in late 2016, is the LTSC. The LTSC does not receive new or updated features through the update service channel. Basically, LTSC will not add or change within its own version. New features for the LTSC rolled out about every three years, which is the same as the rollout of new Windows Server versions in the past. You can install LTSC either as Windows Server Core of Server with Desktop Experience. Microsoft expanded the Windows Insider Program to include Windows Insider Program for Business, which includes preview versions of Windows Server Semi- Annual Channel updates, so that administrators and IT professionals can preview the Semi-Annual Channel versions before they release. You can enroll your Microsoft or organizational account into the Windows Insider Program for Business and download and install the preview builds. You can also send feedback on the preview builds to Microsoft through the same program. Note that preview builds can't upgrade to production builds, because using these requires an SA agreement with Microsoft. As part of the change to the channel servicing model, Microsoft used a considerable amount of customer feedback to change the modes of both the Semi-Annual Channel and LTSC. Support for Nano Server as a virtual machine or a boot-to-vhd htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 e061coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine infrastructure server is no longer available. Nano Server only deploys in a Windows container, and it functions primarily as an application host. Microsoft recommends moving any Nano Server infrastructure roles over to Windows Server 2016 in the Server Core or Desktop Experience mode. Note: This course does not cover the Semi-Annual Channel or Windows Insider Program versions of Windows Server 2016. Check your knowledge True or false question Docker is a container that enables you to run an app in an isolated and portable operating environment. True False Check your knowledge Discovery What new features in Windows Server 2016 do you think will be useful in your organization? Lesson 2: Preparing and installing Server Core When you prepare to install Windows Server 2016, you must understand whether a particular hardware configuration is suitable. You must also select among the installation options: Windows Server with Desktop Experience or Server Core. This lesson describes each of these installation options and provides guidance on how to perform an installation of Windows Server 2016 htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 9161coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine The installation process for Windows Server 2016 requires minimal input from the installer. However, following the installation, you must configure a number of important settings before you can use your server. In addition, because Server Core provides no graphical management tools, you must know how to enable and perform the remote management of your server infrastructure. This lesson identifies the important post-installation configuration options and explains how to enable and use the remote management tools. Lesson objectives After completing this lesson, you will be able to: + Explain how to plan for Server Core. + Explain how to install Server Core. + Explain the post-installation configuration for Server Core. + Explain how to select a suitable installation type. Planning for Server Core htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 2016102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe + Server Core is: - A more security-enhanced, less resource-intensive installation option than the Desktop Experience installation - An installation that cannot be converted to a full graphical shell version of Windows Server 2016 + The default installation option for Windows Server 2016 - Managed locally by using Windows PowerShell and other standard tools + With remote management enabled, you rarely need to sign in locally Server Core is the default installation option when you run the Windows Server 2016 Setup wizard, It uses fewer hardware resources than the full installation option, One of the ways it does this is by not installing a GUI for management purposes. Instead, you can manage Server Core locally by using Windows PowerShell or a command- line interface, or you can manage it remotely by using one of the remote management options described in the last lesson. Server Core has the following advantages over the full Windows Server 2016 installation option: + Reduced update requirements. Because Server Core installs fewer components, its deployment requires you to install fewer software updates. This reduces the number of monthly restarts required and the amount of time required for an administrator to service Server Core. A reduced hardware footprint. Computers running Server Core require less RAM and less hard drive space, When Server Core is virtualized, this means that you can deploy more servers on the same host. + Smaller attack surface. Installing fewer components, especially the client interface, htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 26102-08-2019 207400 - Instalaton, Storage, and Compute with Windows Server 2016 | Sklpipe reduces the potential surface for security vulnerabilities for hackers to exploit. There are some drawbacks to installing Server Core instead of Windows Server with Desktop Experience. If an application depends on the GUI, it will fail when the GUI call is made. For example, an error might occur when a dialog box appears. Also, as mentioned previously, there are more limited local management options. However, when you are connected locally, you can also use the tools that are listed in the following table to manage Server Core deployments of Windows Server 2016. Tool Function Cmd.exe Allows you to run traditional command-line tools, such as ping.exe, ipconfig.exe, and netsh.exe. PowerShell.exe Launches a Windows PowerShell session on the Server Core deployment. You then can perform Windows PowerShell tasks normally. Windows, Server 2016 comes with Windows PowerShell version 5.0 installed. Regedt32.exe Provides registry access within the Server Core environment. Msinfo32.exe Allows you to view system information about the Server Core deployment. Sconfig.cmd Serves as a command-line, menu-driven tool to perform common server administration tasks, Taskmgr.exe Launches Task Manager. Note: In the original release of Windows Server 2016 that included Nano Server, Sconfig.cmd was planned to be deprecated. With changes in the servicing model, however, especially the Semi-Annual Channel release that is only available in Server Core mode, Microsoft is currently re-evaluating the decision to deprecate Sconfig.cmd. Server roles available in Server Core htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 226102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe The following server roles are available on Server Core deployments: + ADCS + ADDS + DHCP Server + DNS Server + File Services (including File Server Resource Manager) + Active Directory Lightweight Directory Services (AD LDS) + Hyper-V + Print and Document Services + Streaming Media Services + Web Server (including a subset of ASP.NET) + Windows Server Update Server + Active Directory Rights Management Server + Routing and Remote Access Server and the following subroles: © Remote Desktop Connection Broker © Licensing o Virtualization Installing Server Core and Server with Desktop Experience htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 2a02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Perform preinstallation tasks: + Disconnect UPS + Back up server if applicable + Disable antivirus software Run the Windows Setup Wizard from the installation media: 1. Provide locale information (language, date, currency, keyboard) Select Server Core Installation Review and accept license Select installation location Provide administrator password Installing Windows Server 2016 is largely the same whether you are installing Server Core or Server with Desktop Experience. Before installing Windows Server 2016 you should perform several tasks to prepare for installation: Disconnect any uninterruptible power supply (UPS) that is connected to the destination computer with a serial cable. Setup attempts to detect any devices connected to serial ports and UPS equipment can cause problems with this process. + Back up your server if this is not a clean install. + Disable virus protection software that might be installed on the target computer. + Copy any mass storage driver files provided by the manufacturer to a disk, flash drive, or other portable media so that the driver can be provided during setup. The actual installation process includes the following steps: 1. Connect to the installation source. Options for this include: htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 20102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe o Insert a DVD-ROM containing the installation files, and boot from the DVD-ROM. © Connect a specially prepared USB drive that hosts the installation files 0 Perform a PXE boot, and connect to a Windows Deployment Services server. On the first page of the Windows Setup Wizard, select the following locale- based information: © Language to install 0 Time and currency format © Keyboard or input method On the second page of the Windows Setup Wizard, click Install now. You also can use this page to select Repair Your Computer. You use this option if an installation has become corrupted and you are no longer able to boot into Windows Server 2016. In the Windows Setup Wizard, on the Select The Operating System You Want To Install page, choose from the available operating system installation options. The default option is Server Core Installation. On the License Terms page, review the terms of the operating system license. You must choose to accept the license terms before you can proceed with the installation process. On the Which Type Of Installation Do You Want page, you have the following options: © Upgrade. Select this option if you have an existing installation of Windows Server that you want to upgrade to Windows Server 2016 You should launch upgrades from within the previous version of Windows Server rather than booting from the installation source. hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 256102-08-2019 207400 - Instalaton, Storage, and Compute with Windows Server 2016 | Sklpipe © — Custom. Select this option if you want to perform a new installation. 7. Onthe Where do you want to install Windows page, choose an available disk on which to install Windows Server 2016. You can also choose to repartition and reformat disks from this page. When you click Next, the installation process will copy files and reboot the computer several times. 8. On the Settings page, provide a password for the local Administrator account, Note: Unlike Windows Server 2012, you cannot convert from Server Core to Server with Desktop Experience, or from Server with Desktop Experience to Server Core. Note: You can also install Windows Server 2016 as a preconfigured VHD from the TechNet Evaluation Center. Refer to: “Windows Server 2016" at: http://aka.ms/Uphshk Post-installation configuration settings htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 266102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe After you install Windows Server 2016, you must complete the following: - Configure the IP address + Set the computer name + Join an Active Directory domain + Configure the time zone - Enable automatic updates - Add roles and features + Enable the Remote Desktop feature - Configure Windows Firewall settings In earlier versions of Windows Server, the installation process required you to configure network connections, the computer name, user accounts, and domain membership information. The Windows Server 2016 installation process reduces the number of questions that you must answer. The only information that you provide during installation is the password that the default local Administrator account uses. After you have installed Windows Server 2016, you typically should complete the following: + Configure the IP address. + Set the computer name. + Join an Active Directory domain. Configure the time zone + Enable automatic updates. + Add roles and features. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 218102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe + Enable the Remote Desktop feature. + Configure Windows Defender Firewall settings. The installation type selected (Windows Server with Desktop Experience or without) during setup determines which tools you can use to complete these configuration tasks. For example, on Windows Server with Desktop Experience, you can use Server Manager on the local server to complete these post-installation tasks. On Server Core, you can use Windows PowerShell or other command-line tools, such as Netsh.exe, locally, Altematively, you can enable remote management and then complete these tasks by using Windows PowerShell Remoting. You can also use Server Manager to configure the Server Core installation remotely. Note: You can also use an XML answer file to provide this information during an automated installation. Discussion: selecting a suitable Windows Server edition and installation type Which Windows Server 2016 installation option would you select? 10 minutes htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 2102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Which Windows Server 2016 installation option would you select? Check your knowledge Discovery Your customer, a small legal firm, has a requirement for a single server that they want you to deploy at their only office. Which Windows Server 2016 installation option would be best? Check your knowledge Discovery One of your enterprise customers has a new branch office. You must deploy Windows Server 2016 to support the local users at this new branch. The server will be managed remotely from IT staff located in the head office. The server will support the DNS, DHCP, and AD DS server roles. Your customer wants to minimize resource consumption on the server. Which Windows Server 2016 installation option would be best? Demonstration: Installing Server Core In this demonstration, you will see how to install Server Core. Demonstration steps Install Windows Server 2016 Core 1. When LON-SVR6 starts Windows Setup, install Windows Server 2016 Core by using the indows Server 2016 Datacenter Evaluation option. 2. Use the Custom option rather than the Update option, accepting all other default values and license agreements. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 2010102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe 3. Use Pa55w.rd for the Administrator's password 4. Verify that when the installation is complete, LON-SVR6 displays the Command Prompt window. Configure a new Server Core installation 1. Open Windows PowerShell on LON-SVR6. 2. Use the $env:computername and Get-NetIPAddress cmdlets to display the LON-SVR6 host name and |Pv4 address information 3. Note that the name is random and that the address is derived from a DHCP server automatically. 4. Run the Sconfig.cmd tool on LON-SVR6. Use the tool to set the following: a. IP address settings: i. Address: 172.16.0.26 ii. Subnet Mask: 255.255.0.0 iii, Default Gateway: 172.16.0.1 iv. Preferred DNS Server: 172.16.0.10 b. Join the Adatum.com domain and use Adatum\administrator credentials. c. Rename the computer LON-SVR6 and use Adatum\Admi credentials. d. Restart the computer. 5. After LON-SVR6 starts, sign in as Administrator with the password PaSSw.rd. 6. Use the $env:computername and Get-NetIPAddress cmdlets to display the LON-SVR6 host name and |Pv4 address information hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 206102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe 7. Note that the name is LON-SVR6 and that the address is 172.16.0.26. 8. Revert all virtual machines, and then start 20740C-LON-DC1. Check your knowledge Select the best answer fe remote Windows PowerShell Which of the following commands do you use to i management? Enter-PSSession -Name Enter-PSRemote -Name Enter-PSSession -ComputerName Enter-PSRemote -ComputerName Lesson 3: Preparing for upgrades and migrations One of the key tasks when deploying Windows Server 2016 is identifying when you should upgrade an existing Windows Server deployment by using the existing hardware or when you should migrate the roles and features to a clean installation of Windows Server 2016 on new hardware. You will also want to use available guidance documentation and tools to determine which options are most suitable and use tools to automate the process, This lesson describes the considerations for performing an in-place upgrade or migrating to a new server. It also provides scenarios you can compare to your current business requirements and explains the benefits of migrating to a clean installation of Windows Server 2016. The lesson also provides you information about tools and guidance you can use to assess your own environment and help you deploy Windows Server 2016. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 aust02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Lesson objectives After completing this lesson, you will be able to: Describe the differences between an in-place upgrade and migration. + Identify scenarios when an in-place upgrade is appropriate. + ‘Identify the benefits of migrating to Windows Server 2016. + List solution accelerators available to help with your upgrade or migration + Describe best practices for server consolidation. In-place upgrades vs. server migration - Upgrading to Windows Server 2016: - Can upgrade from Windows Server 2008 R2 or later - Can only upgrade to same or newer editions + Requires same processor architecture + Migrating to Windows Server 2016: - Must migrate from x86 version of Windows Server + Can use the Windows Server Migration Tools feature When deploying Windows Server 2016, organizations must make the following choice: + Use existing hardware and upgrade from supported editions of Windows Server htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 228102-09-2019 2008 or later. 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe + Install Windows Server 2016 on new hardware, and, if required, migrate the roles, features, and settings from servers that are running supported earlier Windows Server editions. When planning whether to upgrade or migrate a server to Windows Server 2016, consider the options in the following table, Installation option Upgrade Description ‘An upgrade preserves the files, settings, and applications that are installed on the original server. You perform an upgrade when you want to keep all these items and want to continue using the same server hardware. An upgrade requires x64 processor architecture and an x64 edition of the Windows Server operating system. If you are upgrading from Windows Server 2008 R2, you must install Service Pack 1 (SP1) You start an upgrade by running the Windows Server 2016 Setup wizard from the original Windows Server operating system. You can perform the following upgrades to Windows Server 2016: Original operating system and edition Upgrade edition Windows Server 2008 R2 Standard or Windows Server 2016 Standard, Windows Server 2008 R2 Enterprise Windows Server 2016 Datacenter Windows Server 2008 R2 Datacenter Windows Server 2016 Datacenter Windows Web Server 2008 R2 Windows Server 2016 Standard Windows Server 2008 R2 Datacenter Windows Server 2016 Datacenter with SP1 Windows Server 2008 R2 Enterprise Windows Server 2016 Standard or with SP1 Windows Server 2016 Datacenter htps:www-sklpipe.comitireaderibook/8035340-c012-4850-8e60-730bI@Sab7I4 at02-08-2019 207400 Instalaton, Storage, and Compute with Windows Server 2016 | Sklpipe Installation Wassuya Street 2008 R2 Standard —_ Windows Server 2016 Standard or . with SP1 Windows Server 2016 Datacenter option Windows Web Server 2008 R2 with Windows Server 2016 Standard sP1 Windows Server 2012 Datacenter or Windows Server 2016 Datacenter Windows Server 2012 R2 Datacenter Windows Server 2012 Standard or Windows Server 2016 Standard or Windows Server 2012 R2 Standard Windows Server 2016 Datacenter Migration Use migration when you migrate from an x86 edition of Windows Server 2003, Windows Server 2003 R2, or Windows Server 2008. You can use the Windows Server Migration Tools feature in Windows Server 2016 to transfer files and settings from computers that are running the following editions: + Windows Server 2003 + Windows Server 2003 R2 + Windows Server 2008 + Windows Server 2008 R2 + Windows Server 2012 + Windows Server 2012 R2 Additional Reading: For more information on migration, refer to: “Install, Use, and Remove Windows Server Migration Tools” at: http://aka.ms/p3xxrr In-place upgrade scenarios htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 a102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Perform an in-place upgrade when: - Existing servers meet hardware requirements + Software products installed on an existing server support an in-place upgrade - You want to keep existing data and security permissions + You want to keep existing roles, features, and settings An in-place upgrade involves upgrading a Windows Server operating system on the server that is running an earlier Windows Server edition. A benefit of an in-place upgrade is that you avoid hardware expenses because you install Windows Server 2016 on the existing hardware. Another benefit is that files, settings, and programs are kept intact on the server. You would choose an in-place upgrade of the Windows Server operating system in the following scenarios: + When the hardware configuration of the existing servers meets the requirements for Windows Server 2016. Because the hardware requirements for Windows Server 2016 do not differ significantly from those for Windows Server 2012 R2, you can most likely perform an in-place upgrade on those servers. When the software products that run on the existing servers support in-place upgrade of Windows Server 2016. Before performing an in-place upgrade, you must list all of the software products that are running on the server, such as SQL Server, Exchange Server, non-Microsoft software, and antivirus software. Next, verify that these products support an in-place upgrade of Windows Server 2016. If 80, refer to the specific product's documentation to determine how to perform an in-place upgrade, including any issues or risks that might occur. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 asi6tcoon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine + When you want to keep alll user data that is on the existing servers, such as data stored on file servers, and security permissions for accessing those data. When performing an in-place upgrade, user data and security permissions for accessing the data remain unchanged. This scenario is convenient, because after the in- place upgrade, users can continue to access their data on the same file servers. When you want to install Windows Server 2016, but you want to keep all roles, features, and settings of the existing server. Before performing an in-place upgrade on a server that has specific roles, features, or settings—such as Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), or AD DS—iist those configurations. Then, check if those configurations support an in-place upgrade of Windows Server 2016. If so, refer to the detailed instructions for the specific roles, features, or settings on how to perform the in-place upgrade, including any issues or risks that might occur. If any of these scenarios do not meet your organization's requirements, then you should perform a migration to Windows Server 2016. Benefits of migrating to Windows Server 2016 When you perform a migration, you: - Do not affect your current Windows Server 2008 or later IT infrastructure + Perform software product migration in a separate environment + Perform migration of server roles, features, and settings in a separate environment - Ensure new operating system enhancements are installed by default htps:wwsklpipe.comitroaderibook/8035340-c012-4850-8e60-730DI@Sab7I4 601coon2019 207400 nstalition, Storage, and Compute wih Windows Server 2016| Stine When deploying Windows Server 2016, some organizations should consider migration instead of an in-place upgrade. There can be risks that arise from an in- place upgrade, such as server unavailability or data being inaccessible. Therefore, your organization might choose to perform a migration because of the following benefits + You will deploy servers with the Windows Server 2016 operating system installed, and they will not affect the current IT infrastructure. Once you install Windows Server 2016, you can perform tests, such as drivers or system performance tests, before you introduce that server to the domain. In this way, the process of installation and testing is less likely to affect your current IT infrastructure. You will perform software product migration in a separate environment. For any software solution with an earlier Windows Server edition, you must refer to the product documentation for information about how to migrate that solution to Windows Server 2016. In some scenarios, software products that you are using are not supported for installation on Windows Server 2016, and you will require newer editions of those software products. In this case, by using migration, you can perform systematic installation of the operating system and the software products, in a separate environment. This ensures that the migration does not affect the availability of current services that the software provides. + You will perform migration of server roles, features, and settings in a separate environment. As with the migration of software products, refer to the documentation on how to migrate the specific roles, features, or settings, such as DHCP, DNS, or AD DS, to Windows Server 2016. Again, migration enables you to perform systematic configuration in a separate environment, which means that the migration should not affect availability of server roles, features, and settings. + New operating system enhancements are installed by default. When performing an in-place upgrade, for compatibility reasons, Windows Server 2016 is configured with settings for Windows Server 2008 or Windows Server 2008 R2. This means that many enhancements that Windows Server 2016 introduces, such as security, functionality, or performance enhancements, are not enabled by default. When performing migration, Windows Server 2016 deploys as a clean installation with all hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 ais02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe new enhancements installed. This ensures that the operating system is more secure and has new functionalities installed by default. Using solution accelerators + Use Microsoft Deployment Toolkit (MDT) to: - Automate deployments of Windows Server 2016 or other Windows operating systems +Use MAP Toolkit for Windows Server 2016 to: + Perform inventory of your organization's IT infrastructure - Generate a report or proposal based on the Windows Server 2016 Readiness Assessment to plan server consolidation - Use Windows Server Migration Tools to: + Migrate server roles, features, operating system settings, data, and shares Organizations should consider using software tools to help them plan their upgrade and migration to Windows Server 2016. Along with guidance content to help you design and plan your Windows Server 2016 deployment, Microsoft also provides solution accelerators to assist in the process. Microsoft Deployment Toolkit Microsoft Deployment Toolkit (MDT) is both a process and a lightweight tool for automated server (and desktop) deployments. It is used for deploying standardized images. MDT is based on a variety of Microsoft technologies including PXE, Windows Deployment Services (WDS), and System Center Configuration Manager (SCCM). MDT automates the deployment process by configuring unattended Setup htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 et02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe files and packaging the files into an image file that you can deploy to a target computer. Additional Reading: For more information about using MDT as part of a complete deployment solution, refer to: “Automate and manage Windows operating system deployments” at: http://aka.ms/Mi7wfx For more information about MDT, including the latest updates, refer to: “Microsoft Deployment Toolkit” at: http://aka.ms/de2ej0 Microsoft Assessment and Planning Toolkit (MAP) The Microsoft Assessment and Planning Toolkit (MAP) is a solution accelerator that analyzes the inventory of an organization's server infrastructure, performs an assessment, and then creates reports that you can use for upgrade and migration plans. MAP is available for Windows Server 2016, Windows Server 2012 R2, Windows 10, Windows 8.1, and for other products, such as SQL Server 2014 and Hyper-V. Use MAP to perform the following tasks: + Inventory your organization's IT infrastructure. Based on the inventory, MAP displays a detailed report about which machines are capable of running Windows Server 2016, which machines are capable of running Windows Server 2016 with minimum system requirements, and which machines are not capable of running Windows Server 2016. MAP also recommends specific upgrades that ensure computers are capable of running Windows Server 2016. + Generate a report or proposal based on the Windows Server 2016 Readiness Assessment. The report or proposal is a document that contains an Executive Overview, Assessment Results, Next Steps, and a worksheet summarizing Windows Server 2016 readiness for computers that are running Windows Server. + Capture the performance metrics of the current IT infrastructure to help plan consolidation and server virtualization. The performance assessment generates reports on performance and presents the server consolidation recommendations. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 96102-08-2019 207400 - Instalaton, Storage, and Compute with Windows Server 2016 | Sklpipe + Estimate server utilization based on that metric before and after the virtualization. You also can choose which current physical servers are the best candidates for virtualization, and the hosts on which you should place those virtual machines. Reference Links: For more information about the Microsoft Assessment and Planning (MAP) Toolkit, refer to: http://aka.ms/u7x2mf Windows Server migration tools Windows Server 2016 includes tools to assist you in migrating server roles and features from one computer to another. These Windows PowerShell cmdlets are part of a snap-in that are installed as part of a full installation or Core Server installation Microsoft also provides detailed migration guides for specific roles. Additional Reading: For more information about the Windows Server Migration Tools and migration guides for specific roles and features, refer to: “Migrate Roles and Features to Windows Server’ at: http://aka.ms/mr3jqp Recommendations for server consolidation htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 406102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe + Analyze if cohosting of multiple roles is supported «Deploy roles that are not supported for cohosting on additional servers - Determine if cohosting multiple roles affects server performance (it should not) -Analyze if cohosted roles are supported for high availability When Deploying Windows Server 2016, you should plan your placements of server roles, such as AD DS, DNS, and DHCP, to make the best use of hardware and network resources. Organizations should consider cohosting multiple roles, where possible, to achieve the most economical solution. Virtualization is also considered as a consolidation of the server roles. However, you should not implement cohosting if it affects server performance or available disk space. Therefore, organizations should evaluate and test whether installing multiple server roles on a server would result in lower overall performance and disk usage. Furthermore, organizations should evaluate the security risks of collocating server roles. For example, the server that hosts the root Active Directory Certificate Services role should not be collocated with other server roles and should be offline most of the time. Smaller organizations should consider the following best practices: + Plan which server roles you need. If the operating system supports cohosting of those roles on one server, multiple roles can be installed and cohosted on a single server. If cohosting multiple server roles on one physical server affects the performance of the physical server, administrators should not cohost the server roles and should install server roles on different physical servers. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 astcoon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine + If the operating system on a physical host does not support cohosting of multiple server roles, administrators should deploy server roles on multiple physical servers Medium and large organizations should consider the following performance and high- availability issues when cohosting: + Ifyou are cohosting multiple roles on a single server, there might be performance issues because of the large number of client computers that are connecting to that server. In this situation, organizations should consider adding multiple servers that cohost the same multiple roles. They also should consider relocating some of the roles from the first server to the other physical servers. High availability configurations of roles have specific requirements and setting, which might not support cohosting of multiple roles. In this situation, organizations could have a high availability solution for one server role, and then must locate remaining roles on other servers Demonstration: Using MAP In this demonstration you will see how to: + Review the MAP options. + Perform an inventory assessment by using MAP. + Review the inventory from a sample database. Demonstration steps Review the MAP options 1. On LON-CL1, run the Microsoft Assessment and Planning Toolkit. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 426102-09-2019 2. 207400 nstalition, Storage, and Compute wih Windows Server 2016| Stine In the Microsoft Assessment and Planning Toolkit console, review the default window that displays the Overview page. In the Microsoft Assessment and Planning Toolkit console, in the left pane, select Cloud, and then review the readiness information for the different cloud scenarios. In the Microsoft Assessment and Planning Toolkit console, in the left pane, click Desktop, and review the readiness information for the different desktop scenarios. Repeat step 4 for all remaining items in the left pane: Server, Desktop Virtualization, Server Virtualization, Database, Usage Tracking, and Environment. Perform inventory On LON-CL1, in the Microsoft Assessment and Planning Toolkit console, in the left pane, select Overview, and then, in the Overview page, create an inventory database named INVENTORY. On Overview page, select Perform an inventory. In Inventory and Assessment Wizard window, perform the following steps: a. _Onthe Inventory Scenarios page, select the following check boxes © Windows computers o — Exchange Server o Lyne Server o SQL Server © Windows Azure Platform Migration b. On the Discovery Methods page, select Use Active Directory Domain hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 ait02-09-2019 20740¢- salon, Storage, and Compute wih Windows Sever 206 | hiine Services, Use Windows networking protocols, and Scan an IP address range c. On the Active Directory Credentials page, in the Domain field, enter Adatum.com. In the Domain Account field, enter Adatum\Administrator, and then in the Password field, type PaS5w.rd, and on the next two pages accept the default settings, d. On the Scan an IP Address Range page, enter the range from 172.16.0.1 to 172.16.0.100. e. On the All Computers Credentials page, accept the default settings. f. On the Summary page, review the inventory options, and then cancel the wizard. Note: You cancel the inventory procedure because the lab does not contain an environment with older operating systems for MAP to discover. In the next step, you review the test inventory that you import from the sample database in MAP. Review the MAP inventory from a sample database In the Microsoft Assessment and Planning Toolkit console, on the File menu, select Manage Databases In Microsoft Assessment and Planning Toolkit dialog box, import the sample database using the following steps: a. Select Manage. b. Import the sample database located in following path: In the File name field, type C:\Program Files\Microsoft Assessment and Planning Toolkit\Sample \MAP_SampleDB.bak. c. Inthe Database Name field, type MAPDEMO. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 at02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe d. In the Microsoft Assessment and Planning Toolkit window, choose the Use an existing database option, and then select MAPDEMO database. 3. _ In the Microsoft Assessment and Planning Toolkit console, review the default window that displays the Overview page that includes inventory information from the sample database. Refresh the window in Overview page, if necessary. 4. — In the Microsoft Assessment and Planning Toolkit console, in the left pane, click Cloud, and then review the readiness information on the different cloud scenarios that displays with inventory information from the sample database. 5. Inthe Microsoft Assessment and Planning Toolkit console, in the left pane, click Desktop, and then review the readiness information on the different desktop scenarios that appear with inventory information from the sample database 6. Repeat step 5 for all remaining items in the left pane: Server, Desktop Virtualization, Server Virtualization, Database, Usage Tracking, and Environment. Check your knowledge Discovery How does virtualization help in server role consolidation? Lesson 4: Migrating server roles and workloads Organizations should plan to spend time creating a server upgrade and migration plan. Planning is critical for organizations that are considering new operating system deployments. There are different elements that affect the planning for a new operating system deployment, such as analyzing current IT infrastructure, choosing hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 4sia102-08-2019 207406 - Instalaion, Storage, and Compute wih Windows Server 2016 | Skipipe an operating system edition, creating an upgrade or migration strategy, and creating a strategy for backup, restoring, monitoring, and maintaining the operating system. You must also determine which roles you can migrate, which you can cohost, and which you can consolidate into a virtual environment. Finally, you must plan for migrating roles within the same domain or across domains Lesson objectives At the end of this lesson, you will be able to: + Explain how to implement server migrations. + Explain how to migrate servers across domains. Migrating server roles within a dom The roles that you can migrate from supported earlier editions of Windows Server to Windows Server 2016 include: - AD FS Role Services > Hyper-V * DHCP - DNS + Network Policy Server + Print and Document Services » Remote Access > WSUS When planning to migrate servers, you must create a list of the server roles that you want to migrate and the steps that each involves. For each server role that you plan htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 461coon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine to migrate, you should refer to the technical documentation and migration guides about how to perform the migration. When performing migration, you should use the Windows Server Migration Tools, which are available with Windows Server 2016. The roles that you can migrate include: + Active Directory Certificate Services * Active Directory Federation Services (AD FS) Role Services + File and Storage Services + DHCP + DNS + Hyper-V + Network Policy Server + Print and Document Services + Remote Access + Remote Desktop Services + Cluster Role Services + Windows Server Update Services (WSUS) Installing and preparing the Windows Server Migration Tools consists of the following steps: 1. Install the tools on destination servers as part of Windows Server 2016 setup. 2. Create a deployment folder containing a copy of the tools on the destination server. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 4718102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe 3. Copy the deployment folder from destination server to source server. 4. _ Register Windows Server Migration Tools on the source server by using the SmigDeploy.exe tool included in the deployment folder. Once the migration tools are installed, you can run them by using one of the following methods: + Run Windows Server Migration Tools as an administrator from the Windows Start screen. + Load the Windows Server Migration Tools snap-in into an elevated Windows PowerShell session. + On source computers running earlier versions of Windows Server, run Windows Server Migration Tools under the Windows PowerShell folder, which is under the All Programs folder of the Start menu. Note: You can migrate roles only from supported earlier Windows Server editions to Windows Server 2016. Additional Reading: For more information about determining which roles and features to migrate, refer to the migration guides for Windows Server 2016 in “Migrate Roles and Features to Windows Server" at https://aka.ms/Xmwr4q Migrating server roles across domains or forests htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 at02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe When migrating serves across domains: » Create a new Windows Server 2016 AD DS forest + Deploy applications on new servers + Establish AD DS trust between the current and the new AD DS forests +» Migrate AD DS objects » Migrate application data and settings - Decommission and remove the old AD DS environment Organizations could choose to deploy Windows Server 2016 in a new AD DS forest. In this scenario, administrators should plan the migration steps carefully to provide users with seamless access to data and services during the migration process. Once the migration is complete, administrators should begin the process of decommissioning and removing the infrastructure of the previous operating system environment To migrate a server across domains: + Create a new Windows Server 2016 AD DS forest that is independent from the forest that is running a previous operating system version. + Deploy new servers that are running the Windows Server 2016 operating system. + Deploy Microsoft applications, such as Exchange Server, SQL Server, and Microsoft SharePoint server in the new AD DS forest. + Deploy corporate custom applications or third-party applications in the new AD DS. forest that the previous infrastructure environment used. * Configure DNS infrastructure in both forests. htps:ww-sklpipe.comitireaderibook/8035340-c012-4850-8e60-T30DIBSab7I4 490102-08-2019 20740¢- salon, Storage, and Compute wih Windows Sever 206 | hiine Establish AD DS trust between the current and the new AD DS forests. Migrate AD DS objects, such as users, computers, groups, and mailboxes. Migrate application data and settings for Microsoft applications, corporate custom applications, and third-party applications. Ensure that users can connect to corporate IT resources in the new AD DS forest. Decommission and remove the environment, based on previous operating system's AD DS forest. Note: For each product and application that you plan to migrate to Windows Server 2016 AD DS forest, read the product documentation and best practices, including the supported migration procedures. You will find this information on the website of each of the products. Note: You must use a tool, such as the Microsoft Active Directory Migration Tool (ADMT), to migrate resources such as users, computers, and groups across forests or within the same forest. While the ADMT tool has not updated from version 3.2, it does work with Windows Server 2016 domains and forests. For more information about using ADMT, see “ADMT Guide: Migrating and Restructuring Active Directory Domains” at http://aka.ms/Lb96ie. Check your knowledge Discovery What are some reasons you would do a cross-forest migration instead of a migration within the same domain? Reset Lesson 5: Windows Server activation models htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 sot02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe As part of planning your server upgrade and migration process, you should also consider how you will manage operating system licensing and activation. Your choice of activation model will be based on the characteristics of your environment. Lesson objectives After this lesson you will be able to: + Describe the volume licensing and activation options for Windows Server 2016. + Plan a suitable volume activation process. Windows Server 2016 licensing and activation Organizations can choose between two activation strategies: Activation strategy | When used Manual Suitable when deploying small number of servers “Automatic Suitable when deploying larger number of servers To ensure that your organization has the proper licenses, and to receive notices for product updates, you must activate every copy of Windows Server 2016 that you install. Windows Server 2016 requires that you activate the operating system after installation. This verifies that the products are licensed and that you receive important update information. There is no activation grace period. If you do not activate htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 suetcoon2019 207400 nstaltion, Storage, and Compute wih Windows Server 2016| Stine Windows Server 2016, you cannot customize your operating system. There are two general activation strategies: + Manual activation. This strategy is suitable when you deploy a small number of servers + Automatic activation. This strategy is suitable when you deploy a larger numbers of servers. Manual activation When you use manual activation, you must enter the product key. Microsoft or an administrator performs the activation over the phone or through a special clearinghouse website. You can perform manual activation by using the retail product key or the multiple activation key. You can use a retail product key to activate only a single computer. However, a multiple activation key has a set number of activations that you can use. This allows you to activate multiple computers, up to a set activation limit. OEM keys are a special type of activation key that a manufacturer receives, and which enable automatic activation when a computer starts. You typically use this type of activation key with computers that are running Windows client operating systems, such as Windows 7 and Windows 8. You rarely use OEM keys with computers that are running Windows Server operating systems. Automatic activation Performing activation manually in large-scale server deployments can be cumbersome. Microsoft provides a method of activating large numbers of computers automatically, without having to enter product keys manually on each system. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 2161coon2019 207400 salation, Storage, and Compute with Windows Server 2018 | Siig There are a several technologies available that help automate the process of activating Windows Server licenses + Key Management Services (KMS). KMS is a service that helps you activate licenses on systems within your network from a server where a KMS host has been installed. The KMS host completes the activation process instead of individual computers connecting to Microsoft to complete activation. Volume Activation Services server role. This server role helps you to automate issuing and managing Microsoft software volume licenses. Volume Activation Services allows you to install and configure KMS and Active Directory-based Activation. KMS requires activating at least five servers and 25 clients. KMS is the default key for volume activation. Active Directory-Based Activation. This is a service that lets you use AD DS to store activation objects. A computer running Windows Server (or client) automatically contacts AD DS to receive an activation object, without the need to contact Microsoft. You can use Active Directory-based activation when activating servers and clients running Windows Server 2012 or later, and Windows 8 or later. Your AD DS schema must also be Windows Server 2012 or later. Volume Activation Tools console. The Volume Activation Tools console is used to install, activate, and manage volume license activation keys in AD DS or KMS Volume Activation Management Tool (VAMT). The VAMT is a no-cost tool that you can use to manage volume activation using Multiple Activation Keys (MAKs) or to manage KMS. You can use VAMT to generate license reports and manage client and server activation on enterprise networks. Multiple Activation Key (MAK). A MAK is a volume license key that you can use for independent activation by connecting with Microsoft or through proxy activation, where a single computer gathers the activation information for multiple computers and contacts Microsoft for them. Use MAK when your systems have poor—or no —connection with your organization's central network. Automatic Virtual Machine Activation (AVMA). AVMA lets you install VMs on a virtualization server with no product key. hitpssiwwu:skilpipe.comitreaderbook/#0c36340-c0'2-4850-8e60-730@Sab7I4 sat02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Reference Links: For more information on VAMT, refer to: “Introduction to VAMT” at: http://aka.ms/b07bed Licensing changes since Windows Server 2008 As part of planning your deployment, you must ensure you have the proper number of licenses for your Windows Server 2016 installation. Windows Server 2016, like Windows Server 2012, is licensed by processor core, not by server. You can purchase additional licenses for two processor cores at a time. Discussion: Planning volume activation Discuss both scenarios. Based on the scenario, what type of volume activation should you implement? To implement a volume-activation process, you must consider which activation type is most suitable for your organization. Not all companies have the same IT infrastructure; therefore, scenarios differ for each company. You should consider the two scenarios that are shown on the slide when planning your organization's volume activation process. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 saat02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Check your knowledge Discovery Your organization's IT infrastructure consists of personal computers and servers that are running different editions of Windows client operating systems and Windows Server operating systems. Next month, your organization plans to deploy 500 Windows 10 client computers and 20 Windows Server 2016 servers. Because of a legacy application in the finance department, you must deploy 10 client computers that are running Windows 8.1 and two servers that are running Windows Server 2012 R2. What type of volume activation should you implement? Check your knowledge Discovery Your organization’s IT infrastructure was upgraded from different editions of Windows client operating systems and Windows Server operating systems to Windows 10 and Windows Server 2016, respectively. What type of volume activation should you implement? Lab: Installing and configuring Server Core Scenario Your team in the IT department at Adatum Corporation just purchased a new server that has no operating system. The team decides to install Windows Server 2016 Datacenter Evaluation in Server Core mode to test Server Core functionality. Your task is to perform the installation and configuration of this server. You will name it LON-SVRG, give it a static IP address of 172.16.0.26, and join it to the Adatum.com domain with all other default settings. Objectives htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 ssiat02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe After completing this lab, you will be able to: + Install the Server Core option for Windows Server 2016 + Configure Server Core. Lab setup Estimated time: 60 minutes Virtual machines: 20740C-LON-DC1 and 20740C-LON-SVR6 User name: Adatum\Adi trator Password: PaSSw.rd For this lab, you will use the available virtual machine environment. Before you begin the lab, complete the following steps: 1. Onthe host computer, start Hyper-V Manager. 2. In Hyper-V Manager, click 20740C-LON-DC1, and then in the Actions pane, click Start. 3. _ In the Actions pane, click Conneet, Wait until the virtual machine starts 4. Sign in by using the following credentials: o User name: Adatum\Administrator 0 Password: PaSSw.rd 5. In Hyper-V Manager, right-click 20740C-LON-SVRG, and then select Connect. In the virtual machine connection window, click Media, point to DVD Drive, and then click Insert Disk. 6. Browse to D:\Program Files\Microsoft Learning\20740\Drives, select htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 seat02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe WinServer2016_1607.iso, and then click Open. Exercise 1: Installing Server Core Scenario You determine that Server Core offers you the best installation option and decide to evaluate a server that uses Server Core. The main task for this exercise is as follows: + Install Windows Server 2016 Datacenter Evaluation on LON-SVR6 Result: After completing this exercise, you will have successfully installed the Windows Server 2016 Core operating system on LON-SVR6 Exercise 2: Completing post-installation tasks on Windows Server 2016 Core Scenario You must now complete the installation of Server Core by configuring the post- installation settings and joining it to the Adatum.com domain. You will also install the DNS Server role. The main task for this exercise is as follows: + Use Windows PowerShell and Sconfig.cmd to configure the settings of Server Core htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 716102-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Result: After completing this exercise, you will have successfully configured the domain and network settings of Server Core and install an additional role. Exercise 3: Performing remote management Scenario Now that you added the DNS Server role to Server Core on LON-SVR6, you want to explore configuring the DNS settings and configuration by using GUI tools on other Windows Server with Desktop Experience systems. The main tasks for this exercise are as follows: 1. Enable remote management with Server Manager 2. Add LON-SVR6 to DNS Manager on LON-DC1 and then add the Adatum.com zone to LON-SVR6 as a secondary zone 3. Examine the new zone information on LON-SVR6. 4. Prepare for the next module Result: After completing this exercise, you will have configured the DNS Server settings on LON-SVR6 remotely. htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 seat02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Review question(s) Check your knowledge Discovery In the lab, you used the Install-WindowsFeature cmdlet in Windows PowerShell to install the DNS Server role on LON-SVR6. How could you do this remotely? Module review and takeaways Common Issues and Troubleshooting Tips Common Issue Troubleshooting Tip Windows PowerShell cmdlets are not Please see Student Companion Content for this course. available You need @non-GUI interface method to Please see Student Companion Content for this course. shut down or restart a computer that is running Server Core ‘You are unable to join a computer to the Please see Student Companion Content for this course. domain Review question(s) Check your knowledge Discovery What major advantages does Server Core have over a full Windows Server 2016 installation? htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 sat02-09-2019 20740C Installation, Storage, and Compute with Windows Server 2016 | Sklpipe Check your knowledge Discovery /e years ago, your organization bought a new rack-mount server and installed Windows Server 2012 on it. You now want to install Windows Server 2016 via the upgrade method. What should you do? Check your knowledge Discovery Which role can you use to manage KMS? Tools The following table lists the tools that this module references. Tool How used Where found RSAT Download from the Microsoft + Used for managing servers remotely from a Windows 10 workstation download center Start from a command prompt or Windows PowerShell console Scontig.cma + Used for configuring a Server Core installation Windows Server Download from the Microsoft Migration Tools + Use for assistance in migrating from one version of Windows Server to download center another version Volume Activation Download from the Microsoft + Use the VAMT to manage Multiple Management Tool Activation Kevs (MAKS) htps:www-sklpipe.comitireaderibook/8035340-c0'2-4850-8e60-T30DI@Sab7I4 ot download center02-09-2019 20740C- Instalation, Storage, and Compute with Windows Server 2016 | Sklpipe Tool How used Where found htps:ww.sklpipe.comitiroaderibook/8035340-c012-4850-5e60-T30DIBSab7I4 oust