Routing & switching
Enterprise switching, VLANs, trunking, inter-network connectivity, and the practical troubleshooting that keeps traffic moving.
Network engineer / Infrastructure / Automation
GlennWyatt
More than a decade of hands-on experience connecting systems, securing networks, and keeping critical infrastructure running.
Explore my expertiseCore technologiesJuniperPalo AltoCiscoFortinetKempPowerShell
01 / Expertise
The network.
And everything around it.
My experience spans network operations, security, enterprise services, and automation. I work across the layers to understand how systems connect and where problems begin.
Network security
Firewall policy, IPsec VPNs, NAT, policy-based forwarding, and investigating connectivity and security events.
Application delivery
Load balancing, reverse proxies, internal and external DNS, and certificate renewal for reliable web services.
Microsoft infrastructure
Directory services, messaging, cloud identity, and the administration that brings on-premises and cloud systems together.
Virtualization & operations
Virtual infrastructure, desktop delivery, monitoring, and vulnerability assessment across interconnected systems.
Scripting & automation
PowerShell tools for repeatable administration, scheduled maintenance, reporting, and service monitoring.
02 / Technology
Hands-on familiarity.
Across the stack.
Network & wireless
Juniper EX and SRX platforms; Cisco Nexus and Catalyst; Ruckus wireless.
Security & delivery
Palo Alto firewalls, Kemp LoadMaster, FortiMail, Microsoft NPS, and DNSMadeEasy.
Systems & identity
Windows Server, Active Directory, Exchange, Microsoft 365, Entra ID, and Linux.
Virtual platforms
VMware vCenter, Hyper-V Failover Clustering, and Parallels RAS.
Visibility & automation
PRTG, Nessus, Lansweeper, PowerShell, Microsoft Graph, and REST API integrations.
03 / Approach
Practical engineering.
Built on experience.
I focus on understanding the whole system: the traffic path, the dependencies, and the operational details that make a solution work day after day.
Technical background
I also served in the U.S. Army as a 94F, working with computer and detection systems repair.
Follow the evidence
Trace the route, parse the logs, and isolate the cause. Good troubleshooting starts with what the system is actually doing.
Make routine work repeatable
Use automation where it brings consistency. Keep scripts understandable, with useful logging and clear results.
Keep operations in view
Consider monitoring, certificates, dependencies, and documentation alongside the configuration itself.