M55341A

Module 1
Installing, upgrading, and
migrating servers and
workloads
 Introducing Windows Server
Module Preparing and installing Server Core
Overview Preparing for upgrades and migrations
Migrating server roles and workloads
• Windows Server activation models
Lesson 1: Introducing Windows Server

Selecting a suitable Windows Server edition

Hardware requirements
Overview of installation options
Managing servers remotely
Using Windows PowerShell 5.0 to manage servers
What’s new since Windows Server 2008 was released?
• Windows Server Servicing Channels
Selecting a suitable Windows Server edition

• Windows Server Essentials

• Windows Server Standard
• Windows Server Datacenter
• Microsoft Hyper-V Server
Hardware requirements

Windows Server has the following minimum hardware requirements

for Server Core installation:

Component Requirement

Processor architecture 64 bit

Processor speed 1.4 gigahertz (GHz)

RAM 512 MB

Hard drive space 32 GB

Overview of installation options
You can choose among the following
installation options when deploying
Windows Server :

• Windows Server (Desktop Experience) - full

server installation
• Windows Server - Server Core installation
• Windows and Hyper-V containers can run
on a Desktop Experience or Server Core of
Windows Server, and provide further
application isolation
Managing servers remotely

Use the following options to remotely manage a computer that is running Windows
Server :

• 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)
• Windows Admin Center

Firewall exceptions may be required for remote management

Using Windows PowerShell 5.1 to manage servers

Windows PowerShell is a scripting language and command-line interface that is

designed to assist you in performing day-to-day administrative tasks
Using Windows PowerShell 7 to manage servers

PowerShell 7.x is an open-source, cross-platform (Windows, macOS, and Linux)

edition of PowerShell, built to manage heterogeneous environments and hybrid
cloud.
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
What’s new since Windows Server 2012 was released?

New features and improvements introduced in Windows Server 2016:

• Containers • PowerShell Direct

• Docker support • Shielded virtual machines
• Rolling upgrades for Hyper- • Windows Defender
V and storage clusters • Storage Spaces Direct
• Hot add/remove virtual • Storage Replica
memory & network adapters • Remote Desktop Services
• Nested virtualization • Microsoft Passport
• Azure AD Join support
• Privileged Access
Management
What’s new since Windows Server 2016 was released?

New features and improvements introduced in Windows Server 2019:

• Windows Admin Center • Encrypted Networks

• Windows Defender (ATP) • Network performance
• System Insights improvements
• HTTP/2
• Storage Migration Service
• Storage Replica
• Linux containers on
Windows
• Kubernetes
What’s new since Windows Server 2019 was released?

New features and improvements introduced in Windows Server 2022:

• Secured-core server • Nested virtualization for

• Hardware root-of-trust AMD processors
• System Insights • Microsoft Edge
• Firmware protection • UDP/TCP Improvements
• Virtualization-based security • Storage bus cache
(VBS) • SMB compression
• Secure DNS
• SMB AES-256 encryption
• SMB Direct
• SMB over QUIC
Windows Server Servicing Channels
Select a servicing channel

Recommendations:

Long-Term Servicing Channel Semi-Annual Channel

General purpose file servers. Containerized applications.

Microsoft and non-Microsoft workloads. Container hosts.

Application scenarios benefiting from adaption of new

Traditional apps.
features.

Infrastructure roles.

Software-defined Datacenter.

Hyper-converged infrastructure.
Lesson 2: Preparing and installing Server Core

Planning for Server Core

Installing Server Core and Server with Desktop Experience
Post-installation configuration settings
Discussion: selecting a suitable Windows Server edition and installation type
• Demonstration: Installing Server Core
Planning for Server Core
• 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
• The default installation option for Windows
Server
• Managed locally by using Windows PowerShell
and other standard tools

• With remote management enabled, you

rarely need to sign in locally
Installing Server Core and Server with Desktop Experience

1. Perform preinstallation tasks:

• Disconnect UPS
• Back up server if applicable
• Disable antivirus software
2. Run the Windows Setup Wizard from
the installation media:
1. Provide locale information (language, date,
currency, keyboard)
2. Select Server Core Installation
3. Review and accept license
4. Select installation location
5. Provide administrator password
Post-installation configuration settings

After you install Windows Server , 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
Sconfig.cmd interface screen
Discussion:
selecting a
suitable
Which Windows Server installation option
Windows
would you select?
Server edition
and installation
type
Demonstration:
Installing Server
Core

In this demonstration, you will see how to install Server Core

Lesson 3: Preparing for upgrades and migrations

In-place upgrades vs. server migration

In-place upgrade scenarios
Benefits of migrating to Windows Server
Using solution accelerators
Recommendations for server consolidation
• Demonstration: Using MAP
In-place upgrades vs. server migration

• Upgrading to Windows Server:

• Not every older operating system has a pathway to every
newer one.
• Can only upgrade to same or newer editions
• Requires same processor architecture

• Migrating to Windows Server :

• Must migrate from x86 version of Windows Server
• Can use the Windows Server Migration Tools feature
In-place upgrades vs. server migration
In-place upgrade scenarios

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
Benefits of migrating to Windows Server

When you perform a migration, you:

• Do not affect your current Windows Server 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
Using solution accelerators
• Use Microsoft Deployment Toolkit (MDT) to:
• Automate deployments of Windows Server or other Windows operating systems
• Use MAP Toolkit for Windows Server to:
• Perform inventory of your organization’s IT infrastructure
• Generate a report or proposal based on the Windows Server Readiness Assessment to plan server
consolidation
• Use Windows Server Migration Tools to:
• Migrate server roles, features, operating system settings, data, and shares
Recommendations for server consolidation

• 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
Demonstration: Using MAP

In this demonstration you will see how to:

• Review MAP options

• Perform an inventory assessment
• Review inventory from a sample database
Lesson 4: Migrating server roles and workloads

Migrating server roles within a domain

• Migrating server roles across domains or forests
Migrating server roles within a domain

The roles that you can migrate from supported earlier editions of Windows
Server to Windows Server include:

• AD FS Role Services
• Hyper-V
• DHCP
• DNS
• Network Policy Server
• Print and Document Services
• Remote Access
• WSUS
Migrating server roles across domains or forests

When migrating serves across domains:

• Create a new Windows Server 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
Lesson 5: Windows Server activation models

Windows Server licensing and activation

• Discussion: Planning volume activation
Windows Server 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

Discussion:
Planning Discuss both scenarios. Based on the scenario,
volume what type of volume activation should you
activation implement?
Lab: Installing and configuring Server Core
Lab 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 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-SVR6, 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

Exercise 1: Exercise 2: Exercise 3:

Installing Server Core Completing post- Performing remote
installation tasks on management
Windows Server
Core
 In the lab, you used the Install-WindowsFeature cmdlet in
Lab Review Windows PowerShell to install the DNS Server role on
LON-SVR6. How could you do this remotely?
 Review Questions
Module Review
and Takeaways Tools
• Common Issues and Troubleshooting Tips
End of presentation