Author: Luke Orellana
Microsoft released a few new features in Hyper-V as part of its Windows 10 Creators Update. Here’s what you need to know!
File screening helps mitigate damage from a ransomware attack, allowing file server configuration for real-time auditing on files that become modified.
Create a VM Compatibility report using Compare-VM cmdlet, when migrating a VM to another host, importing a VM copy, and trying to view a VM config file in Server 2016 and Windows 10. Fix incompatibility issues between a VM and a host now with Compare-VM.
It can be very frustrating to deal with VMs that are experiencing some sort of checkpoint issue. Luckily, Hyper-V gives us the ability to manually merge the AVHDX files with the parenting disk so that we can potentially resolve the checkpoint headache. In this guide we show you how to manually merge Hyper-V Checkpoints.
If you’re administrating a Hyper-V cluster that is a few years in age and you’re thinking of expanding, you might be at the point where it is no longer feasible to purchase a new host with hardware that matches your existing hosts. However, if the CPU on the newer host is of a different version or generation, live migration or restoring a saved state VM between the new and old host will fail. Luckily, Hyper-V comes with a feature called CPU compatibility mode that will allow these functions to continue between CPU generations.
When creating a Hyper-V checkpoint, it is crucial to know where the checkpoint files are being saved, especially since checkpoint files can fill up storage. When trying to find where the checkpoint files are being stored in your Hyper-V environment, it is important to understand what types of files are generated when creating a checkpoint. This is because components of the checkpoint are stored in two separate locations. The AVHDX file is stored with the VHD storage and the checkpoint configuration files are stored with the VM’s active configuration files.