OK, I accept that, but why is not supported or I can't do an upgrade in place. so I can upgrade in place from: 2012 R2 --> 2016 2012 R2 Core --> 2016 Core But I cant upgrade in place from 16299.0 to 16299.15 or either 16299.15 to 16299.15 in place doesn't work
OK, how to get this one? cs_windows_server_version_1709_x64_dvd_100090905.iso I want to extract some language files...
Hey guys, do anyone now how to active this kind of GUIless Server core? Without GUI, i could even not run MSToolkit! How could i active this stuff?
It's just the Desktop Shell not present but the GUI is there, you can run notepad and all other stuffs, just run the MSToolkit from the command line, it will execute.
I am experiencing a need to reboot all ver.1607 servers every 3 weeks or so. I haven't determined if the flaw is in 1607 as a Hyper-V host, or as a VM, or both. I just know if I wait too long between reboots it takes *forever* to do anything on those machines. Every patch Tuesday I am hoping the problem is fixed, but it becomes painfully apparent before next month that it hasn't.
I have the same on Core (no GUI) Server 2016 VM on Hyper-V 2012 R2 Reverted to nightly reboot to have it going On same Hyper-V full GUI Server 2016 VMs are working perfectly fine. Almost like the luck of GUI strains the OS even more
I'm seeing the same behavior on my hyper-v servers. There doesn't seem to be any correlation between the log files and the behavior - just that the server itself becomes 'unavailable' and reboots take forever. Last time a reboot occurred, it sat at "Installing Updates" for literally 40 minutes, despite SSD's being used for the OS drive. 1607 is broken. All the hoopla that Microsoft made when they announced the new lifecycle for Server seems to only be for their Core editions, and not the editions that are actually being used in production environments.
must be hyper v bug with server 2016 as my main os server 2016 that i use with latest cu 1770 no problems; does this happen on vmware if any using on that virtual otherwise latest cu in testing is 1914 or later for december 2017 patch tuesday
just checked so installing on wu the latest cu 1914 for 1607 on my server 2016 as it was released today officially
RE: 1607 slowness, gets worse as days go by between reboots I'm installing the 14393.1914 (KB4051033) hoping it will help. There is a specific fix for something that sounds like it might be the issue I've encountered. The thing it fixes has been broken since September 2016. I guess I will know in a month or so. RE: 1709 GUI, needed for Exchange and other server softwares that won't run on Core I am surprised that nobody has yet built some scripts to do the following tasks (I can design the process but no clue about writing the code to do it): 1. Extract the "with GUI" components from a 1607 Server. 2. Extract the same/similar components from a 1709 Windows Pro/Enterprise where RSAT 1709 has been installed. 3. Take the two things above and combine them so you have the newest 1709 "with GUI" components with the 1607 version of anything that is missing. 4. Take all of that and apply it to a 1709 Server.
i don't think it is that easy as it is not like adding store app as the gui is built into much of the OS and underlying parts and services
Hence my statement about having "no clue" - my hope is that one of the smart people here will take it as a challenge! Having "no clue" means I am quite possibly wrong, but my speculation is it can't be much harder than the project to add WMC back to Windows 10.