The Medieval Physics of IT Infrastructure

Restoring a medieval stained glass window is less about the glass and more about the lead. Peter J.-M., a man whose hands are permanently stained with the grey oxidation of his trade, once explained to me that the lead cames-those H-shaped strips that hold the fragments of history together-have a life cycle that has absolutely nothing to do with the sun hitting the glass.

The lead expands and contracts on its own clock. If you try to force a new pane into a frame that hasn’t finished settling, the glass will eventually shatter under the pressure of a metal that doesn’t care about your schedule. The metal is the reality; the schedule is the hope.

I bit my tongue this morning, quite literally, while chewing a piece of dry toast. The sharp, metallic tang of blood is a reminder that the physical world has a way of asserting its presence exactly when you are thinking about something abstract, like a fiscal quarter.

It is hard to be philosophical about infrastructure when your mouth hurts and your server is about to lock out half the engineering department. The pain is a localized friction, much like the friction Karin is currently feeling as she stares at her desk.

Karin’s Paper Calendar and the 18-Day Desert

Karin is currently mapping dates on a sheet of scrap paper. She doesn’t use a digital calendar for this because digital calendars are too clean; they make impossible things look achievable. On paper, the gap is visible.

The technical deadline for her Remote Desktop Services grace period is 12 June. That is the day the 120-day timer, which started the moment the first user logged into the new terminal server, runs out. Across the page, she has circled 1 July. That is the day the Q3 budget is released. Between those two dates lies an eighteen-day desert where no work can happen because no licenses can be bought.

She is drafting an email-the “Exception Request.” It is a genre of literature she has mastered through repetition. She writes about “critical path items” and “unforeseen infrastructure dependencies,” even though she saw this coming in February. The finance department, however, operates on a Gregorian rhythm that treats the change from June to July as a structural barrier as impassable as a mountain range. They see a calendar; the server sees a countdown.

This mismatch is rarely a failure of planning. We are taught to believe that if we were just slightly more organized, if we had “synergy” or better “forward-looking procurement strategies,” these gaps would close. This is a lie. No software vendor’s grace period is designed to align with a mid-market manufacturing company’s fiscal quarter.

“No Microsoft licensing cycle is synchronized with the tax year of a law firm in Ohio.”

To understand why this happens, you have to look at how the 120-day grace period actually functions under the hood. When you install the Remote Desktop Session Host role, Windows Server is generous. It allows connections without a license server to give you time to “configure the environment.”

But it isn’t a passive timer. The server records the first connection and starts a hardware-linked countdown. Even if you uninstall the role and reinstall it, the timer often remembers. It is a biological clock for a digital organism. It doesn’t know about Q2 or Q3.

Finance, on the other hand, operates on the principle of the “Closed Box.” A quarter is a box. Once the lid is closed on Q2, no more money can leave the box without a level of administrative violence that most managers find exhausting. When Karin asks for money on June 7th, she is asking them to reopen a box that has already been taped shut and moved to the warehouse. They aren’t being difficult; they are simply following the laws of their own physics.

The Cost of Scaffolding and Desperate Moves

This friction is not a bug in the system; it is a feature of the market. If you are desperate, you don’t haggle. If you are desperate, you don’t look for the most efficient long-term solution. You look for the person who can give you a key in fifteen minutes. This is where the urgency-sellers live. They thrive in the eighteen-day desert between the 12th of June and the 1st of July.

I remember Peter J.-M. telling me that the most expensive part of glass restoration isn’t the gold leaf or the cobalt glass; it’s the scaffolding. If you have to keep the scaffolding up for an extra month because the lead hasn’t arrived, the cost doubles.

In IT, your “scaffolding” is the temporary workaround, the manual resets, and the hours spent by sysadmins trying to trick a grace period that cannot be tricked. The only way to bridge the gap between these two incompatible clocks is to find a mechanism that speaks both languages.

Most people wait for the emergency to happen because they believe the calendar will eventually show mercy. It won’t. The 120-day clock is an indifferent machine. It is a lead came that will expand until it cracks the glass.

I’ve seen administrators try to “rearm” the grace period using registry hacks they found on a forum from 2014. It is a desperate move, like trying to fix a broken tooth with superglue. It might hold for a day, but the underlying structure is still compromised, and eventually, the pain returns with interest.

Every time Karin writes one, she loses a little bit of her authority. She has to go, hat in hand, to people who don’t know what a CAL is, and explain why the world will end if she doesn’t get $3,420 by Tuesday. They look at her like she’s a bad gardener who forgot to water the plants, even though she’s been screaming about the drought for months.

The psychological cost of this misalignment is why IT turnover is so high. It isn’t the technology that burns people out; it’s the constant, grinding friction of being the person who has to reconcile two different versions of time.

If we stop viewing the budget cycle as a logical tool and start viewing it as a seasonal weather pattern, we might survive it better. You don’t get mad at the winter for being cold; you buy a coat in October. But procurement is rarely that simple. Procurement is a game of chicken where the server always flinches first.

The Perspective of Generations

Peter J.-M. once showed me a piece of glass from the fourteenth century that had been etched with the name of a glazier who worked on it during a plague. The man knew he might not finish the window, but he signed the glass anyway.

He was working on a timeline that spanned generations, while the world around him was ending in weeks. That is the kind of perspective you need to survive a 120-day grace period in a 90-day fiscal world. You have to realize that the server is temporary, the budget is arbitrary, but the data-the “glass”-is what you are actually trying to save.

Karin finished her email. She didn’t send it. She looked at the blood on her napkin from her bitten tongue and decided she was tired of asking for permission to do her job. She attached the quote for the 43 User CALs, CC’d the Director of Operations, and titled the subject line: “Risk Mitigation for June 12th System Shutdown.” She stopped calling it an “exception.” She started calling it a “requirement.”

The shift in language is subtle, but it’s the only way to survive. When you stop acting like a petitioner and start acting like a translator, the finance department begins to listen. They still might not give you the money until July 1st, but at least they know why the lights went out on the 12th.

We live in the friction. We live in the gap between what the software demands and what the spreadsheet allows. It is a noisy, uncomfortable place to be, but it is the reality of the modern infrastructure.

The lead will always move. The glass will always be at risk. The only thing you can control is whether or not you have the right tools to catch the pieces when they start to fall. Karin hit send. The tongue still hurt, but the plan was finally on the table. Complexity is the only constant.