I have owned infrastructure through normal operations, major transitions, and compound failures. The work spans implementation and support, but the through line is systems engineering: understand the dependencies, reduce the failure surface, instrument what matters, and make recovery repeatable.
01 · ConsolidationTen servers became two hosts in one day.
Planned and completed a production cutover from ten physical servers to two VMware ESXi hosts, reducing hardware sprawl while preserving the services the business depended on.
02 · RecoveryRestored operations through compound SAN failure.
Recovered data and service after simultaneous storage-drive and dual-controller failures—an incident where diagnosis, dependency knowledge, and disciplined recovery mattered more than a routine runbook.
03 · Remote desktopTuned PCoIP as an end-to-end system.
Worked across the network, virtualization, endpoint, and display path to improve remote-desktop responsiveness instead of treating performance as a single-device problem.
04 · Network architectureSegmented services by purpose and risk.
Designed VLAN architecture for storage, voice, printers, guests, desktops, and other service groups, making traffic boundaries and operational dependencies explicit.
05 · Voice infrastructureConnected modern IP telephony to PRI.
Implemented and supported Asterisk-based telephony with PRI integration as part of a broader voice, switching, monitoring, and business-continuity environment.
06 · AutomationTurned multi-hour processes into minutes.
Built internal applications and systems integrations that reduced multi-hour operational workflows to approximately 10–15 minutes.
