Select Page

Configuring a Hyper-V Host with PowerShell DSC (Part 1)

Hello, my name is Michael Godfrey and I am a Platform’s Premier Field Engineer (PFE) at Microsoft. I have been a Fabric Administrator for the past few years and have made it a habit of building quite a few Hyper-V ... continue reading

What’s New in Windows Server 2016 version 1709 #Winserv #Hyperv #Containers

Application containers and micro-services The Server Core container image has been further optimized for lift-and-shift scenarios where you can migrate existing code bases or applications into containers with minimal changes, and it’s also 60% smaller. The Nano Server container image ... continue reading

Container Storage Support with Cluster Shared Volumes (CSV), Storage Spaces Direct (S2D), SMB Global Mapping

By Amitabh Tamhane Goals: This topic provides an overview of providing persistent storage for containers with data volumes backed by Cluster Shared Volumes (CSV), Storage Spaces Direct (S2D) and SMB Global Mapping. Applicable OS releases: Windows Server 2016, Windows Server ... continue reading

DSC Resource Kit Release March 2017

We just released the DSC Resource Kit! This release includes updates to 10 DSC resource modules, including 19 new DSC resources. In these past 6 weeks, 155 pull requests (the most ever!) have been merged and 71 issues have been ... continue reading

Deploying IaaS VM Guest Clusters in Microsoft Azure

Authors: Rob Hindman and Subhasish Bhattacharya, Program Manager, Windows Server In this blog I am going to discuss deployment considerations and scenarios for IaaS VM Guest Clusters in Microsoft Azure. IaaS VM Guest Clustering in Microsoft Azure A guest cluster ... continue reading

Troubleshooting Hangs Using Live Dump

In this blog post https://blogs.msdn.microsoft.com/clustering/2014/12/08/troubleshooting-cluster-shared-volume-auto-pauses-event-5120/ we discussed what a Cluster Shared Volumes (CSV) event ID 5120 means, and how to troubleshoot it. In particular, we discussed the reason for auto-pause due to STATUS_IO_TIMEOUT (c00000b5), and some options on how to ... continue reading