@r3dpand4 said in Configuring Multi-Resilient Volume with Storage Spaces:

Should be noted that any server running 1709 cannot be added to S2D pools as it stands currently since it's not considered production ready....

Correct. S2D is gone from non-GA WS2016.

https://docs.microsoft.com/en-us/windows-server/get-started/server-1709-relnotes

Storage Spaces Direct

Storage Spaces Direct is not included in Windows Server, version 1709. If you call Enable-ClusterStorageSpacesDirect or its alias Enable-ClusterS2D, on a server running Windows Server, version 1709, you will receive an error with the message "The requested operation is not supported". It is also not supported to introduce servers running Windows Server, version 1709 into a Windows Server 2016 Storage Spaces Direct deployment.

good article thanks and handy script

Is that different than hardware defined storage? It has all those issues, too.

Also, in the followup post on the blog they actually do another interesting lab that requires this first bit.

@darek-hamann said in Configuring Windows Server 2016 Core. Part 2: Hyper-V role installation:

@dashrender

This is actually a great article! It simplifies the procedure of installing a Hyper-V role from a GUI free Windows 2016 Core setup.

That's nice, but again - WHY. This is not the way you should NORMALLY install Hyper-V because now you have a license tied to the hardware. I get that there are reasons, but I'm asking what they are.

That's a very good post that covers information people don't often think about after deploying vCenter. Additionally, it's something helpful when studying for the VCP-DCV. Thanks for sharing!

For the TLDR

0_1493385958696_upload-54e54758-7d9b-44bc-9f06-2826daed2714

This is great one! Hope more Hyper-V related stuff is coming 🙂