Elias spends his mornings in a workshop that smells of cedar and old-growth spruce, milling precision timber for high-end guitar makers. He is a man obsessed with the decimal point. If a luthier orders a soundboard planed to exactly 3.2 millimeters, Elias delivers 3.2 millimeters.

He uses a digital caliper that cost more than my first car, and he checks every piece twice before it goes into the shipping crate. But Elias has a recurring nightmare, and it usually arrives in the form of an angry phone call from a studio in a different climate zone.

By the time that spruce travels from the humid, salt-heavy air of his Oregon workshop to a bone-dry studio in the high desert of Arizona, the wood has breathed. It has contracted. The luthier puts his own caliper on the wood and sees 3.14 millimeters.

The luthier feels cheated. Elias feels slandered. But the wood is the only thing speaking the truth. There is a fundamental gap between the promise made on the paperwork and the reality of the material in the room.

Lars is the IT version of that luthier. He doesn’t work with spruce, but he works with something equally temperamental: Microsoft licensing. I watched him last Tuesday, hunched over a workstation in a room that was far too cold, humming a rhythmic, repetitive tune that I eventually recognized as the bassline to “Tom’s Diner.”

It was a nervous tick, a way to keep his hands steady while he navigated the labyrinthine columns of the Remote Desktop Licensing Manager. Lars had a PDF invoice in his hand-a clean, official document confirming the purchase of 50 User CALs for a Windows Server 2022 environment.

01

The Three-Seat Phantom

On the screen, however, the “Total Licenses” column stubbornly insisted on the number 47. He clicked refresh. He waited. He clicked refresh again. The number 47 sat there with a kind of digital insolence, refusing to acknowledge the three seats that existed in the physical world of paper and credit card statements.

COUNT: 47 / 50

This is the “three-seat phantom,” a phenomenon that has eaten more IT man-hours than any malware strain in history. It is the mismatch between the “bought” and the “counted,” and it is a gap that the human in the middle is expected to bridge with their own sanity.

For a long time, I believed that if I followed the instructions, the systems would eventually agree with one another. I believed that because I had paid for a specific quantity, the server was under some logical obligation to recognize that quantity. I was wrong.

When the store says fifty and the server says forty-seven, the software company doesn’t lose a second of sleep. The store has your money, and the server is doing exactly what its code tells it to do. Neither side is incentivized to close the gap.

The only person who suffers is Lars, who now has to spend four hours of his life acting as an unpaid accountant for a multi-billion-dollar ecosystem. He has to dig through event logs, check for “Temporary CALs” that may have been issued and never reclaimed, and verify if a stray “Device CAL” was accidentally assigned.

The server is a fortress of logic, and it does not accept “intent” as a form of currency. If a license isn’t registered in its specific database, in its specific format, under its specific lease terms, it simply doesn’t exist. The fact that you have a receipt from a reputable vendor is, to the server, a piece of irrelevant gossip.

The Lease Labyrinth

This friction exists because of the way licenses are actually handled in the background. In a Remote Desktop Services environment, licenses aren’t just “on” or “off.” They are leased. When a user connects, the server looks for a valid CAL. If it finds one, it earmarks it for that user for a period of 50 to 90 days.

But things get messy when you try to scale. If you add a new pack of licenses to an existing pool, the server doesn’t always perform a clean “plus-ten” addition. It might see those new licenses but refuse to activate them because of a version mismatch, or because the Licensing Grace Period hasn’t technically expired yet.

I once spent an entire afternoon arguing with a server over two missing seats, only to discover that the server had “remembered” two users who had been fired six weeks prior. The licenses were tied up in a 90-day lease that couldn’t be manually revoked without a complex series of WMI commands that felt more like a ritual exorcism than a technical task.

This is why the “where” of the purchase matters almost as much as the “what.” Most people buy licenses like they’re buying a bag of flour-they just look for the lowest price and the right label. But in the world of RDS, you aren’t just buying a key; you’re buying into a tracking system.

If the vendor doesn’t provide you with the exact tools and the exact versioning required for your specific build, you’re going to spend the next three days in Lars’s shoes, humming a nervous tune while you try to find your missing seats.

I’ve found that the only way to stay sane in this profession is to eliminate as many variables as possible before the licenses ever touch the server. You need a source that understands that a “2022 CAL” isn’t the same as a “2019 CAL” being used on a 2022 server, even if the “downgrade rights” say it should work.

There is a specific kind of exhaustion that comes from being right but being unable to prove it to a machine. It’s the same frustration Elias feels when he knows he cut that spruce perfectly, but the atmosphere decided otherwise.

In IT, the “atmosphere” is the complexity of the licensing roles and the underlying registry keys that track them. We are often told that technology is here to automate the boring stuff, but licensing is the ultimate counter-argument. It is a manual, pedantic, and often illogical layer of bureaucracy that has been digitized but not simplified.

02

The Reconciliation Tax

I’ve started telling my clients that the “price” of a license isn’t what they see on the checkout page. The true price includes the “Reconciliation Tax”-the hour or two they will inevitably spend making sure the server actually recognizes what they bought.

Lars eventually found his three seats. It turned out they were being held in a “per-device” buffer because of a misconfigured Group Policy Object that had been sitting dormant for three years. It had nothing to do with the invoice, and everything to do with the fact that the server was interpreting reality differently than Lars was.

When the count finally hit 50, Lars didn’t cheer. He didn’t feel a sense of accomplishment. He just stopped humming, closed his laptop, and walked out of the room. He had reclaimed his 50 seats, but he would never get that Tuesday morning back.

We live in a world where we expect our data to be fluid and our transactions to be seamless. We expect that if A = B and B = C, then A must equal C. But in the world of infrastructure, A is a PDF, B is a human, and C is a database, and they are all speaking different languages.

The next time you see an IT admin staring blankly at a “License Manager” screen, don’t ask them if it’s working. They know it’s working. They’re just waiting for the machine to stop lying to them.