S2D

Manually adding a patch to WSUS

jantorep

So this week there was a new Cumulative Update out that i wanted to test on a Storage Spaces Direct cluster. But as im using WSUS and VMM to patch my clusters i needed that patch to be in WSUS and it’s not. It will still take a few days before that patch get’s synced to WSUS, and i did not want to manualy update my nodes.

I googled and found a few posts about this but none that was good enough and it took me a while to find something relevant. So i decided i should share with you how you manually ad a Windows Update KB to WSUS.

Read more →

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

jantorep

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?

jantorep

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 →