Closed eponerine closed 4 years ago
It looks like if you wrap the Clustering cmdlets in parens, and then pipe, it works. This is still really horrible behavior.
It seems that this question can best be answered via PowerShell Community Links
For bug reports specific to PowerShell, please visit, PowerShell at GitHub.
The issues section of this repository is for content fixes regarding documentation. Feel free to re-open in case you would like to suggest improvements to the article itself.
Thank you.
Let's do something simple, like grabbing a single node of our cluster:
Get-ClusterNode | Select -First 1
You end up with the following pipeline errors:
It appears that this is an issue with a lot of the Failover Clustering cmdlets. Try it with other FCM commands!
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.