Elias Thorne spent the better part of forty years inside a workshop that smelled exclusively of lavender oil and aged brass. He was a master of the escapement, a man who could look at a pile of gears the size of a ladybug’s wing and tell you which one was weeping.
One Tuesday, while I was visiting his shop to trade some nib-polishing compound for a specific grade of watchmaker’s grease, I watched him spend six hours drafting a schematic. He wasn’t working on a watch; he was drawing one. He used a compass and a fine-line pen, detailing the exact tension required for the mainspring and the precise angle of the pallet stones. When he finished, he blew a stray speck of dust off the parchment, nodded with a terrifying amount of satisfaction, and put his tools away.
“Is it finished?” I asked, looking at the broken Longines still sitting in the parts tray, untouched.
“The plan is,” Elias said, as if that were the same thing.
– Dialogue in the Workshop
He felt the weight of the repair was over because the logic of the repair had been captured on paper. The watch, however, remained a corpse. It wouldn’t tick for another three weeks because Elias had confused the act of articulation with the act of execution. He had achieved the “feeling” of a fixed watch without ever touching a screwdriver to the movement.
The Cartography of Modern IT
This is the quiet sickness of the modern IT department, particularly when it comes to the labyrinth of Microsoft licensing. We have become a culture of cartographers who never actually board the ship. We treat a documented plan as a completed one, and in doing so, we leave our infrastructure in a state of perpetual, theoretical readiness that collapses the moment a real user tries to log in.
Total tiles: 312. One water stain shaped like Tasmania. Reality is often the mess in the corner of a perfect grid.
I’ve spent the last few hours counting the ceiling tiles in my workshop-there are 312, by the way, and the one in the far corner has a water stain shaped like Tasmania-mostly because I was waiting for a client to find a “completed” licensing file they swore was ready to go.
They had a PDF. It was a beautiful PDF. It had charts and seat counts and a projected budget for the next three fiscal years. It even had a color-coded breakdown of User versus Device CALs. But when we looked at the actual Remote Desktop Licensing Manager, the “Installed” column was a graveyard of zeros.
The Map vs. The Arrival
The team had checked the box. They had “done” the licensing because they had written down what they intended to buy. In the market’s collective psyche, the document has become the destination. We mistake the map for the arrival, and this bias lets us feel a premature sense of accomplishment that dampens the actual drive to execute.
When you are dealing with Remote Desktop Services (RDS), this delusion is dangerous. Microsoft doesn’t care about your internal wiki pages or your beautifully formatted spreadsheets. The server is a binary beast. It either has a digital certificate to hand out to a requesting client, or it doesn’t.
Yet, I see project managers close Jira tickets simply because a “Licensing Strategy” document was uploaded to a SharePoint folder. They move on to the next fire, leaving a ticking time bomb in the form of a grace period.
The grace period is a four-month window where everything works perfectly despite being fundamentally broken. It is the IT equivalent of flying a plane that has no engines but happens to be caught in a very strong updraft. You feel like you’re flying. You look at your instrument panel-the documented plan-and it says you are a pilot. But eventually, the air thins, and the ground starts looking very large.
By the time the grace period expires, the person who wrote the plan is often three projects away, and the person left to deal with the “Protocol Error” at 8:00 AM on a Monday has no idea that the “completed” licensing plan was just a work of fiction.
We see this same pattern in my world of fountain pen repair. A customer will send me a pen with a note saying they’ve “optimized the ink flow plan.” They’ve read the forums, they’ve decided on the exact milliliter of Iroshizuku ink to use, and they’ve even planned out which paper they will use for their first letter.
But they haven’t noticed that the internal sac is ossified into a substance resembling charcoal. The plan is perfect; the hardware is dead.
The Friction of Reality
In the world of Microsoft Server infrastructure, the friction of execution is where the real work lives. It’s not just about knowing you need 50 seats; it’s about the actual, granular steps of activation. It’s the License Server ID, the clearinghouse connection, and the specific versioning that prevents a Windows Server CAL from working on a host. If you stop at the plan, you haven’t even started.
This is why the market is so frustrated. Most vendors sell you a SKU and a “thank you” page, leaving you to reconcile the gap between the license you just bought and the server that refuses to recognize it. They feed into the “documented = done” myth by treating the transaction as the end of the journey.
I prefer a different approach, one that acknowledges that the plan is just the preamble. When you work with a specialist like the
…the focus shifts from the mere acquisition of a “plan” to the reality of a working deployment.
They don’t just hand you a key and wish you luck; they provide the setup guidance that actually bridges the gap between the spreadsheet and the Licensing Manager. It’s the difference between Elias Thorne’s drawing of a watch and the actual clicking of the gears as they return to life.
Climbing the Implementation Ladder
We have to stop rewarding ourselves for the intention. We have to stop feeling “done” when the PDF is saved. It is the absence of that nagging yellow warning bar that tells you the grace period is evaporating.
I think about those 312 ceiling tiles often when I’m stuck in these cycles of administrative stagnation. Each tile is a grid, much like a spreadsheet. They are tidy, predictable, and entirely stagnant. But the water stain in the corner-Tasmania-that’s the reality. That’s the leak in the roof that no amount of “roofing strategy documentation” will fix.
You have to get on a ladder. You have to touch the shingles. In licensing, the “ladder” is the implementation phase. It’s the configuration of the Group Policy Objects (GPOs) to point the session hosts to the correct licensing server.
It’s the realization that “Per User” licensing requires a functional connection to Active Directory that a “Per Device” setup might handle differently. These are the messy details that people leave out of the plan because they are hard, and because they don’t produce the same hit of dopamine that checking a “Plan Completed” box does.
If you are currently sitting on a licensing plan that is “finished” but not yet “installed,” I urge you to look at it for what it really is: a wish list. It is a ghost. It has no power to authorize a single RDP session.
The industry wants you to believe that once you’ve sourced the licenses, the problem is solved. But the problem isn’t solved until the first user connects and the server hands off a token without a whisper of complaint.
The checkmark on the licensing plan is the only thing currently provisioned in the empty server rack.
Beyond the Paper
I eventually saw Elias Thorne finish that Longines. It took him another month. He had to scrap his original plan three times because the actual metal of the gears didn’t behave like the lines on his paper. The gears were worn in ways his compass couldn’t predict. He had to adapt. He had to get his hands dirty.
When he finally wound it, and that rhythmic ticking filled the lavender-scented air, he didn’t look at his drawing once. He looked at the watch. We need to start looking at the servers. We need to stop trusting the documentation and start verifying the deployment.
The next time someone tells you the licensing is “taken care of” because it’s in the budget or on the roadmap, ask to see the Licensing Manager. Ask to see the green checkmarks in the console.
Don’t let the feeling of a plan well-drafted trick you into a false sense of security. The map is a beautiful thing, but it won’t keep the rain off your head, and it certainly won’t keep your remote workforce connected when the arrives.
Finish the work. Move beyond the paper. Ensure that what you’ve planned is what is actually running, because in the end, a document is just ink on a page, but a working server is a business in motion.
