I didn’t set out to master IT stacks. I set out to solve a problem that felt simple at first: tracking biometric device licenses across hundreds of remote health facilities.
From Spreadsheets to Reality
Originally, we used spreadsheets. But they were error-prone and slow — sometimes requiring hours of phone calls, remote login sessions via AnyDesk, or even trips to facilities just to verify installations. I wanted a better way.
I realized the truth about a license already existed on the computer itself — once activated, the license file landed in a specific location. That meant I could read reality directly instead of relying on human reporting.
Building a System That Works
I wrote a PowerShell script to read the license files and export the information securely to our server. Suddenly, I could see:
- Which licenses were active
- Which were unused
- Where duplication or misuse had occurred
From there, the system naturally expanded:
- Secure data transport
- Database tracking of installations
- Reports highlighting duplicates or errors
- Ability to reinstall licenses if a system failed (as long as the system hash hadn’t changed; otherwise, the vendor reactivation is required)
Reducing Errors and Blame
Beyond saving hours of calls, remote sessions, and trips, the system reduced unnecessary human blame. Questions like:
- “Why didn’t you document that license?”
- “You might have documented incorrectly”
- “You mixed facility licenses”
…are now largely avoided. The truth is recorded automatically, reliably, and centrally.
Making the System a Habit
I’ve encouraged our IT and data teams to run the script whenever they touch a computer — whether installing or reinstalling a license, troubleshooting, or performing maintenance. This ensures the most current system state is always captured.
And the possibilities keep growing. A more advanced version could integrate with a ticketing system, showing which computer was touched, by whom, how many times, and how persistent problems are. Suddenly, license tracking becomes part of broader operational intelligence.
The Tech Behind the Solution
Along the way, I ended up working across multiple IT layers:
- PowerShell automation
- Secure file and license verification
- Domain and IP mappings
- Reverse proxies and virtual hosts
- HTTPS certificates and API keys
- MySQL database with JSON queries
- Reporting and dashboards
All of it grew naturally from the persistent, honest question: “Where is the truth about these licenses?”
The Principle That Guides Me
No one asked me to do this. No one paid me to. I just wanted to remove headaches — mine and everyone else’s. And in doing so, I discovered something powerful:
If a question is honest and persistent, it will force you to learn everything required to answer it.
By following that principle, I built a system that not only solved the original problem but gave visibility, control, and operational clarity far beyond what spreadsheets or manual checks could ever provide.
