About
About Dalton
I’m Dalton Sweet, a systems administrator and technology enthusiast based in Oklahoma. I work across enterprise infrastructure, networking, cybersecurity, cloud services, and automation, helping organizations maintain reliable and secure technology environments. Outside my professional role, I develop software and explore new ways to simplify complex workflows through thoughtful engineering.
01Role & experience
I’m a System Administrator II at The Computer Guy, Inc., a managed services provider in the Tulsa area. My day spans a portfolio of client businesses: their Microsoft 365 and Google Workspace tenants, Windows servers and Active Directory, FortiGate and UniFi networks, and the security tooling that protects their endpoints.
Before that I ran a managed services practice as Director of Managed Services, and before that worked as an IT Systems Analyst, which is where I learned that technology decisions are business decisions first.
02Infrastructure, network & security
My background is cybersecurity: a B.S. in Cybersecurity from Northeastern State University, an associate’s from Tulsa Community College, and certifications including ISC2 SSCP and Cisco CCST Networking. In practice that means I think about how something can fail or be abused before I think about how to make it work.
Most of my work sits where those meet: site-to-site VPNs and segmentation, firewall fleets, identity and MFA, endpoint protection and privilege management, and the monitoring that tells us when any of it drifts.
03Software & automation
I’m happiest when a repeated task turns into a tool. At work that has meant PowerShell and RMM components, a documentation sync built in Rewst, and Zephyra, a password-protected portable toolkit that puts the team’s utilities one click away.
Outside work I write software in JavaScript and TypeScript on Cloudflare’s platform, and I’ve built community portals for gaming groups I’m part of.
04Nexus
Nexus is the product I’m building on my own time: one place for email across Microsoft 365, Gmail, Outlook.com, Yahoo, iCloud and AOL, sorted into lists like Needs a reply and Waiting on them, with spaces for family and work. It runs on Cloudflare Workers, D1 and R2, with privacy designed in: no stored email, a short expiring index, and AI that stays off unless you turn it on.
05How I solve problems
The tools change from client to client. The method doesn’t.
- Understand the symptoms and the impactWhat is actually broken, for whom, and what it is costing the business right now.
- Identify the systems and dependenciesWhat the failing thing relies on, and what relies on it.
- Review logs, configuration and behaviourEvidence first. Guesses come after the logs, not instead of them.
- Isolate the failing layerNetwork, identity, OS, application or permissions: narrow it to one.
- Evaluate solutions and risksPick the change with the best fix-to-risk ratio, and know how to roll it back.
- Implement deliberatelyOne change at a time, communicated, during a window that suits the business.
- Validate and prevent recurrenceConfirm the fix with the people affected, then document it or automate it so it does not come back.
06Where I’m headed
I want to keep growing toward infrastructure and security engineering: designing networks and identity systems that are secure by default, automating the work that should not need a person, and writing software that makes complex things simpler for the people using them.
07Outside work
I’m a husband and a father of two daughters, and most of my time away from a keyboard belongs to them. When it doesn’t, I’m building something: a website, a PC, a tool for a gaming community, or reading more than is reasonable about cosmology and physics.
Hiring, or have a project in mind?
I’m always glad to talk infrastructure, security, automation or software.