Module 1 – Séance 1

Installing, upgrading, and

migrating servers and workloads

Malik Arnold GERALDO

Version Officielle de Microsoft
Modifiée pour faciliter l’explication
Module Overview
• Introducing Windows Server 2016
• Overview of Hyper-V
• Installing Hyper-V
• Configuring storage on Hyper-V host servers
• Configuring networking on Hyper-V host servers
• Configuring Hyper-V virtual machines
• Managing virtual machines
• Preparing and installing Nano Server and Server
Core
• Preparing for upgrades and migrations
• Migrating server roles and workloads
• Windows Server activation models
Lesson 1: Introducing Windows Server 2016

• Selecting a suitable Windows Server 2016 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?
Selecting a suitable Windows Server 2016 edition

Le choix de la version dépendra notamment :

• Du rôle du serveur que vous prévoyez d’installer

(Serveur DHCP, DNS, Contrôleur de domaine,
Serveur d’impression, Web)
• De la stratégie de virtualisation qui sera utilisée
(Le nombre de machines virtuelles à créer).
• Du type de licensing qui sera utilisé (License pour
les bureaux à distance, l’aspect financier, .
Selecting a suitable Windows Server 2016 edition

• 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
Selecting a suitable Windows Server 2016 edition
Selecting a suitable Windows Server 2016 edition
Selecting a suitable Windows Server 2016 edition
Discussion: selecting a suitable Windows Server
edition and installation type

Which Windows Server 2016 edition would

you choose?

10 minutes
Hardware requirements

• Windows Server 2016 has the following minimum

hardware requirements for Server Core
installation:
Hardware requirements

• The maximum capacity of Windows Server 2016

depends on the edition. The Windows Server
Datacenter edition supports up to a maximum of
the following hardware

Hardware Requirement
Processor 640 logical processors

RAM 4 TB
Nombre de 64 failover cluster
connexion nodes
Overview of installation options

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
• Nano Server—minimal server installation of either
Standard or Datacenter edition
Managing servers remotely

• 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
• Invite de commande
• Remote Desktop – Rdp et msra
• Group Policy (not supported on Nano Server)

• Firewall exceptions required for remote

management
Using Windows PowerShell 5.0 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
INTRODUCTION A POWERSHELL

• PowerShell est un langage de script développé par Microsoft

et est inclus dans toutes les versions de Windows à partir de
Windows 7 et Windows Server 2008
• Le langage PowerShell peut être utilisé directement avec
l’interpréteur de commande PowerShell, avec la console
d'édition de script "PowerShell ISE" intégrée à Windows ou
encore avec l’invite de commande Windows.
 INTRODUCTION A POWERSHELL
• Dans PowerShell, il existe quatre paramètres de stratégie d'exécution
des scripts qui sont :

Restricted: paramètre par défaut, n'autorise pas l'exécution des scripts,

AllSigned: n'exécute que les scripts de confiance, donc signés,

RemoteSigned: exécute les scripts locaux sans obligation de confiance

et les scripts de confiance issus d'Internet,

Unrestricted : autorise l'exécution de tous les scripts.

Démarrer Windows PowerShell en tant qu’administrateur, puis utiliser la

commande suivante pour définir la stratégie :

• Commande pour connaître la stratégie en cours : Get-

ExecutionPolicy

• Commande pour modifier la stratégie :

Set-ExecutionPolicy RemoteSigned
INTRODUCTION A POWERSHELL

• Interpréteur de commande PowerShell

INTRODUCTION A POWERSHELL

• Invite de commande Windows

INTRODUCTION A POWERSHELL

• Interpréteur de commande PowerShell ISE

INTRODUCTION A POWERSHELL

• Interpréteur de commande PowerShell ISE

Discussion: First script powershell

1-Copier le contenu du fichier permier

script et coller le dans ISE, puis executer le
2-Execution de second script

10 minutes
 INTRODUCTION A POWERSHELL

• Les commandes (cmdlet)

Powershell dispose d'une aide embarquée que vous pouvez
appeler par la commande « Get-Help »
Get-Help
Cette commande permet d’afficher l’aide en rapport avec une
commande en particulier
 INTRODUCTION A POWERSHELL
La liste des commandes de base est disponible via « Get-
Command ».
Get-ChildItem
Cette commande permet de lister tous les éléments contenus
dans un répertoire (équivalent à la commande "ls" sous Linux ou
"dir" sous Windows)
• d : Répertoire
• a : Archive
• r : Elément en lecture seule
• h : Elément caché
• s : Elément système
 INTRODUCTION A POWERSHELL

Set-Location<Path>
Cette commande permet de changer de répertoire (équivalent
à la commande « cd »). Pour ce faire, il suffit de mettre le
chemin que vous voulez atteindre en paramètre de la
commande, comme par exemple : « Set-Location C:\wamp »
INTRODUCTION A POWERSHELL

Set-Location
Affiche le répertoire courant :
Discussion: Commandes de base

1-Quelle commande permet d’avoir la liste

des disques
2- La liste des services

10 minutes
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 - SSD
• IPAM • Better domain
• Dynamic Access controller
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:
• Nano Server • PowerShell Direct
• Containers • Shielded virtual machines
• Docker support • Windows Defender
• Rolling upgrades for • Storage Spaces Direct
Hyper-V and storage • Storage Replica
clusters • Remote Desktop Services
• Hot add/remove virtual • Microsoft Passport
memory & network • Azure AD Join support
adapters • Privileged Access
• Nested virtualization Management
Module Overview

• Overview of Hyper-V
• Installing Hyper-V
• Configuring storage on Hyper-V host servers
• Configuring networking on Hyper-V host servers
• Configuring Hyper-V virtual machines
• Managing virtual machines
Lesson 1: Overview of Hyper-V

• What is Hyper-V?
• New Hyper-V host features in Windows Server 2016
• New Hyper-V virtual machine features in Windows
Server 2016
What is Hyper-V?

• Hyper-V is the hardware virtualization role in

Windows Server 2016
• The hypervisor controls access to hardware
• Hardware drivers are installed in the host
operating system
• Many guest operating systems are supported:
• Windows Server 2008 SP2 or newer
• Windows Vista SP2 or newer
• Linux
• FreeBSD
Lesson 2: Installing Hyper-V

• Prerequisites and requirements for installing

Hyper-V
• Demonstration: Installing the Hyper-V role
• Nested virtualization
Prerequisites and requirements for installing Hyper-V

• Use Systeminfo.exe to verify that hardware

requirements are met for Hyper-V

• You must have sufficient resources in the host

to meet the requirements of the virtual
machines:
• Processor
• Memory
• Storage
• Network
Demonstration: Installing the Hyper-V role

• In this demonstration, you will see how to

install the Hyper-V server role
Nested virtualization

• Enables a Hyper-V guest virtual machine to

also be a Hyper-V host
• Useful for development and test servers
• Requirements:
• At least 4 GB of static memory
• Windows Server 2016 or Windows 10 host operating
system
• The Hyper-V host and guest virtual machines
running Hyper-V must be the same build
• Some features are not available in the guest
virtual machine running Hyper-V
Lesson 3: Configuring storage on Hyper-V host servers

• Storage options in Hyper-V

• Considerations for virtual hard disk formats and
types
• Fibre Channel support in Hyper-V
• Where to store VHDs?
• Storing virtual machines on SMB 3.0 shares
• Demonstration: Managing storage in Hyper-V
 Module 1 – Séance 2
Installing, upgrading, and
migrating servers and workloads

Malik Arnold GERALDO

Version Officielle de Microsoft
Modifiée pour faciliter l’explication
Storage options in Hyper-V

• Virtual hard disk formats:

• .vhd
• .vhdx

• Virtual hard disk types:

• Fixed-size
• Dynamically expanding
• Pass-through
• Differencing
Considerations for virtual hard disk formats and types

• Create .vhdx virtual hard disks unless you need

backward compatibility with Windows Server 2008
or Windows Server 2008 R2
• A dynamically expanding .vhdx-formatted virtual
hard disk is suitable for production workloads
• The free space shown by dynamically expanding
virtual hard disks is not equal to physical free
space
• Multiple layers of differencing disks decreases
performance
• If you modify a parent disk, the differencing disk is
no longer valid
• You can relink a differencing disk to a parent disk
Where to store VHDs?

• Storage performance is a critical factor in

virtual machine performance
• Consider the following when planning storage
for Hyper-V:
• High-performance connectivity to storage
• Redundant storage
• High-performance storage
• Adequate growth space
Demonstration: Managing storage in Hyper-V

In this demonstration, you will see how to

create a differencing disk based on an existing
disk by using both Hyper-V Manager and
Windows PowerShell
Demonstration: Managing storage in Hyper-V

Devoir:
Créer un disque dynamique de 30 Go sous
Hyper-V
Lesson 4: Configuring networking on Hyper-V
host servers

• Types of Hyper-V networks

• Demonstration: Configuring Hyper-V networks
• Best Practices for configuring Hyper-V virtual
networks
• New Hyper-V networking features in Windows
Server 2016
Types of Hyper-V networks

• Use Virtual Switch Manager to create different

types of virtual networks:
• Externe - Bridge : Comme son nom l’indique,
ce type permet de lier le commutateur virtuel
à une carte réseau physique de votre machine
afin de communiquer avec les autres
ordinateurs du réseau. Autrement dit, toutes
les machines connectées sur ce type de
commutateur virtuel accèdent au réseau
physique comme n’importe quel hôte
physique.
Types of Hyper-V networks

• Use Virtual Switch Manager to create different

types of virtual networks:
• Interne - Nat : A l’inverse ce type de
commutateur virtuel ne permet de connecter
avec le réseau physique, on reste en interne,
c’est-à-dire que la communication sera
uniquement possible entre les machines
virtuelles connectées à ce type de switch.
Toutefois, la machine faisant office de
serveur Hyper-V sera la seule machine
physique à pouvoir communiquer avec les
VM d’un commutateur virtuel interne.
Types of Hyper-V networks

• Use Virtual Switch Manager to create different

types of virtual networks:
• Privé : Reprend le même principe que pour le
type « interne » sauf que là la
communication avec l’hôte physique jouant
le rôle de serveur Hyper-V n’est pas possible.
La communication est donc exclusivement
inter-VM.

Source: https://www.it-connect.fr/
Demonstration: Configuring Hyper-V networks

• In this demonstration, you will see how to

create an external, internal and a private
network switch
Lesson 5: Configuring Hyper-V virtual machines

• What are virtual machine configuration versions?

• Virtual machine generation versions
• Demonstration: Creating a virtual machine
• The Hot Adding feature in Hyper-V
• Shielded virtual machines
• Virtual machine settings
• Best practices for configuring virtual machines
Virtual machine generation versions

Generation 2 virtual machines provide the

following functionality:
• Secure boot
• Boot from a virtual hard disk that is connected to a
virtual SCSI controller
• Boot from a virtual DVD that is connected to a
virtual SCSI controller
• PXE boot by using a standard Hyper-V network
adapter
• UEFI firmware support
The Hot Adding feature in Hyper-V

• Hot adding requires Generation 2 virtual

machines
• Memory:
• Add memory to virtual machines with static memory
while they are running
• Network adapter:
• Add or remove network adapters to virtual machines
while they are running
Lesson 6: Managing virtual machines

• Managing virtual machine state

• Managing checkpoints
• Demonstration: Creating checkpoints
• Importing and exporting virtual machines
• Windows PowerShell Direct
• Demonstration: Using Windows PowerShell Direct
Managing virtual machine state

Virtual machine states define what resources are

being used:
• Off: virtual machine that is off does not use
any memory or processing resources.
• Starting: A virtual machine that is starting
• verifies that resources are available before
allocating those resources.
• Running:
Managing virtual machine state

Virtual machine states define what resources are

being used:
• Paused: A paused virtual machine does not
consume any processing capacity but does still
retain the memory that has been allocated to it
• Saved: A saved virtual machine does not consume
any memory or processing resources. The memory
state for the virtual machine is saved as a file and
is read when the virtual machine is started again.
Managing checkpoints

• Checkpoints allow administrators to make a

snapshot of a virtual machine at a particular
point in time
• Checkpoints do not replace backups
• Standard checkpoints create differencing disks,
.avhd files, which merge back into the previous
checkpoint when the checkpoint is deleted
• Production checkpoints are created by using
VSS and require starting from an offline state
Demonstration: Creating checkpoints

• In this demonstration, you will see how to

create a production checkpoint and a standard
checkpoint in Hyper-V Manager
Importing and exporting virtual machines
• Import options:
• Register the virtual machine in-place (use the existing unique
ID)
• Restore the virtual machine (use the existing unique ID)
• Copy the virtual machine (create a new unique ID)
• Export options:
• Export a checkpoint
• Export a virtual machine including checkpoints
• Moving virtual machine storage:
• Move all the virtual machine’s data to a single location
• Move the virtual machine’s data to different locations
• Move the virtual machine’s virtual hard disks
Demonstration: Using Windows PowerShell Direct

• In this demonstration, you will see how to use

Windows PowerShell Direct
Overview of installation options

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
• Nano Server—minimal server installation of either
Standard or Datacenter edition
What is Nano Server?

Nano Server is ideal for use in the following

scenarios:
• Compute host for Hyper-V virtual machines, either in
clusters or not
• Storage host for a scale-out file server
• DNS server
• Web server running IIS
• Host for apps that are developed by using cloud
application patterns and run in a container or virtual
machine
Managing and configuring Nano Server
Overview of installing Nano Server

• Setup files for the Nano Server in \NanoServer

folder on installation media ( Récupérer le
dossier Nanoserver dans le dossier image de
windows server 2016)
• Can deploy as: (Création de disque du serveur
Nano selon l’hôte)
• A VHD on a Hyper-V host
• A VMDK on Vmware/VirtualBox
• A VHD bootable drive on a physical computer
• A .wim file on a physical computer

• Create images using Windows Power Shell

(Création de l’image sur le disque)
TP: Installation d’un Serveur Nano 2016

Devoir de maison

10 minutes
• Administration du serveur Nano
• Post install et administration d’un serveur Core
• Post install et découverte du Desktop Experience
Administration du serveur Nano

• New-NanoServerImage -MediaPath D:\ -Edition

Standard -DeploymentType Guest -TargetPath
C:\NanoServer\VirtualDIsk\disknano.vhdx
-ComputerName ESGIS-NanoServer -storage
-Package Microsoft-NanoServer-IIS-
Package,Microsoft-NanoServer-Host-Package
-AdministratorPassword (ConvertTo-SecureString -
String "password" -AsPlainText -Force)
Administration du serveur Nano
 Administration du serveur Nano
• Adressage du serveur Nano
 Administration du serveur Nano
• Adressage du serveur Nano
 Administration du serveur Nano
• Adressage du serveur Nano
Discussion: selecting a suitable Windows Server
edition and installation type
Donnez l’adresse:
192.168.2.1 /24
Passerelle ou Gateway: 192.168.2.254
Dns primaire: 8.8.8.8
Dns secondaire: 4.4.4.2

10 minutes
Discussion: selecting a suitable Windows Server
edition and installation type
Donnez l’adresse: Choisissez un
commutateur interne et faites une
adressage automatique sur le Nano.
Depuis votre machine hote, faites un ping
vers le Nano

10 minutes
 Administration du serveur Nano
• Adressage du serveur Nano
 Administration du serveur Nano
• Adressage du serveur Nano
 Administration du serveur Nano
• Adressage du serveur Nano
 Administration du serveur Nano
• Adressage du serveur Nano
Discussion: selecting a suitable Windows Server
edition and installation type
Administrer Nano depuis la machine hote :
Sur la machine hote saisissez la commande
suivante:
- net start winrm
- Set-Item
WSMan:\localhost\Client\TrustedHosts -
Value “address ip nano”
- Se connecter à la machine nano via
powershell
Enter-PSSession -ComputerName address ip
nano -Credential Administrator ( ou
Administrateur )
- Renommer la machine Nano et verifier
l’effectivité sur le Nano
Post install et administration d’un serveur Core

• La commande sconfig permet de personnaliser le

serveur Core.
• Administration: comme server Nano
Post install et administration d’un serveur Core

• Les différents roles disponibles sur Server Core

Post install et découverte du Desktop Experience

• Tableau de bords (Gestionnaire de serveur)

• Personnalisation dans Serveur local (Gestionnaire
de serveur)
• Service de fichier et de stockage (Gestionnaire de
serveur)
• La notion de role: overview sur quelques rôles,
l’installation et le remove.
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 2016
• The default installation option for Windows
Server 20160
• Managed locally by using Windows PowerShell and
other standard tools
• With remote management enabled, you rarely
need to sign in locally
Comparing Server Core with Nano Server and a
full installation

Factors to consider when comparing Nano Server,

Core Server, and Server with Desktop Experience:
• Ease of installation
• Ease of local and remote management
• Hardware resource requirements
• Current application requirements
• Frequency of patches, updates, and uptime
requirements
• Security requirements/attack surface
• Roles/features required now and the possible need to
update them later
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 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
Lesson 3: Preparing for upgrades and migrations

• In-place upgrades vs. server migration

• In-place upgrade scenarios
• Benefits of migrating to Windows Server 2016
• Using solution accelerators
• Recommendations 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
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 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
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
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
Windows Server 2016 licensing and activation

Activation strategy When used

Manual OEM keys
Automatic Key Management Services (KMS)
Volume Activation Services server
role
Active Directory-Based Activation
Volume Activation Tools console
Volume Activation Management
Tool (VAMT)
Multiple Activation Key (MAK)
Automatic Virtual Machine
Activation (AVMA)
Discussion: Planning volume activation

Discuss both scenarios. Based on the scenario,

what type of volume activation should you
implement?
WEBOGRAPHIE

• https://www.developpez.com/actu/40433/Window
s-8-Storage-Spaces-permet-la-gestion-du-
stockage-virtualise-la-mise-en-miroir-et-la-
recuperation-apres-crash/
• Comprendre et Choisir Windows Server |
TechSoup Canada
• Introduction à PowerShell | Powershell | IT-
Connect (it-connect.fr)
• https://pixelabs.fr/administration-nano-server-
2016/