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 as well as Server Core in all 18 server languages, as well as a new build of the next Windows Server Semi-Annual Channel release. Please also refer to this recent blog announcement about updates to the Windows Server Semi-Annual Channel.
There are two major areas that we would like you to try out in each preview release and report back any issues:
- In-place OS Upgrade (from Windows Server 2012 R2, Windows Server 2016)
- Application compatibility – please let us know if any server roles or applications stops working or fails to function as it used to
What’s New in the Latest Build
Click here to see the full list of new features introduced in earlier builds.
Failover Clustering: File Share Witness
One of the witness options available for failover clustering, File Share Witness, has two new enhancements.
The first enhancement blocks the use of a Distributed File System (DFS) share as a location. Adding a File Share Witness (FSW) to a DFS share can cause stability issues for your cluster, and this configuration has never been supported. So, we added logic to detect if a share uses DFS, and if DFS is detected, Failover Cluster Manager blocks creation of the witness and displays an error message about not being supported.
The second enhancement enables use of an FSW for several scenarios that were previously not supported:
- Absent or extremely poor Internet access because of a remote location, preventing the use of a cloud witness.
- Lack of shared drives for a disk witness. This could be a Storage Spaces Direct hyperconverged configuration, a SQL Server Always On Availability Groups (AG), or an Exchange Database Availability Group (DAG), none of which use shared disks.
- Lack of a domain controller connection due to the cluster being behind a DMZ.
- A workgroup or cross-domain cluster for which there is no Active Directory cluster name object (CNO). Find out more about these enhancements in the following posts in Server & Management Blogs: Failover Cluster File Share Witness and DFS New File Share Witness Feature in Windows Server 2019
Failover clustering: Moving Clusters between domains
Moving a cluster from one domain to another has always been a daunting task because you must destroy the cluster to move it. Depending on the roles in the cluster, that role must also be removed and recreated. The following are two common scenarios:
- Company A purchases Company B and must move all servers to Company A's domain
- Main office builds a cluster and ships it to another location
- We have added two new PowerShell commandlets to quickly take you from one domain to another without the need to destroy it. For more information about this new capability, see How to Switch a Failover Cluster to a New Domain in Server & Management blogs.
Storage Replica
Storage Replica (SR) was first released as a technology for Windows Server 2016 Datacenter Edition. SR enables synchronous and asynchronous block replication of volumes between servers or clusters for disaster recovery. SR also enables you to create stretch failover clusters that span two sites, with all nodes staying in sync.
Beginning with Windows Server 2019, responding to customer requests, we've added the following improvement to SR:
- Storage Replica Standard. SR is available on Windows Server 2019 Standard Edition, not just on Datacenter Edition. When installed on servers running Standard Edition, SR has the following limitations:
- SR replicates a single volume instead of an unlimited number of volumes.
- Volumes can have one partnership instead of an unlimited number of partners.
- Volumes can have a size of up to 2 TB instead of an unlimited size.
We will continue to listen to your feedback and evaluate these settings through our telemetry during Insider previews of Windows Server 2019. These limitations may change several times during the preview phase and at RTM.
For more information about Storage Replica, visit http://aka.ms/StorageReplica.
Remote Desktop Session Host (RDSH)
RD Session Host is a Remote Desktop Services role service that enables users to share Windows-based programs or the full Windows desktop. Users can connect to an RD Session Host server to run programs, save files, and use network resources on that server. Because of a bug, the RDSH role was missing in previous releases of Windows Server 2019 – this build fixes that.
Available Content
Windows Server 2019 Preview is available in ISO format in 18 languages. This build and all future pre-release builds will require use of activation keys during setup. The following keys allow for unlimited activations:
|
Datacenter Edition
|
6XBNX-4JQGW-QX6QG-74P76-72V67
|
|
Standard Edition
|
MFY9F-XBN2F-TYFMP-CCV49-RMYVH
|
Windows Server vNext Semi-Annual Preview is available in English only, in ISO or VHDX format. The images are pre-keyed - no need to enter a key during setup.
This build will expire July 2nd, 2018.
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.
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 Server category and then the appropriate subcategory for your feedback. Please indicate what build number you are providing feedback on. We also encourage you to visit the Windows Server Insiders space on the Microsoft Tech Communities forum to collaborate, share and learn from experts.
Known issues
- In‑place OS upgrade: Domain Controllers. During an in-place OS upgrade, Active Directory (AD) Domain Controllers (DC) might not be upgraded correctly. To insure recoverability in the case of failure, back up any AD DC before performing an in-place OS upgrade.
- Editing or creating policies for AppLocker can cause the MMC snap-in to crash when generated rules for a packaged app.
- After upgrading the operating system, the AppX database may have corrupted entries, which causes problems for components that use those entries. An administrator might notice this issue when generating packaged app rules or when managing an installed package, resulting in error messages such as "This wizard has encountered a fatal error and cannot continue" and "MMC has detected an error in a snap-in and will unload it."
Terms of Use
All pre-release software made available to you via the Windows Server Insider program are governed by the Insider Terms of Use, which takes precedence over any license agreement that may be in the product.
