Posts

Want users to preview changes before your PowerShell function makes them? Learn how to add -WhatIf and -Confirm support using SupportsShouldProcess and ShouldProcess() blocks with practical examples.

Ever wondered how much of your S2D Storage Pool is actually available? This PowerShell function shows total size, allocated space, Mirror/Parity available capacity, and reserved space—locally or across multiple clusters.

Cache stats matter! Learn how to monitor your S2D write cache allocation using Windows Server 2019’s Cluster Performance History or Windows Server 2016’s performance counters, plus a handy PowerShell function.

If you’re experiencing Event ID 5120, CSV timeouts, or VM pauses when patching S2D clusters, Microsoft has identified the cause. Here’s the workaround using Storage Maintenance Mode and ready-to-use CAU pre/post scripts.

WS2016Lab by Jaromir Kaspar lets you deploy an entire nested S2D lab on any Hyper-V host—even a Windows 10 laptop! Perfect for testing Windows Server 2019, S2D, Storage Replica, Project Honolulu, and many more scenarios.

The best information on S2D often comes from blog posts rather than documentation. Here’s my curated list of essential reads covering storage pools, SSD endurance, volume resiliency, and why you shouldn’t use consumer SSDs.

Discovered a bug where physical disks stay in maintenance mode after applying September CU to S2D clusters. This breaks CAU patching and causes capacity issues. Here’s how to recover and avoid the problem.

Discovered a bug where S2D incorrectly sets the Performance Tier mediatype to SSD even when SSDs are assigned to cache. Learn how to check your configuration and fix it with a simple PowerShell command.

SCVMM 2016 brought great features like Standard-to-Logical Switch conversion and S2D support. But there’s still room for improvement—here’s my wishlist including a Getting Started GUI, advanced Storage QoS, and native Hyper-V Replica support.

Discover the magical Get-StorageQoSFlow command in Windows Server 2016 that reveals IOPS, latency, and bandwidth stats for all VHD(x)s on your cluster—perfect for finding those VMs burning through your storage.