Windows 10: Top 10 Networking Features in Windows Server 2019

Brink · Jul 18, 2018

Windows Server 2019 provides regulatory compliance with highly accurate time that is traceable and UTC-compliant, including support of leap seconds.In this article, we’ll talk about the technical advances we made between Windows Server 2016 and Windows Server 2019 including true UTC-compliant leap second support, a new time protocol called Precision Time Protocol, and end-to-end traceability. But before we talk about the technical details, let’s talk about why this matters to you.

In the past, the requirement for time accuracy on Windows was limited to domain-based scenarios that required all devices to be synchronized within 5 minutes. Now worldwide government regulations (for example, US: FINRA, EU: ESMA/MiFIDII) are demanding much higher accuracy time – as stringent as 100µs (microseconds). Self-proclaimed accuracy is not enough. You must also be able to prove or “trace” your time back to an authoritative time source – More on this later. ESMA justifies the accuracy and traceability requirements in this way: “…It is also essential for conducting cross-venue monitoring of orders and detecting instances of market abuse and allows for a clearer comparison between the transaction and the market conditions prevailing at the time of their execution.”

As a result, we first brought 1 ms (millisecond) time accuracy to Windows Server 2016 meeting some of the regulatory requirements – This is supported in-market today. However, our work was not done, and so Windows Server 2019 makes improvements to comply with these regulations and allow Windows to be the preferred choice for workloads with time dependencies. Now, let’s talk a little bit about the features you’ll find in Windows Server 2019 and current Insider builds.

Important! While many of our efforts directly address concerns from regulated industries, this technology applies to any industry, application, or cloud-service with a time dependency.

There’s a lot of content in this article (because we did a lot!) – here’s a quick summary of the information you’ll see in this article

Compliant Leap Second Support

Accuracy Improvements (Precision Time Protocol, Software Time-stamping, Clock Source Stability)

Traceability (including system logging, performance counters, and our work with partners)

Click to expand...

Read more: Top 10 Networking Features in Windows Server 2019: #10 Accurate Network Time | Networking Blog

:)

Brink · Jul 18, 2018

New File Share Witness Feature in Windows Server 2019

This blog discusses a new feature in the upcoming release of Windows Server 2019. Currently, Windows Insiders receive current builds of Server 2019. We urge you to become an Insider and play a part in making Windows Server 2019 the best that it can be. To do so, go to this link and sign up.

One of the quorum models for Failover Clustering is the ability to use a file share as a witness resource. As a recap, the File Share Witness is designated a vote in the Cluster when needed and can act as a tie breaker in case there is ever a split between nodes (mainly seen in multi-site scenarios).

I don’t want to go through the list of all the requirements but do want to focus on one in particular.

The Windows Server holding the file share must be domain joined and a part of the same forest.

The reason for this is that Failover Cluster utilizes Kerberos for the Cluster Name Object (CNO) to connect and authenticate the share. Therefore, the share must reside on a domain member that is in the same active directory forest.

There are scenarios where this is not possible. These scenarios are:

No or extremely poor Internet access because of a remote location, so cannot use a Cloud Witness

No shared drives for a disk witness. This could be a Storage Spaces Direct hyper-converged configuration, SQL Server Always On Availability Groups (AG), Exchange Database Availability Group (DAG), etc. All of which do not utilize shared disks.

A domain controller connection is not available as the cluster has been dropped behind a DMZ

A workgroup or cross-domain cluster where there in no active directory CNO object

We have had a lot of requests over the years for how to get around these scenarios and there wasn’t a good story for it. Well, I am here to tell you we listened, and we produced something better than a workaround.
In comes Windows Server 2019 and the new File Share Witness feature to the rescue.

We can now create a File Share Witness that does not utilize the CNO, but in fact, simply uses a local user account on the server the FSW is connected to.

This means NO kerberos, NO domain controller, NO certificates, and NO Cluster Name Object needed. While we are at it, NO account needed on the nodes. Oh my!!

The way it works is that on the Windows Server you wish to place the FSW, create a local (not administrative) user account, give that local account full rights to the share, connect the cluster to the share.

Let’s take for example, I have a server called SERVER and a share called SHARE I want to utilize as the File Share Witness. For creating this type of File Share Witness can only be done through PowerShell. The steps for setting this up are:

Log on to SERVER and create a local user account (i.e. FSW-ACCT)

Create a folder on SERVER and share it out

Give the local user account (FSW-ACCT) full rights to the share

Log in to one of your cluster nodes and run the PowerShell command:

Set-ClusterQuorum -FileShareWitness \\SERVER\SHARE -Credential $(Get-Credential)

You will be prompted for the account and password for which you should enter SERVER\FSW-ACCT and the password.

Viola!! You are done as we just took care of all the above scenarios. The cluster will keep the name and password encrypted and not accessible by anyone.

Just as an FYI, the original demo of this feature was using a USB thumb drive holding the share plugged into a router. Not that we would recommend doing it, but does show how far you could take this.

Please try out this new feature and provide feedback through the Feedback Hub app.

Thanks,
John Marlin
Senior Program Manager
High Availability and Storage
Click to expand...

Source: New File Share Witness Feature in Windows Server 2019 | Clustering and High-Availability

Ahhzz · Jul 18, 2018

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.

Office 2019 apps will be supported on:

Any supported Windows 10 SAC release

Windows 10 Enterprise LTSC 2018

The next LTSC release of Windows Server

The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

Chino · Jul 18, 2018

Microsoft Office 2019 Will Run on Windows 10, and Only Windows 10

As reported yesterday, Microsoft changed the way how they license Windows 10 to their OEM partners. But buckle in folks, the changes just keep on coming. In what looks like an effort to push Windows 7 and Windows 8.1 owners to upgrade, Microsoft has officially announced that Office 2019 will only work on machines with Windows 10 and the next LTSC release of Windows Server. That's only the tip of the iceberg though. Unlike previous version of Office that came with 10 years of support, Office 2019's support lifecycle is shortened to five years of mainstream support and two years of extended support. Additionally, the client applications are only available with a Click-to-Run installer. However, Microsoft will continue to provide a MSI installer for the server applications.

Windows 10: Top 10 Networking Features in Windows Server 2019

Top 10 Networking Features in Windows Server 2019

Top 10 Networking Features in Windows Server 2019

Top 10 Networking Features in Windows Server 2019

Top 10 Networking Features in Windows Server 2019 - Similar Threads - Top Networking Features

Install Wireless Display feature in Windows Server 2019

Install Wireless Display feature in Windows Server 2019

Server 2019: Disabling a feature fails with STATUS_SXS_ASSEMBLY_MISSING

Server 2019: Disabling a feature fails with STATUS_SXS_ASSEMBLY_MISSING

Server 2019: Disabling a feature fails with STATUS_SXS_ASSEMBLY_MISSING

White bar in top of the screen RDS Windows Server 2019

Windows server 2019 Datacenter network errors

Windows Server 2019 Removed & Deprecated features

Windows Server 2019: removed and deprecated features

Users found this page by searching for:

top 10 networking features in windows server 2019