Windows 10: Windows Server 2019

JimKeeb · Nov 13, 2018

My family is using Windows 2016 Essentials. What is our upgrade path to Windows 2019 Server? Our server has 2 cores.

:)

Ahhzz · Nov 13, 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.

Brink · Nov 13, 2018

Remote Desktop Services 2019 generally available Windows Server 2019

We released the newest version of Remote Desktop Services (RDS), RDS 2019, on October 2, 2018. RDS 2019 builds on the strong foundation of RDS 2016, letting you rapidly deploy on-premises or in the cloud. RDS 2019 is generally available with Windows Server 2019.

RDS 2019 will give customers the opportunity to leverage fantastic enhancements that make it the optimal version of RDS, to date, with several areas of innovation to improve the administrative and client experiences.

We brought innovation centered around three areas in RDS 2019 – Simplify IT management, User experience, and Improved security.

Simplify IT management

We have time and again heard from customers that license management should focus on simplification to scale deployments. Over the past few years, we have focused on improving management of Remote Desktop (RD) Licensing servers and entitlement through Active Directory (AD).

Now, you will be able to leverage high availability RD Licensing servers with forward-compatibility for future versions of Windows Server to enable easier management of licenses from a variety of RDS releases.

We have also made it easier to manage licenses for your employees by bringing the ability for the RD Licensing servers to update RDS user Client Access Licenses (CALs) into AD objects without accessing AD directly.

Lastly, we added perfmon (Performance Counters) APIs to provide partners an easy way to access data to build monitoring dashboards and deliver a consistent user experience.

User experience

We have also invested in providing an enhanced user experience where end users will be able to leverage desktops and apps through RDS 2019 to maximize productivity.

To start, we have added modern notifications for RemoteApp in the Action Center to improve productivity with applications like Microsoft Outlook.

We have improved upon innovations in Discrete Device Assignment in RDS 2016 to bring better security, virtual machine (VM) isolation, and performance for your graphic-intensive workloads. These improvements in GPU virtualization technologies will result in reduced network traffic and smooth video playback.

In addition to the GPU virtualization technology, we added high-level redirection of built-in or attached video cameras to deliver optimized video stream at higher frame rates in new and legacy remote applications and desktops. Users can now have a better experience with video-intensive interactions.

Lastly, we have reduced CPU usage on the client and server and bandwidth with better image quality to bring a faster end-to-end web client experience.

Security

One of our primary goals as the Remote Desktop Services product team is to help improve your security posture for your desktop and app virtualization environments. We have improved security through several enhancements.

With Windows Admin Center integration, it is easy to consolidate all local and remote server management into a single pane.

We have brought several Windows Defender optimizations for multi-session to give you more confidence in bringing a secure, scalable and cost-effective desktop experience to end users.

We also added web client support for Single Sign-on (SSO) to deliver a streamlined authentication experience for users connecting via the web client.

A few additional features include easy-to-configure DTLS-based encryption, all of which, work toward providing a trusted end-to-end RDS deployment.

Deploying RDS 2019 on Azure

We recognize that giving you the ability and making it easier to deploy RDS on Azure gives you a lot of flexibility, scalability, security and several other advantages of Azure. To improve flexibility and ease of cloud adoption, we also support hybrid deployments where the infrastructure roles can be in Azure while the host Virtual Machines (VMs) can be on-premises.

Key enhancements for deploying RDS 2019 on Azure include using Azure Key Vault for simplified certificate management and using Azure SQL DB for the RD licensing high-availability feature.

Lastly, later in October we will announce the availability of Remote Desktop Services (RDS) subscriptions through the Cloud Solution Provider (CSP) program. The availability of RDS in CSP addresses customer needs for additional cost-effective solutions that support desktop and app virtualization.

With RDS Subscriptions, partners can directly sell RDS subscriptions through our CSP program, eliminating the extra step of customers and partners acquiring different licenses through various programs. With this model, customers can enjoy a faster licensing cycle due to CSP integration with other Microsoft licenses including Windows Server, SQL Server, and Office to make it easy for partners to simplify the buying process.

For more technical information on RDS 2019, please refer to the RDS documentation page.
Download Windows Server 2019 that includes RDS 2019 now.

Frequently asked questions

Q: When will I be able to download the final version of Windows Server 2019?
A: Windows Server 2019 that includes RDS 2019 became generally available on October 2, 2018. It is available for evaluation and download through Volume Licensing Service Center (VLSC).

Q: Is Remote Desktop Server included in Windows Server 2019?
A: Yes. Remote Desktop Server 2019 will be a server role in Windows Server 2019.

Q: How do we view this announcement with Windows Virtual Desktop announcement at Ignite?
A: This is the most up-to-date version of RDS to enable running the latest on-premises multi-session virtualization available with Windows Server. Windows Virtual Desktop is a desktop and application virtualization service on Azure. Read the blog post Microsoft 365 adds modern desktop on Azure for more information.

Q: How is RDS on Azure different from Windows Virtual Desktop?
A: RDS is the ideal on-premises desktop and application virtualization solution, with a Windows Server operating system to provide a multi-session desktop experience. When deployed on Azure, you can scale your deployment and manage RD infrastructure roles in your own subscription. Windows Virtual Desktop enables customers to deliver a brand-new multi-session capability with a full Windows 10 experience, with the scale and flexibility of Azure. With this new service, Microsoft manages the infrastructure roles. Windows Virtual Desktop will be available for public preview later this calendar year. For more information, please visit the product page.

Q: Will there be a path to go from RDS to Windows Virtual Desktop?
A: Yes, we are developing Azure documentation guidance for this migration path as Windows Virtual Desktop gets closer to public preview later in calendar year 2018.
Click to expand...

Source: Remote Desktop Services 2019 generally available with Windows Server 2019 - Windows Server Blog

Brink · Nov 13, 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

Windows 10: Windows Server 2019

Windows Server 2019

Windows Server 2019

Windows Server 2019

Windows Server 2019 - Similar Threads - Server 2019

RDP Issues and Ghost User Sessions - Windows Server 2019

RDP Issues and Ghost User Sessions - Windows Server 2019

installing SQL Server 2019 and 2016 on an HP ProBook 450 G9 laptop !

installing SQL Server 2019 and 2016 on an HP ProBook 450 G9 laptop !

Windows 2019 Server Updates Failing error code 0x80070003

Windows 2019 Server Updates Failing error code 0x80070003

Download FOD Package for Enabling SNMP Services in Windows 2019 server

Download FOD Package for Enabling SNMP Services in Windows 2019 server

windows server 2019 phone activation issue