VMM 2022 is out and allows you to run Windows Server 2022 and Azure Stack HCI 21H2 wich you wan’t to upgrade to to get new features if you have any of those 2 OS’es. I upgraded my lab last week and had some issues. The VMM 2022 upgrade went perfect.
But upgrading my 2019 cluster agents gave an error. The same with adding new physical hosts to VMM.
So i was setting up a Azure Stack HCI Lab today and came across a error msg when running the set-mocconfig command.
My cluster has static IP addresses on everything and for some reason it then requires the Cloud Service IP CIDR to be set static. And you can’t use a parameter like $cloudservicecidr = “IP Address” You need to specify it in the line.
Error msg i got was
Cloud Service IP CIDR is required when using static IP assignment.
It works if adding -cloudServiceCidr 10.0.0.49 at the end after stable.
Hey everyone, another Failover Cluster issue i came across lately. And i wanted to share this one as i could not find any good resources online for this issue. So here we go.
A client contacted me a few weeks back about a node that would not come online again in the cluster after a reboot. It would not join back to the cluster at all. When looking at the cluster it just did not want to join back to the cluster. The only good error msg’s under failover clustering i could find where these.
Hey everyone, have abit of a strange one this time. About 2 months ago i was patching my Azure Stack HCI test cluster with the July patches and using Cluster Aware Updating via WAC. It went trough fine and the vm’s was up and all good. Nothing indicating any issues.
Hello Friends, it’s been a while since my last post. With covid and all my inspiration has not been the best. And with all my spare time going into renovating the house there has not been so much time. But there will be more posts coming soon.
I got the chance to borrow some Lenovo MX1021 Azure Stack HCI nodes to play with and test. And with the soon to be release public preview of 21H2 release i wanted to start getting some real HW experience. So stay tuned for some Azure Stack HCI blog posts coming soon.
So a few weeks ago i was upgrading a 2016 Cluster to 2019. And suddenly the VMM service crashed out of nowhere. I noticed the client had tried to change a VM by increasing the size of the disk. And it failed by loosing connection to the VMM server.
Hello everyone, a quick and short blog post here. As most of you know for services built in to the windows server os there are default firewall rules that get’s enabled if you install the role or feature and you configure it.
Like Radius, Hyper-V Replica, and so on. In the last few weeks i have had issues with Radius and Hyper-V replica firewall ports not working even tho the default rules where enabled.
So i had a question yesterday about how do you change a subnet mask on a logical network that is already beeing used. Well the short answer is it can’t be done in VMM GUI. So i decided i needed to have a look at how i could do this. Read more to see how
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.