SourcePath not made clear it is relative to the hypervisor when executing remotely

[sammie-p]

After reading the documentation, I understood I would be able to remotely copy a file from my workstation to a VM via its hypervisor with the following command:

Copy-VMFile -ComputerName <hypervisor> -VMName <VMname> -SourcePath <file on my workstation> -DestinationPath <path on VM> -FileSource Host

However, I have learnt from trial and error that -SourcePath is a path to a file on the hypervisor only. This is not made clear anywhere on this page.

Suggestions:

The document summary should be more verbose to explain this functional limitation. "Copies a file to a virtual machine from its hypervisor."

Disambiguate the value "Host" for the required FileSource parameter: Host refers to the Hyper-V host machine. --I can't understand why this parameter is required when it only accepts one value, but I know that's not a question for the documentation team.

Explain that the SourcePath parameter is a path on the Hyper-V host machine, not the machine executing the Copy-VMFile command when it's done remotely by specifying the ComputerName or CimSession parameters.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: c94869f3-0ff2-5d02-e45b-2fabcd78b0a0
• Version Independent ID: 9767d17f-bd62-bd26-cc27-17b1a1c1eb1f
• Content: Copy-VMFile (Hyper-V)
• Content Source: docset/winserver2022-ps/hyper-v/Copy-VMFile.md
• Product: w10
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!