Hello Windows Insiders!
Today we are pleased to release a new build of the Windows Server vNext Long-Term Servicing Channel (LTSC) release that contains both the Desktop Experience and Server Core in all 18 server languages, as well as a new build of the next Windows Server Semi-Annual Channel release in English. In addition, the first preview of Microsoft Hyper-V Server is included with this build.
In each preview release, there are two major areas that we would like you to try out:
In-place OS Upgrade (from Windows Server 2012 R2, Windows Server 2016 or a previous preview build). Build-to-Build upgrade is also supported.
Application compatibility – please let us know if any server roles or applications stops working or fails to function as it used to. Please report any issues you find.
Click here to see the full list of new functionality introduced in earlier builds of Windows Server.
Group Managed Service Accounts We’ve improved the scalability and reliability of containers that use group managed service accounts (gMSA) to access network resources. You should see fewer authentication errors when using a single gMSA with multiple container instances. Additionally, you no longer need to set the container’s host name to be the same as the gMSA. We also fixed a bug that prevented you from using gMSAs with Hyper-V isolated containers.
New base image: Windows
We’re adding a new base image to the Windows Server container collection. In addition to NanoServer and WindowsServerCore container images, the new Windows image is now available. This image carries even more components than its NanoServer and ServerCore siblings, meaning it can support applications that have additional API dependencies. To learn more and get started, go to https://aka.ms/windowscontainer.
- Windows Server 2019 Preview is available in ISO format in 18 languages, and in VHDX format in English only. This build and all future pre-release builds will require use of activation keys during setup. The following keys allow for unlimited activations:
- Windows Server vNext Semi-Annual Preview The Server Core Edition is available in English only, in ISO or VHDX format. The images are pre-keyed – no need to enter a key during setup.
- Microsoft Hyper-V Server
- Server Core App Compatibility FoD Preview
- Windows Admin Center Preview 1806
Symbols are available on the public symbol server – see Update on Microsoft’s Symbol Server blog post and Using the Microsoft Symbol Server. As before, matching Windows Server container images will be available via Docker Hub. For more information about Windows Server containers and Insider builds, click here.
This build will expire December 14th, 2018.
How to Download
To obtain the Insider software downloads, registered Insiders may navigate directly to the Windows Server Insider Preview download page. If you have not yet registered as an Insider, see GETTING STARTED WITH SERVER on the Windows Insiders for Business portal.
We value your feedback!
Use your registered Windows 10 Insider device and use the Feedback Hub application. In the app, choose the Windows Server category and then the appropriate subcategory for your feedback. In the title of the Feedback, please indicate the build number you are providing feedback on in this format:
[Server #####] Title of my feedback
- [NEW] If a system is upgraded from preview release build 17692 to a more recent preview release, System Insights encounters errors when parsing or visualizing the prediction results. To resolve this issue, follow the instructions on System Insights known issues, or clean install a newer preview release.
- [NEW] Get-HgsAttestationBaselinePolicy, PowerShell cmdlet that generates an attestation baseline policy, fails with an error: “Failed to retrieve TPM information.”
- [NEW] On a recent preview release of Server Core, the Advanced Query Syntax (AQS) parser may fail if the default language and locale are changed to something other than US English. If the AQS parser is not working, search functionality in Exchange does not work.
- Creating or modifying environment variables by using setx on a system running NanoServer container fails. On an affected system, setx requires a specific path in the registry, HKCU\Environment\, to exist by default. You can work around this issue by changing where the variable is stored in the registry, or you can add the expected registry path before executing setx commands. To specify that the variable be set for system-wide use in HKLM rather than in HKCU, the default, add the /M switch to a setx command. To instead add the expected registry path, run reg add HKCU\Environment before executing setx commands.
- The Virtual Machine Management Service (VMMS) may experience an error, APPLICATION_FAULT_INVALID_POINTER_READ, in Cluster Manager.
- Editing or creating policies for AppLocker can cause the MMC snap-in to crash when generated rules for a packaged app.
No downtime for Hustle-As-A-Service,