Fix Hyper-V Remoting when using remoting import #24032
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
When on a Windows version that cannot load the Hyper-V module the State property will be of the string type. This change ensures that PowerShell can still parse this value to the VMState type as expected when the module was loaded natively. This should allow PSRemoting cmdlets that call Get-VM to properly get the VM State property.
PR Context
Fixes: #24014
I don't have a Server 2016 host to test against but it seems like the only other props used from
Get-VM
are aString
andGuid
types which should work without any issues in an implicitly remoted module import.PR Checklist
.h
,.cpp
,.cs
,.ps1
and.psm1
files have the correct copyright headerWIP:
or[ WIP ]
to the beginning of the title (theWIP
bot will keep its status check atPending
while the prefix is present) and remove the prefix when the PR is ready.- [ ] Issue filed:
(which runs in a different PS Host).