I recently downloaded Server 2016 from my VL portal, got it installed/configured for testing, and I just thought I would share my discontent with the product (or unimpressed is likely a better wording). This does not require any input from anyone, or have any questions that need to be answered.

I dislike that they removed the ability to convert from GUI to Core, or Core to GUI. That was a great feature! Sorry I am not a PowerShell guru, but these feature allowed me to be flexible. Add this back in! I read your reasoning online. Find a way to overcome it; it worked before, you can make it work again.

Why all the extra services installed by default (even if disabled / set to manual)?

Xbox Live Game Save
Xbox Auth Manager
AllJoyn Router
ActiveX Installer
MapsBroker (download service)
Windows Mobile Hotspot Service

...the list goes on. Why? Just why? This isn't needed... All you need is what is required. Even the print spooler service, why is still even there by default? Trim the server install down to what is required to run itself. Let me install what I want from there. I don't even want to see it as an item/service/other, unless I install the feature/role.

What about HA/Clustered Printing? Why do I have to use Hyper-V? I haven't actually checked this, but I know this was the only 'supported' way to get HA printing in Server 2012R2.

My next complaint isn't huge, but why would you include IE11, but not Edge by default? This isn't an issue, just a source of confusion since it is in Windows 10 by default for both.

When will you stop doing what you want, and focus on doing what we, the admins, want?

Just me complaining.

In my opinion Microsoft is following a wrong paradigm when it comes to providing server admins with context based background information while working on a server desktop.
It is regarding the use of referrals in the interface to sources on the internet in order to provide the administrator with more information. I know that, when Microsofts recommendation is followed and the core version is chosen, this is no issue at all, but since several server implementations still require the full graphical version (e.g. Exchange Server 2016) and many IT organisations still choose to use RDS for server administration, many admins will still be faced with this phenomenon.

An example: While on the desktop in an interactive session of a Windows Server 2016 machine, I click start -> settings (leftmost part of the startmenu), in the settings window I click “update & security”. Right at the bottom there is a link “Learn more”. Clicking on this link causes Internet Explorer to open in IEESC mode. The page that IE tries to open however needs Java script to be enabled, and without Java script enabled, no content is shown.

And this is my main concern: The Windows interface provides the admin with links that encourage enabling features that undermine security best practices.

What makes it even worse: there is no alternative way to obtain the information via another PC (e.g. from a RD session, copying the link and paste it in the browser of your admin PC), so the admin is forced to configure the server in a manner that conflicts with security best practices (best is to avoid using a browser at all, is my opinion, but apparently that is not Microsofts point of view).

I would like to encourage Microsoft to move to text-only referrals/urls or provide at least a way to copy the link to the clipboard. If that is not feasible somehow, make the web pages behind these links as plain as possible, so there is no need for browser extensions on the server.

Ich habe ein paar Ideen um Windows 10 und Windows 10 Mobil noch besser zu machen.

1. Das größte Problem im Windows 10 und Windows 10 Mobil ist das automatische Update ohne Angabe der Dateigröße und der Zeit für die Installation. Update von Build oder App-Update legt Rechner für Stunden lahm!

2. Windows 10 Mobil hängt sich auf und das Smartphone sollte zurückgesetzt werden. Alle Daten auf dem Smartphone sind weg, sowas geht nicht in der Arbeitswelt.

3. Die Sicherheit ist bei Firmen sehr wichtig, darum muss klar sein wo die Daten liegen und teilweise kommt eine Cloudlösung nicht in Frage, weil die Daten nichts auf einem fremden System zu suchen haben. Man kann durch einen Hackerangriff oder Mitarbeiterzugriff alle Daten zentral finden, was unerwünscht ist! Auch die Datenleitungen werden massiv benutzt da die Daten immer von der Cloud abgefragt werden müßen!

4. Was unterscheidet der Microsoft Mobil von Apple, Samsung usw. Da muss schon eine tolle App daher, der Dock-PC ist hier schon ein gute Idee, aber wieso nur mit Office-Produkte usw...

Für diese Punkte usw. hätte ich ein paar Ideen für Microsoft :-)

Mit freundlichen Grüßen

Cross-posted from Technet forums:

I think we've identified a bug in Server 2016. Long story short:
1. Open lusrmgr.msc
2. Set an active users' properties to require password change at next logon
3. Reboot (or just logout, haven't tried that)
4. Press Ctrl+Alt+Del to logon, enter user's current password
5. Press Cancel when informed you need to change your password
6. Press Ctrl+Alt+Del again, enter user's current password, proceed 7. with password change (notice username is blank at this point)
8. Password gets changed but you are returned to the change password screen with no way to go back or proceed
9. Forced reboot appears to be the only way out but you can logon normally after this

We discovered this when running through the sysprep process and had bypassed the standard OOBE set password screen. Windows Server still wants the password set at first logon so we end up setting the password in the standard password change method instead of via OOBE. I realized this wasn't just a problem with our OOBE process though because just checking the box in user properties will make it happen. Tested this on the built-in Administrator account and a standard account I created after the fact.

Obviously most people won't hit the cancel button here, but we did it just playing around and discovered this.

First of all, sorry my poor English. Recently my customer bought two Windows Server 2016 Standard and I have a general group policy to disable autoplay and autorun in all computers in this network. Of course, I have an Active Directory implemented with two DCs, one with W2K8R2 and another with W2K12R2. I´ve downloaded the new ADMX files for Windows Server 2016 and Windows 10 "www.microsoft.com/en-us/download/details.aspx?id=53430" and created a Central Store and I made all steps recomended by Microsoft. This Group Policy works well in all versions of Windows 2012/8.1 and below, but doesn´t work in Windows version 2016/10. I reaserched in the Internet for a similiar problem and I didn´t find anything about this. Does anybody have a clue for this problem??? Thanks for any help.