Simplify portfolio navigation and section flow
ci/woodpecker/push/woodpecker Pipeline was successful
ci/woodpecker/push/woodpecker Pipeline was successful
This commit is contained in:
Keith Casko
+38
-38
@@ -21,23 +21,23 @@
|
||||
<header class="site-header" role="banner">
|
||||
<div class="container">
|
||||
<div class="brand">
|
||||
<span class="name">Keith Casko</span>
|
||||
<span class="tagline">
|
||||
IT Support | Systems Administration | Cloud Operations
|
||||
<span class="location">Kalamazoo, MI</span>
|
||||
</span>
|
||||
<a class="brand-home" href="#home" aria-label="Keith Casko home">
|
||||
<span class="name">Keith Casko</span>
|
||||
<span class="tagline">
|
||||
IT Support | Systems Administration | Cloud Operations
|
||||
<span class="location">Kalamazoo, MI</span>
|
||||
</span>
|
||||
</a>
|
||||
</div>
|
||||
<button class="nav-toggle" aria-expanded="false" aria-controls="primary-nav">Menu</button>
|
||||
<nav class="site-nav" id="primary-nav" aria-label="Primary">
|
||||
<ul>
|
||||
<li><a href="#home" class="active">Home</a></li>
|
||||
<li><a href="#projects">Projects</a></li>
|
||||
<li><a href="#homelab">Homelab</a></li>
|
||||
<li><a href="#skills">Skills</a></li>
|
||||
<li><a href="#credentials">Credentials</a></li>
|
||||
<li><a href="#troubleshooting">Troubleshooting</a></li>
|
||||
<li><a href="#about">About</a></li>
|
||||
<li><a href="#resume">Resume</a></li>
|
||||
<li><a href="#contact">Contact</a></li>
|
||||
<li><a class="nav-resume" href="assets/resume/Keith_Casko_IT_Cloud_Resume.pdf" download>Resume PDF</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</div>
|
||||
@@ -161,8 +161,36 @@
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<!-- ============ Troubleshooting Case Studies ============ -->
|
||||
<section id="troubleshooting" aria-labelledby="notes-title">
|
||||
<div class="container">
|
||||
<div class="section-head">
|
||||
<h2 id="notes-title">Troubleshooting Case Studies</h2>
|
||||
<span class="subtitle">Observed issues, diagnostic work, and verified outcomes</span>
|
||||
</div>
|
||||
<div class="case-grid">
|
||||
<article class="case-card">
|
||||
<span class="case-label">Windows Server 2022 · Time Services</span>
|
||||
<h3>PDC Emulator using its local CMOS clock</h3>
|
||||
<p><strong>Problem:</strong> An AD domain controller reported <code>Local CMOS Clock</code> as its time source. Unreliable domain time can lead to Kerberos clock-skew failures.</p>
|
||||
<p><strong>Action:</strong> Checked the source with <code>w32tm</code>, configured external NTP peers, restarted Windows Time, and resynchronized.</p>
|
||||
<p><strong>Result:</strong> Verified <code>time.windows.com</code> as the source, stratum 5.</p>
|
||||
<a class="view-link" href="homelab.html#validation">See commands and verification</a>
|
||||
</article>
|
||||
<article class="case-card">
|
||||
<span class="case-label">Windows 11 · Active Directory</span>
|
||||
<h3>Restoring a broken domain secure channel</h3>
|
||||
<p><strong>Problem:</strong> WIN11-01 was bridged onto the physical LAN and could not reach DC01 on the VMware NAT subnet. Trust repair initially failed.</p>
|
||||
<p><strong>Action:</strong> Changed the VM network to NAT, pointed client DNS at DC01, and repaired the machine-account trust.</p>
|
||||
<p><strong>Result:</strong> <code>Test-ComputerSecureChannel</code> returned <code>True</code>; <code>nltest</code> located DC01 successfully.</p>
|
||||
<a class="view-link" href="homelab.html#validation">See audit evidence</a>
|
||||
</article>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<!-- ============ Technical Skills ============ -->
|
||||
<section id="homelab" aria-labelledby="skills-title">
|
||||
<section id="skills" aria-labelledby="skills-title">
|
||||
<div class="container">
|
||||
<div class="section-head">
|
||||
<h2 id="skills-title">Technical Skills</h2>
|
||||
@@ -227,34 +255,6 @@
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<!-- ============ Troubleshooting Case Studies ============ -->
|
||||
<section id="troubleshooting" aria-labelledby="notes-title">
|
||||
<div class="container">
|
||||
<div class="section-head">
|
||||
<h2 id="notes-title">Troubleshooting Case Studies</h2>
|
||||
<span class="subtitle">Observed issues, diagnostic work, and verified outcomes</span>
|
||||
</div>
|
||||
<div class="case-grid">
|
||||
<article class="case-card">
|
||||
<span class="case-label">Windows Server 2022 · Time Services</span>
|
||||
<h3>PDC Emulator using its local CMOS clock</h3>
|
||||
<p><strong>Problem:</strong> An AD domain controller reported <code>Local CMOS Clock</code> as its time source. Unreliable domain time can lead to Kerberos clock-skew failures.</p>
|
||||
<p><strong>Action:</strong> Checked the source with <code>w32tm</code>, configured external NTP peers, restarted Windows Time, and resynchronized.</p>
|
||||
<p><strong>Result:</strong> Verified <code>time.windows.com</code> as the source, stratum 5.</p>
|
||||
<a class="view-link" href="homelab.html#validation">See commands and verification</a>
|
||||
</article>
|
||||
<article class="case-card">
|
||||
<span class="case-label">Windows 11 · Active Directory</span>
|
||||
<h3>Restoring a broken domain secure channel</h3>
|
||||
<p><strong>Problem:</strong> WIN11-01 was bridged onto the physical LAN and could not reach DC01 on the VMware NAT subnet. Trust repair initially failed.</p>
|
||||
<p><strong>Action:</strong> Changed the VM network to NAT, pointed client DNS at DC01, and repaired the machine-account trust.</p>
|
||||
<p><strong>Result:</strong> <code>Test-ComputerSecureChannel</code> returned <code>True</code>; <code>nltest</code> located DC01 successfully.</p>
|
||||
<a class="view-link" href="homelab.html#validation">See audit evidence</a>
|
||||
</article>
|
||||
</div>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<!-- ============ About ============ -->
|
||||
<section id="about" aria-labelledby="about-title">
|
||||
<div class="container">
|
||||
|
||||
Reference in New Issue
Block a user