Enterprise Service Desk / IT Support / Systems Growth

Experienced Service Desk Professional — Microsoft 365, endpoints, identity workflows, and documented infrastructure validation.

Jeremy Fontenot

Enterprise IT Support Professional with proven service desk experience and an evidence-backed growth path toward Systems Administration and Infrastructure Operations.

Service Desk Microsoft 365 Active Directory Networking PowerShell Documentation
reviewer console evidence-backed
01

Support disciplineIntake, triage, remediation, validation, and handoff notes.

02

Microsoft operationsMicrosoft 365, identity, endpoint, and policy documentation.

03

Proof-first structureEvery highlighted project points to preserved repository artifacts.

My Portfolio Standard

Built for recruiter review, technical screening, and accurate positioning.

I present proven support experience alongside preserved lab records, sanitized documentation, diagrams, scripts, runbooks, and validation notes. Each major project identifies the objective, technical area, implementation workflow, validation method, and associated proof artifact.

5core recruiter pages
30+proof artifacts indexed
0dead proof links allowed

Technical Focus

Operational skills mapped to real reviewer paths.

I pair each capability with project evidence, documentation, or a validation artifact so the portfolio remains useful for both hiring managers and technical screeners.

Service Desk

Intake and Troubleshooting

Ticket framing, impact assessment, endpoint checks, DNS/DHCP review, escalation context, closure notes, and evidence capture.

Systems

Microsoft 365 and Identity

Microsoft 365 support exposure, identity and access workflows, Conditional Access intent, Active Directory fundamentals, endpoint policy documentation, and tenant-safe change records.

Infrastructure

Infrastructure Validation

DNS, DHCP, VLAN segmentation, pfSense firewall boundaries, VPN access paths, validation checklists, and infrastructure operations documentation.

Automation

PowerShell and Handoff

Reusable provisioning logic, dry-run review, structured logging expectations, change records, validation notes, and operational handoff checklists.

Documentation

Runbooks and RCA

Incident summaries, remediation plans, post-incident reviews, network runbooks, and validation records written for repeatable operations.

DevOps Discipline

Static Delivery and QA

Performance-aware static pages, source-controlled evidence, link validation, accessibility checks, metadata review, and deployment readiness.

Certification Authority

Credential signals aligned to support, systems, cloud, networking, and security work.

I present certification assets as reviewer-friendly context for the technical areas I document across service desk operations, infrastructure labs, Microsoft administration, Linux fundamentals, and network troubleshooting.

Interactive Home Lab

Virtualization, network segmentation, identity, and remote access in one reviewable topology.

I use this preserved lab model to explain how Proxmox, pfSense, Active Directory, DNS, DHCP, VPN access, VLANs, Windows Server, Linux workloads, and IDS/IPS concepts relate in a realistic support and systems administration environment.

Virtualization

Proxmox

I use Proxmox as the virtualization layer for lab workloads, service isolation, snapshot-aware practice, and infrastructure documentation.

Firewall

pfSense

pfSense represents the routing, firewall, NAT, VLAN gateway, WireGuard, OpenVPN, and segmentation-control boundary.

Identity

Active Directory

Active Directory supports domain-service planning, OU structure, Group Policy scope, authentication context, and Windows administration practice.

Core Network Services

DNS and DHCP

DNS and DHCP provide name resolution, lease assignment, reservation review, gateway checks, and common service desk troubleshooting paths.

Remote Access

WireGuard and OpenVPN

WireGuard and OpenVPN model controlled remote access, tunnel validation, firewall rules, and client connectivity troubleshooting.

Segmentation

VLANs

VLANs separate management, server, client, lab, and monitoring traffic so routing and firewall policy remain reviewable.

Server Administration

Windows Server

Windows Server anchors identity, management, service validation, and endpoint support workflows.

Linux

Linux Workloads

Linux workloads support service hosting, package administration, network checks, logging practice, and cross-platform troubleshooting.

Security Monitoring

IDS/IPS

IDS/IPS concepts provide traffic visibility, alert-review context, and segmentation validation without claiming live production monitoring.

Edge

WAN Ingress

The WAN edge shows where outside connectivity reaches the firewall before controlled routing into lab segments.

Repository Governance Platform

Validation Systems Operational

Enterprise-style validation and deployment governance.

I operate this repository as a governed DevSecOps-style engineering platform with automated CI/CD validation, evidence integrity enforcement, Lighthouse auditing, screenshot verification, SEO governance, and operational telemetry reporting.

repository healthonline
PASS

CI validationGitHub Actions quality gate active.

1.00

Lighthouse performanceLatest proof page desktop score.

70

Integrity fingerprintsSHA-256 evidence hashes tracked.

29

Evidence entriesIndexed proof artifacts mapped to claims.

CI Validation

Continuous Validation

GitHub Actions automatically validates accessibility, Lighthouse thresholds, SEO metadata, screenshots, evidence integrity, links, HTML, PowerShell, and deployment readiness.

SHA Integrity

Evidence Governance

Repository artifacts are indexed, mapped, validated, and fingerprinted using SHA-256 integrity hashes to support operational traceability and documentation integrity.

OPS Telemetry

Operational Dashboard

Repository telemetry tracks validation coverage, Lighthouse reporting, governance metrics, evidence inventory health, and CI/CD operational status.

Operating Rhythm

A support workflow recruiters can understand and technical reviewers can validate.

01

Define scope and impact

Capture affected users, devices, service boundaries, urgency, and known-good behavior before changing anything.

02

Investigate from evidence

Use logs, baselines, configuration state, screenshots, diagrams, and repeatable checks to isolate likely causes.

03

Remediate with rollback context

Document the planned fix, risk, expected result, validation method, and follow-up owner.

04

Validate and hand off

Confirm restoration, update notes, preserve artifacts, and keep the record usable for the next incident.