Here are few detailed posts about Windows Server 2016 which will be out this year. Many new features and enhancements is planned. The latest release is the Windows Server 2016 TP5 and it contains all features which shall appear in the final release. In the other words, there should be no major changes in the final release.
Licensing changes might be more important for clients using high core CPUs in their servers. Basically, the systems with more than 8 cores per physical CPU will require an additional licensing … Core licenses will be sold in packs of 2 for incremental licenses. And those additional packs will be needed to cover what’s above of 8 cores per physical processor…
So while Microsoft was always saying that VMware has higher licensing costs this might actually no longer be the case when Windows Server 2016 will hit the market (second half of 2016). The coverage so far, stay tuned for more.
- Windows Server 2016 Active Directory Installation Guide [beginner step-by-step Guide]
- Windows Server 2016 Technical Preview 5 Released [Detailed]
- Windows Server 2016 – Free E-book [Free Download]
- Windows Server 2016 Active Directory Improvements – [details]
- Windows Server 2016 – What is the difference between Standard And Datacenter Edition – [features compare]
- Windows Server 2016 Hyper-V on VMware – [Guide]
Overview of the VM creation wizard in VMware vSphere 6 (through vSphere C# client)….. you'll find the whole process in the post (link above).
The OS is already listed as “Windows Server 2016″….
Yes, there should be a licensing change in the upcoming release, but nothing is sure just yet.
This is just a guess calculation based on the information we have – change on the core where when you have over 8 cores per CPU… read the details in the post.
- Windows Server 2016 Hyper-V allows add/remove RAM while VM is running – This is a lab post where I tested the “hot-add” RAM. n fact you can adjust the amount of memory assigned to a virtual machine while it’s running, even if you haven’t enabled Dynamic Memory. This works for both generation 1 and generation 2 virtual machines.
New VM configuration file format for Hyper-V – (VMCX) Virtual machines now have a new configuration file format which is designed to increase the efficiency of reading and writing virtual machine configuration data. It’s also designed to reduce the potential for data corruption in the event of a storage failure. The new configuration files use the .VMCX file extension for virtual machine configuration data and the .VMRS file extension for runtime state data.
