Announcing Windows Server Insider Preview Build 16237

[Bot]

Hello Windows Insiders!

On June 15th we announced some very exciting news: Windows Server will now have more frequent releases providing customers who are innovating quickly an opportunity to take advantage of new OS capabilities at a faster pace, both in applications – particularly those built on containers and microservices – as well as in the software-defined datacenter.

Today we are very excited to be releasing the first Windows Server Insider Preview to Windows Insiders: Build 16237. To access to the latest Windows Server preview release, register at the Windows Insiders for Business program or the Windows Insider Program.

Windows Server Datacenter Core and Standard Core editions are headless operating systems and are best managed remotely. For more information, please refer to Configure a Server Core installation of Windows Server with Sconfig.cmd. Updated remote administration information will be provided with future Insider releases.

General Scenario Highlights

Developers and Containers:

• New base container images (available on Windows Insider Docker Hub repo)
  • Optimized Nano Server base image (over 70% smaller)
    • The .NET team is providing an preview image based on Nano Server with .NET Core 2.0
    • The PowerShell team is providing a preview image based on PowerShell 6.0
  • Optimized Server Core base image (over 20% smaller)
• Support for SMB volume mounting
• Infrastructure for Orchestrators
  • Networking enhancements for on going Kubernetes work
  • Named pipe mapping support
• Bug fixes, performance enhancements

Cloud Guest:

• IIS
  • TLS info: administrators can make specific recommendations to default to HTTPS
• Disaster Recovery
  • Storage Replica Test Failover
• Guest + Host better together
  • vPMEM in Guest: Tenants can use and manage PMEM/SCM
  • Tenant-Aware VM Start Ordering: App Ready / OS Heartbeat for better load balancing
  • Guest RDMA
• Improvement in time accuracy
• Azure enlightened clusters – optimized to run on Azure IaaS

Cloud Host:

• Software Defined Data Center (SDDC) host
  • Security
    • Shielded Linux VM
    • SDN: Encrypted virtual networks
    • Secure clusters
    • SMB 1 disabled by default
  • Resiliency and Availability
    • SDN: Reduced downtime for tenant connections through gateways
    • Spaces Direct: Scoped Spaces to mitigate impact of multi-node loss
    • Spaces Direct: Marginal drive handling for predictive detection of drive failures
  • Efficiency
    • Data Deduplication available for ReFS
    • New Data Deduplication DataPort API for optimized ingress/egress
    • Space efficiency with ReFS Compaction
    • Performant Spaces Direct Multi Resilient Volumes (MRV)
  • Hyper-converged Scale
    • Cluster Sets: Significantly increases hyper-converged SDDC cloud scale by grouping multiple clusters into a larger fabric
  • Hardware support
    • Support for Storage Class Memory (SCM) in Spaces Direct

What’s New in Build 16237 for Server


Persistent Memory can now be exposed to Hyper-V VMs:

• In this build, NTFS-formatted direct access volumes that are created on non-volatile DIMMs can now be exposed Hyper-V VMs. This enables Hyper-V VMs to leverage the low-latency performance benefits of Persistent Memory devices.
• Virtualized Persistent Memory (vPMEM) is enabled by creating a VHD file (.vhdpmem) on a direct access volume on a host, adding a vPMEM Controller to a VM, and adding the created device (.vhdpmem) to a VM. Using vhdpmem files on direct access volumes on a host to back vPMEM enables allocation flexibility and leverages a familiar management model for adding disks to VMs.
• PowerShell can be used for the creation and management of Virtualized Persistent Memory.

Battery Passthrough:

• With new additions to Set-VM, a PowerShell cmdlet, you can now enable and disable Battery Passthrough, a new feature. Battery Passthrough let your VMs have the same battery state as the host they are on. To use this feature of Set-VM, use the flag -BatteryPassthroughEnabled {$true, $false}. This option is only available for version 8.2 virtual machines.

Improvements to Container Networking:

• This build introduces enhancements to container networking to better support Kubernetes by adding support for multiple containers (w/out Hyper-V isolation) to a single Pod (Network Compartment) as well as only requiring a single endpoint per Pod for all traffic types (e.g. ingress and East-West)
• The Host Networking Service (HNS) now has support for creating ACL, NAT, and Load Balancing network policies for Container endpoints for fine-grained policy application.

RDMA for Trusted Guests:

• This build includes several enhancements for (Trusted) Guest RDMA to enable low-latency storage access with zero CPU usage by Trusted Guest VMs – this is ideal for running Windows File Servers in a Guest to accelerate file serving. Requires updated NIC drivers.

Improvements to Software Defined Networking:

• Encryption can be enabled for virtual network subnets to protect your traffic from anyone with physical access to the wire, including network administrators.
• Failover time for SDN gateways is improved. Now, you will observe much faster failover times for the gateways, even with high number of connections.
• Access control lists can be applied for infrastructure on logical subnets.

Improvements in Networking transports:

• 2X throughput improvement for single connection TCP and UDP performance in low latency intra-datacenter scenarios
• Default congestion control algorithm CUBIC for high speed networks

Improvements in HTTP(s):

• SSL throttling to enable predictable service for established connections, in the face of high incoming SSL traffic.
• Deterministic certificate updates for HTTPS enabling greater service availability.

Improvements in time accuracy:

• Pressing EU regulations in 2018 require strict time precision and traceability. Win32tm improvements in RS3 support greater time accuracy, and jitter is removed from the measurements that calibrate the service.
• New system event logging lets you archive time service data to support traceability compliance.
• System center monitoring now includes a new rule which lets you detect when a machine in your environment is out of compliance.

Nano Server optimized for Containers:

• Nano Server is now a container only option and optimized for containers, more information is available in the Delivering continuous innovation with Windows Server blog post. To optimize for containers, several features were removed that were in the Nano Server base image in Windows Server 2016, these include WMI, PowerShell, .NET Core, and the Servicing stack, which has significantly reduced the image size.

Server Core base image optimizations:

• The Windows Server Core base image has been optimized saving over 20% download and on disk space.

How to Download


The latest Windows Server build and matching symbols are available for download here. Matching Windows Server container images will be available via the Docker Hub. For more information about Windows Server containers and Insider builds, please visit Windows Containers Documentation.

The following keys are available for unlimited activations of Windows Server. These keys may be used throughout the pre-release cycle.

• Server Datacenter Core: B69WH-PRNHK-BXVK3-P9XF7-XD84W
• Server Standard Core: V6N4W-86M3X-J77X3-JF6XW-D9PRV

SPECIAL NOTE: If you signed up for Windows Insiders for Business using an AAD account, there is a temporary issue with access to the Windows Server Download page using AAD accounts. If you registered using an MSA account at the Windows Insider program, your MSA account may be used to access the page and to download builds until this is resolved.

It’s all about your feedback!


Use the Feedback Hub app to provide feedback on Windows Server builds. Feedback Hub comes pre-installed on Windows 10. Register a Windows 10 device with the Windows Insider or Windows Insider for Business programs. Open the Feedback Hub application. Choose the Server category and then the appropriate subcategory for your feedback. Please indicate what edition and build number you are providing feedback on. The Feedback Hub app cannot scan a server for diagnostic information, however you may manually attach screenshots or other files to your feedback entry.

We encourage you to visit the Windows Server Insiders space on the Microsoft Tech Communities forum to collaborate, share and learn from experts.

NOTE: The expiration date for this server preview build will be 12/4/2017.

Known issues

• Local vs remote management: Some command-line tools and PowerShell modules may not be available for use locally on a Server Core installation. To remotely manage Server Core by using the full set of GUI tools, command-line tools, and PowerShell modules, use Remote Server Administration Tools for Windows 10, available for download from the preceding link.
• If a user attempts to update to the latest OS build on a device that has .NET Framework 3.5 installed, the update may fail because of a side-by-side (SXS) assembly missing error (0x80073701), and the device will roll back to the previous build. To work around this issue, uninstall .NET Framework 3.5, perform the OS update, and then reinstall .NET Framework 3.5. (The last step is optional if the user does not have apps that are dependent on .NET Framework 3.5.)
• Some devices using a common 64-bit chip architecture may not be able to update to the latest OS build because of an unexpected error (E_UNEXPECTED, error code 0x8000FFFF).
• An app may become unresponsive because of an application hang end task error (0xCFFFFFFF) in the Windows firewall API library (FirewallAPI.dll), which occurs when the library is blocked on an advanced local procedure call (ALPC) while attempting to diagnose a connection failure and retrieve information during network isolation.
• Cluster Sets: A couple of key functionalities to enable end-to-end testing of Cluster Sets scenarios are not present in this build, so defer all evaluation of this scenario to a future build.
• Bugcheck during volume creation: A stop error may occur during volume creation in a cluster. The recommended workaround is, after restarting the computer, to delete the volume and try creation again.
• Bugcheck during volume repair: A stop error may occur during volume repair in a cluster. The recommended workaround is to restart the computer. No corruption or data loss is expected.
• AEP is not supported in this build.
• Clone support for Hyper-V isolated containers does not work, this can be disabled temporarily and will be fixed in subsequent Insider Preview builds. See the Insider section on Windows Containers Documentation for more details

No downtime for Hustle-As-A-Service,
Dona <3

Source