Missing Get-ClusterNodeSupportedVersion in the FailoverCluster doc

Open
#3,950 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
powershell
Domain
documentation

Research direction

Start with the linked FailoverCluster module documentation and check how existing cmdlet pages are organized. Verify Get-ClusterNodeSupportedVersion on Windows Server 2019 or 2022, then add its documentation so the cmdlet appears in the module reference and its purpose is covered.

Written by the indexing model from the issue text.

Description

issue-doc-bug needs-triage
Prerequisites
  • Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
  • Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in Get-Foo cmdlet" instead of "Typo."
  • Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.
Links

https://learn.microsoft.com/en-us/powershell/module/failoverclusters/?view=windowsserver2025-ps

Summary

The Get-ClusterNodeSupportedVersion is missing from the documentation.
The command was mentionned by a Microsoft employee back in 2019 by in this blog post
The command is working, tested in Windows Server 2019 and 2022.

Details

No response

Suggested Fix

No response

Dominant language
Dockerfile
Stars
504
Forks
635
Avg merge
1d 3h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftDocs/windows-powershell-docs

All issues in MicrosoftDocs/windows-powershell-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.