Windows 2016 Stability for Hyper V

It is getting better and better

some people will say stable but there are still some issues on VM

example
If you attempt to run Microsoft Exchange 2016 CU3 on Windows Server 2016 on VM, you will experience errors in the IIS host process W3WP.exe. There is no workaround at this time. You have to postpone deployment of Exchange 2016 CU3 on Windows Server 2016 until a supported fix is available.

I consider 2012r2 to be more stabil even as 2016 has Great new features.

Cheers

We run 2016 hyper-v since it came out - no problems yet. Two hosts, about 12 machines with different OS's.

Thr qureshi, do you have any link for me? I was about to install Exchange 2016@ server16 on it, soon.

@McKnife
I believe thr qureshi is talking about this url
I also installed exchange 2016 on server 2016 and after Windows updates my box blewup and we started again with 2012r2, no issues.

@McKnife
Here is an example article
https://www.petri.com/exchange-2016-says-no-to-windows-2016

Here you can find some Best Practice Exchange 2016 virtualization
http://searchexchange.techtarget.com/tip/Best-practices-for-Exchange-2016-virtualization

Host machine requirements for Exchange 2016 virtualization
https://technet.microsoft.com/en-us/library/jj619301(v=exchg.160).aspx

Thanks Tom. That issue was fixed months ago, though: https://blogs.technet.microsoft.com/exchange/2016/12/13/released-december-2016-quarterly-exchange-updates/

Dear All,

Thanks for all the response however, I believe the original question is not related to hosting exchange on Hyper V but if Windows 2016 is stable enough to build a private cloud based on Hyper V clustering using Storage spaces direct

Request someone to clarify over the same

Regards

Thank you Andrew you clarified my questions.

Thank you everyone for all the responses.

Thank you Andrew for the reply.

Agree with you Lee, Though we are running 2016 under test environment I just wanted to make sure if it is not creating major stability issues as we are intending to go for 2016 in production environment

Thanks

We have quite a few clusters deployed on Server 2016 with little to no issue though MPIO seems to be a bit buggy.

We deployed our first Exchange 2016 on Server 2016 with .NET 4.6.2 and are experiencing out of memory issues with 8GB of virtual RAM on our VMs. We've had to bump the VMs up to 12GB to keep things happy. It seems to be a bug somewhere in .NET. We have Exchange 2016 running on 2012 R2 with 8GB vRAM with no issues.

Speaking from personal experience and customer feedback, I can tell that Windows 2016, and Hyper-V 2016 in particular, is stable enough to upgrade from Windows 2012R2. I've noticed a few minor issues with adding storage to Failover Cluster (local disks were added along with shared storage) but they got it fixed in previous patches.

To sum up, Windows Server 2016 and Hyper-V 2016 is a tremendous step forward and, really, there is no need to avoid upgrading due to "instability concerns".