Installation, Storage, and

Compute with Windows

Server 2016
Agenda - list all main modules
01-Install Windows Servers in host and 04-Implement Windows containers (5–
compute environments (10–15%) 10%)

02-Implement storage solutions (10–15%) 05-Implement high availability (30–35%)

06-Maintain and monitor server

03-Implement Hyper-V (20–25%)
environments (10–15%)
01-Install Windows Servers
in host and compute
environments
Install, upgrade, and mitigate servers and workloads
Windows Server 2016 OS Editions
Edition
Windows Server 2016 Essentials
Windows Server 2016 Standard Edition
Windows Server 2016 Datacenter Edition
Microsoft Hyper-V Server 2016
Windows Storage Server 2016 – Workgroup Edition
Windows Storage Server 2016 – Standard Edition
Purpose
Designed for small businesses
Designed for physical server environments with
little to no virtualization
Designed for highly virtualized environments –
including cloud and hybrid cloud environments
Acts as a stand-alone virtualization server for
virtual machines
Allows 50 users, one processor core, and 32 GB
of RAM. Supports domain joining
Supports up to 64 sockets but is licensed on a
two-socket, incrementing basis
Windows Server 2016 Installation Requirements

Component Requirement
Processor architecture 64-bit
Processor speed 1.4 gigahertz (GHz)
RAM 512 MB
Hard drive space 32 GB
*Server Datacenter supports 640 lCPU, 4Tb RAM, and 64 nodes

(1) Allocate > 800 MB RAM or

(2a) Use Diskpart.exe create a partition
(2b) Run createpagefile command

• UEFI 2.3.1c for Secure Boot

Windows Server 2016 Installation Requirements

• Clean Installation
• Upgrade
• Migration

• Standard & Datacenter

• Desktop Experience = GUI

• Datacenter, Standard, Essentials, Multipoint

Premium Server,
• Storage Server, Hyper-V Server
What is a Nano Server
Nano Server: A new headless, 64-bit only,
deployment option for Windows Server
• Deep refactoring with cloud emphasis

• Extend the Server Core pattern

Install and configure Nano Server
Nano Server Installation Options
Description: Super Small Footprint
Install options: Physical Host, VM Guest, Container OS
Roles Supported:
• Hyper-V
• Scale-out File Server
• DNS Server
• Failover Clustering
• IIS (subset)
• IIS.NET Core
• ASP.NET Core can be installed
Getting started
Nano Server Roles and Features
• Nano Server folder has a Packages sub-folder
Role or feature
Hyper-V role
Failover Clustering
File Server role and other storage components
Windows Defender Antimalware, including a default signature file
Reverse forwarders for application compatibility, for example
common application frameworks such as Ruby, Node.js, etc.
Package file
Microsoft-NanoServer-Compute-Package.cab
Microsoft-NanoServer-FailoverCluster-Package.cab
Microsoft-NanoServer-Storage-Package.cab
Microsoft-NanoServer-Defender-Package.cab
Microsoft-OneCore-ReverseForwarders-Package.cab

• Dism /Add-Package
/PackagePath:.\packages\<package>
• Dism /Add-Package /PackagePath:.\packages\en-
us\<package>
Installing Roles/Features from the Package Repository
• Nano Server roles and features are
available on the media and from a package
repository
• NanoServerPackage provider for the
PackageManagement PowerShell module

• You can then search for, download, and

install Nano Server roles and features from
the repository
Convert WIM to VHD
On Windows 10 or Windows Server 2016, mount the ISO, and, assuming the drive letter for the mounted image
1 is D:\, run the following:
Copy "D:\NanoServer" "C:\NanoServer" -Recurse
Generate a VHD from NanoServer.wim by using Convert-WindowsImage.ps1 from TechNet Script Center.
2 C:\
Cd \NanoServer
. .\Convert-WindowsImage.ps1
Convert-WindowsImage –SourcePath C:\NanoServer\NanoServer.wim –VHDPath
C:\NanoServer\NanoServer.vhd –VHDFormat VHD -Edition CORESYSTEMSERVER_INSTALL
Optional Nano Customizations
Can be used to further specialize Nano Server for your environment
Remotely Managing Nano Server
Remote Graphical PowerShell VM and Container Deployment & Partners &
& Web Tools Remoting Management Monitoring Frameworks
• Server Manager • Core PowerShell • Hyper-V Manager • DISM online & • Chef integration
• Azure Portal tools engine, language, • Hyper-V cmdlets VHD support • .NET Core and
• Task manager and cmdlets* • PowerShell Direct • Unattended setup CoreCLR
• Registry editor • Windows Server over PSRP • Visual Studio • ASP.NET 5
cmdlets (network, • CimSession integration • Python, PHP,
• File explorer
storage, etc.) support • DSC Local Config Ruby, Node.js
• Server
• PowerShell DSC • Docker Manager • PowerShell
configuration
• Remote file • SCVMM agent & • Setup & boot Classes
• Event viewer
transfer console eventing • PS Script Analyzer
• Disk manager
• Remote script • 3rd party agents • SCOM agent • PowerShell
• Device & driver authoring &
management & consoles • VSO App Insights Gallery
debugging
• Performance • Azure Op Insights • PowerShellGet
• PowerShell Web
• Users & groups Access
 Server management tools
Web-based
Includes replacements for
local-only tools
• Task Manager
• Registry Editor
• Event Viewer
• Device Manager
• Sconfig
• Control Panel
• Performance Monitor
• Disk Management
• Users/Groups Manager
• File Explorer

Also manages Server Core

and Server with GUI
Create, manage, and maintain images for deployment
Planning for Windows Server
Virtualization

• Which servers will be virtualized

• Existing servers or new servers only

• Many workloads can be virtualized, but some can’t

(custom vendor apps, for example)
• Use MAP (Microsoft Assessment and Planning) to
scan those that can be virtualized to design the
host and guest infrastructure

• Backup and fault tolerance for hosts and for guest

VMs
Plan for Virtualization: Using MAP Toolkit
• Solutions Accelerator used to scan networks
and servers, for operating systems, hardware
and software inventory, Hyper-V and VMWare
guests and hosts, etc…

• Discovery
• Hardware and software inventory
• Virtual Server Consolidation Wizard
• Private Cloud Fast-track Wizard
Planning for Linux and FreeBSD Deployments
• Both emulation and running within Hyper-V are supported scenarios
• Hyper-V offers better performance
• With Hyper-V you need Hyper-V specific drivers

• Linux Integration Services is added to the Linux kernel (newer versions), provides these drivers, and
is updated with new Linux releases
• FreeBSD Integration Services provides these drivers and is built into newer FreeBSD builds
• For older versions of either, download the latest available

https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/supported-
linux-and-freebsd-virtual-machines-for-hyper-v-on-windows
Updating Images – Patches, Hotfixes, Drivers, Roles
• Sector-based images require you to install the image, update it, re-capture
• File-based images can be updated offline

• Windows setup: include an answer file with setup to install updated drivers, patches, etc…
• Online servicing: like sector-based, this requires installing the image to a reference computer,
updating it, and re-capturing the OS
• Offline servicing: use DISM to mount the image, update the drivers, or install hotfixes, language
packs, or add/remove folders

• Installing applications via .exe or .msi files

• Installing a feature or component that requires a running Windows service, such as .NET Framework
Practice Question

A. Install-NanoServerPackage Microsoft-NanoServer-DCB-Package
B. Install-NanoServerPackage Microsoft-NanoServer-Host-Package
C. Install-NanoServerPackage Microsoft-NanoServer-Guest-Package
D. Install-NanoServerPackage -Compute

https://technet.microsoft.com/en-us/windows-server-docs/compute/nano-server/getting-started-with-nano-server
Installing Windows Server

Setup.exe includes
Server Core (default) or
with GUI (desktop
experience)
02-Implement storage
solutions
Configure disks and volumes
Determine the Partition Table Format
• Standard partition table format since early
1980s
• Supports a maximum of four primary
partitions per drive
• Can Partition a disk up to 2 TB

• Successor of the MBR Partition table format

• Supports a maximum of 128 partitions per
drive
• Can partition a disk up to 18 exabytes

Reference Link on GPT disks - https://support.microsoft.com/en-us/kb/302873

When to use NTFS and ReFS file systems
• Basic file system
• Partition size limitations
• FAT32 to enable larger disks
• exFAT developed for flash drives

• Metadata
• Auditing and journaling
• Security (ACLs and encryption)

• Backward compatibility support for NTFS

• Enhanced data verification and error correction
• Support for larger files, directories and volumes
Virtual Hard Disks
• Hyper-V, VHD boot, virtualized storage
for storage spaces, iSCSI storage

• Disks up to 2TB. Format backwardly

compatible
• Compatible with Azure VMs

• Used in WS2012+
• Sizes > 2TB
• Can be used for shared storage for VMs
Disk management tools
Tool Purpose
Server Manager Create volumes, storage spaces, shares, disk deduplication
Disk Management Simple tool, lacks features but OK for basic tasks

Diskpart Command-line tool, useful for scripting

PowerShell +150 cmdlets for storage

Useful for scripting, and for managing Server Core

Exam Tip: Know the limitations/features of each. E.g. which tool(s) can create a storage space?
Implement server storage
Storage Pools
1. Add disks (any type) to a pool
2. Create virtual disks using the pool
3. Virtual disks can be thin provisioned or
use physical space
4. Create volumes and format

• Local storage on 3+ nodes

• Networked nodes present JBOD/SAS
storage to the pool.
• The pool can be configured as a CSV for
applications.
• Primary use-case: Hyper-V VM
storage
Disk Layouts

• Simple – data is striped across disks, no

resilience
• 2 way mirror – 2 disks, protects against 1 drive
failing
• 3 way mirror – 5 disks, protects against 2 drives
failing
• Parity – 3 disks min to protect against 1 drive
failing or 7 min to protect against 2 drives failing
iSCSI Components
• Used to connect to iSCSI targets on the network
• Can use IP/FQDN/iSNS to locate targets
• Remote disks appear as ‘local’ disks in disk tools

• Installable role service part of the file server role

• Presents storage to networked initiators
• Secured access using IP white-list and authentication
• Uses standard TCP/IP components and commodity Ethernet to
access storage
• Cheaper than a fiber-channel SAN
• Low-cost software based shared storage solution
Storage Replica

• Stretch cluster
• Server-to-server
• Cluster-to-cluster
Implement Data Deduplication
Configuring
Deduplication
Practice Question

A. Simple storage layout with 7 physical drives

B. Mirror layout with 5 disks
C. Parity layout with 5 disks
D. Parity layout with 4 disks
03-Implement Hyper-V
Install and configure Hyper-V
Hyper-V requirements

• 64-bit CPU with SLAT

• VM Monitor mode extensions • GUI mode
• Virtualization support on in BIOS/UEFI • Server Core
• Nano server

• Enough RAM for workloads

• Windows Vista – Windows 10
• Windows Server 2008 – WS2016
• Linux
• FreeBSD
Virtual Machine Management

• Hyper-V Manager
• PowerShell
• RSAT tools

• Uses PowerShell
remoting to a VM where
you would not have
network access to
normally
Nested virtualization

• Host running WS2016 Hyper-V

• VM running WS2016 or Windows 10 anniversary update
• A Hyper-V VM with configuration version 8.0 or greater
• An Intel processor with VT-x and EPT technology

To configure:
1. Create a virtual machine
2. While the virtual machine is in the OFF state, run the following on the Hyper-V host to enable nested virtualization

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

3. Start the virtual machine

4. Install Hyper-V within the virtual machine, just like you would for a physical server
Configure virtual machine (VM) settings
VM Settings
Gen1 & Gen2 Support

• Secure boot
• Disks - must boot from IDE disk in Gen1
• No IDE disks in Gen2
• Legacy NIC Gen1 only (allows PXE)
• BIOS vs Firmware
• Gen2 is for WS2012+ guest OS
• TPM in Gen2
• Shielded VMs possible with new hardware presented
Configure Hyper-V storage
Types of disk
Formats
VHD
• Classic format. Backward compatible
VHDX
• Larger disk size beyond 2TB (64TB)
Pass-through
• Uses physical disks from host exclusively

Types
Fixed
• Uses physical space from day 1 equal to disk size
Dynamically expanding
• Space is consumed on demand up to max disk
size
Differencing
• Disk chains allow parent-child disk relationships
for speed of deployment
Shared VHDX files
Configure Hyper-V networking
Add and remove virtual network interface cards (vNICs)
• Used in Gen1 VMs
• Limited bandwidth 100Mbps

• Gen1 and Gen2 support

• 10 Mbps connections

• Legacy network adapter only in Gen1 VMs

• Native support in Gen2 Network adapters
Configure Hyper-V virtual switches, optimize network
performance

• Uses physical NIC in host to allow LAN/Internet

connectivity.
• VM NIC must use IP address relevant to physical subnet

• Connectivity between VMs and host only on the same

switch

• Connectivity between VMs only on the same switch

Bandwidth Management
New-VMSwitch -Name “NATSwitch” -SwitchType NAT - VLAN ID
NATSubnetAddress 172.16.1.0/24 SR-IOV
VMQ
NIC teaming

• Combine network adapters into a team with up to 8 network adapters

• All of the network adapters in a team must be identical with the same firmware version and driver. SET is automatically
enabled when multiple network adapters are used
Configure NIC settings
• Configurable on host, always starts 00-15-5D

• Know when you would – NLB, Nested VMs

• If a VM uses NLB or similar services that use a common MAC

address

• Protects leakage of packets from a VM acting as a DHCP server

• Suppresses router advertisements from VMs configured as routers

Practice Question

VM Name Installation VM Configuration version Network configuration

type
Server1 Server with GUI 7.0 Internal network switch
Server2 Server Core 8.0 External network switch
Server3 Nano Server 8.0 NAT switch
Server4 Server Core 8.0 MAC address spoofing configured

A. Server1 and Server2

B. Server2 and Server3
C. Server1 and Server3
D. Server3 and Server4
https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/user_guide/nesting
Hyper-V Networking

SR-IOV
VMQ
NIC Teaming
04-Implement Windows
containers
Deploy Windows containers
What is a container?
Containers = Operating system virtualization Windows Server containers
Maximum speed and density
Container Container Container

Container Container Container

Applications

Kernel

Traditional virtual machines = hardware virtualization Hyper-V containers

Isolation plus performance
Container Container Container
VM VM VM
Containers overview

• Provide app isolation through process and

namespace isolation technology
• Containers share the OS kernel with the
host
• Provides fast startup experience
• Does not provide complete isolation of the
containers
• Host can run on GUI/Core/Nano

• Each container runs in a virtual machine

(VM).
• The OS kernel of the container host does
not share with the Hyper-V containers.
• Can use nested virtualization (see Hyper-V
section)
• Requires Intel VT-x extensions (only)
Installing support
Docker Containers
Native support for the Docker in-host daemon.

Docker.exe
• Docker engine that sits on Windows Server 2016
• Can be installed on WS2016 or Nano Server
• Configured with c:\ProgramData\docker\config\daemon.json

DockerD.exe
• Used to register Docker as a Windows service
• c:\Windows\System32\dockerd.exe –-register-service
• Start-Service Docker

Download Docker from https://aka.ms/tp5/dockerd

Installation steps (too many to write!)
Manage Windows containers
Managing Containers
• Network switches
• NAT switches
Practice Question

A. Create a Generation 2 Virtual Machine

B. Create a Nano Server instance
C. Create a Windows Server Container
D. Create a Hyper-V Container
Containers

New feature!
05-Implement high
availability
Implement high availability and disaster recovery
options in Hyper-V
Implementing High Availability (HA)
• High availability
• Continuous availability
• Business continuity
• Disaster recovery

• Configure Hyper-V replica and Hyper-V movement in clustered environment

• Fail-over clustering
• Storage spaces direct (SSD)
• Network Load Balancing (NLB)
High Availability with Hyper-V
Option Details
• Host clustering Host clustering • VM’s are highly available
• Guest clustering • Applications in guest do not need to
be cluster aware
• Network load balancing
Guest Clustering • VM are failover cluster nodes
• VM applications must be cluster-
• Move VMs between physical hosts without aware
shutting down first • Requires iSCSI or Fibre Channel
• Clustered non-clustered interface
NLB • Virtual machines are NLB cluster
nodes
• Used for web-based applications
Implement failover clustering
Implementing Failover Clustering
• A cluster is a group of computers or storage devices that work together as a single organized system
• A Failover Cluster is a group of independent computers that work together to increase the availability
of applications or services

• Each node has full connectivity and communication with all other nodes and is aware when another
node leaves or joins the cluster
• Each node is connected to a network where client computers can access the cluster and through
iSCSI connection to shared storage
• Each node is aware of the services or applications that are running locally and the resources running
on the other nodes in the cluster

• Cluster Operating System Rolling Upgrade

 Failover Clustering – Terminology and Types

Term Description Node Location Description

Node A Windows Server 2016 computer that is part of a failover cluster, and Single Site All nodes located in a single data center
has the failover clustering feature installed. Multi-site Stretch-clusters deployed, where nodes are spread across datacenters.
Service or A service that can be moved between cluster nodes (for example, a This may include brick and mortor or Azure
application clustered file server can run on either node).
Shared storage External storage that is accessible to all cluster nodes.
Quorum The number of elements that must be online for a cluster to continue
to run. The quorum is determined when cluster nodes vote.
Witness A server that is participating in cluster voting when the number of
nodes is even.
Failover The process of moving cluster resources from the first node to the
second node, as a result of node failure or administrator’s action.
Failback The process of moving cluster resources back from the second node Cluster type Description
to the first node, as a result of the first node going online again or an Active-Active Multiple nodes run cluster application resources and accept client
administrator’s action. If the service or application fails over from connections
Node1 to Node2, when Node1 is again available, the service or Active-Passive One node runs the cluster applications, while the other nodes are
application will fail back to Node1. passive and do not accept client connections. If the active node fails,
Clients Computers that connect to the failover cluster and are not aware one or more of the remaining nodes become active and accept client
which node the service is running on. connections
The Software-Defined Datacenter—Drilling Down
Compute Cluster
• Virtualized workloads generate I/O
to the connected file shares
• Typically additional I/O from replication
and backup operations

Scale-Out File Server Cluster

• The storage head node, which connects clients to the
underlying storage
• SOFS & Clustering provide continuous availability,
while SDS provides fault-tolerant storage using
commodity JBODs and disks

Physical Storage
SSD SSD SSD • Shared SAS Disk Enclosures w/ bunch
of HDDs and SSDs
• Each SOFS node is physically connected
to each JBOD through SAS cables
Storage choice: Traditional SAN or Microsoft SDS
Shared Storage Options for Failover Clustering
• Lowest-cost option

• Transmits SCSI commands over IP Networks. Inexpensive, Acceptable Performance

• Better performance than iSCSI SANs, but more expensive

• Use Shared VHDs as VM guest-clustering storage. Use CSV or SOFS cluster

• Utilizes shared Server Message Block (SMB) as the shared location for some failover cluster roles
Creating a Failover Cluster
Failover Clustering: In-Box Management
Some workflow PowerShell only Full provisioning and management

Intended for smaller scale

Storage Replica: Protection of key data and workloads

• Storage agnostic mirroring of data in physical sites with crash-

consistent volumes ensuring zero data loss at the volume level

• Unlocks new scenarios for metro-distance cluster-to-cluster

disaster recovery and stretch failover clusters for automated
high availability

• End-to-end for storage and clustering, including Hyper-V,

Storage Replica, storage spaces, cluster, Scale-Out File Server,
SMB3, deduplication, Resilient File System (ReFS), NTFS, and
Windows PowerShell

• Graphical management for individual nodes and clusters

through Failover Cluster Manager and Azure Site Recovery
Implement Storage Spaces Direct
Windows Server 2016: new architecture

• Build Windows Server cluster

• Enable Storage Spaces Direct
• Create storage pool
• Create Storage Spaces from pool
• Create Scale-Out File Server
• Create Continuously Available file shares
on the Spaces
• Optimize for Storage Spaces Direct
Storage Spaces Direct

Cloud design points and management

• Standard servers with local storage
• New device types such as SATA and NVMe SSD
• Prescriptive hardware configurations
• Deploy, manage, and monitor with SC VMM,
OpsMgr, and PS
Reliability, scalability, flexibility
• Fault tolerance to disk, enclosure, node failures
• Scale pools to large number of drives
• Simple and fine grained expansion
• Fast VM creation and efficient VM snapshots
Use cases
• Hyper-V IaaS storage
• Storage for backup and replication targets
• Hyper-converged (compute and storage together)
• Converged (compute and storage separate)
Windows Server 2016: new architecture

• Build Hyper-V cluster

• Enable Storage Spaces Direct
• Create storage pool
• Create Storage Spaces from pool
• Create Cluster Shared Volumes
• Optimize for Storage Spaces Direct
Manage failover clustering
Failover clustering

VM compute resiliency
• Provides resiliency to transient failures such as a temporary network
outage, or a non-responding node
• In the event of node isolation, VMs will continue to run, even if a node
falls out of cluster membership
• This is configurable based on your requirements – default set to 4
minutes.
VM storage resiliency
• Preserves tenant virtual machine session state in the event of transient
storage disruption
• VM stack is quickly and intelligently notified on failure
of the underlying block or file based storage infrastructure
• VM is quickly moved to a PausedCritical state
• VM waits for storage to recover and session state retained on recovery
Failover clustering

Node quarantine
• Unhealthy nodes are quarantined and are no longer allowed to
join the cluster
• This capability prevents unhealthy nodes from negatively affecting
other nodes and the overall cluster
• Node is quarantined if it unexpectedly leaves
the cluster three times within an hour
• Once a node is placed in quarantine, VMs
are live migrated from the cluster node,
without downtime to the VM
Guest clustering with Shared VHDX

Flexible and secure

• Shared VHDX removes need to present the physical
underlying storage to a guest OS
• NEW Shared VHDX supports online resize
Streamlined VM shared storage
• Shared VHDX files can be presented to multiple VMs
simultaneously, as shared storage
• The VM sees shared virtual SAS disk that it can use for
clustering at the guest OS and application level
• Utilizes SCSI-3 persistent reservations
• Shared VHDX can reside on a Cluster Shared Volume
(CSV) on block storage, or on SMB
file-based storage
NEW Protected
• Shared VHDX supports
Hyper-V Replica and host-level backup
Manage VM movement in clustered nodes
Perform a Live Migration
• The Failover Cluster Management console
• The VMM Admin Console
• WMI for Windows PowerShell Script

1. Migration Setup • Machines placed in

2. Guest-memory transfer saved state
3. State transfer • Causes downtime
4. Cleanup

Exam Tip: In Windows Server 2016, you can perform a virtual machine Live Migration by using server
message block (SMB) 3.0 as a transport.
Moving VMs in clustered nodes (comparison)
• VM is placed in saved state causing downtime while memory is copied

• Migrate VMs without any downtime, also Shared Nothing Live Migration is possible

• Migrate VM storage to the same host, another host, or an SMB share

• A very time consuming procedure. But much simpler to import with Server 2016
Understand Network Health Protection

• Protected Network setting is enabled for all virtual network adapters.

• Save the virtual machine state • Failover cluster placed in pause state
• Turn off the virtual machine • If Server 2008 or Earlier > Quick Migration
• Shutdown the quest operating system • If Server 2012 or later > Live Migration
Implement Network Load Balancing (NLB)
NLB: How it works
• Allows clients to address the application using the
NLB cluster address

• Adding or removing nodes from a NLB cluster is known

as convergence
• NLB can only detect server failure
• Use NlbCluster
• Use NlbClusterNode
• Can have up to 32 Nodes
• Unicast vs Multicast vs IGMP multicast
NLB Considerations
Practice Question

A. Perform a live migration

B. Perform a quick migration
C. Export and Import VM1
D. Perform a storage migration
06-Maintain and monitor
server environments
Maintain Server Installations
Windows Server Update Services (WSUS)
• Downloads and distributes updates to clients and Phase 1:
servers Assess
• WSUS client can be a desktop OS or server OS

• Single server or multiple single servers (isolated

locations) Phase 4: Phase 2:
Deploy Identify
• Larger hierarchy with upstream server and one or
more downstream servers
• Disconnected: receives updates from removable media
Phase 3:
Evaluate
and plan
WSUS Administration
• Used to download and approve updates
• Can organize clients into groups for
patch deployment by department, or
pilot testing, etc.
• Generate reports
• Cmdlets included with Server 2016
• Include commands for managing the
server
Cmdlet
Add-WsusComputer
Add-WsusDynamicCategory
Approve-WsusUpdate
Deny-WsusUpdate
Get-WsusClassification
Get-WsusComputer
Get-WsusDynamicCategory
Get-WsusProduct
Get-WsusServer
Get-WsusUpdate
Invoke-WsusServerCleanup
Remove-WsusDynamicCategory
Set-WsusClassification
Set-WsusDynamicCategory
Set-WsusProduct
Set-WsusServerSynchronization
Description
Adds a specified client computer to a specified target
group.
Adds a dynamic category to a WSUS server.
Approves an update to be applied to clients.
Declines the update for deployment.
Gets the list of all WSUS classifications currently
available in the system.
Gets the WSUS computer object that represents the
client computer.
Gets dynamic categories on a WSUS server.
Gets the list of all products currently available on
WSUS by category.
Gets the value of the WSUS update server object.
Gets the WSUS update object with details about the
update.
Performs the process of cleanup on a specified WSUS
server.
Removes a dynamic category from a WSUS server.
Sets whether the classifications of updates that WSUS
synchronizes are enabled or disabled.
Sets the synchronization status of a dynamic category.
Sets whether the product representing the category of
updates that needs to be synchronized is enabled or
disabled.
Sets whether the WSUS server synchronizes from
Microsoft Update or from an upstream server, and if it
uses the upstream server’s properties.
WSUS Patch Management
• Used to download updates to specific sets of computers
• All computers are members of the “All Computers” and “Unassigned Computers” groups by default
• Create customer computer groups for pilot computers, or specific departments, etc.
• In Server 2016, computers may be members of multiple groups and nested groups

• Mixed WSUS versions in use

• Features on upstream server that are not available on downstream server will not replicate (nested
groups or multiple group memberships, for example)

• Include Windows Defender and Definition Updates in the Products and Classifications Sync options
Windows Server Backup
• Used to perform full server backup or selected volumes
• Can backup/restore individual files or folders, system state, individual VM’s on Hyper-V host
• Can perform a bare-metal restore without first installing an OS

• Hyper-V hosts and guests

• Install on host to perform host-level backup
• Install on guest to perform an in-guest backup
• Active Directory
• Cannot restore from a backup that is older than 180 days. Consider this when creating backup schedule
• Files servers
• Web servers
Monitor Server Installations
Performance Monitor
• Used to collect, analyze, and interpret
performance-related data
• Create baseline data during multiple use-cases
• Helps with trend analysis, capacity planning,
understanding bottlenecks and slow-downs

• Processor
• Memory
• Network
• Disk
Data Collector Sets
• Include performance counters, event trases,
and system configuration information
• Can collect in real-time or schedule data
collection, for example Run for 10 minutes each
hour from 8-5
• Can analyze historical data

• Create from template

• Create from existing performance monitor data
• Manually add data collectors

• Configure an action to occur if a DSC hits the

min or max limits
Resource Monitor
• Provides real-time information on server’s
performance
• Similar to Task Manager, but shows historical
data as well

• From Task Manager

• From Start menu

• Expand each element for detailed information

on how each process is using server resources
Practice Question

A. Load settings into Resource Monitor

B. Use Performance monitor to create a report view.
C. Use Performance monitor to start the system data collector set
D. Use Performance monitor to create a user-defined data collector set
Monitor and maintain servers

Host-level backup
--
In-Guest back-up
© 2016 Microsoft Corporation. All rights reserved. The text in this document is available under the Creative Commons Attribution 3.0 License, additional terms may apply. All other content contained in this
document (including, without limitation, trademarks, logos, images, etc.) are not included within the Creative Commons license grant. This document does not provide you with any legal rights to any
intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some
examples are for illustration only and are fictitious. No real association is intended or inferred. Microsoft makes no warranties, express or implied, with respect to the information provided here.