Blog Post
Getting Started with Windows Admin Center Virtualization Mode
Hello,
It's great to hear about this WAC Virtualization mode. We've been testing it and we have a question.
It's also good to hear that we still develop traditional Hyper-V, as not all companies are looking at Azure Local, specially taking in mind the current geopolitics around the world.
Now focusing on our testing. No issues to add a cluster, but for an standalone hyper-v node, why we force the need to use a storage intent? This makes sense for a cluster, but for an standalone? We have an standalone with a Management intent and a Compute intent, but we can't add it because a Storage intent is needed?!?!? Is this a bug? or are we missing something?
I had the same thought, but someone on Reddit also mentioned it could be used for live migrations and CSV redirections (if that happens). So in that sense, kind of makes sense to have the two storage intents if that is correct. I wasn't originally thinking of it like that.