We still need a Windows Version for small customers getting easy connection to Azure and Office 365. So do NOT remove the Essential Role out of Version 2019.

it is better put a vides clearly about installing both CALs Users and CALs device .
I am using Windows Server 2008 on local PC , my question how to implementate RDC with CALs on which many Users can access the server concurrently, which one I choose , Users CALs or Device CALs ?

LTSB is a beautiful thing. Its what Enterprise should be. No stupid candy crush icons, no cortana, no store. Updates are larger than normal, but you dont have to deal with compatibility issues every 12 months when the OS goes through radical changes.

MS have hamstrung LTSC by removing its ability to run o365...... They have made the greatest current OS build unusable.

I understand the whole "Its for critical systems...." Adapt it to Enterprise. Give w10 the wings to rise out of the candy crush, cortana, 'access any open hotspot' ashes.....

EVERTHING WILL SAFE FOR ....

You should add Windows Server 2019, Windows 10 Enterprise LTSB / LTSC to the list of "Latest updates" below. Not everyone can distinguish the corresponding update.

Summary of new Japanese era Windows updates - KB4469068
https://support.microsoft.com/en-us/help/4469068/

I want to use Windows Server at home. But I will never pay the current amount for a license.

It would be nice to have a heavily-discounted (or free) version for individuals to use at home. I don't know what restrictions could be put in place to keep the license from being used for business, but I'm sure there's a way.

How to activate the VMs under 2016 standard? AVMA is for DC version.

The OOBE of Server 2019 1809 includes mandantory security questions for creating an initial local account.

This is apparently a left-over from Home / Pro SKU

Please release a CU to such remove consumer stuff from enterprise and server SKUs for Server 2016 / 2019.

I neither want to guess what's the favorite color of the admin that forgot the password nor where he went to school. Thank you very much!

Please post the Windows 10 version 1803 KMS Client Setup Keys.

It would be great if we could license just the virtual machines, not the entire host. There are lot of mixed environments where customers need to run several Windows Server VMs, but not all of them and not on Hyper-V. The minimum price can be licensing 16 cores, regardless of actual number of cores is less. Running just a few Windows Servers VMs in cluster environment and properly licensing them is way to expensive. This wan't push customers to cloud if that is the intention of present virtual machine licensing.

S2D is an awsome technology for small Business to create small Cluster environment without expensive SAN or NAS boxes. The datacenter licensing requirement absolutely kills the usecase for small deployments.

For me I'm not looking to install as many vm's as i can possibly do. I'm looking to allocate more ram and processing power per VM to improve performance of older apps. Microsoft penalise users in this scenario which means i have less budget to licence development servers ect. I have 2 new dual 12 core servers so 48 cores. I have 8 VM's total and unlikely to need more. However I'm forced to licence 48 cores which is not cheap. Microsoft is assuming users are going to install as many VM's as possible which is not the case.....

KMS is annoying and provides no value to the customer, only to Microsoft. It should be made drop dead easy and flawless so admins have to spend virtually no time on it both for installing and maintaining it.

The WS2012 licensing model with absolutely the same features in Standard and Datacenter Editions was the greatest thing. Virtualization rights was the only thing to think about - no headache about what is supported in which edition, what I should install, will it work etc. Please keep it like this in Windows Server 2016.

No longer are Windows 8 and Windows 10 Professional suitable for my clients. Going to Windows 2016 Standard in LTSC has solved a lot of problems. The semi-annual channel is too disruptive (creates a number of problems) in the work that traders are doing.

There is a list on MS’s website regarding Server Core, but not nano server. Can we get a list of supported features.

SILA complements the built-in SIL. After tricking the setup to successfully install on a German server using an existing database (see my install localization bug report) another issue pops up.

Executing Sop-SilAggregator in PowerShell will result in a .Net SqlClient Data Provider InvalidOperation exception referring to conversion problems from nvarchar to datetime with the value being out-of-range (see screenshot with German error message).

This raises suspicion to be a German vs. US date format issue ("23.10.2017 22:44:00" German vs. "10/23/2017 10:44:00pm" US vs. "2017-10-23 22:44:00" ISO).

https://gntmrw-am3pap001.files.1drv.com/y4mQHyfRpoGlajra0F8TFHjtfjQM8wm-ijcChA-Q-O7ABZYM_GfnoSM09fsLdH8YdnG_v05o5v7PhZ5FBD_6BrExpqULVfJj1KCJh3YBM-n03BsLc7wsHt2Jmk_-EkoZ7Ek23pA_04nw1ntgs7O0z2V5cIC1t2L1v2q8656QXZ8Ytuna6qrl3cz4Iji2OFjP46sEnLaXZBOYcqYDJAytaib8g?width=994&height=834&cropmode=none

SILA complements the built-in SIL but it seems the MSI (https://www.microsoft.com/en-us/download/details.aspx?id=49046) though having a German download and UI is not working properly on German (and maybe other localized) servers.

The setup breaks with an error regarding "NT AUTHORITY\SYSTEM" which is localized to "NT-AUTORITÄT\SYSTEM" on German servers.

Inspecting the MSI also shows one SQL script having "NT AUTHORITY\SYSTEM" in hardcoded form.

https://gnt7uq-am3pap001.files.1drv.com/y4mtP2tOncjwsBEW4a23maV1aDWnWw4i9lN3gUP63UIEy1YNfHy8wQNipzec6JCKcvyVJT3GM7pTusRXzg6LP6gHYun0Ar7u85Z1LlUVP4jfkdtTGnGsh4KAdnJqEFaIJk0lb_6t3oFKlLHqpJBwb821PLZIPstwrNT5pdxNe4UX919JeqhOsBGxOHaVRc0Ja6d1z71gkdd2UTf4pGRLdNQBQ?width=1047&height=880&cropmode=none