Weekly blog series featuring real-world IT solutions, cloud security strategies, automation projects, and development tutorials to help professionals build resilient, scalable environments.
Minutes before boarding at Salt Lake City International Airport, I received an urgent text about a disabled Azure AD account. I opened my laptop, tethered to my phone’s hotspot, connected to Cisco VPN, and got to work—resolving the issue securely without relying on public Wi-Fi
Introduction: Last Friday, just as I was getting ready to board my flight to JFK from the Salt Lake City airport, I received a message from an end user:
“I think I’m blocked. I can’t access Outlook, Teams, or OneDrive.”
Time was limited, and I was already seated at the gate with my laptop ready. Instead of panicking, I tethered through my phone’s personal hotspot and launched Cisco AnyConnect VPN. I deliberately avoided the airport’s public Wi-Fi to reduce the risk of a security breach.
Once I authenticated and connected securely, I logged into Azure. I discovered that the user’s account in portal.azure.com was disabled. Fortunately, there are two ways to quickly resolve this kind of issue:
✅ Method 1: PowerShell (Quickest & Most Efficient)
If you have the AzureAD or Microsoft Graph PowerShell module installed and proper permissions, this method is the fastest.
Step-by-step using Microsoft Graph PowerShell:
# Connect to Microsoft Graph
Connect-MgGraph -Scopes "User.ReadWrite.All"
# Re-enable the disabled account
Update-MgUser -UserId [email protected] -AccountEnabled $true
Note: Replace [email protected] with the actual UPN or Object ID of the affected user.
Advantages:
Fast (under 30 seconds)
No GUI needed
Can be scripted for multiple accounts
🧭 Method 2: Azure Portal (GUI Approach)
If you’re not ready to run PowerShell or don’t have the module available, the Azure Portal offers a visual way to fix it.
Both approaches—PowerShell and the Azure portal—get the job done. However, for IT professionals constantly on the move, PowerShell is king. It’s fast, efficient, and doesn’t rely on a graphical interface.
That said, having the flexibility to switch between GUI and scripting tools is essential. Some situations demand precision and speed; others might call for a visual confirmation or audit trail.
In the end, what matters most is being prepared. Whether you’re at your desk or at an airport gate, the ability to jump in and resolve an issue on the fly is what defines a reliable IT Engineer.
Intro: When internal emails from trusted coworkers suddenly stop showing up in your focused inbox or fail to trigger your Outlook rules, it’s easy to miss critical messages. In my case, one sender was previously blocked due to a spoofing incident, and although removed from the block list, her messages were still bypassing my folder rules—buried in the inbox. Message Trace confirmed the emails were delivered, but not filtered correctly. Here’s how I resolved the issue using PowerShell.
🔍 Problem Recap:
Despite the sender being trusted and allowed, her emails:
Skipped my Outlook inbox rules
Did not show up in Focused Inbox or designated folders
Were confirmed delivered via Message Trace
Were previously on the Blocked Sender List, but later removed
The Exchange Admin Center (EAC) didn’t offer the flexibility I needed to create an accurate spam bypass rule. So I switched to PowerShell.
🛠️ Solution: Create a Transport Rule via PowerShell
Instead of struggling with the limited dropdowns in the modern Exchange portal, I used the New-TransportRule cmdlet to create a spam filter bypass rule in just a few lines.
Conclusion: PowerShell remains the most powerful tool in any IT administrator’s arsenal—especially when the GUI can’t keep up. If you ever run into stubborn mail delivery or spam issues, consider creating targeted transport rules using PowerShell. It’s fast, clean, and gets the job done without frustration.
Jordan 4s laced, knee braces locked, and 20s in hand—another stair session. I train to stay ready, not just fit.
I train to stay rooted in purpose, faithful in service, and prepared for life’s demands. Fitness clears my mind and sharpens my focus. The goal isn’t just strength—it’s being able to make a difference.
That’s why I wear McDavid knee braces, elbow support, and back support. My workouts are non-stop—compound, high-rep, and uninterrupted. You have to train smart. No shortcuts. No injuries.
Tonight’s training flow?
30-minute stair run (1st floor to basement, non-stop)
120 reps each of:
Pushups
Sit-ups
Leg raises
Abs crunches
Bird/Dog exercise for balance and core control
Crab-walks to engage hip and glute strength
20-minute plank rotation
All while my laundry spins in the background
Tilapia fillets thawed and ready for a clean dinner
Playlist? Pure Church music, filling the air with purpose
This is a multi-tasked project of body, spirit, and home.
During sacrament, the hymn “Because I Have Been Given Much” played softly—but its message roared inside me.
It asked me: What are you giving in return?
I reflected:
👉🏼 I give my focus to study—choosing AZ-104 over passive scrolling 👉🏼 I give my energy to fitness—choosing movement over comfort 👉🏼 I give my rest to quality sleep—choosing recovery over distraction 👉🏼 I give my time to the Lord—choosing temple service over idle time 👉🏼 I give my work my best—choosing to document, secure, and improve
This isn’t boasting. This is realignment. When you’ve been preserved, protected, and placed where you are for a purpose— you can’t just sit still.
You move. You give. You train. You serve. Because you’ve been given much.
I love Integral Calculus. In today’s digital world, I revisited that concept and expressed it in three ways: JSON, PHP, and Python. Below are the format:
Introduction Ransomware is a digital hostage situation—and it’s getting worse. It can freeze hospitals, paralyze billion-dollar businesses, and devastate small IT shops. I’ve survived multiple ransomware attacks in my career, and I’ll tell you how: I never put all my eggs in one basket. This blog explains what ransomware is, how it spreads, and how I protected myself. My defense? Layered backups. Not just the cloud—Veeam, Commvault, and old-school external drives.
What is Ransomware? Ransomware is a form of malware that encrypts files and demands payment for the decryption key. It comes in two common forms:
Locker Ransomware: Locks you out of your device or system.
Crypto Ransomware: Encrypts your files and threatens to destroy or leak them if payment isn’t made.
It often arrives silently—via phishing emails, malicious downloads, or exposed ports—and acts fast. In just minutes, entire systems can be taken hostage.
Real-World: How I Survived Ransomware
At Tarzana Medical Center, ransomware struck without warning. Medical data became inaccessible in minutes. I’ve seen even global giants like Ingram Micro fall victim to attacks.
Yet every time, my systems stayed intact. Why? My systems always stayed intact—because I followed one simple rule: diversify your backups.
Here’s how I stayed ahead of attackers:
I never relied solely on cloud backups (they can be corrupted or locked by the same attack).
I used Veeam for virtualized workloads, giving me granular recovery options.
I ran Commvault for enterprise-grade backup and disaster recovery.
I manually created offline backups to external drives and physically disconnected them to avoid remote encryption.
This multi-layered approach allowed me to recover in hours—not days—and saved thousands in downtime and potential ransom.
How Ransomware Spreads
Phishing emails with malicious attachments or links
Weak RDP access without MFA
Unpatched vulnerabilities in apps or OS
Rogue websites and drive-by downloads
How to Prevent Ransomware Attacks
Educate Your Team Train staff on email safety, suspicious links, and phishing red flags.
Patch Everything Keep OS, firmware, and all third-party software up to date.
Lock Down RDP & Admin Access Use MFA and limit RDP access with strict firewall rules.
Deploy EDR or XDR Tools Use behavior-based endpoint protection—not just signature-based antivirus.
Segment Your Network Don’t allow lateral movement. Use VLANs and access controls.
Adopt a Backup Strategy That’s Offline-Friendly
Veeam for VM and application backup
Commvault for large-scale environment coverage
External drive backups add a final safety layer against data loss.
Test Your Backups Frequently A backup that isn’t tested is a gamble. Run simulations regularly.
Responding to a Ransomware Incident
Isolate the infected systems
Notify your incident response team or external partner
Do not pay the ransom—this only fuels more attacks
Restore from offline or clean backups
Report to authorities (FBI, IC3)
Conclusion Conclusion Ransomware attacks are relentless—but with the right strategy, you can stay ahead. A strong backup routine, tested regularly, makes all the difference.
Avoid relying on just one cloud backup. Use multiple layers—offline, cloud, and local. Act now—before a breach locks you out.
Confidence is earned — often forged in quiet moments when no one’s watching. Often, it’s forged in quiet moments when no one’s watching. Whether I’m at a blank PowerShell console or gripping a loaded barbell, the principle is the same: discipline, consistency, no shortcuts.
I’ve Always Been an ABC Person
I’ve always lived by three words: Always Be Curious.
That curiosity pulled me into IT. I lacked credentials, but I had grit and a drive to learn. I’ve never believed in shortcuts — not in spiritual growth, troubleshooting IIS, or transforming your body. Temporary fixes cover symptoms — but they rarely solve the root cause.
You don’t fix problems with assumptions, Google, and a quick prayer. You fix them with logs, tools, and patience. That’s what I’ve learned — the hard way — through years of trial, error, and persistence.
Why I Don’t Believe in Band-Aid Fixes
Quick fixes fade fast. They treat symptoms, not root problems. Take IIS, for example — a broken SSL binding or 503 error might vanish temporarily, but it usually comes back with greater risk.
That’s why I value discipline over speed. Precision over panic.
It’s the same principle my son applies as he preps for his first fitness competition. He doesn’t rely on shortcuts or crash diets. And definitely no “quick fixes” to look lean. Just clean eating, consistent training, and unwavering focus — day in and day out.
Watching him chase excellence reminds me of my early days — hungry, overlooked, and determined to make noise through results, not volume.
I didn’t wait for permission—I made my own path. I spoke up when others stayed silent, dove into neglected technologies…, and taught myself to harden and scale IIS in real-world, high-pressure environments. I wasn’t the loudest voice in the room, but I became the go-to problem solver—delivering solutions that worked the first time.
Triple D: Discipline. Dedication. Determination.
Tonight’s fuel: Baked Atlantic salmon with lemon, garlic, and power greens — topped with walnuts and 42g of clean protein. Discipline doesn’t stop at the keyboard — it continues at the dinner table.
Confidence isn’t found. It’s forged — through repetition, patience, and precision. Knowledge doesn’t come overnight. Much like getting fit, it takes what I call the Triple D: Discipline. Dedication. Determination.
Tonight’s early dinner? Fresh Atlantic salmon baked with lemon, garlic, and a bed of power greens. To boost nutrients, I topped it with walnuts and washed it down with 42g of Fairlife protein. I eat twice a day — every bite calculated, nutrient-packed, and designed for peak performance..
As for training, I’m in the zone six days a week — no shortcuts. Mostly bodyweight: push-ups, sit-ups, glute bridges, crab walks, planks, and shadow boxing. I train with intensity — until the burn says I’m done..
That’s how I’ve kept my edge for decades — by showing up, sweating, and sticking to the plan.
You train your body the way you train your mind. Log files are your feedback loop. Errors are your instructors. Study. Adapt. Try again.
That mindset shapes how I approach IT and life.
Bruce Lee Said It Best
“If you always put limits on everything you do — physical or anything else — it will spread into your work and into your life. There are no limits. There are only plateaus, and you must not stay there, you must go beyond them.” — Bruce Lee
I carry that with me daily. In both IT and fitness, mastery is a moving target — the moment you think you’ve arrived, growth demands a new challenge.
My Son’s Grit, My Quiet Pride
24 days out from competition.
“Starvation is at its highest for me… it feels like I’m crawling my way to survive all day long. This is the toughest sport I’ve ever experienced.”
Those are the words my son texted me as he prepares for his upcoming debut at TheFitExpo in Anaheim on August 2, 2025.
His commitment to clean eating, intense workouts, and honest prep — no shortcuts — mirrors the way I built my IT career: with sweat equity.
He used to dominate dance stages as a four-time All-Male hip-hop champion with West Covina High School. After college, he became a CNA and now works as a gym personal trainer — turning his passion for fitness into purpose. He’s carrying the torch of discipline — and I couldn’t be prouder.
From IIS to Iron: A Shared DNA
Take IIS — often dismissed as legacy tech, yet it powers critical internal systems beneath the buzzwords. But the reality is, it still powers critical internal applications..
When it breaks — when HTTP 500 errors fill your logs — assumptions won’t fix it. First, trace the issue. Dig through the logs. Slow down. Understand the root cause — then take action.
That’s the same mental muscle my son flexes in the gym. He logs his intake. Monitors results. Makes adjustments.
We train differently — I with bodyweight and discipline, he with prep meals and physique goals. The goals differ — but the grit is the same.
Here’s a script I wrote to search the most recent IIS log file for errors — the same kind of tool I use to avoid assumptions and find the real issue:
🧰 PowerShell Script: Digging Through IIS Logs
# Find the latest IIS log and search for error codes
$LogPath = "C:\inetpub\logs\LogFiles\W3SVC1"
$LatestLog = Get-ChildItem -Path $LogPath -Filter *.log | Sort-Object LastWriteTime -Descending | Select-Object -First 1
Select-String -Path $LatestLog.FullName -Pattern " 500 " | Select-Object LineNumber, Line
If it’s worth fixing, it’s worth fixing the right way.
Conclusion: Carry On
This week’s Church hymn, “Carry On,” stirred something quiet in me — It reminded me that sometimes, the holiest thing we can do is simply hold our ground. It reminded me:
It reminded me:
“Firm as the mountains around us, Stalwart and brave we stand…”
We don’t walk this path alone. Others cleared the way — now it’s our turn to keep going.
This isn’t about spotlighting effort. It’s for the ones working in silence. In server rooms. In waiting rooms. In small spaces where no one claps.
The message doesn’t seek attention — it invites action: carry on.
They say when you see a man on top of the mountain, he didn’t fall there.
He planned the climb, stumbled on jagged trails, and kept going even when the sky turned gray.
This post isn’t just about photography, or starting a new role, or PowerShell scripts. It’s about finding your footing again when life shakes your routine—whether you’re debugging a script, chasing stars at 2AM, or collecting a laptop that brings back a hundred memories.
You’ll find stories about IT challenges, career shifts, Milky Way photography, emotional storms—and most of all, how to rise above the blues when everything feels heavy.
Carrying the gear, chasing the stars—because purpose isn’t found at the summit, it’s carried every step.
⛰️ New Job, New Mountain
They say starting a new job is like standing at the foot of a mountain. The view is exciting—but the climb? Uncertain.
No one really tells you what it feels like to start over. You’re learning people, process, and pace all at once. Even if you’re an expert, you’re blind on day one. And if you’re in IT, like me, the terrain can feel like a minefield.
Pros:
A fresh start
The chance to sharpen or add new skills
A clean slate to prove your value again
Cons:
Culture shock
Pressure to perform quickly
Emotional whiplash, especially when you’re still letting go of the last place
I’ve lived this cycle more than ten times—moving from job to job, project to project. From my first IT gig where I got fired after just a few days (yes, really), to roles in telecom, manufacturing, finance, education, government, and now infrastructure engineering—every restart brought unexpected lessons.
That early firing? It broke me. But it built me too. It taught me to expect the unknowns. It made this scripture real to me:
“For of him unto whom much is given much is required.” – Luke 12:48
And that’s what they don’t tell you: Starting a job doesn’t just mean you’re on probation— it means you’re learning the language, the culture, the personalities, and the systems. Sometimes you’re expected to run before you even learn where the shoes are.
So how do I handle it?
Soft skills. Empathy. Active listening. And above all, humility.
The technical side is always tough, but people are the real challenge. Knowing how to adapt, how to read the room, and when to ask versus when to figure it out—those are the survival tools.
“If ye are prepared ye shall not fear.” – D&C 38:30 That verse? It’s more than a motto. It’s how I show up—every first day, every new login, every fresh deployment.
I’ve seen people not make it past the 90-day mark. Sometimes they didn’t fit. Sometimes the job was the problem. Sometimes—let’s be honest—they oversold their résumé, got lucky at the interview, and then the real work revealed the truth.
Others just get carried by the blues—barely holding it together until their tank runs empty.
That’s why preparation matters. You don’t go to war without gear. You don’t climb a mountain without checking your boots. And you don’t start a new role without anchoring your mindset.
Finally, land where you love. A job shouldn’t just pay the bills — it should fuel your purpose. When you love what you do, it’s a win-win: You rise, and so does the company.
But if you’re stuck in a rut just to make ends meet… eventually, it drains more than your energy — it drains your spirit.
So don’t just look for a job. Climb toward work that gives you life.
A glimpse of the heavens through earthly shadows—chasing the Milky Way isn’t just about light, it’s about learning to see in the dark.
🌌 Chasing the Milky Way
There’s something sacred about standing in the desert with the Milky Way overhead.
I’ve chased it from Joshua Tree in California to Grand Canyon in Arizona, Monument Valley in Utah, and Moab—and every time, I feel the same awe.
My process is disciplined and deliberate. I survey the area in daylight, using the PhotoPills app to map the galactic core. Then I visualize my composition, mark the safest route from the car, and prep all my gear.
Primary lens: Nikon 14-24mm f/2.8G
Backup: Nikon 24mm f/1.4G
Tripod, remote shutter, red LED headlamp
Pre-focus and manual mode to avoid lens hunting
ISO, shutter speed, aperture—all dialed in
Everything is anticipated—just like in IT. One missed step, and the whole shot—or system—can fail. Just seeing the Milky Way with your own eyes is breathtaking—but to compose it meaningfully, that takes skill.
A great Milky Way shot is not just about stars— it’s about how you prepare in the dark.
🛠 When PowerShell Becomes Armor
It’s Monday morning. Your inbox is full. A user can’t log in, the SQL service is down, and your boss wants answers.
If you’re not ready, it feels like going to war without armor.
That’s where PowerShell becomes your weapon.
Let’s say you’re troubleshooting remote system uptime across 50 servers. Instead of logging in one by one:
📊 Real-time uptime scan across multiple servers using PowerShell – one script, instant clarity.
In just 10 seconds, you’ve got eyes on the entire server fleet. Who’s up. Who’s down. Who’s silent. The sharp tech doesn’t panic—he pinpoints, isolates, and executes. Fast. Focused. Fix deployed.
PowerShell isn’t just a tool—it’s your recon drone.
Like photographing the Milky Way, the best troubleshooting happens when everything is ready before chaos begins.
🎈 Rise Above the Blues
You’re not a machine. You weren’t built to be immune to fear, fatigue, or failure.
Unlike AI, we can’t predict everything. Life throws us emotional landmines—doubt, loneliness, weariness, fear and grief. And sometimes, it hits out of nowhere. A memory. A song. A walk past an empty office.
But here’s what I’ve learned:
You don’t need to erase the blues— you rise above them.
Just like launching a balloon skyward, it takes intention:
You eat clean even when you feel messy.
You work out even when your spirit is sore.
You create even when motivation lags.
And yes, you kneel—asking God for strength.
Whether you’re debugging a failed script, standing under a galaxy of stars, or simply trying to make it through a quiet night…
💪 The Endurance Factor
Endurance isn’t just for the gym — it’s a mindset I carry into every part of my life. Whether I’m hammering out code at 2AM or waiting patiently for the perfect light in photography, the principle is the same: lasting through the grind matters more than talent alone. Battle rope training reminds me that breakthroughs come after fatigue — in the gym, in IT, and behind the lens. Those who endure, evolve. Those who push past comfort zones, create lasting impact.
Each battle rope rep runs 180 seconds — just like a boxing round. I push through up to 6 rounds, simulating the intensity of a 12-round fight. It’s not just training — it’s conditioning for IT, for life, for the moments when quitting is easier. Endurance is the quiet strength behind every breakthrough.
🎯 Precision Under Pressure: Shooting, Striking, and Showing Up
Whether I’m at the range or on the mat, the ritual is the same: Prepare. Focus. Repeat.
When I train with my pistols, I practice daily with dummy rounds—loading, unloading, chamber checks, slide control. I break them down, clean them, reassemble them blindfolded—until every movement is instinctive.
It’s the same with MMA and air punching drills. My body is conditioned not just for strength, but discipline. Every strike, every stance, is deliberate. I don’t train to show off—I train to be ready.
You see, when it’s Monday morning and something breaks at work—your system is down, a PowerShell script fails, a teammate’s counting on you—that’s your moment. That’s your live fire.
You don’t rise to the occasion. You fall back on your training.
Whether I’m troubleshooting a crashed server, hiking a steep trail for that perfect Milky Way shot, or helping someone start their climb—discipline is the thread. I’ve learned that showing up prepared is half the victory.
Just like the range:
No second chances if you’re not ready.
Precision comes from practice.
And calm comes from confidence.
🏁 Conclusion
There are mountains I’ve climbed—in IT, in life, and in silence.
From my early days as a PC Support Specialist at USC, through roles in telecom (Verizon), manufacturing (Alcoa), local government (City of West Covina), law firms, education (The Claremont Colleges), our Worldwide Church, regional banking (City National Bank), fintech (Payforward), retail (Monster Energy), global finance (PIMCO), and now as an Infrastructure Engineer in Utah—none of those summits came easy.
Even when I chase the stars with my camera, it’s the climb that makes the view meaningful.
So to anyone out there starting over, picking up the pieces, or doubting their path:
You don’t fall on a mountaintop. You climb it. And you keep climbing. Even when you’re tired. Especially when you’re tired.
Captured from Coronado Island on the 4th of July — a night of light, a heart full of gratitude, and a quiet prayer for the generations who will carry our name forward. Photo by Jet Mariano.
Intro: Every Fourth of July brings with it more than fireworks and flags—it brings reflection. For me and my family, this day is a reminder that freedom isn’t just an idea, it’s a reality we prayed for, waited for, and worked for. As an immigrant father and a lifelong believer in divine purpose, I wrote this for my children, as a quiet reminder of where we came from, what we’ve been given, and why I remain grateful for this land of promise.
Main Post: We are immigrants, you and I. We waited 15 long years before our U.S. visa was approved. And when we finally arrived, I didn’t start in a fancy office—I started by hauling office furniture off 30-wheelers in Burbank from 4 PM to midnight, earning $4.25 an hour.
Hard work was not an option—it was survival. But in this country, effort doesn’t go unnoticed. I went back to school, studied IT, and eventually earned a degree in Management in Telecommunications. No shortcuts, just faith, sweat, and purpose.
In the words of Paul H. Dunn:
“We are immigrants, you and I, because the Lord made immigrants of us and brought us here. We have done as well as could be expected, and are richly blessed despite our shortcomings because the Lord has thus far held us in His hands and worked His purposes, His ultimate purpose, through us. We’re wanderers, you and I.”
This nation welcomed me. And in return, I gave it my best. I built a career, provided for my family, and used my knowledge to bless others. Not as a way to boast—but as a testimony of what’s possible when freedom is honored and faith is kept.
President Thomas S. Monson once declared:
“When we safeguard the heavenly virtue of freedom, when we honor it, when we protect it, we will walk with Washington, we will pray with patriots, and we shall have peace on earth, good will to men.”
And as N. Eldon Tanner taught:
“We are all a part of America’s future. Our job is to learn and benefit from the past and to go forward in righteousness, keeping the commandments of God.”
My story is not unique—but it is deeply personal. I share it today not only as a celebration of America, but as an invitation to never take freedom for granted. To all those I love and care about: your future in this land is filled with promise—but always remember where we came from, and how far we’ve come.
This is the land of the free. This is the home of the brave. And I am forever grateful to be part of it.
I’ve always been the strong one—at home, at work, in faith. The one people come to for answers, comfort, and solutions. But lately, I’ve been sitting in a kind of silence that echoes deeper than I expected. When the texts stop, when the calls go unanswered, when temple appointments fade into the background—I start to feel it: even the strong get tired.
This week, I found myself in a strange place—surrounded by truth, but pierced by silence. I sat at my desk feeling the weight of isolation. No messages, no check-ins, no unexpected “Hey, how are you?” from anyone. It felt like my soul was stuck in a paused moment, waiting for a response that never came.
But I remembered Alma 26:27:
“Now when our hearts were depressed, and we were about to turn back, behold, the Lord comforted us…”
Even Ammon and his brethren—men of God—were depressed. These weren’t weak men. These were spiritual giants who had seen miracles, preached the gospel with power, and endured rejection. And still, they felt what I’m feeling now.
Photo I took of the Oquirrh Mountain Utah Temple a few weeks ago. It’s calling me back.
Tomorrow, I’ll walk into the Oquirrh Mountain Temple after more than a month. I’m not going to ask for miracles. I’m going because I need to be in the presence of Heaven. I need to let my spirit breathe again. I need to feel my Father’s love, even when words fail.
Quote for Reflection:
“Your silence is deafening.” — The Fault in Our Stars But maybe… God’s silence isn’t absence. It’s invitation.
“When Silence Speaks” — Oquirrh Refrain
When silence came like falling snow, And all the noise had ceased to be, I felt a pull, a quiet glow— The temple gates were calling me.
At Oquirrh’s base I bowed my head, Not for answers—just for peace instead, A quiet place where tears are shed, And unseen angels softly tread.
Inside the stillness, soft and wide, The Celestial Room embraced my soul— I reached to write, with God as guide, Yet someone’s name first filled the scroll.
No knock, no text, no morning sound, Yet still I stood with faith intact. Some bonds may sleep beneath the ground, But truth remains, and light comes back.
Not every path must be explained, Not every bond can bear a name— But in that light, I still remained, And walked back out, no longer flame… but flame.
A Gentle Addition (Post-Poem):
Before I left for the temple that day, my hand wrote a name I didn’t expect. It reminded me that sometimes God places people in our hearts not by accident, but by design. I won’t name them here. I’ll just say this: I’m grateful for the quiet nudges that guide us back to love—even when words are few and time is short.
Sometimes, the name written in silence is the one Heaven hears the loudest.
Even techs get stuck. Yesterday reminded me that sometimes, the person everyone calls for help also hits a wall. I was working remotely via VPN, ready to assist a teammate, when my own RDP session froze on “Please wait.” I couldn’t move, couldn’t connect, and couldn’t help. It was like watching a surgeon get locked out of the operating room.
What Happened: From home, I connected to VPN and tried to RDP into my office desktop, but I got stuck at the “Please wait” screen. VPN was up, but Remote Desktop was frozen. I launched a Command Prompt window and ran:
query session /server:xx.xx.xx.xx
Note: IP address redacted for security.
Here’s a redacted example of the output:
SESSIONNAME USERNAME ID STATE TYPE
services 0 Disc
rdp-tcp#16 johdoe 1 Active rdpwd
console johdoe 2 Conn wdcon
From the list above, I saw that ID 1 was in a Disc (Disconnected) state — an orphaned session that blocked me from connecting normally.
To fix it, I ran:
reset session 1 /server:xx.xx.xx.xx
After a few seconds, I reconnected via RDP successfully — and the session loaded instantly.
Conclusion: This was a humbling moment. VPN doesn’t mean much if a stuck session locks you out. Knowing how to query session and reset session remotely is like having a digital master key. When the helper needs help, this trick puts you back in the game.
Father’s Day this year came with more than just cards and hugs—it came with quiet reflection, a few emotional flashbacks, and a full heart.
After work on Friday, I found myself doing something I rarely stop for: slowing down. I cleaned the house top to bottom, did laundry—including fresh bedding—and made sure everything smelled just right. I even went grocery shopping with purpose… because my wife, my son, and his family were driving from out of state to visit me.
I had to make it special.
Saturday Night: Baked Salmon & Family Time That evening, I surprised them with something I’m still learning to master—cooking. I baked fresh salmon for dinner. I’m not usually known for my kitchen skills, but there was something sacred about preparing a meal with my own hands for the people I love.
We gathered at the table, shared stories, laughed over seconds, and created a memory I didn’t know I needed.
Father’s Day breakfast I made for my wife and grandson—blueberry protein shake, pancakes with fresh fruit, and a Core Power finish. Even in silence, I chose to serve with love.
Sunday Morning: Blueberry Pancakes & That Peter Pan Moment I woke up early on Father’s Day and made blueberry pancakes for my wife and grandson. I plated them with sliced bananas, strawberries, blackberries, and a side of protein shakes—my quiet way of saying “thank you” for the joy they bring into my life.
And in that stillness, as I looked at my breakfast creation and heard the house stirring awake, I had a moment—a flashback.
I remembered holding my kids when they were small. The scraped knees, the sleepy hugs, the silly jokes. I heard myself whisper something I once told them years ago, a line from Peter Pan:
“I wish we never grew up.”
Not because I regret the years passing, but because I wish I could freeze-frame every laugh, every moment of chaos and wonder. I miss being their superhero. I miss us.
This Father’s Day card from my firstborn daughter brought tears to my eyes. She reminded me that all the sacrifice, all the years of hard work, didn’t go unnoticed. This photo of us from decades ago says it all: I gave my youth for my family—and they remember.
A Handwritten Card & A Jersey Mike’s Gift A few days before Father’s Day, I received a card from my firstborn daughter. She made it personal—printed with an old photo of me holding her as a baby, and a handwritten message that simply said, “Hoping you feel our love.” Inside was a Jersey Mike’s gift card—she remembered it’s my favorite sandwich spot.
That card brought me back 35 years. I smiled. I teared up. I felt young again.
🟩👔 A Shirt That Spoke Volumes
Later in the afternoon, I received a thoughtful gift from my youngest daughter—a Julep Green, long-sleeve button-down shirt. It was simple, stylish, and exactly my kind of color. She has an eye for things I’d never think to get for myself. It wasn’t just a shirt—it was her way of saying, “Dad, I see you.”
Grateful Moments 💝
One of the most meaningful parts of this Father’s Day weekend was the unexpected gestures from loved ones. A beautifully wrapped gift appeared on the table—simple, thoughtful, and quietly affirming. It added a layer of warmth to a weekend already filled with home-cooked meals and heartfelt greetings.
Reflections from the Heart
I don’t share these things to impress or prove anything. I write them down to remember—because life moves fast, and these quiet moments remind me I’ve done something right. Even when life feels distant or heavy, love has a way of showing up.
PowerShell remains my go-to tool for automating everyday IT tasks. In this post, I share real-world examples and weekly routines that help streamline system administration.
Whether you’re fixing a misconfigured router, debugging PowerShell scripts, or tracking down a memory leak in a cloud app—troubleshooting in IT demands more than technical skills. It requires discipline, logic, and humility. After three weeks of blogging about health and discipline, let’s talk about the fitness of your mind—the kind that solves problems.
The Ultimate Troubleshooting Framework
1. Observe First, React Later Don’t panic. The biggest failures come from rushing. Rebooting blindly or clicking wildly rarely fixes anything long-term. Start with awareness—what changed? When did it work last?
2. Replicate the Issue Can you consistently reproduce the error? Replicating the issue puts you in control of the variables. Screenshot everything, test on another device, or simulate in a lab. If it’s not reproducible, it’s not solvable—yet.
3. Isolate the Fault Line Is this a client-side or server-side issue? Is the failure network-based or application-specific? Drill down layer by layer—network > system > application > user. Think like a detective following leads.
4. Validate What Works Don’t just look for what’s broken—look for what still works. This narrows the gap. If ping works but DNS fails, your network isn’t down; your resolution layer is. Know the baseline.
5. Eliminate, Don’t Guess Avoid shotgun fixes. Remove assumptions through testing. Disable policies, roll back updates, swap hardware. Let evidence drive your conclusions—not your emotions.
6. Document the Process Take notes. Every screenshot and command helps build tribal knowledge for the team. Great IT pros don’t just fix—they record and teach.
7. When You’ve Hit a Wall—Call in Experts If all else fails, this is where humility shines. Bring in the vendor, escalate to support, or call your team. Vendors will often start from ground zero, treating you like a novice. Swallow your pride. Be a team player. The goal is resolution, not recognition.
8. Loop in Your Peers Sometimes the fix is just one conversation away. Your teammate might’ve solved it last week. Break the silence, share your screen, and troubleshoot together.
Conclusion
Troubleshooting is not a talent—it’s a craft. And like any craft, it’s forged through practice, patience, and process. This framework doesn’t belong to one domain of IT—it belongs to every discipline. Whether you’re in the trenches of a VMware outage or debugging a line of Python, the rules are the same.
Train your mind as you train your body. Master your process and the problems will surrender.
In today’s fast-paced IT world, embracing the cloud isn’t optional—it’s mission-critical. Whether you’re managing hybrid infrastructure or securing endpoints across continents, mastering cloud tools separates the reactive techs from the proactive engineers.
Here are five powerful cloud solutions I’ve used in the trenches throughout my IT career.
1. Microsoft Azure
“Scalable. Scriptable. Secure.”
Azure remains the backbone of enterprise cloud. From spinning up VMs to enforcing conditional access, Azure gives you granular control and powerful automation—especially when paired with PowerShell or Azure CLI.
Use Cases:
VM provisioning via templates
Azure AD security policies
Hybrid join deployments
Log Analytics and Sentinel integration
2. Microsoft Intune + Autopilot
“Endpoint management that actually works.”
Modern endpoint management has moved beyond on-prem GPOs. Intune and Autopilot let you enroll, configure, and secure devices—from factory to desk—with zero IT touch.
Use Cases:
BYOD device compliance
Windows Autopilot provisioning
App deployment without VPN
3. Microsoft 365 Admin Tools
“Collaboration is nothing without control.”
Exchange Online, SharePoint, Teams, and OneDrive all live under the M365 umbrella—but it’s how you manage access, retention, and security that defines your IT strength.
Use Cases:
eDiscovery & retention policies
Shared mailbox automation
Microsoft Purview for compliance
4. PowerShell + Graph API
“Automate everything—or drown in tickets.”
The real power of cloud lies in scripting. With PowerShell and Graph API, you’re not just managing users—you’re managing scale.
Use Cases:
Bulk license assignment
Dynamic group creation
Real-time audit scripting
5. Cloud-Based Backups (Veeam, Acronis, etc.)
“Your last line of defense is only as strong as your last backup.”
Whether you’re backing up M365 mailboxes or Azure VMs, cloud-native backups ensure business continuity, ransomware defense, and fast recovery.
Use Cases:
Immutable backup storage
Backup alerts and automation
Hybrid backups (local + cloud)
Final Thoughts:
Cloud mastery doesn’t mean knowing everything—it means knowing what works, and how to leverage automation to reduce human error. I’ve learned this through real-world pressure, testing, and relentless problem-solving.
After spinning up a few test VMs in Azure, I realized the costs were creeping up from unused resources. Manual cleanup was time-consuming, especially when tracking which NICs, disks, and IPs belonged to what. I needed a faster, cleaner solution—one script to deploy, another to destroy.
The Solution
I wrote two PowerShell scripts:
New-AzServerVmRdp-20250509_GitHub.ps1: Fully automates deployment of a Windows Server 2019 VM with RDP access.
Remove-AzServerVmRdp-20250509_GitHub.ps1: Cleans up the entire environment by removing the resource group.
These scripts not only deploy the VM but configure the VNet, subnet, NSG, public IP, and NIC—all with one command.
I can now spin up a fresh, RDP-ready Windows Server in under 10 minutes and wipe it clean with a single line. I tested the RDP connection, confirmed the VM’s performance, and removed the environment—no residual charges, no clutter.
Respect in IT isn’t handed out with certifications, job titles, or seniority. It’s earned — quietly, repeatedly — through solutions delivered under pressure, systems recovered when no one else could, and long hours spent automating what others assumed had to be manual.
I’ve restored failed VMs when the backups looked hopeless. I’ve rebalanced VMware clusters to keep production workloads running efficiently. I’ve automated daily cloud operations across Azure — from onboarding to Defender alert responses — reducing hours of repetitive tasks into seconds of silent execution.
In one instance, proactive Azure Defender tuning flagged behavior that could have led to a ransomware attack. No one ever knew how close it came — and that’s the point. The better your work, the less noise it makes.
I’ve diagnosed why provision-on-demand failed in a live CTS environment, traced financial VM crashes back to Veeam I/O timing conflicts, and implemented site-to-site VPN connections that quietly brought entire departments online again.
No one claps for any of it. No one sees the nights spent scripting, or the documentation created while others sleep.
But that’s where respect lives in IT — Not in applause, but in quiet confidence. Not in recognition, but in results.
You don’t demand respect in this field. You build it.
One restored environment at a time. One secure connection at a time. One automated fix before someone even files the ticket.
🔥 Final Thought:
If you’re still working toward that respect — Don’t force it. Deliver, document, and repeat.
Sooner or later, your work will do all the talking.
Why SIEM matters: Security Information and Event Management (SIEM) provides centralized visibility into security alerts, system logs, and suspicious activities — helping organizations detect and respond to threats faster.
What SIEM solves:
Detects intrusions and anomalies in real time
Helps meet compliance standards like HIPAA, PCI-DSS, and SOX
Centralizes event monitoring across hybrid cloud and on-premises environments
How to Implement SIEM:
Deploy Azure Sentinel for cloud-native SIEM integration
Integrate Cisco Meraki logs, VMware security logs, and endpoint protection (XDR) tools like Palo Alto
Set up detection rules, incident response playbooks, and dashboards
Welcome to my personal blog—a space where I share real-world IT strategies, PowerShell automation, and cloud projects alongside life reflections, spiritual insights, and personal milestones.
From scripting fixes to soul-deep realizations, each post reflects what I’ve learned in both the server room and the quiet room. Whether you’re here for the tech or the testimony, there’s something here for you.
