SD Tech Solutions is a one-person infrastructure shop focused on getting
the fundamentals right: identity, networking, storage, backup, and automation.
The goal is simple: build environments that are understandable, repeatable,
and easy to support — not endless science projects.
Focus Areas
Microsoft-centric infrastructure: AD DS & Entra ID, Windows Server, secure remote access, and storage that fits how teams actually work.
Design and harden AD DS domains, OUs, and GPOs for sign-in, mapped drives, printers, and desktop baselines.
Stand up and maintain IIS sites and internal tools such as CRM, ERP, and line-of-business web apps.
Provide secure remote access with RDP over VPN, backed by MFA on users’ phones for admins and staff.
Offer SSH access for power users and automation where it makes sense, with tight role-based controls.
Build storage layouts using SMB shares, iSCSI targets, and SharePoint / cloud storage for typical departmental setups.
Enforce least-privilege access so users have what they need — and nothing they shouldn’t.
Approach
Start where you are, stabilize what’s fragile, then iterate toward better performance, security, and observability.
Begin with a quick assessment to find the highest-risk and highest-impact issues in your current stack.
Stabilize core services first: identity, networking, storage, and backup, so outages stop being a daily concern.
Improve performance by tuning systems, cleaning up legacy configs, and upgrading hardware only where it matters.
Layer in security: hardened baselines, MFA, logging, and alerting instead of one-off fixes.
Increase observability so you can see problems early through dashboards, logs, and simple health checks.
Follow ITIL-inspired practices — clear change management, incident/problem workflows, and continual improvement — without drowning you in process.
How I Work
Clear scope, small proofs of concept, and practical, no-nonsense delivery — with room for creative, out-of-the-box solutions.
Define scope, success criteria, and constraints up front so everyone knows what “done” looks like.
Use small proof-of-concepts and pilots to prove value before rolling changes across the whole environment.
Work iteratively: ship something useful, gather feedback, then refine instead of disappearing for months.
Favor simple, maintainable designs that your team can own after the engagement — not fragile one-offs.
Bring creative and intelligent solutions when you have unique constraints or need to work around older systems.
Leave behind diagrams, documentation, and runbooks that real admins can follow on a busy Monday morning.
