Invoke-OSLicense with Token Based Activation

Open
#4,153 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
powershell
Domain
documentation

Research direction

Start with the linked Invoke-OSLicense documentation and identify the page source in this repository. Check how the ActivationID parameter and Token Based Activation are documented, then confirm the reported parameter-set failure and misleading unsupported-edition error against the issue details. Done when the page accurately explains the supported activation parameters and the reported behavior.

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/oslicense/invoke-oslicense?view=windowsserver2025-ps

Summary

When utilizing Invoke-OSLicense with ActivationID parameter for Token Based Activation (TBA). It fails specifying "Parameter set cannot be resolved using the specified named parameters." Because Invoke-OSLicense is too broad, activating via TBA results in a misleading unsupported-edition error.

Details
Image Image
Suggested Fix

No response

Dominant language
Dockerfile
Stars
510
Forks
643
Avg merge
2d 21h
Merged PRs (30d)
8

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.