The password reset request for ‘t_hargrove’ failed three times before I realized the account shouldn’t have existed. According to the master service agreement, the client, a mid-sized logistics firm in northern New Jersey, operated strictly between the hours of eight in the morning and six in the evening. It was currently on a Tuesday.
The air in my office was stale, smelling faintly of an old toasted sandwich and the ozone smell that comes from a laser printer that has been left on for too long. I clicked the ‘Security Groups’ tab. Hargrove was listed as a ‘Seasonal Field Associate,’ a role that was not mentioned in the contract I had signed . I looked at the activity logs. Hargrove had been logging in from a mobile hotspot in a parking lot in Secaucus for the last .
The Map is Not the Territory
The contract is a static document. It is a series of ‘whereas’ clauses and ‘heretofores’ that describe a company that was frozen in amber on the day the lawyers finally stopped arguing. It describes forty-two full-time employees, two physical servers running Windows Server 2019, and a predictable rhythm of data usage that follows the sun.
The reality, which I was staring at in the form of a scrolling wall of green text on a black background, was a chaotic, living organism. There were eighteen contractors like Hargrove who didn’t exist on the payroll I was supposed to support. There were three virtual machines that had been spun up by a rogue department head who didn’t want to wait for a budget approval. There was a night shift that had manifested out of thin air to handle a surge in shipping volume.
The “Ghost Gap”: Supporting 22 users who technically don’t exist in the legal framework.
I spent the better part of last week reading every word of the standard Microsoft licensing terms and conditions. I didn’t do it because I had to; I did it because I wanted to see if the language of the law had any room for the messiness of the world. It doesn’t.
The language of a license is the language of a grid. It assumes you can count your people like you count sheep. It assumes that a user is a person with a name and a desk and a predictable pulse. It does not account for the fact that people share logins because they’re in a hurry, or that a ‘device’ in might be a tablet, a phone, and a smart fridge all connected to the same Remote Desktop session.
The practitioner-the person like me who sits at the console while the rest of the world sleeps-lives in the movie. The contract is just a still frame at the beginning of the credits. I am the one who has to reconcile the two. I am the unpaid keeper of the difference between the fiction the CEO signed and the reality the night shift is currently breaking.
Lessons from the British Admiralty
In the mid-nineteenth century, the British Admiralty had a similar problem with their nautical charts. A surveyor would go out to a harbor in the West Indies, spend measuring the depth of the water with lead lines, and draw a beautiful, precise map. That map would be engraved on copper, printed on heavy paper, and distributed to every captain in the fleet.
The map said the harbor was thirty feet deep at the entrance. But the ocean is not a document. A hurricane would come through, or a river would deposit ten thousand tons of silt, and the thirty-foot entrance would become a twenty-foot trap. The captains who survived were the ones who stopped looking at the chart and started looking at the color of the water. They knew the chart was a historical record of what the harbor used to be, not a report on what it was.
My clients send me org charts that are basically those old copper-plate maps. They show a neat hierarchy with boxes and lines. They show ‘Department of Finance’ and ‘Department of Operations.’ They never show ‘The Guy Who Only Works Weekends and Borrowed a Laptop from His Cousin.’
When I see an unauthorized user pinging the server from a residential IP address in the middle of the night, my first instinct is to think it’s a breach. I go through the protocols. I check the geofencing. I look for suspicious file transfers. Then I realize it’s just the reality of the business outgrowing its paperwork.
The business needed more hands, so it hired them. It didn’t tell the IT department, and it certainly didn’t tell the legal department, because the business is trying to survive, and paperwork is the friction that slows survival down.
Professional Vertigo
This creates a specific kind of professional vertigo. I am billing for forty-two users because that’s what the contract says. But I am supporting sixty-four users because that’s what the server says. If I shut down those twenty-two ‘ghost’ users, the client’s business stops. If I don’t shut them down, I am technically in violation of the very contract I’m supposed to enforce. I have become a sort of silent partner in a functional lie. I keep the ‘fictional’ infrastructure running on ‘real’ time.
Every once in a while, the gap becomes too wide to ignore. The server starts to lag because the RDS sessions are oversubscribed. The CPU usage spikes to 98% and stays there, a flat line of digital exhaustion. That’s when the client calls. They don’t call to tell me they hired twenty new people. They call to tell me “the internet is slow.”
They describe a technical symptom for a structural problem. They want me to fix the server, but what they really need is to fix their relationship with the truth. They need to admit that the company on the paper is gone.
Licensing the Pulse
When we finally get to the point of reckoning, I have to find a way to bring the paperwork in line with the pulse of the company. I have to find the right count of licenses that doesn’t punish the client for growing, but doesn’t leave them vulnerable to an audit that would ruin them.
This is where the standard enterprise procurement process usually fails. It’s too slow. It wants to sell you a bucket of a thousand seats when you only need twenty-three. It wants you to sign another three-year fiction. To fix the real-world problem, I need a real-world source. I often find myself looking for providers that allow for that kind of granular, immediate adjustment.
When the reality on the ground demands twenty-five more seats because a new warehouse just opened, I don’t have time to wait for a corporate account manager to return my call in . I need to go to the RDS CAL Store and get exactly what the telemetry says I need, right now. It’s about licensing the movie, not the still frame.
Archaeology of the Logs
There is a certain dignity in the details. Joseph Mitchell used to write about the ‘bottom of the harbor,’ the things that accumulated on the floor of the New York bays-old anchors, brass buttons, rotted timbers. An MSP’s logs are the bottom of the corporate harbor.
You see the things that the management has forgotten or ignored. You see the user who hasn’t logged in since but still has an active ‘Super Admin’ account. You see the printer that is still trying to authenticate every thirty seconds even though it was tossed into a dumpster . You see the software version that was supposed to be decommissioned but is still being used by one person in the basement because ‘it’s the only way to open the old files.’
I remember a client-a small manufacturing firm that made specialized valves for chemical plants. Their contract said they had ten office users. When I did my first audit, I found thirty-seven unique MAC addresses connecting to the Remote Desktop server every day.
It turned out the shop floor workers had figured out that they could use an old thin client in the breakroom to check their personal email and look at the production schedule. They weren’t trying to be malicious. They were just trying to do their jobs and stay connected. The contract knew nothing of the breakroom. The contract didn’t know about the dusty thin client with the cracked screen. But I knew. I saw the traffic. I saw the heartbeat of the factory floor through the flickering lights of the switch.
For a long time, I tried to be a purist. I tried to force the client to match the contract. I sent emails with ‘Urgent’ in the subject line, pointing out that their user count was out of compliance. I was ignored. Or worse, I was told to ‘just make it work.’ I realized then that the role of the modern technologist is not to be a policeman of the paperwork. It is to be a bridge. My job is to manage the friction between the way things are written and the way things are done.
It is a strange way to make a living. You are the only person in the room who knows exactly how many people are actually working. You are the only one who knows that the ‘99.9% uptime’ promise is being held together by a script you wrote on a Sunday afternoon and a license you bought with a credit card because the procurement department was on vacation.
You live in the gap. You reconcile the fiction with the fact, one CAL at a time, one password reset at a time, until the movie finally matches the map, at least for a few minutes, before the world moves again.
Closing the Ticket
Last night, I finally closed the ticket for Hargrove. I didn’t delete his account. I didn’t send a stern memo to the client about unauthorized night-shift contractors. I just updated the internal documentation to reflect that ‘Seasonal Field Associates’ are now a part of the real-world infrastructure.
I adjusted the license count to make sure we were legal. I looked at the monitor one last time before turning off the lights. The screen showed thirty-two active sessions. The contract still said twenty. But the server was breathing steady, the fans were humming a low, mechanical song, and for the first time in weeks, the logs were clean.
The fiction was still there, filed away in a cabinet, but the reality was finally accounted for.
