The dry-erase marker emitted a high-pitched squeak, the kind that sets your molars on edge, as I dragged it across the whiteboard to create yet another jagged arrow. It was 4:38 PM. In the kitchen, the smoke alarm hadn’t gone off yet, but I could smell the distinct, acrid scent of the chicken breasts I’d forgotten in the pan while trying to explain the difference between a person and a piece of hardware to a man who viewed both as identical line items on a spreadsheet. We were staring at a diagram that looked less like a network map and more like a crime scene investigation. There were 28 terminals in the shipping bay, 48 seasonal contractors who shared a single login because ‘it’s easier,’ and 108 remote sales reps who hadn’t stepped foot in the building since 2018.

My client, the finance director, wanted it simple. He wanted a single number he could plug into a cell and turn green. But work isn’t green. Work is grey, messy, and smells like slightly charred poultry. The fundamental frustration of the User vs. Device CAL debate isn’t actually about the licensing terms themselves-Microsoft has written those out in dry, agonizing detail thousands of times. The frustration stems from the fact that nobody actually knows how work happens anymore. We have built these massive, interconnected digital cathedrals, but we’re still trying to count the congregants using 19th-century census methods. We pretend we have ‘users’ who sit at ‘devices,’ but in reality, we have a fluid, chaotic swarm of activity that defies the neat little boxes we try to buy.

I think about Carter Y. often in these moments. Carter is a dollhouse architect-a man who spends 58 hours a week meticulously carving mahogany banisters the size of toothpicks. I met him at a hobbyist convention years ago, and he told me that the hardest part of building a miniature isn’t the scale; it’s the expectation of the human eye. If you build a chair at 1:12 scale, it looks wrong if you don’t account for how light hits a full-sized chair.

Carter Y. once showed me a miniature library he’d built, where every single one of the 888 books had actual, readable text if you used a magnifying glass. He was obsessed with the integrity of the thing. He wouldn’t just glue blocks of wood together and call them books; they had to be books. This is where we fail in IT management. We glue blocks of wood together. We say, ‘We have 508 employees, so we need 508 licenses,’ without ever stopping to ask if those employees are actually the ones doing the work, or if they’re just ghosts in the machine. In the warehouse I was currently mapping, the ‘User’ didn’t exist in the way the finance director thought. The ‘User’ was a collective consciousness of three different shifts, all using the same ruggedized tablets to scan barcodes. If I licensed them by user, I’d be paying for 158 people. If I licensed the devices, I’d only need 38.

Warehouse Licensing Conflict (User vs. Device)

But then you have the corporate office, where one person has a desktop, a laptop, a tablet, and a phone, all hitting the server simultaneously. In that room, the device CAL is a trap that leads to a $2008 headache. It’s a referendum on how we see our people. Are they assets that move between tools, or are the tools the anchors of our production? The reason the ‘User vs. Device’ question is so hard to answer is that it forces us to admit we don’t know who is doing what. We’ve lost track of the rhythm of the floor. We’ve replaced observation with automation, and now that the bill is due, we’re realizing the automation doesn’t have a heartbeat.

The Burnt Chicken Analogy

I walked back to the kitchen to flip the chicken, which was now more carbon than protein. It was a mistake born of distraction, a small failure in my own personal infrastructure. I should have set a timer. I should have known my own limits. But instead, I tried to multitask through a complex licensing audit, and now I’m eating toast for dinner. This is the exact same mistake companies make. They try to ‘multitask’ their way through growth without ever auditing the actual physical reality of their workstations. They assume that because they bought the software, the usage will naturally align with the most cost-effective legal framework. It never does.

We spent the next 48 minutes arguing over the RDS environment. Remote Desktop Services is the great equalizer, but it’s also the place where licensing goes to die a slow, confusing death. If you’re running a terminal server, the stakes are higher because the audit trail is digital and unforgiving. You can’t just shrug and say you didn’t know. You have to choose a path. If you have a high turnover of staff, you’re almost always looking for a windows server 2016 rds cal price that fits the device, so you aren’t constantly reassigned seats to people who quit three days after being hired. But if your staff is lean and mobile, the user-based approach is the only thing that makes sense.

Confusion is just the tax we pay for not paying attention.

Solving a Psychology Problem

I looked at the whiteboard again. Carter Y. would have hated this drawing. There was no symmetry. There was no scale. It was a mess of 18 different colors and crossed-out numbers. I realized then that I was trying to solve a math problem that was actually a psychology problem. The finance director didn’t want to know about the warehouse shifts; he wanted to know why he couldn’t just have one ‘unlimited’ button. He wanted the digital world to be as simple as the dollhouses Carter builds, where the people are made of plastic and never move from where you put them.

Real people are inconvenient. They lose their passwords. They take their laptops to Starbucks. They share their tablets with the guy who forgot his badge. They are the variables that break the 1:1 scale of our licensing models. I’ve seen companies fail audits because they forgot about a single closet full of 28 old thin clients that were still pinging the server every 58 seconds. Those ghosts are expensive.

The Hard Truth vs. The Easy Lie

I eventually convinced the director that we needed a hybrid approach, even though it made his spreadsheet look ‘ugly.’ We needed to license the warehouse by device and the office by user. It required more management, more oversight, and about 88 more minutes of data entry, but it saved them nearly $5008 in the long run. He hated it. He wanted the ‘easy’ lie, not the ‘hard’ truth. People always want the easy lie until the audit letter arrives in an envelope that looks suspiciously like a summons.

Personal Infrastructure Failure

As I sat down to my burnt dinner, I realized that my own life is just as poorly licensed as that warehouse. I have four devices, three email addresses, and I can barely manage to cook a single meal without something catching fire. I am a ‘User’ in the most chaotic sense of the word. I am the reason these systems are complicated. We want the freedom to work from anywhere, on anything, at any time, but we want the billing to be as simple as a punch card from 1958. We want the complexity of the modern world with the administrative overhead of a lemonade stand.

Tomorrow, I’ll have to go back and fix the Active Directory groups to reflect the new reality. It will take at least 8 hours. I’ll probably drink 8 cups of coffee. And I’ll think about Carter Y., carving his tiny mahogany chairs, making sure that even the things no one will ever see are built to the correct scale. There is a dignity in that kind of precision. There is a peace in knowing exactly what you have and where it sits. IT licensing is the opposite of that peace. It is a constant, shifting battle against entropy, a struggle to define the indefinable. But if we stop trying to count, if we just give up and guess, we aren’t just losing money. We’re losing the ability to understand how our own organizations actually breathe. We’re just building dollhouses and pretending we live in them, while the kitchen burns down in the background.