<div>
Not to overlook the obvious, but are you sure that is the VM's name? You shouldn't have to do anything special to export the VM even with the files in a different location. As long as the VM is properly defined, the Hyper-V management service will know where the files are and export the VM properly.
</div>


Not to overlook the obvious, but are you sure that is the VM's name? You shouldn't have to do anything special to export the VM even with the files in a different location. As long as the VM is properly defined, the Hyper-V management service will know where the files are and export the VM properly.

<div>
<div class="content wysiwyg-content">
I have physical box with two VMs running. I want to use a script to export the VMs to a different server. &nbsp;On a another server where I installed VM to default dir this command works export-vm -name VM -path c:\backup however this server the VMs are stored on a data partition not in the default dir. I get an error Hyper-v was unable to find a virtual machine with name &quot;App1&quot; I can't find the syntax to run the export with the files in a different location.
</div>
</div>


I have physical box with two VMs running. I want to use a script to export the VMs to a different server.  On a another server where I installed VM to default dir this command works export-vm -name VM -path c:\backup however this server the VMs are stored on a data partition not in the default dir. I get an error Hyper-v was unable to find a virtual machine with name "App1" I can't find the syntax to run the export with the files in a different location.

Hyper-v command line export cant find VM

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.