Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 198737

Re: Getting weird error: Get-VM : The Hyper-V Management Tools could not access an expected WMI class on computer

$
0
0

With the number of PS modules available, there are bound to be some name collisions going to happen.

There are a number of solutions:

  1. Use the Prefix parameter on the Import-Module cmdlet.
  2. Use the fully qualified name (modulename\cmdletname), as you did
  3. Check if the module comes with a builtin prefix (the DefaultCommandPrefix setting in the module's manifest file). Also present on the object returned from Import-Module
  4. Make sure that one of the modules with the conflicting cmdlet is not loaded. Which might be a bit of a challenge with module autoloading and the cache it uses.

Viewing all articles
Browse latest Browse all 198737

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>