Contents of this articleThis two-part post will look at the networking enhancements coming in Server (and by extension, to Windows 10 since they share the same codebase).
Users who have LIKED this post:Use Windows Admin Center with PowerShell
Answer “Y” for Yes of course, and close this shell when it’s done.
Again, answer “Y” for Yes of course. This will then spit out a lengthy EULA:
Answer “Y” for Yes or the installation will abort.
After signing in:
And after clicking the “Full Desktop” icon:
- HTTP/2
- Cubic
- LEDBAT
- Data Plane Development Kit
- Kubernetes
- Azure Network Adapter
- Keeping time
Regardless of when you're looking to implement the new version, be aware that on top of the 'visible' improvements, they’ve done a lot of work under the hood. New features include Storage Spaces Direct support for storage-class memory, Server Core Feature on Demand (FoD), Cluster Sets, and moving failover clusters between domains, containers, and Docker support along with Storage Migration Service (SMS) and System Insights.
Windows Server 2019 Backgrounds
In this first part, we'll look at HTTP/2, Cubic, and Low Extra Delay Background Transport (LEDBAT) for congestion management, Data Plane Development Kit (DPDK) for high-throughput applications, networking for Kubernetes on Windows, the Azure Network Adapter, and timekeeping. In the next part, we'll cover software-defined networking (SDN) and Hyper-V networking improvements.
HTTP/2 ^
The older version of HTTP (1.1) came out in 1999, so when HTTP/2 emerged in 2015, a lot had happened in between. As a quick overview of what the new protocol brings, HTTP/2 multiplexes TCP (and TLS when using HTTPS) requests over a single TCP connection whereas 1.1 requires a dedicated connection for each request. It also compresses the header using HPACK, reducing the amount of data exchanged between servers and clients; see more here. For security, it supports only TLS 1.2 and newer, and it blacklists older cipher suites.
Windows Server 2016 and the corresponding version of Windows 10 implemented HTTP/2 on both the server (IIS) and the client side.
Like so often when you have a migration period from an older protocol to a newer version, there are trade-offs and workarounds to deal with the legacy way of doing things. So Windows Server 2019 brings connection coalescing to mitigate sharding. Because the number of connections controlled the overall speed in HTTP 1.1, site owners sometimes had several domains appear as one to force more connections, something no longer required in HTTP/2.
But a large proportion of websites still do sharding, so 2019 (both Edge and IIS) will share a single TCP connection for domains that have the same certificate. Windows Server 2019 also fixes a problem where incorrect cipher suite ordering could cause disconnections by not processing the ciphers in the order they're listed and instead picking the most secure one supported by both client and server.
Cubic ^
Managing congestion on networks is crucial to overall performance, and the way this occurs has been changing over the years as the internet (and WAN networks) have moved from slow, unreliable high-latency networks to high-speed, reliable connections that still have high latency because you can't pay to increase the speed of light.
Cubic, now the default in Windows, manages congestion better by ramping up to higher speeds faster, leading to an overall throughput improvement.
Comparison of throughput between Cubic and the older Windows default (image source Microsoft)LEDBAT ^
Making sure different types of network traffic play nicely together on your tubes is an ongoing challenge for network admins. Traffic such as patches, backup, and other 'non-time-critical' data needs to coexist with more business-critical data. We can use several approaches today. For example, Background Intelligent Transfer Service (BITS) that Windows Update applies uses an adaptive bit rate to adjust, but it can take up to two seconds for each adjustment.
System Center Configuration Manager (SCCM) on the other hand uses a throttling setting where you can set a distribution point (DP) to use only 40% of the available bandwidth, for example. The problem here is that if there's no other traffic, you'll only ever get 40%, and if there's a lot of other important traffic, it might need more than the 60% you've shared.
The answer is LEDBAT, which you could enable in Windows Server 2016 through a registry hack, but that version didn’t officially support it whereas 2019 fully supports it. The key is that LEDBAT monitors latency very closely, and latency is a key metric when it comes to user experience.
You enable LEDBAT (and switch from Cubic) with this PowerShell cmdlet:
I followed the validation guide for LEDBAT with two Windows Server 2019 virtual machines (VMs). You can see two continuous pings below: in the beginning without any network traffic, then with the CtsTraffic open-source network traffic generator active between the two VMs. Notice how the latency without LEDBAT for the first ping shoots up. Had this been a user's experience in an application, it would have been terrible. The second screen capture is with LEDBAT, and you can see that the latency stays reasonable because LEDBAT controls the network usage of the traffic.
Network latency without LEDBATEnabling LEDBATNetwork latency with LEDBATData Plane Development Kit ^
The move from HD to 4K streaming means a change from about 1.5 Gb/s to 12 Gb/s per stream. Add to that many other high-throughput, latency-sensitive workloads such as real-time gaming, edge computing, and augmented/virtual reality streaming, and the need for fast networking has never been greater.
The Linux Foundation's Data Plane Development Kit (DPDK) project aims to provide fast packet processing and direct access to network interface controller (NIC) resources for user-mode applications. Microsoft is bringing DPDK to Windows Server (and to Azure) in conjunction with Cisco, helping to move the industry from the current serial digital interface (SDI) to an IP-based networking infrastructure with the open-source Herisson platform.
While Microsoft has laid the foundation in Windows Server, the technology requires NIC driver support called poll mode drivers (PMDs). Superior drummer 3 demo download. Currently Intel has drivers, with Chelsio and Cavium 'coming soon.'
Kubernetes ^
Containers are becoming the default for creating new software, and Kubernetes is becoming the de facto standard for orchestrating those containers. Through Microsoft's semi-annual channel of Windows Server (1709 and 1803), they've released various pieces of the required networking for Kubernetes. They project official support for Windows Server 2019 as a platform to run Kubernetes with the GA release of Kubernetes 1.13.
You can use network policy to control network traffic and isolate containers, deployments to monitor the health of your containers, services to define load-balanced pods to handle incoming traffic, and connecting application services to help services in Windows and Linux containers to find each other. Here's a video that shows some of these features in action. This is all coming through Container Network Interface (CNI) plug-ins such as Flannel, Wincni, etc.
As a side note, I should point out that deploying and running Kubernetes on your own hardware is not for the faint of heart. A better option may be to adopt a managed platform such as Azure Kubernetes Service (AKS). We're still waiting for Windows Container support in AKS though.
Azure Network Adapter ^
Speaking of Azure, Windows Server offers an interesting way to configure isolated servers (think branch offices) directly to Azure using a point-to-site VPN. Windows Admin Center takes care of the configuration for you, and if you've already registered with Azure, the configuration is literally a couple of clicks.
Note that this feature negates having a network expert configuring a VPN router device for site-to-site (S2S) VPN, having a public fixed IP address, or forking out for an expensive ExpressRoute connection. Be aware though that if you don't have a VPN gateway already configured for the Azure Virtual Network you're connecting to, the wizard in Windows Admin Center will create one for you (which can take 20 to 30 minutes). But it'll incur a monthly cost (depending on the SKU you select in the wizard). It'll also create self-signed certificates (or you can supply your own from a certificate authority), configure auto-reconnect, and it's persistent even if no user is logged on to the server.
Configuring the Azure Network AdapterKeeping time ^
If you're running an ordinary Windows network, and your biggest challenge is keeping all the computer clocks within five minutes of each other so as to not cause Active Directory issues (except it doesn't anymore), this section isn't for you. If, however, you have regulations that demand accurate time (healthcare is one sector; financial services another), say to within 100 microseconds, read on. Windows Server 2016 brought one-millisecond accuracy, but Windows Server 2019 adds compliant leap-second support, further accuracy improvements, and traceability.
Leap seconds are added to Coordinated Universal Time (UTC) to compensate for the earth's rotation slowing down; starting in 1972, they've added one about every 18 months. It's not just a matter of adding the second; it's also about how you do it. Some systems simply slow down their clocks around the time (the end of June or December), called leap second smearing, which is now frowned upon. Windows Server 2019 just adds the second at the right time.
While Network Time Protocol (NTP) continues to be the default, a newer protocol is Precision Time Protocol (PTP). NTP works through the clock in a system synchronizing with a time server, but it assumes that any delays the network adds in between the client and the server are symmetrical, something unlikely when you're looking for very accurate time. PTP on the other hand asks each network device (and the Windows Server 2019 networking stack) to add the latency it adds to the processing into the timing measurements.
Another way Server 2019 keeps the clock accurate over time is to take each packet's value, eliminate outliers, and average the values. The granularity for the system to change the clock has also progressed from 6.4 microseconds per second to 100 nanoseconds per second.
The final part of accurate time is being able to report on it to regulators. Windows Server can participate in data collection by third-party services that will gather time information from all network equipment involved.
In the next part, we'll dive into Hyper-V networking improvements along with SDN improvements in Windows Server 2019.
Win the monthly 4sysops member prize for IT pros
3+Users who have LIKED this post:
Related Posts
Install and use tcpdump for network analysisA version of the Windows NT operating system | |
Developer | Microsoft |
---|---|
OS family | Microsoft Windows |
General availability | October 2, 2018; 8 months ago[1] |
Latest release | 10.0.17763 / October 2, 2018; 8 months ago[2] |
Latest preview | 10.0.17744 / August 28, 2018; 10 months ago[3] |
Platforms | x64 |
Kernel type | Hybrid (Windows NT kernel) |
Default user interface | Windows shell (Graphical) Microsoft PowerShell (Command line) |
Preceded by | Windows Server 2016 (2016) |
Official website | microsoft.com/windowsserver |
Support status | |
|
Windows Server 2019 is the latest version of the serveroperating system by Microsoft, as part of the Windows NT family of operating systems.
Development and release[edit]
Windows Server 2019 was announced on March 20, 2018, and the first Windows Insider preview version was released on the same day.[5] It was released for general availability on October 2, 2018.[6]
On October 6, 2018, distribution of Windows version 1809 (build 17763[7]) was paused while Microsoft investigated an issue with user data being deleted during an in-place upgrade.[8] It affected systems where a user profile folder (e.g. Documents, Music or Pictures) had been moved to another location, but data was left in the original location.[9] As Windows Server 2019 is based on the Windows version 1809 codebase, it too was removed from distribution at the time,[10] but was re-released on November 13, 2018.[11] The software product life cycle for Server 2019 was reset in accordance with the new release date.[10]
Features[edit]
The witcher 3 wiki. Windows Server 2019 has the following new features:[12][13][14]
Windows Server 2019 Background Design
- Support for Kubernetes (Beta)
- Other GUI new features from Windows 10 version 1809.
- Storage Spaces Direct
- Storage Migration Service
- Storage Replica
- System Insights
- Improved Windows Defender
Version history[edit]
Version | Release date | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Old version, no longer supported: 10.0.17623 | March 20, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17627 | March 24, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17666 | May 15, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17692[15] | June 19, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17709[16] | July 10, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17713[17] | July 16, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17723[18][19] | July 31, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17733[20][21] | August 14, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17738[22][23] | August 21, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version, no longer supported: 10.0.17744 | August 28, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Current stable version:10.0.17763[2] | October 2, 2018 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Old version Latest version Future release |
See also[edit]
References[edit]
- ^https://cloudblogs.microsoft.com/windowsserver/2018/10/02/windows-server-2019-now-generally-available/
- ^ ab'Windows Server 2019 – now generally available!'. Retrieved October 2, 2018.
- ^'Announcing Windows Server 2019 Insider Preview Build 17744 - Windows Experience Blog'. blogs.windows.com. Retrieved August 29, 2018.
- ^'Microsoft Product Lifecycle'. Microsoft Support. Microsoft.
- ^Introducing Windows Server 2019 – now available in preview – Windows Server Blog
- ^Windows Server 2019 – now generally available!
- ^What's New in Windows 10 for developers, build 17763
- ^'Microsoft yanks buggy Win10 1809 upgrade, leaving zapped files in its wake'. ComputerWorld. Retrieved October 18, 2018.
- ^'Updated version of Windows 10 October 2018 Update released to Windows Insiders'. Microsoft. Retrieved October 18, 2018.
- ^ abWindows 10 Update History
- ^Resuming the rollout of the Windows 10 October 2018 Update
- ^What’s New in Windows Server 2019 Insider Preview Builds | Microsoft Docs
- ^https://www.networkworld.com/article/3265052/data-center/top-6-features-in-windows-server-2019.html
- ^New Windows Server 2019 test build adds more clustering features | ZDNet
- ^Announcing Windows Server 2019 Insider Preview Build 17692 - Windows Experience Blog
- ^Announcing Windows Server 2019 Insider Preview Build 17709 - Windows Experience Blog
- ^Announcing Windows Server 2019 Insider Preview Build 17713 - Windows Experience Blog
- ^Announcing Windows Server 2019 Insider Preview Build 17723 - Windows Experience Blog
- ^Microsoft releases new Windows Server 2019 test build, plus Windows 10 'Redstone 5' ISOs | ZDNet
- ^Announcing Windows Server 2019 Insider Preview Build 17733 - Windows Experience Blog
- ^Microsoft releases Windows Server and SDK Preview build 17733 [Update] - Neowin
- ^Announcing Windows Server 2019 Insider Preview Build 17738
- ^'Windows Server 2019 Insider Preview build 17738 is out - here's what's new'. Neowin. Retrieved August 26, 2018.
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Windows_Server_2019&oldid=895061385'
There are several good writeups of the HTML5 WebClient already, like Freek Berson’s: http://microsoftplatform.blogspot.com/2018/01/html5-client-for-microsoft-remote.html
This post will simply show the installation on a Windows Server 2019 Remote Desktop Services deployment.
The Microsoft guide for installing the client can be found here: https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin
So lets start by following the guide on Windows Server 2019.
First of all, find the certificate that is used by your RD Connection Brokers and export this to a BASE64 encoded .cer file.
Open an elevated PowerShell prompt and update the PowerShellGet module as you would on Windows Server 2016:
Answer “Y” for Yes of course, and close this shell when it’s done.
Open a new elevated PowerShell prompt and install the RDWebClientManagement module:
Again, answer “Y” for Yes of course. This will then spit out a lengthy EULA:
Answer “Y” for Yes or the installation will abort.
When it’s done installing, run the following command:
Remember that RD Connection Broker .cer file? Skyrim survival mode mod. Import it now:
Finally, publish the RDWebClient package to enable it:
Open a HTML5 compatible browser, and navigate to https://<your rdwebaccess url>/RDWeb/Webclient/
After signing in:
And after clicking the “Full Desktop” icon:
So yes, the current version (October 6th 2018) also works on a Windows Server 2019 Remote Desktop Services deployment.
For a quick Step-By-Step guide for deploying Remote Desktop Services on Windows Server 2019, check this post: Step by Step Windows 2019 Remote Desktop Services – Using the GUI
Arjan
Advertisements
25+ years experience in Microsoft powered environments.Enjoy automating stuff using powershell.In my free time (hah! as if there is any) I used to hunt achievements and gamerscore on anything Xbox Live enabled (Windows Mobile, Windows 8, Windows 10, Xbox 360 and Xbox One).Recently I picked up my Lego addiction again.
Tagged with: RD Web Access, Remote Desktop Services, Windows 2019, Windows 2019 Remote Desktop
Posted in Remote Desktop, Step-by-Step guide, Windows 2019
-->Posted in Remote Desktop, Step-by-Step guide, Windows 2019
Applies To: Windows Server 2019
Locks and Limits
Locks and Limits | Windows Server 2019 Standard | Windows Server 2019 Datacenter |
---|---|---|
Maximum number of users | Based on CALs | Based on CALs |
Maximum SMB connections | 16777216 | 16777216 |
Maximum RRAS connections | unlimited | unlimited |
Maximum IAS connections | 2147483647 | 2147483647 |
Maximum RDS connections | 65535 | 65535 |
Maximum number of 64-bit sockets | 64 | 64 |
Maximum number of cores | unlimited | unlimited |
Maximum RAM | 24 TB | 24 TB |
Can be used as virtualization guest | Yes; 2 virtual machines, plus one Hyper-V host per license | Yes; unlimited virtual machines, plus one Hyper-V host per license |
Server can join a domain | yes | yes |
Edge network protection/firewall | no | no |
DirectAccess | yes | yes |
DLNA codecs and web media streaming | Yes, if installed as Server with Desktop Experience | Yes, if installed as Server with Desktop Experience |
Server roles
Windows Server roles available | Role services | Windows Server 2019 Standard | Windows Server 2019 Datacenter |
---|---|---|---|
Active Directory Certificate Services | Yes | Yes | |
Active Directory Domain Services | Yes | Yes | |
Active Directory Federation Services | Yes | Yes | |
AD Lightweight Directory Services | Yes | Yes | |
AD Rights Management Services | Yes | Yes | |
Device Health Attestation | Yes | Yes | |
DHCP Server | Yes | Yes | |
DNS Server | Yes | Yes | |
Fax Server | Yes | Yes | |
File and Storage Services | File Server | Yes | Yes |
File and Storage Services | BranchCache for Network Files | Yes | Yes |
File and Storage Services | Data Deduplication | Yes | Yes |
File and Storage Services | DFS Namespaces | Yes | Yes |
File and Storage Services | DFS Replication | Yes | Yes |
File and Storage Services | File Server Resource Manager | Yes | Yes |
File and Storage Services | File Server VSS Agent Service | Yes | Yes |
File and Storage Services | iSCSI Target Server | Yes | Yes |
File and Storage Services | iSCSI Target Storage Provider | Yes | Yes |
File and Storage Services | Server for NFS | Yes | Yes |
File and Storage Services | Work Folders | Yes | Yes |
File and Storage Services | Storage Services | Yes | Yes |
Host Guardian Service | Yes | Yes | |
Hyper-V | Yes | Yes; including Shielded Virtual Machines | |
Network Controller | No | Yes | |
Network Policy and Access Services | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience | |
Print and Document Services | Yes | Yes | |
Remote Access | Yes | Yes | |
Remote Desktop Services | Yes | Yes | |
Volume Activation Services | Yes | Yes | |
Web Services (IIS) | Yes | Yes | |
Windows Deployment Services | Yes* | Yes* | |
Windows Server Essentials Experience | Yes | Yes | |
Windows Server Update Services | Yes | Yes |
*WDS Transport Server is new to Server Core installations in Windows Server 2019 (also in the semi-annual channel starting with Windows Server, version 1803)
Features
Windows Server Features installable with Server Manager (or PowerShell) | Windows Server 2019 Standard | Windows Server 2019 Datacenter |
---|---|---|
.NET Framework 3.5 | Yes | Yes |
.NET Framework 4.6 | Yes | Yes |
Background Intelligent Transfer Service (BITS) | Yes | Yes |
BitLocker Drive Encryption | Yes | Yes |
BitLocker Network Unlock | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
BranchCache | Yes | Yes |
Client for NFS | Yes | Yes |
Containers | Yes (Windows containers unlimited; Hyper-V containers up to 2) | Yes (all container types unlimited) |
Data Center Bridging | Yes | Yes |
Direct Play | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Enhanced Storage | Yes | Yes |
Failover Clustering | Yes | Yes |
Group Policy Management | Yes | Yes |
Host Guardian Hyper-V Support | No | Yes |
I/O Quality of Service | Yes | Yes |
IIS Hostable Web Core | Yes | Yes |
Internet Printing Client | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
IPAM Server | Yes | Yes |
iSNS Server service | Yes | Yes |
LPR Port Monitor | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Management OData IIS Extension | Yes | Yes |
Media Foundation | Yes | Yes |
Message Queueing | Yes | Yes |
Multipath I/O | Yes | Yes |
MultiPoint Connector | Yes | Yes |
Network Load Balancing | Yes | Yes |
Peer Name Resolution Protocol | Yes | Yes |
Quality Windows Audio Video Experience | Yes | Yes |
RAS Connection Manager Administration Kit | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Remote Assistance | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Remote Differential Compression | Yes | Yes |
RSAT | Yes | Yes |
RPC over HTTP Proxy | Yes | Yes |
Setup and Boot Event Collection | Yes | Yes |
Simple TCP/IP Services | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
SMB 1.0/CIFS File Sharing Support | Installed | Installed |
SMB Bandwidth Limit | Yes | Yes |
SMTP Server | Yes | Yes |
SNMP Service | Yes | Yes |
Software Load Balancer | Yes | Yes |
Storage Replica | Yes | Yes |
Telnet Client | Yes | Yes |
TFTP Client | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
VM Shielding Tools for Fabric Management | Yes | Yes |
WebDAV Redirector | Yes | Yes |
Windows Biometric Framework | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Windows Defender features | Installed | Installed |
Windows Identity Foundation 3.5 | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Windows Internal Database | Yes | Yes |
Windows PowerShell | Installed | Installed |
Windows Process Activation Service | Yes | Yes |
Windows Search Service | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Windows Server Backup | Yes | Yes |
Windows Server Migration Tools | Yes | Yes |
Windows Standards-Based Storage Management | Yes | Yes |
Windows TIFF IFilter | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
WinRM IIS Extension | Yes | Yes |
WINS Server | Yes | Yes |
Wireless LAN Service | Yes | Yes |
WoW64 support | Installed | Installed |
XPS Viewer | Yes, when installed as Server with Desktop Experience | Yes, when installed as Server with Desktop Experience |
Features available generally | Windows Server 2019 Standard | Windows Server 2019 Datacenter |
---|---|---|
Best Practices Analyzer | Yes | Yes |
Constrained Storage Replica | Yes, (1 Partnership and 1 Resource Group with Single 2TB volume) | Yes, unlimited |
Direct Access | Yes | Yes |
Dynamic Memory (in virtualization) | Yes | Yes |
Hot Add/Replace RAM | Yes | Yes |
Microsoft Management Console | Yes | Yes |
Minimal Server Interface | Yes | Yes |
Network Load Balancing | Yes | Yes |
Windows PowerShell | Yes | Yes |
Server Core installation option | Yes | Yes |
Nano Server installation option | Yes | Yes |
Server Manager | Yes | Yes |
SMB Direct and SMB over RDMA | Yes | Yes |
Software-defined Networking | No | Yes |
Storage Management Service | Yes | Yes |
Storage Spaces | Yes | Yes |
Storage Spaces Direct | No | Yes |
Volume Activation Services | Yes | Yes |
VSS (Volume Shadow Copy Service) integration | Yes | Yes |
Windows Server Update Services | Yes | Yes |
Windows System Resource Manager | Yes | Yes |
Server license logging | Yes | Yes |
Inherited activation | As guest if hosted on Datacenter | Can be host or guest |
Work folders | Yes | Yes |