Issues getting output from Hyper-V Tools or Failover Cluster Manager

Hello, a few weeks ago i had some issues at a client where Failover Cluster Manager would not repsond when trying to anything. It would just hang and eventually fail.

Even Hyper-V manager or the normal Powershell tools where hanging and taking forever. Doing a simple Get-VM, Get-Storagejob or any powershell command related to Hyper-V or Storage Spaces Direct would hang for ages, and maybe give out a response after 10-20 min.

Read more

Adding a new Cache device and you setup your cluster with -CacheDeviceModel and now the new device wont be used as Cache?

Hello Everyone, it’s been a while since my last blog post. So i thought id share something i came over in our Azure Stack HCI(Former S2D) slack channel. https://azurestackhci.slack.com

Someone said that they had a new Node that when they added that node to the cluster, the new Cache devices would not bind to the Capacity drives on that cluster. The reason for this is when the cluster was created, it was run with Enable-ClusterS2D -CacheDeviceModel. When doing so you tell the cluster that the only allowed Cache device is this model.

Read more

How to configure System Center VMM Part 10 – Physical Computer Profiles

Welcome back for Part 10 of this System Center VMM series, in this post I will talk to you about Physical Computer Profiles

In the previous posts i have spoken about all the different fabric items that needs to be in place for Bare Metal Deployment to work. Physical Computer Profiles is the last piece of the puzzle for doing BMT deployment.

Read more