Moving a Hyper-V VM

From where to where?

The VM, its configuration files, and .VHDX files or components thereof?

Yesterday I used the "Move" to move a VM to a new location and it worked fine.   However, it was not a VM that users use.

I want to move the entire VM

I've not done this before, but MS has this to say about it:
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/use-live-migration-without-failover-clustering-to-move-a-virtual-machine

I'll go through it

I'll leave the exactly how to move the VM to those who responded already, however, I'll point out that in my experience, Microsoft Access is VERY sensitive to network disruptions.  My understanding of the migration options is that such migrations will BRIEFLY disrupt the network connectivity (1-5 seconds).  But that's long enough to cause Access to consider the connection broken and force end users to close the database and re-open and POTENTIALLY cause data corruption.  Most other applications - Word, Excel, etc (non-database applications) wouldn't notice the move, but Access, I suspect, would.

I am moving the entire VM and the hard drive to a new virtual host. based on Lee's comment I will not do this until after hours.

I frequently use Replica to move machines.  Less complicated then setting up shared nothing migrations.  And you can essentially stage the transfer so that later, you can complete it in a minute.

You setup replica to replicate to the new server with a 30 second replication window.

Then let it go.  The size of the VM, speed of your disks, and speed of the network will be the major factors in determining how long the replication takes.  Once the initial replication completes, you can migrate it when you're ready.  *I* would shutdown the original VM, wait 1 minute for replication to catch up, then "fail over" the vm on the other machine and start it.  Total time to bring up will be however long it takes to start on the new host plus a minute or so.  Typically, my migrations like this, all told (shutdown, one more replication cycle, start up) take about 5 minutes, give or take.

Thanks

I want to close this out but I don't have an answer to the question.

Lee, is Replica a software?

Replica is a built in feature of Hyper-V since 2012.  No additional licensing required.  (Although standard Windows licensing still applies - meaning OEM licenses are non-transferrable (in most areas) and retail/volume licenses are transferrable once every 90 days.  And you can't split up your 2 VM licenses - the host you move it to must have a free license to use).  https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica

thanks

Thanks