1. Server Management and Automation Windows Server 2012 R2
5/22/2019
Server Management and Automation Windows Server 2012 R2
Won Huh
Product Marketing Manager

2. Deployment Real world scenario Server Core Minishell Full GUI
5/22/2019
Deployment
Deployment options
Server Core
Minishell
Full GUI
Real world scenario
Deployment method
Server Manager
Needs to be a summary of the next slides
Desired state configuration

3. Deployment Deployment options Server Core Server with a GUI
5/22/2019
Deployment
DEPLOYMENT
Deployment options
Server Core
The default deployment option.
RSAT for remote GUI management.
PowerShell support achieves critical mass with cmdlets.
More roles and features available.
Server with a GUI
Equivalent of full Server in Windows Server 2008 R2.
Provided for backwards compatibility.

4. Deployment Configuration levels Classic “Full Server”
5/22/2019
Deployment
DEPLOYMENT
Configuration levels
Server with a GUI
Classic “Full Server”
Full Metro-style GUI shell.
Install Desktop Experience to run Metro-style apps.
Full Server without Server Graphical Shell
No Explorer, Internet Explorer or associated files.
MMC, Server Manager, and a subset of Control Panel applets are still installed.
Provides many of the benefits of Server Core for those applications or users that haven’t yet made the transition.
Server Core
Can move between Server Core and Full Server by simply installing or uninstalling components.
Minimal Server
Interface
Server Core

5. Deployment Server with a GUI Minimal Server Interface Server Core
5/22/2019
Deployment
DEPLOYMENT
VHDX Template Size
Full Installation
Core Installation
Windows Server 2012
8,392,704 KB
5,509,120 KB
Windows Server 2012 R2
7,442,432 KB
4,624,384 KB
OS deployment type
# of updates
Restart Required
Windows Server 2012 56 31
Windows Server 2012 (Core) 42 20
Windows Server 2008 R2 SP1
220
133
Windows Server 2008 R2 SP1 (Core)
127 74
Server with a GUI
Minimal Server
Interface
R2 supports the compression for SxS storage.
Windows Server 2012: from Nov to Jul. 2013
Windows Server 2008 R2 SP1: Nov to Jul. 2013
 In-depth Analysis: How the 42 patches above for Windows Server 2012 Core deployment affected Hyper-V availability
.Net
Active Directory
Client-like*
Kernel
HTTP
IP-HTTPS
NFS
Printer
Total
Windows Server 2012 Core 16 1 2 4 42
Server Core
Only updates that should be applied is 2 while running Hyper-V role only.
The two updates for Kernel are against Denial of Service vulnerability. And it can be mitigated if Hyper-V management network is segregated.
Windows Server 2012 Hyper-V availability is not impacted by Security Updates if there is a risk-based update policy in place.
*Client-like: It’s vulnerability that is exposed when a user who locally logged on browses or executes malicious programs. That’s usually not going to happen on Parent-partition of Hyper-V.

6. Deploying with Server manager
DEPLOYMENT
Server manager deployment
Select installation type: role or feature-based.
Select destination server: server pool or VHD.
Select server roles.
Select features.
Confirm selection and install.

7. Desired State Configuration
5/22/2019
Desired State Configuration
DEPLOYMENT
DSC
Components of your data center have the correct configuration.
PowerShell language extensions and providers which enable declarative, repeatable deployment.
Define the exact configuration of target nodes (computers or devices) and prevent “configuration drift.”

8. Desired State Configuration
5/22/2019
Desired State Configuration
DEPLOYMENT
“Make it so” phase
Declarative configuration is reified through imperative providers.
Providers implement changes:
Monotonic.
Imperative.
Repeatable.
Staging phase
Fully declarative configuration representation using DMTF standard MOF instances.
Configuration is calculated for all nodes.
Authoring phase
May include imperative as well as declarative code.
*** When authoring in PowerShell, on top of PSV3 imperative features, PSV4 adds:
Declarative syntax extensions.
Schema validation (early-binding).
Agent of consistency
Imperative providers
Local DSC cache
3rd party languages and tools
PS V1, V2, V3
PS V4***
Configuration staging area
(Contains DSC data)
Show: Simple Provider
Show: Ability to execute Get-Website, etc.
Note: Others (puppet, chef, cfengine… anyone) can plug in and utilize different components of this architecture.
LCM:….
Consider this:  The mechanics are that PS produces a MOF file that is consumed by the agent which makes it so.
What that *really* means is that we are shipping a Desired State Configuration agent which consumes standards-base-management documents which can be produced by *any* tool.
In other words, we are delivering a single agent which ANY and ALL configuration management tools (e.g. Chef/Puppet/CfEngine/System Center/etc) can use.
Today, each of these tools is out trying to convince everyone in the world to write providers for their tools.
In the new world, people will write a single provider and will be able to light up all the tools (once the tools use our agent).

9. DSC Deploy and maintain in a desired state
Demo
DSC Deploy and maintain in a desired state