Virtualization of your work servers is a necessary action, but the problem is when you do that, you basically put all your eggs in one basket. Let’s imagine that your Hyper-V host with several VMs on it requires rebooting. Well, in that case, you won’t be able to boot a specific VM until the host OS is restarted, and all VMs are booted. And there’s no guarantee they will be available after that! Now, that surely doesn’t sound too good. However, luckily there are ways to make this process less painful and more efficient.
While configuring Hyper-V host, you’ll have to be able to boot your VMs in a specific order. I gotta admit, even though it took me a while to figure out how to customize this process, I have some results for you.
Mind, even if your server OS isn’t prone to failure, it’ll still be wise to configure Hyper-V automatic start action for VMs. One way or another, someday, you’ll have to reboot your server. So, when such a reboot occurs, it would’ve been nice if you didn’t have to boot ever separate VM manually, don’t you think so?