Forem: Judith Lethuwa

Debugging the Deployment Pipeline (When the MDT Image Goes Ghost)

Judith Lethuwa — Tue, 05 May 2026 10:47:31 +0000

They call me a Support Tech, but I see myself as a Value Architect. I don’t just "install apps"—I engineer the logic that makes them deploy at scale. Recently, my flow was interrupted when our MDT image decided to stop cooperating. What should have been a routine laptop setup quickly turned into a high-stakes deep dive into systems integrity and deployment architecture.

The Glitch: The Logic Break
I was preparing to image a batch of fresh laptops when the process hit a wall. The system couldn't find the instructions it needed to start, and Disk Management showed the drive as "Unallocated".

The Problem: The bootable logic on the MDT image was corrupted.
The Stake: High-stakes deployments for the IMEA region were at a complete standstill.

The Systems Logic Fix
Instead of just re-downloading and hoping for a miracle, I treated the failure like a software bug that needed a structural fix:

Re-partitioning via Script: I didn't just format the drive; I used Diskpart to re-align the partition logic to match modern UEFI standards—the specific environment Windows 11 requires to function.
Verifying Source Integrity: I navigated back to the source on SharePoint to download a fresh, verified IMEA MDT image. This ensured the "code" I was deploying was clean and optimized from the start.
The Result: The "ghost" drive was restored, becoming a perfectly functioning deployment tool once again.

Why This is Software Development
Software development is ultimately about creating repeatable, logical processes. By fixing the MDT pipeline, I wasn't just fixing one laptop; I was ensuring that every future deployment followed a clean, automated script.

This is the exact mindset I am bringing into Data Science—identifying where a data flow is broken and re-building the pipe for maximum efficiency. Whether you're writing Python or managing MDT images, the goal is Systems Logic. If the foundation is broken, the software won't run. Fix the foundation first. ✌️

Understanding the Zscaler Connectivity Paradox: Why Port 443 is Non-Negotiable

Judith Lethuwa — Tue, 05 May 2026 09:47:58 +0000

In a modern enterprise environment—especially one managing global logistics—the transition to Zero Trust security through Zscaler is a game-changer. However, even the most robust security stacks can fail if the underlying network logic is ignored.

One of the most common "jump-scares" for IT Support teams is when the Zscaler Client Connector refuses to connect, effectively "ghosting" the user’s cloud applications.

The Technical Glitch: Service Tunnel Failure
When users report a total loss of access to secure sites, the instinct is often to blame the ISP or a corrupted local installation. However, the issue is frequently a communication breakdown between the local client and the Zscaler Enforcement Nodes (ZENs).

The Value Architect Logic: The Port 443 Requirement
Zscaler operates by creating a secure tunnel for all user traffic. Because this tunnel uses SSL/TLS encryption, it relies on a specific "door" to communicate with the cloud:

The Critical Pathway: TCP Port 443 is the industry standard for HTTPS traffic.
The Paradox: Even though Zscaler is a security tool, it cannot function if the local firewall or network policy blocks its primary communication port.
The Consequence: Without an open path on Port 443, the service tunnel "suffocates," leading to cascading system deadlocks and "Access Denied" errors.

The Solution: Ensuring Network Transparency
To resolve this without unnecessary software re-installs, follow this logical workflow:

Analyze Connection Logs: Verify if the Client Connector is reaching the cloud nodes or failing at the handshake stage.
Firewall Explicit Allowance: Ensure that outbound traffic on Port 443 is explicitly allowed in your network configuration.
Service Verification: Once the port is open, restart the Zscaler service to re-establish the secure tunnel.

Final Thoughts
In the world of IT
Support, the most "complex" problems often have the most logical solutions. By understanding the traffic requirements of your security stack, you move from a "reactive" support role to a proactive Value Architect.

POV: The Laptop Says "No OS Found" but You’re a Value Architect💅✨

Judith Lethuwa — Mon, 04 May 2026 12:37:49 +0000

In a fast-paced logistics hub, a Blue Screen of Death (BSOD) isn't just a technical glitch; it’s a killer vibe for the whole workflow. I recently had a user come to me with the ultimate jump-scare: their laptop crashed, rebooted, and hit them with: "No Bootable Device — Please download and install an operating system." 💀

To most people, that screen means "your files are gone." But as a Value Architect, my job is to look past the panic, apply logic, and bridge the gap between a "disaster" and a simple fix.

The "Ghost" Operating System Logic 🧠
The system was basically gaslighting the user into thinking Windows didn't exist. Before doing anything dramatic—like a full re-image or downloading a fresh OS—I went straight to the source: the BIOS.

Enter the "Command Center" (BIOS)

Turn the laptop OFF.

Turn it ON and immediately tap F10 repeatedly until the settings menu pops up.

Fix the Vibe (UEFI Mode)

Use your arrow keys to go to the Advanced tab.

Select Boot Options.

Find Configure Legacy Support and Secure Boot.

Change it to "Legacy Support Disable and Secure Boot Enable". (Windows 11 requires this modern UEFI vibe to start).

Make the Drive Visible (AHCI Mode)

Stay in the Advanced tab.

Select System Options.

Look for SATA Mode.

Change it from "RAID" to "AHCI". This makes your hard drive "visible" again so the laptop can actually find Windows.

Put Windows First in Line

Go back to Advanced > Boot Options.

Find UEFI Boot Order.

Highlight OS Boot Manager and press F5/F6 to move it to the very top (#1).

Save and Exit

Press F10 one last time.

Select Yes to "Save Changes and Exit".

The Result 🚀
By following these steps, the laptop detected the drive immediately, and Windows loaded perfectly. No data lost, no "re-downloading" needed, and zero downtime for the user.