Replies: 2 comments 1 reply
-
The FailoverClustering module is built for Windows PowerShell ( <= 5.1 ) so PowerShell 7.5 has to load it in compatibility mode. (I'm not sure, but I think it's implicitly doing the same thing as the UseWindowsPowerShell parameter for If certain commands are still failing, it could be that they have dependencies on types from the .NET Framework that are not included in .NET anymore. Do you get any better clues if you run |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
(Get-ClusterNetwork -Name '<ClusterNetworkName>').Role = 'None'
succeeds when using Windows PowerShell (check by running
(Get-ClusterNetwork -Name '<ClusterNetworkName>').Role
.When using PowerShell 7.5, the Role property is unchanged when checking with
(Get-ClusterNetwork -Name '<ClusterNetworkName>').Role
.What's the reason I need to use Windows PowerShell for this command?
Beta Was this translation helpful? Give feedback.
All reactions