Shulou(Shulou.com)06/01 Report--

This article is to share with you why there are two Hyper-V PowerShell modules in Windows 10. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

If you install Hyper-V in Windows 10 and use PowerShell's Get-Module to view the Hyper-V module, you will find that there are two versions of the Hyper-V PowerShell module.

In fact, Microsoft does this for two main reasons:

◆ Microsoft has never supported using one version of Hyper-V PowerShell to manage Hyper-V on remote computers. Although in the real world, we may be using it normally, it has not been supported and verified by Microsoft. However, there are users, especially IT Pro, who need to use Hyper-V PowerShell for cross-version Hyper-V host management.

◆ to support users' suggestions, Microsoft controls PowerShell Module from Windows 10 to provide cross-version Hyper-V management compatibility. If you need to remotely manage Hyper-V instances in Windows 8.1 / Windows Server 2012 R2 through Windows 10, you need to load v1.1 Hyper-V PowerShell module;. If you need to remotely manage Hyper-V instances in Windows 10 / Windows Server 2016, you need to load v2.0 PowerShell module.

Note: when we use Hyper-V Cmdlet directly in Windows 10, v2.0 is loaded by default. Of course, you can switch on your own.

That's why there are two Hyper-V PowerShell modules in Windows 10, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.