The smell of burnt coffee in a windowless conference room has a way of sharpening the senses, though usually in all the wrong directions. It is , and I have been on a diet since precisely .
My stomach is currently composing a minor symphony of protest, a low-frequency growl that harmonizes perfectly with the overhead hum of the industrial HVAC system. On the table sits a binder so thick it could be used as a structural support beam for the building. It’s the new Corporate Licensing and Infrastructure Standard, a document that smells of fresh toner, laminated dividers, and the absolute certainty of people who haven’t touched a server rack in a decade.
The binder represents a “clean slate.” It is a beautiful, logical, and entirely fictional map of how our IT environment is supposed to function. In its pages, every user is a unique digital entity with a singular path to productivity. Every device is a modern, patched, and sanctioned endpoint. It is a world of perfect geometry.
The Logic of the Spreadsheet
We are currently looking at a formal policy that outlaws the very arrangement that keeps the lights on in our manufacturing plants and our logistics hubs. The policy states, in no uncertain terms, that all Remote Desktop Services (RDS) environments must transition to a User-based Client Access License (CAL) model.
The logic is “simplicity.” One user, one license. It looks great on a spreadsheet. It simplifies the billing cycle for the procurement department. It creates a neat, linear relationship between headcount and cost.
But in the actual world-the one with grease on the floor and 24-hour shifts-this rule is an absurdity. In our regional distribution centers, we have terminals that are bolted to the side of steel pillars. These machines are used by three different shifts of workers. A person walks up, scans a pallet, logs out, and moves on.
Covers one terminal for 15+ humans per day.
Requires 15 separate licenses for the same pillar.
The mathematical collision between “standard simplicity” and 24-hour logistics operational reality.
Over a 24-hour period, a single terminal might be touched by fifteen different humans. Under the “New Rule,” we would need fifteen User CALs for that one machine. Under the “Exception”-which has been our working reality for -we use a single Device CAL.
The rulebook has decided that the exception is a deviance to be corrected. It has labeled the most efficient, cost-effective, and logical way to run a warehouse as a “legacy artifact” that must be phased out by . It is a classic case of the plan refusing to acknowledge the terrain.
When a rational standard is written without observing the emergent reality of the shop floor, it doesn’t actually improve the world; it just criminalizes the people who are making the world work.
“A contract isn’t what’s written on the paper; it’s the distance between what the boss wants and what the workers are willing to survive.”
– Kendall D.R., Union Negotiator
The IT equivalent is just as stark. A standard is just a wish the C-suite made before they encountered the physical limitations of a 100,000-square-foot warehouse.
Now, instead of a supported, documented configuration, we have a “shadow IT” situation where the admins are quietly hiding their device-based deployments from the auditors, praying that the next scan doesn’t flag their perfectly functional, perfectly legal-at-the-source licenses as non-compliant with the new “vision.”
This is where the frustration peaks. The licensing isn’t actually the problem-the licenses themselves are versatile. Whether you are running Windows Server 2019 or the latest 2022, the software doesn’t care if you use a User CAL or a Device CAL.
Microsoft provides both because they know that different environments have different physics. But the internal “standard” has decided to be more restrictive than the vendor itself, all for the sake of a “clean” audit report.
If you’re the admin caught in this vice, you’re stuck between a policy that demands one thing and a reality that requires another. You need to maintain compliance with the vendor while navigating the arbitrary “laws” of your own organization.
$14,000
The amount of capital we’d be lighting on fire just to change the license type without changing a single bit of functional output.
Navigating the Bureaucratic Fog
Often, the best way to handle this is to have your data ready-to show the cost-benefit analysis of the “exception” versus the “standard.” Finding the right partner to navigate these waters is half the battle.
When the “Standardization Committee” starts breathing down your neck, you need a source that understands the nuances of these versions-someone who can provide exactly what’s needed for a legacy 2016 environment or a brand-new 2025 rollout without the corporate fluff.
This is why many teams end up at the
because when you are trying to solve a real-world deployment problem, you don’t need a vision statement; you need a 50-pack of Device CALs that ship in fifteen minutes so you can get the night shift back online.
Being on a diet makes the absurdity of these meetings feel sharper. My blood sugar is dipping, and I’m losing my patience for the “Modern Workspace” slides. The presenter is currently talking about “unified identity management” and how it “streamlines the user journey.”
He’s using a laser pointer to trace a path that ignores the three forklifts currently idling in the loading dock. In his world, the “user journey” involves a clean desk, a designer coffee, and a single sign-on.
“In my world, the ‘user journey’ involves a guy named Mike who has three minutes to log into a shared RDP session before the next truck arrives, and Mike doesn’t give a damn about the corporate identity initiative. He just needs the terminal to respond.”
The committee views the warehouse’s reliance on shared devices as a “failure to modernize.” They see the persistence of the old way as a lack of discipline. They don’t see that the old way is actually a highly evolved response to a specific environment.
We see this everywhere in tech. We see it in the push for “cloud-only” mandates in locations with satellite-only internet. We see it in “mobile-first” designs for data entry tasks that require a full-sized keyboard and three monitors. We see it in the “User CAL only” policy for a factory that runs on shared machines. It is the arrogance of the center over the periphery.
As the meeting drags into its second hour, I realize that my job today isn’t to “align” with the standard. My job is to protect the reality. I am the one who has to explain that “compliance” with a flawed internal policy is a path to operational failure.
The danger of these rulebooks is that they eventually become self-fulfilling prophecies. If you outlaw the working reality long enough, people will stop telling you the truth. They will start lying about their deployments.
They will hide their “non-standard” servers in closets. They will buy licenses through back-channels or find workarounds that are less secure and harder to manage. The “Standardized Ghost” eventually haunts the entire network, creating a gap between what the dashboard says and what is actually happening in the rack.
The “Secondary Workstream”: Visualizing the 494% increase in required licenses under a User CAL mandate during peak volume.
I finally speak up. I ask the presenter how the User CAL mandate accounts for the 420 seasonal workers who cycle through the facility in . The room goes quiet.
The “Chief Standards Officer”-a man whose shoes cost more than my first car-looks at me like I’ve just asked him to explain the thermodynamics of a toaster. He tells me that we will “address the seasonal variance as a secondary workstream.”
Translation: “We didn’t think about that, but we’re going to keep the rule anyway.”
This is the moment where the diet truly hurts. I want a bagel. I want a bagel more than I want “synergy.” But more than that, I want a licensing strategy that reflects how we actually work. I want the rulebook to be a reflection of the best practices we’ve already discovered, not a fantasy novel written by a consultant.
As I leave the room, the binder remains on the table, a heavy, plastic-wrapped monument to the way things “should” be. Outside, in the real world, the servers are still humming. The Device CALs are still doing their invisible work, quietly routing sessions for people who will never read the policy.
The exception is still the rule, and the rule is still a ghost. I’m going to go find a salad. Or a pizza. Probably a pizza. Because if I’ve learned anything today, it’s that the “official plan” for my dinner is likely going to be the first thing that gets ignored once I actually hit the ground.
Real life, whether in licensing or in lunch, has a way of asserting itself, no matter what the binder says. The trick is to make sure you have the right tools to handle the reality when the theory inevitably fails. That’s not being a rebel; that’s just being an admin who knows how to keep the warehouse running.
Theory | Friction | Reality
And if the warehouse is running, the committee can stay in their room and talk about “secondary workstreams” as long as they want. Just as long as they don’t touch the server room.
The sun is setting, casting long shadows across the parking lot. I’m thinking about the Windows Server 2022 rollout next month. The plan says “User CALs.” I’ve already got the quote for the Device CALs.
Because at the end of the day, my responsibility isn’t to the binder. It’s to Mike on the loading dock. And Mike needs his terminal to work. That’s the only standard that actually matters.
The diet lasted exactly two hours and twelve minutes. The standard will likely last a year before it’s quietly revised to include “supplementary addendums” that essentially re-legalize everything it just outlawed. It’s a cycle as old as bureaucracy itself.
The map-makers will eventually have to talk to the hikers. Until then, we’ll just keep the machines running in the spaces they haven’t learned to map yet.