Što nam donosi Windows Server vNext (Technical Preview)? Tomica Kaniški Citus d.o.o.

DISCLAIMER: Content presented here is „the current state of things” and, because components are still in the early stages of development, they may change in the final version of the product (or have been changed already)! If not stated otherwise, all content is referring to the Technical Preview release, not final version!

Agenda Hyper-V Windows Defender Remote Desktop Services Storage Services Failover Clustering Networking PowerShell 5.0 Important issues

Hyper-V (1) new VM upgrade process ‐ new VM version (not generation!) – 6.0 (Windows Server 2012 R2 VMs were 5.0) ‐ Hyper-V will not automatically upgrade virtual machines ‐ upgrading a virtual machine is a manual operation that is separate from upgrading the host ‐ individual virtual machines can be moved back to earlier versions, until they have been manually upgraded  Update-VMConfigurationVersion VM servicing ‐ drivers delivered directly to the guest operating system via Windows Update ‐ no vmguest.iso anymore…

Hyper-V (2) new virtual machine configuration file ‐ binary format for efficient performance at scale ‐ resilient logging for changes ‐ new file extensions .VMCX and.VMRS Secure Boot support for Linux ‐ kernel code integrity protections for Linux guest operating systems (Ubuntu and later, and SUSE Linux Enterprise Server 12)  Set-VMFirmware "Ubuntu" -SecureBootTemplate MicrosoftUEFICertificateAuthority

Hyper-V (3) Runtime Memory Resize ‐ dynamic memory is great, but more can be done ‐ you can now increase and decrease the memory assigned to virtual machines while they are running (Windows Server Technical Preview guests only) Production checkpoints ‐ delivers the same Checkpoint experience that you had in Windows Server 2012 R2, but now fully supported for production environments ‐ you can choose, and checkpoints can be „turned off” also ‐ uses VSS instead of Saved State to create checkpoint ‐ restoring a checkpoint is just like restoring a system backup ‐ "ON" by default!

Hyper-V (4) hot add/remove of network adapters ‐ network adapters can be added and removed from Generation 2 virtual machines while they are running network adapter naming ‐ you can name individual network adapters in the virtual machine settings – and see the same name inside the guest operating system ‐ host:  Add-VMNetworkAdapter -VMName "TestVM" -SwitchName "Virtual Switch" -Name "Fred" -Passthru | Set-VMNetworkAdapter -DeviceNaming On ‐ guest:  Get-NetAdapterAdvancedProperty | ?{$_.DisplayName -eq "Hyper-V Network Adapter Name"} | select Name, DisplayValue

DEMO Hyper-V

Windows Defender by default: ‐ installed and functional  GUI not installed ‐ real-time monitoring enabled & default exclusions included ‐ Windows Update (definitions) disabled manage it by using WMI, Windows PowerShell, or by using Group Policy list of available cmdlets ‐ *

DEMO Windows Defender

Remote Desktop Services RemoteFX capabilities that improve the experience in a Windows VDI environment and support OpenGL and higher memory ‐ support for OpenGL 4.4 and OpenCL 1.1 API ‐ configurable, larger dedicated video memory  larger dedicated VRAM and configurable VRAM ‐ performance improvements targeting stability and application compatibility MultiPoint Services role in Windows Server ‐ new role ‐ enabling „DaaS” for classrooms and Point-of-Sale in Retail and SMB ‐ no more „20 users per MultiPoint Server limit” *

DEMO MultiPoint Services

Storage Services (1) Storage Quality of Service (QoS) ‐ centrally monitor end-to-end storage performance and create policies using Hyper-V and Scale-Out File Servers ‐ policy specifies a reserve (minimum) and a limit (maximum) to be applied to a collection of data flows, such as a virtual hard disk, a single virtual machine or a group of virtual machines, a service, or a tenant ‐ PowerShell or WMI  examples: ‐ if multiple virtual hard disks share the same policy, performance is fairly distributed to meet demand within the policy minimum and maximum *

Storage Services (2) ‐ provided by Scale Out File Servers and Hyper-V ‐ Scale Out File Server exposes file shares to the Hyper-V servers using the SMB3 protocol ‐ a new Policy Manager has been added to the File Server cluster, which provides the central storage performance monitoring ‐ as Hyper-V servers launch virtual machines, they are monitored by the policy manager ‐ the Policy Manager will communicate the Storage QoS policy and any limits or reserves back to the Hyper-V server, which will control the performance of the virtual machine as appropriate ‐ when there are changes to Storage QoS policies or to the performance demands by virtual machines, the policy manager will notify the Hyper-V servers to adjust their behavior ‐ this feedback loop ensures that all virtual machines perform consistently according to the Storage QoS policies defined *

Storage Services (3) Storage Replica (SR) ‐ new feature that enables storage-agnostic, block-level, synchronous replication between servers for disaster recovery, as well as stretching of a failover cluster for high availability ‐ provide an all-Microsoft disaster recovery solution for planned and unplanned outages of mission-critical workloads ‐ use SMB3 transport with proven reliability, scalability, and performance ‐ stretch clusters to metropolitan distances ‐ use Microsoft software end to end for storage and clustering, such as Hyper-V, Storage Replica, Storage Spaces, Cluster, Scale-Out File Server, SMB3, Deduplication, and ReFS/NTFS *

Storage Services (4) ‐ helps to reduce cost and complexity:  hardware agnostic, no requirement for a specific storage configuration like DAS or SAN  allows commodity storage and networking technologies  ease of graphical management for individual nodes and clusters through Failover Cluster Manager  includes comprehensive, large-scale scripting options through Windows PowerShell  provides supportability, performance metrics, and diagnostic capabilities

DEMO Storage QoS

Failover Clustering (1) Cluster Operating System Rolling Upgrade ‐ easily upgrade a Hyper-V or Scale-Out File Server failover cluster (without downtime) ‐ upgrade phases (for each node in a cluster):  the node is paused and drained of all virtual machines that are running on it  the virtual machines (or other cluster workload) are migrated to another node in the cluster  the existing operating system is removed and a clean installation of the Windows Server Technical Preview operating system on the node is performed  the node running the Windows Server Technical Preview operating system is added back to the cluster at this point, the cluster is said to be running in mixed mode, because the cluster nodes are running either Windows Server 2012 R2 or Windows Server Technical Preview

Failover Clustering (2)  the cluster functional level stays at Windows Server 2012 R2 new features in Windows Server Technical Preview that affect compatibility with previous versions of the operating system will be unavailable  eventually, all nodes are upgraded to Windows Server Technical Preview  cluster functional level is then changed to Windows Server Technical Preview using the Windows PowerShell cmdlet Update-ClusterFunctionalLevel at this point, you can take advantage of the Windows Server Technical Preview features ‐ all the additional functions (like Cluster-Aware Updating) can be restored again

DEMO Cluster Operating System Rolling Upgrade

Networking (1) Network Controller ‐ new, highly available and scalable server role ‐ provides the point of automation that allows you to configure, monitor, and troubleshoot  Virtual networks  Physical networks  Network services  Network topology  IP address management ‐ manage your datacenter network with Network Controller by using management applications, such as System Center Virtual Machine Manager and System Center Operations Manager *

Networking (2) ‐ allows you to configure, monitor, program, and troubleshoot the network infrastructure under its control ‐ can also expose the network infrastructure to network aware applications, such as Microsoft Lync and Skype ‐ example:  Administrator uses a Management Tool that interacts directly with Network Controller  Network Controller provides information about the network infrastructure, including both virtual and physical infrastructure, to the Management Tool, and makes configuration changes according to the Administrator’s actions when using the tool *

Networking (3) Web Application Proxy ‐ preauthentication for HTTP Basic application publishing  provides support to publish an app using HTTP basic by enabling the HTTP app to receive a non-claims relying party trust for the application to the Federation Service ‐ wildcard domain publishing of applications  external URL for the application can now include a wildcard to enable you to publish multiple applications from within a specific domain, for example, apps.contoso.com which will simplify publishing of SharePoint appshttps://*.sp- apps.contoso.com ‐ HTTP to HTTPS redirection ‐ publish HTTP applications using pass-through preauthentication ‐ publishing of Remote Desktop Gateway apps ‐ UI improvements *

Networking (4) GRE Tunneling for the Windows Server Gateway ‐ enables connectivity between tenant virtual networks and external networks ‐ GRE protocol is lightweight and supported on most of network devices, so it becomes an ideal choice for tunneling where encryption of data is not required ‐ feature designed to address the following requirements:  hosting provider must be able to create virtual networks for forwarding without modifying the physical switch configuration  hosting provider must be able to add subnets to their externally facing networks without modifying the configuration of the physical switches within their infrastructure ‐ relatively easy to deploy *

Networking (5) DHCP ‐ Network Access Protection (NAP) is deprecated in Windows Server 2012 R2, and in Windows Server Technical Preview the DHCP Server role no longer supports NAP (DHCP scopes cannot be NAP-enabled) DNS ‐ DNS Policies  you can configure the DNS server to control the responses to DNS queries  DNS responses can be based on the public IP address of the DNS client, the time of the day, or several other parameters  they enable location-aware DNS, traffic management, load balancing, and other scenarios ‐ no PowerShell support yet! *

PowerShell 5.0 (1) you can now use classes (Class, Enum) ‐ formal syntax and semantics similar to other OOP languages new module Microsoft.PowerShell.Archive ‐ compress, extract and update files and folders into archive (ZIP) files new module OneGet ‐ discover and install software packages on the Internet New-Item, Remove-Item, and Get-ChildItem ‐ create and manage symbolic links detailed script tracing ‐ lets you enable detailed tracking and analysis of Windows PowerShell scripting use … and many more *

PowerShell 5.0 (2) OneGet workflow ‐ load OneGet module in PowerShell ‐ use a Provider for each Package Manager that plugs into OneGet ‐ package manager will then query its software repository to retrieve the package ‐ package manager downloads a configuration file OR get the URI where it will find the instruction to install the package ‐ provider will then execute the configuration file and download the actual software (+ its dependencies) from a repository, and install it *

DEMO OneGet & PowerShell

Important issues current issues : ‐ computer authentication ‐ restart after installing the Failover Clustering feature ‐ cannot access Apple file servers running SMB 2.0 or later ‐ must disconnect all USB monitors or docking stations prior installation ‐ WSUS post-installation may fail ‐ GUI „bugs” ‐ OneGet issues ( ‐ … (continuously updated)

Next steps… download the Technical Preview installation bits ‐ read the Release Notes ‐ look at the roadmaps ‐ center-roadmap-update.aspx center-roadmap-update.aspx ‐ up-to-date/?WT.mc_id=Blog_ServerCloud_Announce_CEA up-to-date/?WT.mc_id=Blog_ServerCloud_Announce_CEA start testing, but do not put it in production!

THANK YOU!