Practical tools for system, network, security, and operations administrators.

SYS-C0115 · Windows Server & PowerShell

Windows Server Licensing Explained

Estimate a Windows Server edition on numbers you type, and treat it as arithmetic, not a license.

Updated 25 October 2026 · Explainer

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

Edition, cores, and client access are the three numbers people mix up. The selectors and calculators do arithmetic on numbers you type. They do not know what you bought, and they are not a Microsoft quote.

This page is not legal advice and not a purchasing approval. The contract you have is the license. A calculator result that disagrees with that contract does not change the contract.

Write the edition you think you run and the core count you counted. Do not invent a core count to make the number smaller. 192.0.2.10/24 and example.com are documentation. They stay in the note.

The change you can finish

Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.

Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.

  1. Write the edition and the core count you counted.
  2. Run the calculator.
  3. Label the result as arithmetic.
  4. Compare it later with the agreement you have.
  5. Do not treat the result as a quote.
  6. Stop.

Mistakes that outlive the command

Windows Server Licensing Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for Windows Server Licensing Explained: The numbers are ones you counted. The result is labeled arithmetic. The agreement remains the license. No purchase was made from the page alone. And this is not legal advice.

Checks before you call it done

Confirm this before you call the change done: Edition is written. Core count is written. The result is labeled arithmetic. The agreement is named as the thing you still must read. And no order was placed. If one of those fails, stop.

# Arithmetic, not a license quote.
# Not legal advice.
# The agreement you have is the license.

Before you leave the host

Windows Server Licensing Explained ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.

192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.

One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.

A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.