Make Hyper-V plugin more explicit
Problem
The problem occurs when the VMWare PowerCLI module is also installed on a system. In this case, calling the Get-VM cmdlet leads to the following error:
Get-VM You are not currently connected to any servers. Please connect first using a Connect cmdlet.
Reason
The reason is that the Get-VM cmdlet of the PowerCLI module is incorrectly used because there is an overlap in the naming of the Hyper-V cmdlet and the PowerCLI cmdlet.
Solution
The solution to this is to specify the name of the cmdlet absolutely: Hyper-V\Get-VM instead of Get-VM
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA.
recheck
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅