How to use this presentation 1/27/2018 8:41 AM Length 60 Min – can be customized based on presenter preference Key Message Nano Server is a remotely administered server operating system optimized for private clouds and datacenters. It is similar to Windows Server in Server Core mode, but significantly smaller, has no local logon capability, and only supports 64-bit applications, tools, and agents Target Audience Developers, IT Pro, ITDM, CxO Demos Preparation Resources MSDN: https://channel9.msdn.com/Series/Nano-Server-Team Technet Blogs: https://technet.microsoft.com/en-us/windows-server-docs/compute/nano-server/getting-started-with-nano-server Microsoft MVA: https://mva.microsoft.com/en-us/training-courses/a-deep-dive-into-nano-server-13785 © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Nano Server Just-enough operating system for the cloud 1/27/2018 8:41 AM Nano Server Just-enough operating system for the cloud Name Title © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Agenda What we hear from customers Our journey 1/27/2018 Agenda What we hear from customers Our journey Nano Server – Management Nano Server as an Application Platform Preliminary results Roadmap Next steps © 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.

Challenges customers face Cost “When I need to reboot my system, I need it to be back in service ASAP.” Security “I need to minimize OS vulnerabilities.” Density “My infrastructure requires too many resources; I need more VMs on a single host.” COST Reboots impact my business. When a reboot is required, the systems need to be back in service ASAP. Large server images take too long to configure and install. Large images take a long time to install and configure. Transferring images consumes too much network bandwidth. Storing images requires too much disk space. SECURITY Shrink the surface to help prevent attacks. I need an OS without as many vulnerabilities. DENSITY Infrastructure requires too many resources. If the OS consumes fewer resources, I can increase my VM density. Higher VM density lowers my costs and increases my efficiency & margins.

Why security is top IT priority Microsoft Build 2016 1/27/2018 8:41 AM Why security is top IT priority Increasing incidents Multiple motivations Bigger risk In the last several years, breaches have hit government agencies, banks, energy companies, retailers and even a cybersecurity firm. It’s become a daily headline in the news. No one wants to be the next headline. Increasing incidents The incidents are growing in both volume and sophistication, 64 percent more security incidents in 2015 than in 2014. according to the Cost of a Data Breach study from IBM and Ponemon. Multiple motivations Not that long ago, when we thought of hackers we pictured teenagers in basements causing trouble. Things changed when organized crime realized there was money to be made in hacking. Today, there are nations, terrorists and activists all trying to steal secrets for various reasons. Bigger risk As these threats become more complex, the cost to companies continues to rise, according to the study, with companies losing $158 per compromised record. Breaches in highly regulated industries were even more costly, with healthcare reaching $355 per record – a full $100 more than in 2013 Companies that continue to rely solely on prevention and detection technologies like firewalls and antivirus products are considered sitting ducks. In nearly every case, by the time the victims noticed that hackers were inside their systems, their most sensitive information, trade secrets and customer data had already left the building. © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

I want just the components… …I need… …and nothing more

Our server journey* Monolithic Modular Server core Full server 1/27/2018 8:41 AM Our server journey* Server roles/features Windows/ Windows NT Windows NT to Windows Server 2003 Server core Full server Windows Server 2008 and Windows Server 2008 R2 Server core Minimal server interface GUI Shell Windows Server 2012 and Windows Server 2012 R2 Before 2003, Windows Server was installed as a monolithic server with most services and ports running without any firewall protection. The Security Development Lifecycle (SDL) was announced in 2003 and all software development, including Windows Server, followed a process that helps developers build more secure software and address security compliance requirements while reducing development cost while the code is being built. As part of the defense in depth strategy along with SDL, the Server Core installation option of Windows Server 2008 or Windows Server 2008 R2 was created. This install option requires initial configuration at a command prompt. A Server Core installation does not include the traditional full graphical user interface. Once you have configured the server, you can manage it locally at a command prompt or remotely using a Terminal Server connection. You can also manage the server remotely using the Microsoft Management Console (MMC) or command-line tools that support remote use. With Windows Server 2016, this concept is taken to the extreme with Nano Server. Nano Server is a deeply refactored version of Windows Server with a small footprint and remotely managed installation, optimized for the cloud and a DevOps workflow.  It is designed for fewer patch and update events, faster restarts, better resource utilization and tighter security. Informed directly by our learnings from building and managing some of the world’s largest hyperscale cloud environments, and available in the next version of Windows Server, Nano Server focuses on two scenarios: Born-in-the-cloud applications – support for multiple programming languages and runtimes. (e.g. C#, Java, Node.js, Python, etc.) running in containers, virtual machines, or on physical servers. Microsoft Cloud Platform infrastructure – support for compute clusters running Hyper-V and storage clusters running Scale-out File Server. Monolithic Modular * Admin GUIs on servers are poison © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

We need server configuration optimized for the cloud

Nano Server installation option Just enough OS 1/27/2018 Nano Server installation option Just enough OS Provides higher density, reduced attack surface and servicing requirements Ideal for cloud inspired infrastructure Smaller image size, smaller attack surface, faster boot time Ideal for next generation app development Built for containers and cloud-native apps Full developer experience with Windows SDK and Visual Studio Third-party applications RDS experience Full GUI Specialized workloads Existing VM workloads Server Core Lower maintenance server environment Nano Server is a remotely administered server operating system optimized for private clouds and datacenters. It is similar to Windows Server in Server Core mode, but significantly smaller, has no local logon capability, and only supports 64-bit applications, tools, and agents. It takes up far less disk space, sets up significantly faster, and requires far fewer updates and restarts than Windows Server. When it does restart, it restarts much faster. The Nano Server installation option is available for Standard and Datacenter editions of Windows Server 2016. Containers and modern applications Nano Server Just Enough OS © 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.

Nano Server Cloud-ready when you are 1/27/2018 8:41 AM Nano Server Cloud-ready when you are Zero-footprint model Server roles and optional features live outside of Nano Server. Standalone packages that install like applications. Key roles and features Hyper-V, Storage (SoFS), clustering IIS and DNS Server available in TP4 Core CLR and ASP.NET 5 Full Windows Server driver support Anti-malware optional package System Center VMM and OM agents supported With Nano Server, the concept of which is a zero footprint model that delivers faster speed and lower resource consumption.. Nano Server is ideal for a number of scenarios: As a "compute" host for Hyper-V virtual machines, either in clusters or not As a storage host for Scale-Out File Server. As a DNS server As a web server running Internet Information Services (IIS) As a host for applications that are developed using cloud application patterns and run in a container or virtual machine guest operating system This below shows the roles and features that are available in this release of Nano Server, along with the Windows PowerShell options that will install the packages for them. Some packages are installed directly with their own Windows PowerShell switches (such as -Compute); others you install by passing package names to the -Packages parameter, which you can combine in a comma- separated list. You can dynamically list available packages using Get-NanoServerPackage cmdlet. Hyper-V role (including NetQoS Failover Clustering Basic drivers for a variety of network adapters and storage controllers. This is the same set of drivers included in a Server Core installation of Windows Server 2016 Technical Preview. 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. DNS Server role Desired State Configuration (DSC) Internet Information Server (IIS) Host support for Windows Containers System Center Virtual Machine Manager agent Network Performance Diagnostics Service (NPDS) Data Center Bridging (including DCBQoS Deploying on a virtual machine Deploying on a physical machine Secure Startup Shielded VM © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

1/27/2018 8:41 AM “ “ Nano Server is so quick to reboot, often our monitoring tools don’t realize it has happened. David Knappett Technical Architect Alternative Networks © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Nano Server – Management

Manage Nano Server remotely 1/27/2018 8:41 AM Manage Nano Server remotely Not Command Line only Server Manager Hyper-V Manager Failover Cluster Manager PerfMon, Event Viewer, etc. Server Management Tools (SMT) – new web-based remote GUI PowerShell Core Nano Server is managed remotely. There is no local logon capability at all, nor does it support Terminal Services. However, you have a wide variety of options for managing Nano Server remotely, including Windows PowerShell, Windows Management Instrumentation (WMI), Windows Remote Management, and Emergency Management Services (EMS)., Server management tools, PowerShell Core © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Nano Server Management 1/27/2018 8:41 AM Nano Server Management Eliminate the need to ever sit in front of a server. Configure via PowerShell Desired State Configuration (DSC). Use PowerShell Core and WMI for remote management/automation. Integrate into DevOps toolchains. Nano Server is managed remotely. There is no local logon capability at all, nor does it support Terminal Services. However, you have a wide variety of options for managing Nano Server remotely, including Windows PowerShell, Windows Management Instrumentation (WMI), Windows Remote Management, and Emergency Management Services (EMS). Using Windows PowerShell remoting To manage Nano Server with Windows PowerShell remoting, you need to add the IP address of the Nano Server to your management computer's list of trusted hosts, add the account you are using to the Nano Server's administrators, and enable CredSSP if you plan to use that feature. Stop the remote session with the command Exit-PSSession Using Windows PowerShell CIM sessions over WinRM You can use CIM sessions and instances in Windows PowerShell to run WMI commands over Windows Remote Management (WinRM). Windows Remote Management You can run programs remotely on the Nano Server with Windows Remote Management (WinRM). To use WinRM, first configure the service and set the code page © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

PowerShell Core Refactored to run on CoreCLR 1/27/2018 8:41 AM PowerShell Core Refactored to run on CoreCLR Full PowerShell language compatibility & remoting Invoke-Command, New-PSSession, Enter-PSSession, etc. Most core engine components Support for all cmdlet types: C#, Script, and CIM Limited set of cmdlets initially Starting with version 5.1 (the version included with Windows Server 2016), PowerShell is available in different editions which denote varying feature sets and platform compatibility. Desktop Edition: Built on .NET Framework and provides compatibility with scripts and modules targeting versions of PowerShell running on full footprint editions of Windows such as Server Core and Windows Desktop. Core Edition: Built on .NET Core and provides compatibility with scripts and modules targeting versions of PowerShell running on reduced footprint editions of Windows such as Nano Server. Nano Server includes the PowerShell Core edition by default in all Nano Server installations. PowerShell Core functions in the same way as other editions of PowerShell, such as the Desktop edition of Windows PowerShell running on Windows 10 and Windows Server 2016 with Desktop Experience. If there’s a question about this: However, the reduced footprint of Nano Server means that not all PowerShell features from Windows Server 2016 are available in PowerShell Core on Nano Server. The reduced footprint of .NET Core also means that not all existing cmdlets written in C# will run on PowerShell Core. © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Server management tools 1/27/2018 8:41 AM 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 Server management tools offers a set of web-based GUI and command line tools to manage Windows Servers. This is especially useful when managing headless servers such as Nano Server and Server Core. These tools also provide rapid access to your on premises infrastructure alongside your Azure resources. In this first release, the tools can only be used to manage Windows Server 2016 running on-premises as well as in Azure. The tools are hosted in Microsoft Azure are can be accessed anywhere/anytime. Currently, the tools offer the following capabilities: View and change system configuration View performance across various resources and manage processes and services Manage devices attached to the server View event logs View the list of installed roles and features Use a PowerShell console to manage and automate © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Setup and boot event collection Broader environment visibility Microsoft Ignite 2015 1/27/2018 8:41 AM Setup and boot event collection Broader environment visibility Greater visibility Remotely view debug errors, events from your deployment process, boot loader, OS, and services. Troubleshoot issues without requiring physical access. Simple setup Works on both physical and virtual machines. Requires little additional infrastructure and can be set up using PowerShell or an unattend file. Lower MTTR Access to data is real-time and can be correlated with other diagnostic data to identify problems faster. Physical machines Virtual machines ETW messages ETW collector Setup and Boot Event Collection is a new feature starting in Windows Server 2016 Technical Preview that allows you to designate a "collector" computer that can gather a variety of important events that occur on other computers when they boot or go through the setup process. You can then later analyze the collected events with Event Viewer, Message Analyzer, Wevtutil, or Windows PowerShell cmdlets. Previously, these events have been impossible to monitor because the infrastructure needed to collect them doesn't exist until a computer is already set up. The kinds of setup and boot events you can monitor include: Loading of kernel modules and drivers Enumeration of devices and initialization of their drivers (including "devices" such as CPU type) Verification and mounting of file systems Starting of executable files Starting and completions of system updates The points when the system becomes available for logon, establishes connection with a domain controller, completion of service starts, and availability of network shares The collector computer must be running Windows Server 2016 (it can be in either Server with Desktop Experience or Server Core mode). The target computer must be running either Windows 10 or Windows Server 2016. You can also run this service on a virtual machine which is hosted on a computer that is not running Windows Server 2016. Service ETL files Analysis tools © 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Recap Nano Server management Microsoft Ignite 2015 1/27/2018 8:41 AM Recap Nano Server management DevOps mindset: "Treat servers like cattle, not pets." Goal: Eliminate the need to ever sit in front of a server. Remote graphical and web-based management tools Remote management and automation via PowerShell & WMI © 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Nano Server in Windows Server 2016 1/27/2018 8:41 AM Nano Server in Windows Server 2016 An installation option, like Server Core Not listed in Setup because image must be customized with drivers Separate folder on the Windows Server media You can run a Nano Server VHD either in a virtual machine or boot to it on a physical computer; the steps are slightly different. Nano Server in a virtual machine Follow these steps to create a Nano Server VHD that will run in a virtual machine. To quickly deploy Nano Server in a virtual machine Copy NanoServerImageGenerator folder from the \NanoServer folder in the Windows Server Technical Preview ISO to a folder on your hard drive. Start Windows PowerShell as an administrator, change directory to the folder where you have placed the NanoServerImageGenerator folder and then import the module with Import-Module .\NanoServerImageGenerator -Verbose Create a VHD for the Standard edition that sets a computer name and includes the Hyper-V guest drivers by running the following command which will prompt you for an administrator password for the new VHD: New-NanoServerImage -Edition Standard -DeploymentType Guest -MediaPath <path to root of media> - BasePath .\Base -TargetPath .\NanoServerVM\NanoServerVM.vhd -ComputerName <computer name> Nano Server on a physical computer You can also create a VHD that will run Nano Server on a physical computer, using the pre-installed device drivers. If your hardware requires a driver that is not already provided in order to boot or connect to a network, follow the steps in the "Adding Additional Drivers" section of this guide. To quickly deploy Nano Server on a physical computer © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Nano Server Quick Start Scripts included in Nano Server folder to make it easy to build a customized Nano Server image. New-NanoServerImage.ps1 Convert-WindowsImage.ps1 Use scripts to generate a Nano Server image for: Physical machine Virtual machine

Nano Server customizations Required Add right set of drivers for hardware or VM* Add required roles or features for servers role* Set Administrator password* Convert WIM to VHD* Optional Set Computer Name* Run commands on first boot, e.g. set a static IP address Domain Join* Dual Boot Enabling Emergency Management Services (EMS)* Installing Agents and Tools * - supported by New-NanoServerImage.ps1

1/27/2018 8:41 AM Installing drivers For the leanest image, install just the drivers your hardware requires. Dism /Add-Driver /driver:<path> Nano Server includes a package of all drivers in Server Core. Dism /Add-Package /PackagePath:.\packages\Microsoft-NanoServer-OEM-Drivers-Package.cab To run Nano Server as a VM install: Dism /Add-Package /PackagePath:.\packagesMicrosoft-NanoServer-Guest-Package.cab © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Installing roles and features Nano Server folder has a Packages sub-folder: Dism /Add-Package /PackagePath:.\packages\<package> Dism /Add-Package /PackagePath:.\packages\en-us\<package>

Installing agents and tools on Nano Server No MSI support in Nano Server. Current builds of Nano Server require xcopy or custom PowerShell script Windows Server Installer (WSI) in next TP, which will provide: Install Uninstall Inventory WSI in next TP is Nano Server only, will be added to Server Core and Server for Windows Server 2016.

Emergency Management Console Provides local access to basic configuration and network settings: Computer name Domain or workgroup name Ipconfig /all information for each network adapter Ability to modify network settings to follow.

Nano Server as an application platform

Nano Server Cloud application platform 1/27/2018 8:41 AM Nano Server Cloud application platform Born-in-the-cloud application support Subset of Win32 CoreCLR, PaaS, and ASP.NET 5 Available as OS everywhere Host OS for physical hardware Guest OS in a VM Windows Server containers Hyper-V containers Future additions PowerShell Desired State Configuration (DSC) & PackageManagement available in TP4 Additional Roles and Application Frameworks © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Server application development Deep refactoring Client stack for RDS Developers target Nano Server Deploy to physical, virtual, or containers Remote Desktop Server Local Admin Tools Client (aka Server w/a Desktop Exp) (Aka Full Server) Physical, Virtual, Containers Server Core Nano Server

Nano Server Developer experience Nano Server has a full developer experience, unlike Server Core. Windows SDK and Visual Studio 2015 target Nano Server. Rich design-time experience. Project template, full IntelliSense, error squiggles, etc. Full remote debugging experience.

Reverse Forwarders Provide a way to run existing apps without recompiling for Nano Server. Try apps and tools that don’t have GUI and work on Server Core with the Reverse Forwarder package. Does not eliminate the need to refactor code to what is available in Nano Server. What runs today with the Reverse Forwarders? Chef PHP Nginx Python 3.5 Node.js GO Redis MySQL OpenSSL Java (OpenJDK) Ruby (2.1.5) SQLite

Optimized for containers Nano Server Server Core Highly optimized Born-in-the-cloud applications Highly compatible Traditional applications

What is a container? Containers Microsoft Build 2016 1/27/2018 8:41 AM What is a container? Containers Windows Server containers Maximum speed and density Container Kernel OS Applications Kernel = Operating system virtualization Container OS Hardware Traditional virtual machines = hardware virtualization VM Hyper-V containers Isolation plus performance Hyper-V Container Kernel When it comes to applications, historically, IT administrators deployed with a 1:1 application to server ratio. When a new application was required by the business, it was deployed onto a newly provisioned physical system, to ensure no conflicts with existing applications and workloads. This resulted in a huge number of physical servers, all with very low utilization. Fast forward to a more modern datacenter, where virtualization is now prevalent, and you’ll find significantly higher consolidation ratios, much greater utilization and significantly accelerated app deployment speeds as administrators deploy applications in minutes, compared with hours, days or weeks in a purely physical datacenter. Compared with applications that ran on individual physical servers, the compatibility of those same apps to run inside virtual machines was typically very high. After all, the virtual machine just presents virtual hardware to the same operating system that was running in the physical world. The only consideration being, if that application or workload has a requirement for a specific piece of hardware, such as a PCI-E card, that couldn’t be virtualized and presented through to the guest operating system. In addition, once that application was encapsulated inside the virtual machine, it benefited from higher levels of redundancy, and also mobility, through features such as live migration. There is however, a new and increasingly popular way to build, ship, deploy and instantiate applications. Containers can further accelerate application deployment and streamline the way IT operations and development teams collaborate to deliver applications to the business. But what are containers? Well, to give the computer science definition, containers are an operating system- level isolation method for running multiple applications on a single control host. With developers building, and then packaging their applications into containers, and providing them to IT to run on a standardized platform, it reduces the overall effort to deploy applications, and can streamline the whole dev and test cycle, ultimately reducing costs. As containers can run on a host OS which itself could be physical or virtual, it provides IT with flexibility, and the opportunity to drive an increased level of server consolidation, all whilst maintaining a level of isolation that allows many containers to share the same host operating system. Windows Server 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 security. The kernel object namespace is isolated per container. 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 Application OS Hardware © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Preliminary results

Footprint improvements 26 44 98 73 25 11 Nano Server Server Core

Resource utilization improvements 26 306 139 21 108 61 Nano Server Server Core

Deployment improvements 5.42 6.3 300 40 .4 .41 Nano Server Server Core

Roadmap Nano Server is the future nucleus of Windows Server. Target for cloud components and born-in-the-cloud applications. New foundation for all components. Provides a Just Enough OS model for all applications. Not everything will run on Nano Server. Server Core provides compatibility for existing Enterprise applications. Physical, Virtual, Containers Existing Enterprise applications Born-in-the-cloud applications Server Core Nano Server

What customers are saying?

Next steps Learn more: www.microsoft.com/WindowsServer2016 1/27/2018 8:41 AM Next steps Learn more: www.microsoft.com/WindowsServer2016 Deploy Nano Server, apps, and tools. Deployment guide at: https://msdn.microsoft.com/en-us/library/mt126167.aspx Remote Management feedback http://windowsserver.uservoice.com/forums/295071-remote-management-tools © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Current Branch for Business (CBB) Nano Server will be CBB only What does this change? Nano Server will not have an LTSB with Windows Server 2016 and therefore not have 5+5 years of servicing Nano Server installations will have to move forward to future CBB releases of Nano Server to continue to be serviced Licensing Nano Server will require Software Assurance (SA) What doesn’t this change? The quality, features, and functionality of Nano Server Installation of new CBBs are always controlled by administrators, no forced upgrades Context ONLY: What is the LTSB servicing model? This is the traditional servicing model Windows Server has always used 5 + 5 years of servicing Security and quality fixes only No new features or functionality Two Windows Server 2016 installation options use this model Server with Desktop Experience Server Core How frequently will you be updating the Nano Server installation option? The goal is to provide updates 2-3 times per year. Are the Nano Server CBB releases automatically applied by Microsoft or do I have control over their rollout? These CBB releases are not automatically applied by Microsoft and the customer retains full control over when the CBB is installed. The CBB releases are, however, mandatory and will be required to be installed over time in order to keep receiving security patches. How long will I have to install the latest Nano Server CBB in my environment? Customers can be no more than 2 Nano Server CBB releases behind. Only 2 CBB releases will be serviced at any given time, therefore when the 3rd Nano Server release comes out you will need to move off of 1 as it will no longer be serviced. When 4 comes out, you will need to move off of 2, and so on. Are the CBB releases ‘in place’ upgrades? No, these CBB releases will require a reinstall of the operating system. However, given the core use cases for Nano Server at Windows Server 2016 GA (e.g. as the host for compute or storage clusters or the base kernel for Windows Server containers), updates should happen without disruption to the services they support. Will the product notify me when a new CBB release is available? No. You will need to check the Windows Server blog, Nano Server blog, and Windows Server Web site. You will have to manually download the new CBB release. Can I transition from an CBB deployment of Windows Server 2016 Nano Server to a ‘long-term’ deployment of Windows Server 2016 (with Desktop Experience or Server Core)? Yes, but this requires a reinstall of the operating system and you will move to LTSB. Do I need to have Software Assurance associated with a Nano Server deployment? Yes. Since a Nano Server CBB deployment continues to move forward with new technologies and ultimately new features and functionality, Software Assurance is required to ensure rights to these future enhancements of the operating system.

1/27/2018 8:41 AM © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.