In the previous part we took the time to set up our AzS HCI lab. If you’ve been following along (I’d strongly recommend to if you haven’t!) you have a 4-node cluster and WAC installed. We have not connected the cluster to Azure just yet and I think it’s better if we looked around the
After reading a lot about Azure Stack HCI, and comparing the two flavors (Windows Server HCI vs Azure Stack HCI), I think it is about time we get some dirt on our hands. That’s right, it is time to spin up our own Azure Stack HCI lab and see it in action! I found this
Recently I made a career switch and with that, here I am back to learning the alphabets! I mainly come from a software/application background and the new role I’ve landed myself into requires of me not only the application knowledge but also the relevant hardware understanding. What that means for me is going back to
When you deploy Azure Stack HCI, you deploy it in the form of a cluster, with multiple nodes participating. A cluster is basically a group of otherwise independent servers (nodes) that are interconnected to work with each other to provide features like scalability, high availability, load balancing, etc. and many more. An HCI cluster collects
AnalyticOps Insights 