Windows Server 2019 build 17650

10.0.17650.1001.rs_prerelease.180414-2140
	Build of Windows Server 2019
OS family	Windows 10 (NT 10.0)
Version number	10.0
Build number	17650
Build revision	1001
Architecture	x64
Build lab	rs_prerelease
Compiled on	2018-04-14
Expiration date
Timebomb	2018-07-02 (+79 days)
SKUs
	Standard Server; Standard Server Core; Datacenter Server; Datacenter Server Core
About dialog

Windows Server 2019 build 17650 is the third Insider Preview build of Windows Server 2019. It was released on 24 April 2018.

New features and changes[edit | edit source]

File Share Witness, which is a feature for failover clustering, has two new enhancements in this build. The first one blocks the use of a Distributed File System (DFS) share as a location. If you attempt to add a File Share Witness to a DFS share, Failover Cluster Manager stops the "witness" from being created and it displays an error message instead about it not being supported. The second enhancement enables the use of an FSW for several scenarios that were previously not supported in older versions of the operating system. These include cases where Internet access is absent or extremely poor because of a remote location, lack of shared drives for a disk witness, lack of a domain controller connection due to the cluster being behind a DMZ (a buffer zone between a completely untrusted network and a trusted network), and a workgroup or cross-domain cluster where an Active Directory cluster name object (CNO) is not present.
Added two new PowerShell commandlets to quickly migrate a failover cluster from one domain to another without having to destroy it.
Storage Replica is now available on the Standard SKU. Compared to the Datacenter SKU, this feature has limitations, including the ability to replicate only one volume, only have one partnership on a volume, and a 2TB size limit on a volume instead of an unlimited size.
Re-added the Remote Desktop Session Host (RDSH) role after it was absent in the previous builds because of a bug.

Active Directory domain controllers may not upgrade correctly during an in-place OS upgrade.
If you create or edit a policy for AppLocker, the associated MMC snap-in can crash when generated rules for a packaged app.
After an upgrade, the AppX database may have corrupted entries, which can cause problems for components that use said entries.