Windows editions, and choosing the one the job actually needs

Why this matters

Edition questions look like trivia and are not. Almost every one of them is really a question about a feature somebody needs — a machine that has to join a domain, a laptop that has to be encrypted, a workstation that has to accept a remote desktop connection — and the edition is just where that feature happens to live.

That is also how the exam asks. You will rarely be asked "what is in Pro". You will be given a requirement and asked which edition satisfies it, and the distractors will be editions that satisfy most of it. So the useful thing to learn is not a feature matrix but a short list of the features that actually differ, because everything else is identical and cannot be the answer.

The lesson

What separates Home from Pro, and the four features that decide it

Home and Pro run the same kernel, the same drivers and the same applications. The differences that matter for support work are a small set, and it is worth learning them as a list of four rather than as a table of thirty.

• Domain join. Home cannot join an Active Directory domain. This is the single most common reason a machine has to be upgraded, and it cannot be worked around.
• BitLocker. Whole-volume encryption with management is a Pro feature. Home has device encryption on hardware that supports it, which is not the same thing and cannot be administered centrally.
• Remote Desktop host. Home can connect out to another machine. It cannot accept an incoming Remote Desktop session. Both editions can run remote assistance tools, which is why this one catches people out.
• Group Policy. The local Group Policy editor and the ability to receive domain policy are Pro. Home is configured through Settings and the registry.

Two more show up occasionally: Hyper-V (Pro) and the ability to defer feature updates properly (Pro). Everything else a user notices — the interface, the applications, the driver support — is the same.

The consequence worth holding on to: if a scenario mentions a domain, central encryption management, an incoming remote session, or policy, the answer is at least Pro. If it mentions none of those, Home is sufficient and cheaper, and saying so is the right professional answer.

Domain join against workgroup, and what joining a domain hands over

A workgroup is the absence of central management. Every machine holds its own accounts, and an account on one machine has no meaning on another. Sharing works by creating the same username and password in two places, which is why workgroup estates drift within weeks.

A domain centralises three things: authentication, authorisation and configuration. A domain account is created once and works on every joined machine. Permissions are granted to domain groups. Policy is written once and applied everywhere.

Joining a domain hands over more than people expect, and it is worth being able to say so plainly to a user:

• The machine gets a computer account in the directory, and the directory can apply policy to it whether or not anyone is logged in.
• Domain administrators become administrators on that machine.
• Local accounts still exist but stop being the normal way in.
• Policy can enforce settings the local user cannot change, including encryption, update behaviour, and what software may run.

None of that is sinister; it is the point. But a user who is told "we'll just join it to the domain" and then finds their own laptop enforcing a screen lock has been under-informed, and that is a support failure rather than a technical one. Joining a personally-owned machine to an employer's domain is a decision with consequences for the owner, and it deserves a sentence of explanation before it happens rather than a ticket afterwards.

Enterprise and Education, who gets them, and how they are licensed

Enterprise is Pro plus management and security features aimed at large estates, and it is not sold to individuals. It arrives through volume licensing or through a subscription that upgrades an existing Pro installation in place — which is worth knowing, because the upgrade is a licence change rather than a reinstallation, and a machine can move from Pro to Enterprise without the user noticing anything except new policy.

Education is Enterprise's equivalent for schools and universities, with the same relationship to Pro Education that Enterprise has to Pro.

The licensing shapes a technician actually meets:

• Retail. Bought by a person, transferable to another machine, tied to a Microsoft account for reactivation.
• OEM. Shipped with the hardware, tied to that motherboard, not transferable. Replacing a motherboard is the case where this bites.
• Volume. Bought by an organisation against an agreement, activated against a local service or a key management host rather than against Microsoft directly.
• Subscription. Per-user, entitles a number of devices, and lapses if the subscription does.

The examinable point is that activation failures usually trace back to which of these a machine has, not to a technical fault. A machine that deactivated after a hardware change is almost always OEM; a machine that deactivated overnight in an office is almost always a volume activation host it can no longer reach.

32-bit and 64-bit, memory ceilings, and the software that still cares

64-bit is the assumption now, but the distinction has not quite finished mattering and it is still examined.

• A 32-bit operating system can address about 4 GB of memory, and in practice gives a user rather less. That ceiling is the reason 32-bit died.
• A 64-bit operating system runs both 64-bit and 32-bit applications. A 32-bit operating system runs only 32-bit applications.
• Drivers must match the operating system exactly. A 32-bit driver will not load on a 64-bit system, which is the real reason some organisations keep old machines: a scanner, a till, or a machine tool whose vendor never shipped a 64-bit driver.
• There is no in-place upgrade from 32-bit to 64-bit. It is a clean install, and saying so early saves an afternoon.

The software that still cares is almost always an interface to hardware — laboratory instruments, industrial controllers, specialist printers — or very old line-of-business software with a 16-bit installer, which a 64-bit system cannot run at all even though it runs the 32-bit application fine.

When a scenario describes software that will not install on a new machine and worked on an old one, the 16-bit installer is a strong candidate, and the answer is usually a virtual machine running the old system rather than downgrading the new one.

Reading a requirement list and picking an edition you can defend

Here is the method, and it is deliberately boring: read the requirement, list the features it implies, and pick the cheapest edition that has all of them.

Worked through. "Forty laptops for a firm with Active Directory. They must be encrypted, managed centrally, and support staff must be able to connect to them remotely to fix problems."

• Active Directory → domain join → not Home.
• Encrypted and managed centrally → BitLocker with recovery key escrow → not Home.
• Support connects to them → Remote Desktop host → not Home.
• Forty machines, one firm, no mention of the advanced deployment or security features Enterprise adds → Pro is sufficient.

Answer: Pro, and you can say why in one sentence per requirement. That is what "an edition you can defend" means, and it is also exactly what the exam is scoring.

Two failure modes to avoid. The first is reaching for Enterprise because it sounds appropriate for a business; it costs more, requires volume licensing, and adds nothing this firm asked for. The second is assuming Home is never right — for a sole trader with no domain, no central management and no inbound remote access, Home is the correct and cheaper answer, and recommending Pro anyway is not being thorough, it is spending someone else's money.