Priya M.-C. leaned forward, her palm resting lightly on the dashboard of the sedan as she watched the student’s eyes in the rearview mirror. We were creeping through a residential neighborhood in late autumn, the kind of afternoon where the light turns thin and amber, making every shadow on the pavement look like a pothole.
The student, a soft-spoken teenager who treated the brake pedal like a fragile heirloom, was trying to navigate a gentle curve. Every few seconds, he would give the steering wheel a sharp, nervous tug toward the center line.
He was over-correcting, though the car was perfectly aligned with the arc of the road, because he had not yet learned to trust the physics of the machine. He couldn’t feel the tires “biting” the asphalt, so he kept adding more input, more rotation, and more force. In his mind, the absence of a jarring sensation meant he wasn’t doing enough.
To Priya, who had spent in the passenger seat of various dual-brake vehicles, this was the most common error of the novice: the belief that if you aren’t actively pushing against something, you are losing control.
This sensory disconnect is not limited to teenagers in sedans. It is the defining characteristic of the modern IT department’s relationship with its budget. Specifically, it is why the industry continues to buy more software capacity while the existing infrastructure sits half-empty. We are over-steering into the curve because the waste doesn’t vibrate the steering wheel.
The Phantom Twenty
A few days ago, I pulled a pair of heavy denim jeans out of the dryer-the ones I only wear when the temperature drops below fifty degrees. In the small watch pocket, I found a crumpled twenty-dollar bill. The rush of localized joy was entirely out of proportion to the value of the money. It was “found” money, a tiny victory against the entropy of the household.
The sensory disconnect: We react to the physical twenty, but ignore the hundreds lost in “ghost” licenses.
But earlier that same morning, I had looked at a client’s server report and noticed fourteen idle Remote Desktop Services seats that had been paid for and never touched. That loss represented hundreds of dollars, yet it triggered none of the visceral reaction that the twenty-dollar bill provided.
The twenty-dollar bill has mass. It has a tactile presence. An idle license, however, is a ghost. It produces no heat, it occupies no physical rack space, and it never sends an alert to the dashboard saying it is lonely. Because unused capacity produces no pain, there is no biological signal to stop buying. We keep adding seats for new projects without ever checking the attic to see how many chairs we already own.
The Survival Instinct Failure
I once spent a considerable amount of time arguing that this was a failure of management or a lack of discipline. I told a regional director that his team was being negligent with their licensing renewals. I was wrong. It wasn’t negligence; it was a fundamental failure of the feedback loop.
Humans are evolutionarily hardwired to react to felt pain. If you touch a hot stove, you pull your hand away. If a server goes down and fifty people can’t log in to their desktops, the “pain” is immediate and deafening. The phones ring, the tickets pile up, and the adrenaline spikes.
To avoid that pain, we over-provision. We buy twenty percent more than we need as a “buffer.” But because there is no corresponding pain for having too much, the buffer only ever grows. It never shrinks.
In the world of Microsoft Server infrastructure, specifically regarding Remote Desktop Services (RDS), this over-steering becomes expensive very quickly. Whether you are running Windows Server or preparing for the transition to , the licensing model relies on Client Access Licenses (CALs).
The Invisible Dust
You have the choice between User CALs and Device CALs. Most organizations default to User CALs because they seem simpler in an age of multiple devices. A single user can hop from a laptop to a home PC to a tablet, all under one license.
The trouble starts when those users leave the company, change roles, or simply stop using the remote environment. In a traditional physical office, you would see the empty desk. You would see the dust gathering on the monitor.
But in the digital environment, that “seat” remains assigned. The procurement officer, seeing a request for ten new hires, looks at the current project requirements and buys ten more seats. They don’t register the twelve idle ones already on the books because nothing about paying for unused capacity ever hurts enough to prompt a second look.
The market has responded to this by creating ready-made packs-increments of 5, 10, 20, or 50. This is convenient, certainly, but it also encourages the “rounding up” mentality. If you need 32 licenses, you buy two packs of 20 or a pack of 50 to be safe. That extra eighteen-seat margin is a silent tax. It is the “phantom lane” that Priya’s student was trying to steer into.
Finding the Road Feel
When you are looking to expand or refresh your environment, the goal should be to find a signal for that silent waste. This is where tools like a dedicated CAL calculator or pre-sales sizing help become more than just “customer service.” They are sensory extensions.
They provide the “road feel” that the digital invoice lacks. If you are uncertain about the exact count, sourcing from a specialist like the
allows for a more surgical approach to procurement. Instead of just guessing and over-steering, you can match the license count to the actual human requirement of the server.
Precision Sizing vs. Ghost Steering
The industry likes to talk about “scalability” as if it only moves in one direction: up. We celebrate the ability to add a thousand users in an afternoon. But true scalability requires the ability to feel the edges of your environment. It requires knowing where the utility ends and the waste begins.
Steering Against Ghosts
I think back to Priya and the silver Honda. At one point, she had the student pull over to the side of a quiet road. She told him to take his hands off the wheel for a second and just look at the car’s position.
“You’re trying to fix a problem that hasn’t happened yet. You’re steering against a ghost.”
– Priya M.-C., Driving Instructor
In IT infrastructure, we are constantly steering against the ghost of “insufficient capacity.” We are terrified of the moment a user receives an error message saying no licenses are available. That fear is a powerful motivator. It is so powerful that it blinds us to the opposite problem.
We end up with “zombie” licenses-perpetual rights to software that no longer has a purpose, tied to users who no longer have a login. This isn’t just about the money, though the money is significant. It’s about the clarity of the system.
A bloated system is a complex system. When you have three hundred licenses for two hundred and ten active users, your auditing becomes a nightmare. You start to lose track of which versions of Windows Server you are actually supporting. Are these licenses? Have they been upgraded to ? Will they carry over to ?
The Licensing Staircase
If you look at your licensing history over the last , you will likely see a staircase. The line goes up, stays flat, and goes up again. It almost never goes down. This is the visual proof of the sensory disconnect.
The “No-Pruning” Growth Pattern
We add during the growth spurts and we hold during the lean times, but we rarely prune. We treat digital licenses like permanent furniture rather than what they actually are: access rights for living, breathing, changing humans.
The more “noise” you have in your license pool, the harder it is to make a clean, strategic decision when the next major tech debt cycle hits. The solution isn’t to become stingy or to risk the “out of licenses” error that everyone fears.
The solution is to introduce a signal that mimics the pain of waste. For some teams, this is a monthly audit that is presented not as a spreadsheet, but as a literal dollar figure compared against active login sessions. For others, it’s about changing the procurement habit from “buying for the worst-case scenario” to “buying for the actual trajectory.”
Shaping the Fleet
There is a specific kind of satisfaction in right-sizing an environment. It feels remarkably similar to that moment when you find a twenty-dollar bill in your jeans. It’s the realization that you had more resources than you thought, simply because you stopped letting them leak out into the digital ether.
When you buy exactly what you need-whether it’s a custom quantity or a specific 10-pack of User CALs-you are no longer over-steering. You are finally feeling the road. We need to stop treating software procurement as a chore of “filling the tank” and start treating it as a discipline of “shaping the fleet.”
The server doesn’t care if you’ve over-paid. The vendor, in most cases, won’t complain if you buy more than you use. The only person who can feel the vibration of that waste is the person who looks past the “buffer” and asks why the seats are empty.
The extra seat remains invisible because the invoice for an idle license never demands a chair.
Priya’s student eventually got the car into the parking space. It took him three tries and a lot of unnecessary wheel-turning, but he got there. As he put the car in park, he sighed with a relief that was almost physical. He thought he had conquered the road.
Priya, however, just looked at the tire marks he’d left-erratic, jagged lines that told the story of a driver who was fighting a battle that didn’t exist. “Next time,” she said, “try to feel the car’s weight. Don’t just look at the lines. Feel where the weight is shifting.”
That is the challenge for the modern IT leader. Don’t just look at the “User” count in Active Directory. Feel where the financial weight of the infrastructure is shifting. If you are paying for capacity that isn’t carrying any weight, you aren’t being “safe.” You’re just over-steering into a curve that ended three miles ago.
When you finally stop adding steering input to a car that is already straight, something wonderful happens. The ride gets smoother. The engine doesn’t have to work as hard. You stop fighting the machine and start moving with it.
The same is true for your server environment. When the licenses match the users, the “noise” of procurement disappears, leaving you with a clean, efficient system that does exactly what it was designed to do: provide access, not collect digital dust.
The next time you find yourself about to “round up” on a license purchase, think about that twenty-dollar bill in the watch pocket. Think about how much better it feels to have the money in your hand than to have it sitting in an unused “seat” on a server that will never know it’s there.
Realizing that you have the power to stop the silent waste is the first step toward building a department that doesn’t just survive the audit, but actually understands the value of every single seat in the room. In an industry that keeps buying because it can’t feel the loss, the most “extraordinary” thing you can do is to start feeling the road.