I once convinced a mid-sized architectural firm to spend $14,230 they did not need to spend. It remains my most successful failure. I sat in a boardroom with wood-paneled walls. I spoke with the calm authority of a man who had seen a thousand server rooms. I told them they needed exactly 95 Device CALs for their infrastructure.
I was wrong. I was deeply, fundamentally incorrect about their growth trajectory and their shift toward remote work. As I finished the final sentence of my recommendation, I sneezed seven times in a row. It was a violent, rhythmic interruption that should have felt like an omen. Instead, I just wiped my nose and accepted their handshake.
They followed my advice to the letter. have passed since that meeting. To this day, the firm believes I saved them from a compliance nightmare. They never once ran out of licenses. Their remote desktop environment never crashed due to a seat shortage. The server never issued a single error message regarding their entitlement.
Because I over-prescribed, the system worked perfectly. This is the great curse of my profession. A wrong recommendation that is too small generates a crisis. A wrong recommendation that is too large looks identical to a perfect one.
The Asymmetry of Silence
In this field, we consistently confuse being certain with being right. We have no correction mechanism. If an engineer builds a bridge too weak, it cracks. If a doctor prescribes the wrong dose, the patient reacts. But if an IT consultant prescribes a license count that is 30% higher than necessary, the only result is silence. Silence is often mistaken for success.
This lack of feedback creates a dangerous psychological environment. It allows “experts” to accumulate decades of experience without ever being corrected by reality. We operate in a domain where the signal of failure is asymmetric. You only hear the alarms when you provide too little. You never hear the sirens when you provide too much.
Under-Provisioning
Immediate crisis, error messages, and management visibility. Failure is loud and corrected quickly.
Over-Provisioning
Perfect uptime, no warnings, and expert validation. Failure is silent and remains a permanent budget item.
Consider the following aspects of this feedback vacuum:
-
01
The Absence of Failure: An oversized purchase creates a permanent buffer against errors.
-
02
The Repetition Bias: Advice that does not cause a crash is repeated as truth.
-
03
The Financial Buffer: Waste is often hidden within the complexity of annual budgets.
To understand this, we must define the concept of a “Silent Success.” A Silent Success is an outcome that achieves a goal through unnecessary excess. Imagine buying a fleet of twenty buses to move fifty people. The people move. The goal is met. The person who ordered the buses is seen as a logistical genius. No one ever asks if ten buses would have sufficed. The waste is invisible because the mission succeeded.
The Licensing Echo Chamber
In the world of Microsoft licensing, this happens daily. An admin is told they need a specific number of Remote Desktop Services (RDS) Client Access Licenses. They are under pressure. The grace period is ticking down. They reach out to a senior peer.
That peer, having never been told they were wrong in the past, gives a “safe” number. This number is usually inflated. The admin buys the licenses, the warning goes away, and the peer’s “expertise” is validated once again.
“
The loudest voice in the room is usually the one most afraid of being audited by the truth.
– Blake S.K., Conflict Resolution Mediator
He was talking about labor disputes, but he could have been talking about sysadmins. Confidence is not a metric of accuracy. It is a metric of how many times you have said the same thing without being hit by a metaphorical car.
The problem is that the “car” in our industry is invisible. We do not have a dashboard that shows us the gap between what we bought and what we used. We have no “Correction Mechanism.” Without that mechanism, we are just guessing with increasing levels of volume.
This is why deliberate sizing must be a positive, conscious act. It cannot be left to “gut feelings” or the “industry standard.” The industry standard is often just a collection of people who all overbought. If you want to break this cycle, you have to look at the data. You have to use tools that force you to confront the actual needs of your environment.
Buying Precision, Not Rumors
Stop overpaying for a security blanket. Calculate exactly what your environment requires.
Explore the RDS CAL Store
They provide a calculator to help you size the purchase before you spend a dime.
The User vs. Device Dichotomy
When we talk about Remote Desktop Services, the confusion usually centers on the choice between User and Device CALs. A User CAL follows the person. A Device CAL follows the hardware. It sounds simple. Yet, people get this wrong constantly.
They buy Device CALs for a workforce that uses three devices per person. Or they buy User CALs for a factory floor where twenty people share one computer. Both mistakes “work.” The lights stay on. The users can log in. The only difference is the invoice.
Initial Waste (20%)
$5,000
10-Year Cumulative Waste (Upgrades + Maintenance)
$28,500
If you are currently staring at a server that is about to lock you out, the temptation is to overreach. You want the problem to go away forever. You want to buy so much “compliance” that no one ever asks you a question again. But that is how the Certainty Trap snaps shut. You are paying a tax on your own lack of data.
The danger of the “Safe Number” is that it becomes a permanent line item. Software licensing is rarely a one-time event. It is a foundation. If you build your foundation 20% larger than it needs to be, every upgrade for the next decade will be 20% too expensive. You are not just buying licenses; you are buying a legacy of waste.
I think back to that architectural firm. They are probably on their third server migration by now. They likely still buy 95 licenses every time they upgrade. They do this because I told them to in . My ghost sits in their procurement office, whispering a number that was born of a guess and validated by a lack of disaster.
It makes me feel a bit sick. I didn’t give them expertise; I gave them a very expensive security blanket. We must learn to value precision over comfort. Precision requires effort. It requires looking at the actual number of unique users versus the actual number of workstations. It requires understanding that contractors might only need access for , not forever.
A New Mark of Expertise
The field of IT infrastructure is full of people who have been “right” for twenty years only because they have never been proven wrong. We have to stop using the absence of an error message as a certificate of brilliance. True expertise is the ability to find the thin line where necessity meets efficiency.
If you are a sysadmin, your job is to be the steward of company resources. That stewardship is undermined by the Certainty Trap. When a consultant gives you a number, ask them how they calculated it. If they say “it’s just what most people do,” you should be worried. “What most people do” is usually a sign of a domain with no feedback loop.
To fix this, we need a cultural shift. We need to celebrate the person who finds a way to use 10% fewer licenses through better management. Currently, we only notice the person who bought too few and caused a lockout. We reward the over-buyer with peace and quiet, and we punish the precise-buyer with the risk of a “License Limit Reached” notification.
This is a perverse incentive structure. It rewards the waste of capital. We have to become our own correction mechanism. We have to be the ones who look at the usage reports. We have to be the ones who ask if the Device CAL model still makes sense in an age of iPhones and tablets.
The next time you are about to make a purchase, stop and ask if you are being right or just being certain. If you don’t know the difference, look at the data again. Use a calculator. Talk to someone who cares about the sizing, not just the sale. If you do that, you might find that the “industry standard” is just a very expensive rumor.
I still sneeze when I think about that architecture firm. My body remembers the mistake even if their accounting department doesn’t. I can’t go back and change that recommendation. But I can make sure that the next person who asks me for advice gets a number based on reality, not on a fear of the unknown.
We owe it to our companies, and our industry, to stop hiding in the safety of the oversized. Precision is the only true mark of an expert. Anything else is just a very loud guess.