Closed GeriOnline closed 3 years ago
Hi Jaromir that's exactly the location in deploy.ps1. It would be great if you would commit this in one of the next upcoming releases. Thank you Gerhard
Cool! I merged it to master. New version will be built right away...
When deploy.ps1 is running on a non English Hyper-V host and tries to enable the guest service interface of a vm (EnableGuestServiceInterface=$true in LabConfig.ps1) an error is thrown that the requested component does not exist.
Reason: deploy.ps1 tries to enable the guest service interface by name:
Enable-VMIntegrationService -Name "Guest Service Interface"
However the name depends on the language of the Hyper-V Host - in German for example it is named "Gastdienstschnittstelle".
Suggestion: What do you think of an implementation similar to the one in the xVMHyper-V DSC resource where the guest service interface is referenced by its ID and not by name. In my experience this works for all languages of Hyper-V hosts (Windows 10, Server 2016, Server 2019 and also in the latest Server 2022 Insider Preview).