The heavy brass paperweight on the CFO’s desk is shaped like a resting lion, an object of significant heft that serves no purpose other than to remind the room that some things are meant to stay exactly where they are put. It is a physical manifestation of gravity in a world that increasingly feels like it is made of smoke.

Ivan stares at that lion while the air in the boardroom grows thin, waiting for the verdict on a quote he has spent three weeks perfecting. To Ivan, the quote represents a fortress; to the woman behind the desk, it represents a puncture in her quarterly projections.

Although the budget cycle demands a predictability that favors the slow drip of a subscription, Ivan knows that the drip eventually becomes a flood that drowns the department in recurring liabilities. He is here to argue for a “perpetual” purchase-a word that, in modern software procurement, sounds almost as atavistic as a handwritten ledger.

His CFO, however, is looking for a way to make the number smaller, even if that means paying it forever. The disagreement is rarely about the total amount of money. It is a fundamental conflict of visibility.

The CFO is looking at a two-dimensional sheet where every number is a competitor for limited space. Ivan is looking at a four-dimensional architecture where the fourth dimension is time-specifically, the time between 2:00 AM on a Sunday and the moment a licensing server decides to stop recognizing a temporary “grace” token.

When she looks at his request for a 50-pack of Remote Desktop Services (RDS) Client Access Licenses, she sees a capital expenditure. He sees four years of not being woken up by a frantic helpdesk lead.

The Transparency of Helplessness

The tension in the room is a quiet, vibrating thing. I felt a similar version of it this morning, standing in the rain outside a grocery store, staring through the window of my car at my keys hanging in the ignition. It is a specific kind of helplessness-to be separated from the thing you need by a transparent but impenetrable barrier.

In IT, that barrier is often the “subscription expired” notification. You have the server, you have the users, you have the network, but because a recurring payment failed or a credit card expired in a system no one has checked in eighteen months, the door is locked.

Although the cloud promised us freedom from hardware, it also introduced a new kind of fragility: the dependency on a constant handshake with a distant billing department. Ivan’s goal is to remove that handshake. He wants to buy his keys, put them in his pocket, and know that the door will open every time he turns the handle.

The Central Myth of “Flexibility”

“Is there a monthly option?” the CFO asks, her voice carrying a certain weary perspicacity. “The board likes to see opex. They like the flexibility of turning things off if we downsize.”

This is the central myth of the subscription economy. It assumes that “flexibility” is a benefit for things that are actually foundational. You don’t want “flexibility” in your foundation. You want it to be as obdurate as a mountain.

Remote desktop access for a distributed workforce is not a “maybe” that you might want to turn off next Tuesday; it is the central nervous system of the company.

To ground this in the technical reality of how these things actually work, we have to look at the RD Licensing role. When a user tries to connect to a session host, the host doesn’t just let them in. It goes on a scavenger hunt for a valid license.

It checks the license server, which must be activated through a Microsoft clearinghouse. If you are using a subscription model, that server is constantly checking its pulse, making sure the subscription is still active.

If you use a perpetual license, the server stores a permanent key. Once that key is installed, the conversation is over. The “clearinghouse” has done its job, the license is issued to the user or device, and the connection is made. It is a local, private transaction that requires no further permission from the outside world.

The Lighthouse Principle

Maria J.-P., a lighthouse keeper I once met on the rugged coast of the North Atlantic, understands this better than any systems administrator. Although the modern world suggests that everything can be managed remotely via a dashboard, Maria knows that when a storm hits, the only thing that matters is the gear you have in the room with you.

She keeps a year’s worth of fuel and physical spare parts for the rotating lens. She doesn’t “subscribe” to a light-as-a-service model. If the light goes out, ships hit rocks. If the licensing server goes out, the company hits a wall.

Ivan explains that he found a provider, the RDS CAL Store, that specializes in exactly this kind of permanence.

He points out that they provide formal quotes for specific quantities-not just the round numbers that make a spreadsheet look tidy, but the actual 35 or 120 seats the company needs right now. He emphasizes the 15-minute delivery.

In the CFO’s world, 15 minutes is a coffee break. In Ivan’s world, 15 minutes is the difference between a minor hiccup and a full-scale mutiny by the sales team who can’t log into their CRM.

The Interruption Tax

The CFO taps her pen against the lion’s head. She is calculating the “tax” of ownership versus the “tax” of renting. But she isn’t calculating the “interruption tax.”

She isn’t calculating the cost of the four hours Ivan will spend on the phone with a vendor two years from now because a subscription seat-count didn’t sync correctly during a server migration.

Although the finance office views a one-time payment as a “lumpy” expense, the IT department views it as a “set and forget” insurance policy. This is where the instruments fail. Her thermometer says the room is expensive; his barometer says the pressure is dropping and a storm is coming.

“What happens if we upgrade?”

Ivan is ready for this. He explains that by purchasing perpetual licenses for Windows Server 2022 or 2025, they are buying a runway. Licenses are backward compatible.

If they buy for 2025 now, they can use them on their 2022 servers today and have the rights ready for the migration tomorrow. There is no “grace period” anxiety. There is no susurrus of doubt about whether the keys will work.

I remember the click of my car door closing this morning, that final, irrevocable sound that told me I was on the wrong side of the glass. That is the sound of a license grace period ending.

Microsoft gives you 120 days of “free” remote desktop access when you first set up a server. It is a seductive, dangerous gift. It creates a false sense of security. Companies live in that 120-day bubble, forgetting that the clock is ticking.

When day 121 arrives, the server simply stops accepting connections. There is no warning shot. There is just the lock. Ivan doesn’t want to live in the bubble. He wants to own the lock and the key.

He shows her the 60-day money-back guarantee and the PayPal Buyer Protection offered by the store. He is trying to speak her language-the language of risk mitigation. He isn’t just buying software; he is buying an exit strategy from the cycle of recurring anxiety.

The CFO finally stops tapping the pen. She looks at the quiddity of the situation-the essence of the thing. She sees that Ivan isn’t asking for a toy. He is asking for a structural component.

“The ledger measures the shadow of the quote, while the server lives inside the light of the license.”

“Fine,” she says. “Get the quote converted to a purchase order. But I want a document showing exactly what we own and where the keys are stored.”

Ivan nods, a small smile playing at the corners of his mouth. He knows that once the licenses arrive-which they will, in about the time it takes him to walk back to his desk and finish his cold coffee-he can install them, activate the server, and effectively delete that entire category of worry from his brain for the next half-decade.

The Value of Silence

We often mistake the cost of an object for its value, but the value of a perpetual license isn’t in the bits and bytes. It is in the silence. It is in the absence of a “payment declined” email.

It is in the knowledge that your infrastructure doesn’t have an expiration date. Although the CFO sees one line item on a spreadsheet, Ivan sees four years of peaceful Sunday mornings, a lighthouse with plenty of fuel, and a car with the keys firmly in his hand.

In the end, every organization has to decide which instruments it trusts. You can trust the thermometer and react to the heat of the moment, or you can trust the barometer and prepare for the long haul. Most of the time, the cheapest way to buy something is to buy it once.