@travisdh1 I'm surprised too, but I guess. I think they're probably counting things like rogue USB devices left lying around and such as part of the malicious group.

@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.

@dafyre Exactly 🙂 That is the reason why this feature was created

good article thanks and handy script