Windows 10: Windows Server 2019 Removed & Deprecated features

WinClub · Mar 7, 2019

Just like Windows 10 for consumers, Microsoft keeps building new features and functionality for its server editions. Apart from adding, functions are also removed and deprecated. Here is a list of Windows 10 Server 2019 Removed & Deprecated features Windows [...]

This post Windows Server 2019 Removed & Deprecated features is from TheWindowsClub.com.

read more...

Ahhzz · Mar 7, 2019

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.

LEOPEVA64 · Mar 7, 2019

Features being removed or deprecated in Windows 10 version 1809

It's funny that Microsoft has not included disk cleanup in the list of "Features we’re no longer developing", in another blog they already announced that this feature will be "deprecated", although in this list this clarification is made:

PS, @Brink, just out of curiosity, why did you add the word "deprecated"? in the original text it doesn't appear.

Brink · Mar 7, 2019

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

Windows 10: Windows Server 2019 Removed & Deprecated features

Windows Server 2019 Removed & Deprecated features

Windows Server 2019 Removed & Deprecated features

Windows Server 2019 Removed & Deprecated features

Windows Server 2019 Removed & Deprecated features - Similar Threads - Server 2019 Removed

Windows Server 2022 Features removed or deprecated

List of Features to be Deprecated or Removed in Windows 11

These are the deprecated and removed features of Windows 11

Features removed and deprecated in Windows 10 version 1909

Windows 10 version 1903: removed and deprecated features

Windows Server 2019: removed and deprecated features

Windows 10 version 1809: removed and deprecated features

Windows 10 v1809 removed or deprecated features list

Deprecated and Removed Features in Windows 10 Version 1803