Category: Nano Server

Last updated by at .

Windows Server Insider Preview Build 17074

Sneak Peak of Windows Server 1803 (RS4) – Windows Server Insider Preview Build 17074

Yesterday, Microsoft announced a new Windows Server Insider Preview Build (17074) which will be released as the next Semi-Annual Channel release for Windows Server. This release will likely be called Windows Server 1803 (Codename: Restone 4), which is aligned to the Windows Client releases.

Microsoft talked about improvements in the next Windows Server releases and the investments in Containers and Storage Spaces Direct at Microsoft Ignite 2017, and we already got some early Windows Server Insider Preview builds to see what is coming next. The official list is not to big right now, but we can expect Microsoft to add and announce more features in the comment weeks and months.

What is new in Windows Server 1803 (RS4)

  • Storage Spaces Direct (S2D)
    • Microsoft adds Data Deduplication support Storage Spaces Direct and ReFS
    • Microsoft removed the requirement for SCSI Enclosure Service (SES) on the hardware, which enables more hardware to work with S2D
    • Storage Spaces Direct adds support for Persistent Memory (Storage Class Memory), which brings very fast and very low latency storage to S2D. The prices for this devices is still pretty high, but we can expect this to change in the future and we can also see them as a great use as caching devices.
    • Storage Spaces Direct now also supports Direct-connect SATA devices to AHCI controller, which also make more hardware work with S2D
    • CSV Cache is now enabled by default, which delivers an in-memory write-through cache that can dramatically boost VM performance, depending on your workload.
  • Failover Clustering
    • Azure enlightened Failover Cluster – This is a very exciting feature if you run Windows Server Failover Clusters in Microsoft Azure. This feature will let the Windows Server cluster know if there is Azure host maintenance going on and will exclude the specific cluster node from placing workloads on it.

      By making high availability software running inside of an Azure IaaS VM be aware of maintenance events of the host, it can help deliver the highest levels of availability for your applications.

  • Container
    • Microsoft promised to add more Container feature and provide updated Windows Server Container Images. One feature which made it already into this and early Preview builds is a long waited feature which caused some confusion before. Developers can now use localhost or loopback (127.0.0.1) to access services running in containers on the host.
  • Other Improvements

As mentioned before we can expect Microsoft to add and announce new feature for the next Windows Server release in the next couple of weeks and months.

How to download the Windows Server Insider Preview

You can download the Windows Server Insider Previews from the Windows Server Insider Preview download page. If you are not yet an Insider, check out how to get one on the Windows Insider for Business portal.

Careful, this is pre-release software and it is not supported in production.

Test and Provide Feedback to Windows Server

For Microsoft it is very important that they get feedback about the latest releases. To send feedback use the Feedback Hub application in Windows 10, and choose the Server category with the right subcategory for your feedback.

 

 

 



Tar and Curl on Windows 10

Today Microsoft released Windows 10 Insider Preview Build 17063 which includes a lot of great new features like Timeline, Activities, Microsoft Edge, Windows Subsystem for Linux improvements and much more. But Microsoft also included something for IT Pros and Developers. After the OpenSSH client and the OpenSSH server. Microsoft brings two new command-line tools for the Windows toolchain: curl and bsdtar. These tools are very well known tools in the open source world. Including them in Windows should make Windows even a better development platform.

 

Tar on Windows 10
Tar: A command line tool that allows a user to extract files and create archives. Outside of PowerShell or the installation of third party software, there was no way to extract a file from cmd.exe. We’re correcting this behavior 🙂 The implementation we’re shipping in Windows uses libarchive.

curl on Windows 10

Curl: Another command line tool that allows for transferring of files to and from servers (so you can, say, now download a file from the internet).

Why this, so first of all you have PowerShell which has similar functionality, but PowerShell is not always available (Think about Nano Server container images where you have not the Full .Net Framework available). Secondly Developers which come from other operating systems are already familiar with these tools and they can use, as they would on their “old” operating system.

If you want to know more, check out Craig Wihite’s (Microsoft) blog post: Tar and Curl Come to Windows!

As mentioned this is included in the Windows 10 Insider Preview Build 17063 and should ship to production customers in the next Windows 10 release, which might be Windows 10 (1803).



Thomas Maurer Speaking

Speaking at HPE Discover 2017 Madrid

Today I am happy to announce that I have the honor to speak at HPE Discover in Madrid next week. In a presentation together with HP Enterprise I will talk about how HPE and Microsoft improve the Hybrid Cloud experience using Microsoft Azure Stack.

HPE Discover 2017 Madrid Azure Stack

Building your Azure hybrid cloud business is easier when you work with Hewlett Packard Enterprise

With the release of Azure Stack, now is the time to develop your hybrid cloud business. Hewlett Packard Enterprise and Microsoft have partnered to make it easy for you to accelerate your business by offering Azure-consistent services with HPE ProLiant for Microsoft Azure Stack. Come hear about HPE’s solution for Azure Stack and how HPE can help you develop and grow your Azure business. This session is designed for HPE partners.

I hope to see you next week in Madrid, if you have the chance, step by the HIAG Data booth and ask for me.



Windows Server Semi-annual Channel Overview

Windows Server – Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC)

I was already blogging about the new Windows Server servicing options including the Long-Term Servicing Channel (LTSC) and the new Semi-Annual Channel (SAC) options. It seems that there is a lot of confusion about what the purpose and the advantages of the Semi-Annual Channel releases. With that blog post I will try to explain what both servicing options are and when which servicing option should be used. Especially since SAC releases, like Windows Server 1709, will only be available as Windows Server Core. Spoiler alert: Windows Server Semi-Annual Channel releases are not for everyone and everything.

Windows Server Long-Term Servicing Channel (LTSC)

The Long-term Servicing Channel is the release model you’re already familiar with (currently called the “Long-term Servicing Branch”) where a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support, 5 years of extended support, and optionally 6 more years with Premium Assurance. This channel is appropriate for systems that require a longer servicing option and functional stability. Deployments of Windows Server 2016 and earlier versions of Windows Server will not be affected by the new Semi-annual Channel releases. The Long-term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.

Example for Long-Term Servicing Channel releases

  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

Long-Term Servicing Channel installation options

  • Windows Server Core
  • Windows Server with Desktop Experience
  • Windows Server Core as a container Image

Use cases for Long-Term Servicing Channel releases

As use cases for the Long-Term Servicing Channel releases you can basically count everything in which need predictable long term support, do not support Windows Server Core and where you don’t use the new features included in the Semi-Annual Servicing Channel releases and you prefer less updating.

  • General Purpose File Server – Traditional information worker file server which need long term support
  • Legacy Software – Legacy software which do not support server core
  • Static Software – Software which does not leverage any of the new features of Semi-Annual Channel releases, which need predictable long term support
  • Legacy Hardware – End of life hardware
  • SQL Server – Traditional databases with long lifecycles which need predictable long term support
  • Active Directory and other infrastructure roles – which benefit from long term support

Semi-Annual Channel (SAC)

Windows Server 1709

The Semi-annual Channel releases will deliver new functionality for customers who are moving at a “cloud cadence,” such as those on rapid development cycles or service providers keeping up with the latest Hyper-V and Storage investments. Windows Server products in the Semi-annual Channel will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release.

Most of the features introduced in the Semi-annual Channel will be rolled up into the next Long-term Servicing Channel release of Windows Server. The editions, functionality, and supporting content might vary from release to release depending on customer feedback.

The Semi-annual Channel will be available to volume-licensed customers with Software Assurance, as well as via the Azure Marketplace or other cloud/hosting service providers and loyalty programs such as MSDN.

Example for Semi-annual Channel releases

  • Windows Server 2016 Nano Server
  • Windows Server 1709
  • Windows Server 1803

Semi-annual Channel installation options

  • Windows Server Core
  • Windows Server Core Container Image
  • Windows Server Nano Server Container Image

Use cases for Semi-annual Channel releases

Use cases for the Semi-annual Channel releases right now are application and services which leverage new feature very quickly and go with cloud cadence.

  • Lift and Shift applications into Containers
  • New cloud-based applications
  • Applications which can be quickly and easily redeployed
  • Linux containers on Windows Server
  • Hyper-V and Cluster nodes for Hyper-converged scenarios
  • Hyper-V hosts which are benefiting from continuous innovation

Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC) Overview

To make it a little easier, here is a quick overview of the two servicing channels:

 Long-Term Servicing ChannelSemi-Annual Channel
Recommend ScenariosGeneral purpose File Servers, SQL Servers, Active Directory and other infrastructure rolesContainerized applications and container hosts, Hyper-converged hosts benefiting form faster innovation
New ReleasesEvery 2-3 yearsEvery 6 months
Support5 years of Mainstream support +5 years of Extended support18 months
EditionsAll available Windows Server editionsStandard and Datacenter
Installation OptionsServer Core and Server with Desktop ExperienceServer Core only
LicensingAll customer through all channelsSoftware Assurance and Cloud customers only

Conclusion

As you can see, Windows Server Semi-annual channel are not designed for everyone. And if you don’t feel comfortable with Windows Server Core (btw you should check out Microsoft Project Honolulu), the fast release cadence or the short support life cycle you should go with the Windows Server Long-Term Servicing Channel. You will not lose anything you had today, you still will get new versions every 2-3 years with all the options you had today. If you need the fast innovation and you get something out of the new features the Semi-annual channel will provide you with 2 releases a year. But make sure, that your deployment, configuration and management is automated, otherwise you will suffer from the fast release cadence. I have three other very important points I want to make sure you know about:

  • Not all your servers have to go with LTSC only or SAC only – as long as you have the right licensing in place you can choose for each server, which ever fits your needs best.
  • You don’t have to switch now – you can also decided to go with LTSC today and switch to a SAC release as soon as you benefit from it. You can also switch back to LTSC from SAC if you don’t like it. (With Switch I mean redeploy)
  • Upgrades are not in-place – It doesn’t matter which servicing channel you are using, servers need to be redeployed. (Not like in Windows 10 where you can leverage in-place upgrades)

I hope this helps to understand the point about Windows Server Semi-Annual Channel (SAC) vs Long-Term Servicing Channel (LTSC). The Semi-Annual Channel releases are a new offer from Microsoft for customers to get their hands on new features much quicker, this offers a huge benefit if you can make use of it. But Microsoft is not forcing you to use SAC, LTSC for some scenarios and customers is still the better option. So both solutions are having huge value in different scenarios.



Docker Windows Server Container Images

Docker Container Images for Windows Server 1709 and new tagging

Last week Microsoft announced new Windows Server 1709 and the new Windows Server 1709 container images. The new container images in Windows Server version 1709 are highly optimized, especially in size. So for example the new Nano Server Container Image in 1709 is 5x smaller than the Nano Server Container Image in Windows Server 2016.

Microsoft also made some changes to tagging which is interesting.

If you want to use the latest images of the container images based on the Windows Server 2016 (which is in the Long-Term Servicing Channel, LTSC) you just run:

This will give you the latest images of the Windows Server and Nano server container images. If you want to run a specific patch level of the Windows Server 2016 (LTSC)m images, you can run the following:

Docker Windows Server Container Images Size

If you want to use the new Windows Server 1709 container images from the Semi-Annual Channel you can run the following

and again you cans also add a specific base OS container image by using a KB number:

If you already tried out the new container images during the development using the insider images, they still existing:

However, I am not sure what the plan for the insider images is going forward.



How to run Docker Linux Container on Windows Server 1709

As mentioned Microsoft released the final version of Windows Server 1709 in the last week. Windows Server 1709 brings a couple of new improvements, especially in the container space. Microsoft and Docker are working on bringing Linux Container support to Windows Server, so you can now run Windows and Linux Container at the same time on a Windows Server Container Host running Windows Server 1709 or Windows 10 with the Fall Creators Update (1709).

In this post I want to show you how you setup up a Container Host to run Windows and Linux Containers at the same time using Docker.

Create Container Host Virtual Machine

Enable Nested Virtualization

If you run Docker on a physical server you can skip this step. If you want to run Docker Containers using Linux inside a Virtual Machine running on Hyper-V you should enable Nested Virtualization for the Container Host Virtual Machine. You can do this by running the following command:

if you want to do this on a Hyper-V Server in Azure, check out this post: How to setup Nested Virtualization in Microsoft Azure

Install Docker Enterprise Edition Preview on Windows Server 1709

First you have to install Docker Enterprise Edition Preview on your Windows Server 1709 container host. You can install the Docker EE preview using PowerShell package management, using the following commands:

As mentioned this is a preview version of Docker EE which enables a bunch of new features, to run Docker in production environments please use Docker EE 17.06.

Enable Docker Linux Containers on Windows

The preview Docker EE package includes a full LinuxKit system (13MB) for use when running Docker Linux containers. To enable this use the following command:

to disable it again use the following:

Run Linux Docker Container on Windows Server

Docker Ubuntu Container on Windows Server

Now you are able to run Linux Containers on Windows Server 1709.

for fun you can also run Nyancat!

Docker Nyan Cat on Windows Server

Things are still in preview, so don’t expect to work 100% 🙂



Microsoft Ignite Speaker

Speaking at Microsoft Ignite 2017

I just came back from Experts Live Europe 2017 in Berlin where I was speaking about Container, Azure Stack and Windows Server. Now I already started preparing for the largest Microsoft Conference in September. I am happy to announce that I will be speaking at the Microsoft Ignite 2017 Conference in Orlando Florida.

Thomas Maurer Speaking

This is a huge honor and I am happy to speak in several sessions. The first one I want to announce is my Theater Session about Windows Server 2016:

Lessons learned from deploying Windows Server 2016

Join this session to learn about how to deploy Windows Server 2016 in your datacenter. Learn about real-world experience for Storage Spaces Direct, Nano Server, Hyper-V, and a lot more.

I will announce other sessions soon as they are public available. I hope you join Microsoft Ignite and see you in my sessions.