Sharpen role targeting and troubleshooting proof
ci/woodpecker/push/woodpecker Pipeline was successful
ci/woodpecker/push/woodpecker Pipeline was successful
This commit is contained in:
+29
-5
@@ -50,6 +50,7 @@
|
||||
<div class="container">
|
||||
<div class="hero-grid">
|
||||
<div>
|
||||
<p class="hero-target">Targeting IT Support, Junior Systems Administration, and Cloud Operations roles.</p>
|
||||
<h1 id="hero-title">Hands-On IT Support.<br />Verified Systems Troubleshooting.</h1>
|
||||
<p class="lede">
|
||||
I operate a Windows Server Active Directory domain, maintain monitored Linux
|
||||
@@ -109,7 +110,7 @@
|
||||
</article>
|
||||
|
||||
<article class="project-card">
|
||||
<div class="thumb">
|
||||
<div class="thumb screenshot-frame">
|
||||
<img src="assets/screenshots/bytegeist-support-live.png"
|
||||
alt="ByteGeist Support Lab — live app screenshot" />
|
||||
</div>
|
||||
@@ -126,7 +127,7 @@
|
||||
</article>
|
||||
|
||||
<article class="project-card">
|
||||
<div class="thumb">
|
||||
<div class="thumb screenshot-frame">
|
||||
<img src="assets/screenshots/bytegeist-infrastructure-live.png"
|
||||
alt="ByteGeist Infrastructure Lab live control plane showing host telemetry, container health, and service status"
|
||||
style="object-position: top center;" />
|
||||
@@ -145,7 +146,7 @@
|
||||
</article>
|
||||
|
||||
<article class="project-card">
|
||||
<div class="thumb">
|
||||
<div class="thumb screenshot-frame">
|
||||
<img src="assets/screenshots/aws-tracker.png"
|
||||
alt="AWS Cloud Study Tracker — live app screenshot" />
|
||||
</div>
|
||||
@@ -172,9 +173,29 @@
|
||||
<h2 id="notes-title">Troubleshooting Case Studies</h2>
|
||||
<span class="subtitle">Observed issues, diagnostic work, and verified outcomes</span>
|
||||
</div>
|
||||
<div class="proof-strip" aria-label="Quick verification evidence">
|
||||
<details class="proof-callout">
|
||||
<summary>Verified Fix: Domain trust failure</summary>
|
||||
<div class="proof-body">
|
||||
<p><code>Test-ComputerSecureChannel</code> failed while WIN11-01 was on the wrong VMware network.</p>
|
||||
<p><strong>Fix:</strong> Returned the client to VMnet8, restored DC01 as DNS, repaired the secure channel, then verified with <code>Test-ComputerSecureChannel</code> and <code>nltest</code>.</p>
|
||||
</div>
|
||||
</details>
|
||||
<details class="proof-callout">
|
||||
<summary>Verified Fix: PDC time source</summary>
|
||||
<div class="proof-body">
|
||||
<p><code>w32tm /query /source</code> reported <code>Local CMOS Clock</code> on the PDC Emulator.</p>
|
||||
<p><strong>Fix:</strong> Configured external NTP peers, resynchronized Windows Time, then verified <code>time.windows.com</code> as the active source.</p>
|
||||
</div>
|
||||
</details>
|
||||
</div>
|
||||
|
||||
<div class="case-grid">
|
||||
<article class="case-card">
|
||||
<span class="case-label">Windows Server 2022 · Time Services</span>
|
||||
<div class="case-meta">
|
||||
<span class="case-label">Windows Server 2022 · Time Services</span>
|
||||
<span class="status-pill verified">✓ Verified Fix</span>
|
||||
</div>
|
||||
<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>
|
||||
@@ -182,7 +203,10 @@
|
||||
<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>
|
||||
<div class="case-meta">
|
||||
<span class="case-label">Windows 11 · Active Directory</span>
|
||||
<span class="status-pill verified">✓ Verified Fix</span>
|
||||
</div>
|
||||
<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>
|
||||
|
||||
Reference in New Issue
Block a user