1. Transform IT delivery in 2016
12/27/2017
Transform IT delivery in 2016
<your name>
<your role>
<the date>
Slide 1: Slide title here
Speaker notes
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Which option does your datacenter resemble?
12/27/ :38 PM
Which option does your datacenter resemble?
Traditional
Tight coupling between infrastructure and apps
Expensive, vertically integrated hardware
Silo-ed infrastructure and operations
Highly customized processes and configurations
Software defined
Loosely coupled infrastructure with apps & micro-services
Industry-standard hardware
Service-focused delivery
Standardized processes and configurations
Slide objectives
Establish that traditional approaches to operating datacenters are insufficient to help enable the app-fueled innovation that was discussed earlier
Compare and contrast traditional vs. modern approaches
Key talking points
Highlight the following points to emphasize the differences between traditional and modern approaches:
Apps in traditional datacenters are typically “hard coded” with the infrastructure, making things rigid. What’s really needed is the ability to decouple apps from the infrastructure so IT has the freedom to decide where they should run without sweating about where the infrastructure resides. App owners benefit from this freedom too, as they can focus on specifying app requirements without having to get into infrastructure details.
Customers pay hardware vendors a lot of $$ today for what’s essentially monolithic, proprietary infrastructure that needs a lot of feeding. In particular, hardware configuration tends to be unnecessarily complicated since IT admins need to perform such tasks one-device at a time. In contrast, the infrastructure in a modernized datacenter is based on industry-standard low cost designs and they looks fairly homogeneous. Management and configuration is done centrally in software thereby simplifying things drastically.
Infrastructure teams in traditional datacenters tend to be siloed – e.g. we regularly see “fiefdoms” of storage, networking, and server virtualization teams each with their own operational models, which may or may not align with all-up objectives of the business. In contrast, a modernized approach would focus on “services” and not “servers”, thereby streamlining roles and responsibilities to make them much more innovation-friendly.
Building on the above, traditional datacenter approaches tend to have unique custom-built processes and tools that have been built over the years – customers tend to maintain them at a high cost, mostly because they fear that things might “break” if they modify anything. In contrast, a modern approach attempts to standardize processes and infrastructure configurations resulting in much more predictable and efficient operations.
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Transform IT Software-defined datacenter Cloud service delivery
Modern development
platform
Management anywhere
Slide #: Chapter 1: software-defined datacenter
Speaker notes
Operations Management Suite
System Center
Windows Server

4. Software-defined datacenter Cloud service delivery Modern development
platform
Management anywhere
Slide #: Chapter 1: software-defined datacenter
Speaker notes
Operations Management Suite
System Center
Windows Server
Azure Stack
Azure

5. Cloud-inspired infrastructure
Windows Server | Hyper-V | System Center
infused with Azure designs and technologies
Provisioning and operations
Standard APIs
Compute
Compute cluster
Virtual machines
Industry-standard servers
Standard APIs
Storage
Storage cluster
File servers
Industry-standard disks
Standard APIs
Networking
Network controller
Virtual networks
Physical network
Standard APIs
Security
Security controller
Shielded VMs
TPM-enabled hardware
Windows Server | Hyper-V | System Center

6. Server & Tools Business
12/27/2017
New in Windows Server 2016
Compute
Networking
Storage
Security
Industry-standard servers
Physical network
Industry-standard disks
TPM-enabled hardware
Network controller, including a high availability mode
East-West load balancing
Virtual Machine Multi-Queue to enable 10G+ performance
Containter specific networking
Hyper-converged option using Storage Spaces Direct for increasing efficiency
Storage Health Service with a single monitoring point per cluster
Increased flexibility with maximum bandwidth settings for a VHD/X using storage QoS
Nested virtualization
PowerShell support for VM upgrade / versioning
Node fairness for better resource utilization
Shared VHDX integration
Shielded VMs
Just Enough Administration and Just In Time administration for separation of roles on all systems
Compute
Node fairness identifies idle nodes in a cluster and distributes VMs to utilize idle nodes
Guest clusters can now resize shared VHDX storage without downtime
Networking
In TP3, we introduced the new Azure consistent SDN stack with the new network controller, the new data plane, and various services such as virtual networking, load balancing, distributed firewall, and increased resiliency of our gateways. Thank you for deploying the new SDN stack and providing us valuable feedback! TP4 incorporates this feedback with the network controller now being deployable in a high availability mode, the load balancer providing better East-West load balancing, tenant traffic being load balanced across multiple gateways and segregated for traffic type (eg. MPLS/IPsec), and support for live migration. In addition, in TP4, we introduce Virtual Machine Multi-Queue to enable 10G+ performance. Finally, we continue to make strides on container networking with support for NAT and transparent IP addressing. For more details, refer to the overview blog on networking.
Storage
Storage Spaces Direct now supports all-flash configurations with NVMe SSD and SATA SSD devices, and Erasure Coding for increased storage efficiency.
Windows Server Technical Preview 4 now supports Storage Health Service for easier health monitoring and more streamlined operations. Faults and health information bubble up to a single monitoring point per cluster.
Storage QoS now supports adjusting the normalization size of the algorithm from the current default 8 KB settings. Also a VHD/X can now have a maximum bandwidth setting, in addition to maximum IOPs, and the lowest of the two will be enforced.
Security
Protect VMs from compromised host
Readiness for production environments – robustness and high availability.
Control & monitor admin privileges
Just Enough Administration for domain controllers and for server maintenance roles.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

7. Confidently virtualize anything
Compute
Networking
Storage
Security
Frictionless “cloud-cadence” infrastructure upgrades
Benchmark-setting scale, performance, and availability
Best-in-class support for Linux
Rolling upgrades without downtime, no new hardware needed
Mixed-mode clusters
High-performance live migration and Storage QoS
Guest clustering
Mission-critical scale: SQL, Exchange, SharePoint, SAP, Oracle
Broad distribution support, including: RHEL, SLES, Ubuntu, CentOS
Hot add | remove vNIC and in-guest vRSS

8. Flexible workload placement
Compute
Networking
Storage
Security
Cloud-scale fundamentals
SDN infrastructure
Network function virtualization
Connect to Azure
Data plane based on Azure
High-throughput, low- latency packet processing [up to 40G]
Programmable network controller based on Azure
NVGRE, VXLAN, and OVSDB support
Load balancer that is proven in Azure
Distributed firewall
Custom service chaining, including Linux appliances
Azure ExpressRoute
Multi-tenant gateways

9. High-performance storage, fraction of the cost
Compute
Networking
Storage
Security
Cloud-scale, cost-effective platform
Scalable hybrid-cloud storage solution
Workload-aware protection
Cross-site availability and disaster recovery
Storage Spaces Direct
Predictable workload performance with Storage QoS
Microsoft StorSimple
Azure storage
Azure Site Recovery
Azure Backup
System Center Data Protection Manager
Sync replication with Storage Replica
“Stretch” clusters with automatic failover
Cluster-to-cluster replication with orchestrated recovery

10. Security designed for zero-trust environments
Compute
Networking
Storage
Security
Protect virtual machines from compromised host
Control and monitor administrator privileges
Add access and usage policies to sensitive information
Detect and respond to breach faster
Hardware-rooted security
Shielded virtual machines
Guardian Service
Just-in-time administration
Just enough administration
Next generation credentials
File Classification Infrastructure
Azure Rights Management Services
Dynamic Access Control
Privilege Security Event Logging
Cloud-based security analysis
Out-of-the-box anti-malware

11. Software-defined datacenter Cloud service delivery Cloud service
Modern application platform
Modern development
platform
Management anywhere
Slide #: Chapter 1: software-defined datacenter
Speaker notes
Operations Management Suite
System Center
Windows Server
Azure Stack
Azure

12. New deployment option: Nano Server
12/27/2017
New deployment option: Nano Server
“Just enough OS”
Optimized for modern applications
Higher density and performance
Reduced attack surface and servicing requirements
Next-gen distributed app frameworks
Interoperate with existing server applications
Third-party applications
RDS experience
Traditional VM workloads
Containers and modern applications
Just enough OS: Simplified deployment Improved resource utilization Reduced servicing requirements
Full GUI
Specialized workloads
Server Core
Lower maintenance server environment
Nano Server
Just enough OS
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

13. What is a container?
Traditional virtual machines = hardware virtualization
Application VM VM VM VM VM … OS
Hardware
Hardware
Containers = Operating system virtualization
CONTAINER
CONTAINER
CONTAINER
CONTAINER
CONTAINER OS …
Processes
Kernel
Kernel

14. Windows Server Containers Anatomy and key capabilities
12/27/ :38 PM
Windows Server Containers Anatomy and key capabilities
Container A
Container B
Container C
Spotlight capabilities
Web tier
App tier
DB tier
Build: write, run, and scale within containers
Run: container capabilities built into Windows Server
Manage: deploy and manage using PowerShell
Resources: define resources per container
Network: IP options for connectivity
LOB app (+Binaries)
LOB app (+Binaries)
LOB app (+Binaries)
Libraries (Shared across containers)
Libraries
Build: Developers will use familiar development tools, such as Visual Studio, to write apps to run within containers.
By building modular apps leveraging containers, modules can scale independently, and be updated on independent cadences.
Run: Container capabilities built into Windows Server
Manage: Deploy and manage containers using PowerShell, or using Docker.
Resources: Define CPU and memory resources per container along with storage and network throughput.
Network: Provide NAT or DHCP/static IP for network connectivity.
So what are some of the core Windows Server container capabilities.
The first key takeaway, is that there is core functionality for containers, supported natively within the kernel, and they will be available in the next release of Windows Server.
Developers will use familiar development tools, such as Visual Studio, to write apps to run within containers. Instead of trying to backport existing applications, by building modular apps leveraging containers, modules can scale independently, and be updated on independent cadences, providing the developer with much greater flexibility and speed.
Applications can rely on other packages to provide core functionality. As you can see from the graphic, there are 2 containers that are sharing a number of libraries. In addition, when packaging, the packages also depend on a base package which describes the underlying operating system, such as Server Core, which has a large number of APIs that Windows supports, such as .NET, IIS etc. Nano Server is another, however this has a much smaller surface, that will target apps that have been written from the ground up, with the cloud in mind.
Containers are isolated behind their own network compartment. This can be provided a NAT DHCP or Static IP. Each container has an independent session namespace, which helps to provide isolation and additional security. The kernel object namespace is isolated per container.
Each container also has access to certain CPU and memory resources, along with storage and network capacity – these are controlled by the administrator, and ensures predictable and guaranteed control of processes.
These containers can be managed using tools such as PowerShell, or using the Docker management tools.
Host OS w/Container Support
Server (Physical or Virtual)
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. Hyper-V Containers Anatomy and key capabilities
12/27/ :38 PM
Hyper-V Containers Anatomy and key capabilities
Hyper-V Container
Hyper-V Container
Spotlight capabilities
Consistency: consistent container APIs
Compatibility: identical container images
Strong isolation: dedicated kernel copy
Highly trusted: proven Hyper-V technology
Optimized: virtualization layer and OS optimized
App A
Bins/Libraries
App A
Bins/Libraries
Windows Guest OS Optimized for Hyper-V Container
Windows Guest OS Optimized for Hyper-V Container
Consistency: Hyper-V Containers use the same APIs Windows Server Containers ensuring consistency across management and deployment toolsets.
Compatibility: Hyper-V Containers use the exact same images as Windows Server Containers.
Strong Isolation: Each Hyper-V container has it’s own dedicated copy of the kernel
Highly Trusted: Built with proven Hyper-V virtualization technology.
Optimized: The virtualization layer and the operating system have been specifically optimized for containers
Hyper-V Containers take a slightly different approach to containerization. To create more isolation, Hyper-V Containers each have their own copy of the Windows kernel and have memory assigned directly to them, a key requirement of strong isolation. We use Hyper-V for CPU, memory and IO isolation (like network and storage), delivering the same level of isolation found in VMs. Like for VMs, the host only exposes a small, constrained interface to the container for communication and sharing of host resources. This very limited sharing means Hyper-V Containers have a bit less efficiency in startup times and density than Windows Server Containers, but the isolation required to allow untrusted and “hostile multi-tenant” applications to run on the same host.
So aren’t Hyper-V Containers the same as VMs? Besides the optimizations to the OS that result from it being fully aware that it’s in a container and not a physical machine, Hyper-V Containers will be deployed using the magic of Docker and can use the exact same packages that run in Windows Server Containers. Thus, the tradeoff of level of isolation versus efficiency/agility is a deploy-time decision, not a development-time decision – one made by the owner of the host.
Hypervisor
Server
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Management anywhere Software-defined datacenter Cloud service delivery
Modern application platform
Modern application platform
Management anywhere
Management anywhere
Slide #: Chapter 1: software-defined datacenter
Speaker notes
Operations Management Suite
System Center
Windows Server
Azure Stack
Azure

17. Shifting needs in IT management
TECHNOLOGY FLUCTUATING
RETOOLING
FOR VELOCITY
CLOUD BASED
INNOVATION
ANALYTICS | CONTAINERS
DEVOPS | SERVICE MANAGEMENT
CLOUD MIGRATION | SERVICES

18. System Center 2016 (Standard and Datacenter)
Device Management
Support for Windows 10 deployments, MDM enrollment with Azure AD, Access restriction based on device enrollment and policy
Provisioning
Support for Windows Server 2016 Hyper-V features, Rolling cluster upgrades, Simplified networking, Shielded VM provisioning, Guarded host management, Support for vCenter 5.5
Monitoring
Nano Server, Windows storage, SMI-S support, MP Catalog, Performance improvements, Enhanced Data Visualization, SCOM Partner Program
Automation
Migration to cloud, SCO Integration Packs and Runbooks
Self-Service
Improved usability and perf, HTML5 self-service portal, New Exchange connector
Data Protection
Azure Express Route support, Shielded VM, Storage spaces direct

19. Operations Management Suite
WPC 2015
12/27/ :38 PM
Hybrid
Operations Management Suite
Visibility
Any Platform
Control
Microsoft Hybrid Management
Application
Management
Real-time performance visibility
Dynamic application dependency mapping
Faster fault analysis
AlwaysOn backup and disaster recovery
Continuous health monitoring
Automated backup and disaster recovery process
Any Cloud
Protection
Security
On-premises
System Center
© 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. System Center and OMS better together
Visibility | Control | Protection | Security
Malicious IP detection
Patching on your terms
Comprehensive security posture
End-to-end dependency view
Streamlined alert management
Holistic network monitoring
Elevate process automation
Easy configuration management
Quick automated remediation
Always-on applications
Central backup management
Cloud integrated disaster recovery

21. 12/27/2017
© 2015 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.