VMware PowerCLI
The Best User Interface for your VMware Datacenter!
The Best User Interface for your VMware Datacenter!
The Best User Interface for your VMware Datacenter!
Vmwares noun prefixes conflict with hyper-v, can you please fix that?
Guest
When Microsoft copied the names of our cmdlets to use for Hyper-V, they provided a way to work with conflicting cmdlet names. Jeff Hicks has a great blog post demonstrating this with Hyper-V and PowerCLI: https://mcpmag.com/articles/2013/08/20/powershell-name-duplicates.aspx
I believe around 6.5R1 is when we made the move to modules, and in 6.5.1 we got rid of the MSI and moved to the PowerShell Gallery (RIP Snapins!). I completely understand your frustration, and it will definitely come up again in my meeting with the PowerShell team.
yes.
When did powercli move to being a module as opposed to the snap-in?
Anyway, this is just frustrating is all.
Also, the Hyper-V module is an optional windows feature. Are you actually using it?
I'll share this with the PowerShell team at Microsoft, as this is really needs to happen at the PowerShell platform level. No one should expect 3rd parties to change cmdlet names every time Microsoft takes one for their own usage.
It would be nice though if they worked together by default. Given that the default system behavior uses the hyper-v module, and that you are a third party, it would be great if you engineered one of those solutions in to the package to work that way by default. Instead of users having to spend time with additional configuration just to make your tools work.