IT Infrastructure & Mobility

The Centralized Inventory and the Fluidity Nobody Mentions

A story of blue lines, red dots, and the impossible task of counting a workforce that refuses to stay frozen.

The floor plan has blue lines. The blue lines show the walls of the office. The office is on the fourth floor of a glass building. There are 212 desks on the floor plan. Each desk has a red dot. The red dot represents a computer.

212

Desks / Dots

1:1

Assumed Ratio

The static inventory model: One desk, one device, one authority.

The computer connects to the server. This is the inventory. The inventory is a list of red dots. The IT manager wrote the inventory in a spreadsheet. The spreadsheet has columns for the serial number. The spreadsheet has columns for the user name.

The spreadsheet was the authority. The IT manager believed the spreadsheet.

The Assumption of Boundaries

The IT manager built the inventory on an assumption. The assumption was that the red dots stayed in the office. The assumption was that the workers stayed at the desks. The network had boundaries. The boundaries were the walls on the floor plan.

The inventory manager assigned one license to each red dot. The math was simple. The math was 212. The company bought 212 licenses. The company felt safe. The company felt compliant.

A salesman went to a hotel in a different city. The salesman opened a laptop. The salesman connected to the server. The server looked at the connection. The server did not see a red dot from the fourth floor.

The server saw a new IP address. The server saw a new MAC address. The server saw a new device. The inventory system created a new row. The count became 213.

The salesman was the same person. The salesman was already on the list. But the inventory did not care about the person. The inventory cared about the access point.

Inventory Discrepancy Log

Initial Baseline:

212 Units

Remote Connection (Hotel):

+1 (Total: 213)

Coffee Shop Access:

+1 (Total: 214)

The inventory was a static model. The workforce was a fluid force.

The IT manager looked at the spreadsheet the next morning. The spreadsheet showed an error. The error said the company was out of licenses. The IT manager checked the desks. All 212 desks were in place.

No new computers had arrived in the mail. No new employees had been hired. The IT manager looked at the logs. The logs showed the hotel connection. The logs showed a connection from a coffee shop.

The logs showed a connection from a home office. Each connection was a new device in the eyes of the software. Each new device required a new license.

The Ghost in the Bag

A contractor arrived on Tuesday. The contractor brought a personal tablet. The contractor needed to check the database. The contractor connected to the Remote Desktop Services.

The inventory system saw the tablet. The inventory system created row 214. The contractor finished the work. The contractor went home. The row remained in the inventory.

The license remained tied to the tablet. The tablet was now in a bag in a different zip code. The license was trapped.

The IT manager tried to clean the spreadsheet. The IT manager deleted the hotel connection. The IT manager deleted the tablet connection. The salesman connected again from the airport. The inventory created row 215.

The system was a machine. The machine followed the rules. The rules said that every unique connection was a unique device. The IT manager was fighting the machine. The IT manager was losing.

$9,240

Initial Sunk Cost

The company thought the cost was a one-time event. They were paying a tax on movement.

The company had spent $9,240 on the initial setup. The company thought the cost was a one-time event. The company was wrong. The company was paying a tax on movement.

Every time a worker changed locations, the inventory broke. Every time a worker used a phone to check an email, the inventory broke.

You are reading this because you have a spreadsheet. You are reading this because your count does not match your reality.

The problem was the choice of license type. The company chose Device CALs. Device CALs are good for factories. Device CALs are good for libraries.

In a library, the computer stays on the table. Different people sit at the table. The computer is the constant. In the modern office, the person is the constant.

The person moves from the desk to the train. The person moves from the train to the house. The person is one entity. The person uses four devices.

The centralized inventory tried to count the four devices. The inventory should have counted the one person.

Switching the Logic

The IT manager realized the error. The IT manager needed User CALs. User CALs do not care about the red dots on the floor plan. User CALs do not care about hotel IP addresses.

A User CAL follows the person. If the salesman connects from a hotel, the server checks the user ID. The user ID is already licensed. The inventory does not create a new row. The count stays at 212. The math stays simple. The math stays true.

The transition was not easy. The IT manager had to explain the failure to the director. The director liked the map. The director liked the red dots.

The director did not like the fluidity. The director thought fluidity was a lack of control. The director was wrong.

The IT manager looked for a way to fix the environment. The IT manager needed a reliable source for the new licenses. The IT manager needed a partner that understood the difference between a static desk and a mobile human.

Finding the Right Partner

The IT manager found a specialized provider for the new infrastructure needs.

Visit the RDS CAL Store

The store offered User CALs for Windows Server 2022 in packs of 50 units.

The IT manager calculated the need. The company had 212 users. The IT manager ordered five packs of 50. The delivery was fast. The delivery took .

The licenses were digital. The licenses did not have physical boxes. The licenses did not need a shelf. The IT manager installed the licenses on the server. The setup guidance was clear. The IT manager followed the steps. The server accepted the new logic.

A List of People, Not MAC Addresses

The spreadsheet changed. The column for MAC addresses disappeared. The column for Device IDs disappeared. The column for User Names became the only column that mattered.

The inventory became a list of people. People have names. People have roles. People do not change their names when they go to a hotel. The inventory stopped growing. The inventory stopped breaking.

The informal reality of the workforce was finally acknowledged. The workers were mobile. The workers were flexible. The licensing model was finally as flexible as the workers.

INVENTORY STABILITY

100% RELIABLE

The IT manager stopped checking logs every hour. The truth was finally in the names.

The IT manager stopped checking the logs every hour. The IT manager stopped deleting rows. The spreadsheet was finally a reflection of the truth.

There is a gap between how a system is designed and how a system is used. The designers of the centralized inventory lived in a world of desks. They lived in a world of wires.

They did not live in a world of 5G and home Wi-Fi. They built a cage. The workers stepped out of the cage. The IT manager was left holding the door.

The World Wins

Choosing the right license is about more than compliance. It is about admitting how the work happens. If the work happens in one place, buy a Device CAL. If the work happens everywhere, buy a User CAL.

Do not try to force a mobile world into a static inventory. The world will win. The inventory will fail.

The company now has a surplus of 38 licenses. This is a buffer. A buffer is a sign of a healthy system. A buffer means the next hire will not break the math.

The next sales trip will not trigger an audit warning. The company paid for the access. The company owns the access. The access is perpetual. It does not expire. It does not demand a subscription.

The floor plan still hangs on the wall. The blue lines are still there. The red dots are still there. But the IT manager does not look at the red dots anymore.

The IT manager looks at the people walking through the door. The inventory is finally quiet.

The map grew smaller as the wires grew longer.

The True Price of Rigid Logic

The cost of a mistake in licensing is usually hidden. It is hidden in the hours spent reconciling logs. It is hidden in the stress of an upcoming audit. It is hidden in the friction between the IT department and the remote staff.

The salesman at the hotel does not want to hear about license counts. The salesman wants to send an invoice. The contractor does not want to hear about MAC addresses. The contractor wants to finish the code.

The centralized inventory failed because it prioritized the machine over the activity. It treated a connection as a liability. A connection is not a liability.

A connection is the purpose of the server. The server exists to be reached. The server exists to be used.

When you simplify the inventory, you simplify the business. You remove the “informal reality” that keeps breaking the “tidy count.” You accept that the count was never tidy to begin with.

The count was an illusion based on the assumption that nobody would ever connect from somewhere new. But someone always connects from somewhere new.

The world is too big to stay at a desk. The server is too powerful to stay in a room. The licenses must be as big as the world and as powerful as the server.

The transition to a user-based model is the only way to stop the spreadsheet from lying. The truth is found in the people, not the hardware.

By