Publish all 21 posts, fix Post 1 numbering, remove em dashes, update footers

Author: kristopherjturner

arc-enabled-blog-improvement-doc.md

@@ -27,7 +27,7 @@ lastmod: 2026-04-05T02:14:44.686Z
 
 This is where the keyboards come out.
 
-Posts 1 through 4 made the business case, dismantled the myths, and confirmed your hardware is ready. Now it's time to build something. In this fifth post of the **Hyper-V Renaissance** series, we're going to take a bare-metal server—or a freshly wiped former VMware host—and turn it into a production-ready Hyper-V node that's fully validated for cluster membership.
+Posts 1 through 4 made the business case, dismantled the myths, and confirmed your hardware is ready. Now it's time to build something. In this fifth post of the **Hyper-V Renaissance** series, we're going to take a bare-metal server, or a freshly wiped former VMware host, and turn it into a production-ready Hyper-V node that's fully validated for cluster membership.
 
 Every step is scripted. Every configuration is documented. If you can't reproduce it with PowerShell, it doesn't belong in a production deployment.
 
@@ -71,7 +71,7 @@ Before you begin, ensure you have the following:
 
 Install Windows Server 2025 Datacenter from your preferred media. If you're automating at scale, use an unattended answer file or your existing deployment solution (MDT, SCCM/MECM, or PXE). For a single host build, a standard interactive install works fine.
 
-**Server Core vs. Desktop Experience**: Server Core is the recommended deployment option for Hyper-V hosts. It has a smaller attack surface, fewer updates, and lower resource overhead. Everything we do in this guide works on both options. If your team isn't comfortable with Server Core yet, Desktop Experience works—you can always convert later.
+**Server Core vs. Desktop Experience**: Server Core is the recommended deployment option for Hyper-V hosts. It has a smaller attack surface, fewer updates, and lower resource overhead. Everything we do in this guide works on both options. If your team isn't comfortable with Server Core yet, Desktop Experience works, you can always convert later.
 
 Once Windows is installed and you've set the local administrator password, connect via RDP or the console and open an elevated PowerShell session.
 
@@ -654,9 +654,9 @@ Write-Host "`nValidation report saved to: $($ReportPath.FullName)" -ForegroundCo
 
 The validation report uses three indicators:
 
-- **Green checkmark**: Test passed — configuration meets Microsoft requirements.
-- **Yellow triangle**: Warning — the configuration works but doesn't meet all best practices. Investigate these, but they don't block cluster creation.
-- **Red X**: Failure — this issue must be resolved before creating the cluster. Common failures include mismatched drivers between nodes, network connectivity issues, or storage path problems.
+- **Green checkmark**: Test passed ,  configuration meets Microsoft requirements.
+- **Yellow triangle**: Warning ,  the configuration works but doesn't meet all best practices. Investigate these, but they don't block cluster creation.
+- **Red X**: Failure ,  this issue must be resolved before creating the cluster. Common failures include mismatched drivers between nodes, network connectivity issues, or storage path problems.
 
 **Keep the validation report.** Microsoft Support will request it if you ever open a cluster-related support case.
 
@@ -777,7 +777,7 @@ The most common network warning is nodes having different network configurations
 
 You now have a fully configured, validated Hyper-V host ready for cluster membership. Repeat this process on each additional node, keeping configurations consistent across all nodes.
 
-In the next post, **[Post 6: Three-Tier Storage Integration](/post/three-tier-storage-integration)**, we'll connect your hosts to external storage arrays using iSCSI, Fibre Channel, and SMB3—covering universal principles that work with any vendor and including a detailed Pure Storage reference implementation.
+In the next post, **[Post 6: Three-Tier Storage Integration](/post/three-tier-storage-integration)**, we'll connect your hosts to external storage arrays using iSCSI, Fibre Channel, and SMB3, covering universal principles that work with any vendor and including a detailed Pure Storage reference implementation.
 
 The foundation is laid. Time to connect the storage.
 
@@ -803,7 +803,7 @@ The foundation is laid. Time to connect the storage.
 ---
 
 **Series Navigation**
-← Previous: [Post 4 — Reusing Your Existing VMware Hosts](/post/reusing-existing-vmware-hosts)
-→ Next: [Post 6 — Three-Tier Storage Integration](/post/three-tier-storage-integration)
+← Previous: [Post 4 ,  Reusing Your Existing VMware Hosts](/post/reusing-existing-vmware-hosts)
+→ Next: [Post 6 ,  Three-Tier Storage Integration](/post/three-tier-storage-integration)
 
 ---

content/post/2026-02-04-odin-azure-local-community-tool-deep-dive.md

@@ -27,11 +27,11 @@ lastmod: 2026-04-05T02:14:44.684Z
 
 Not everything needs to be hyper-converged.
 
-There's a strong narrative in the infrastructure world that three-tier architecture—separate compute, network, and storage tiers—is outdated. That hyper-converged infrastructure (HCI) is the only path forward. That separating your storage from your compute is a legacy pattern.
+There's a strong narrative in the infrastructure world that three-tier architecture, separate compute, network, and storage tiers, is outdated. That hyper-converged infrastructure (HCI) is the only path forward. That separating your storage from your compute is a legacy pattern.
 
 That narrative is incomplete.
 
-Three-tier architecture remains the right answer for many workloads and many organizations. If you have an existing SAN investment, if your workloads require deterministic storage performance, if you need storage-level replication for disaster recovery, or if your team has deep storage operations expertise—three-tier isn't just viable, it's often superior.
+Three-tier architecture remains the right answer for many workloads and many organizations. If you have an existing SAN investment, if your workloads require deterministic storage performance, if you need storage-level replication for disaster recovery, or if your team has deep storage operations expertise, three-tier isn't just viable, it's often superior.
 
 In this sixth post of the **Hyper-V Renaissance** series, we're going to connect your freshly built Hyper-V hosts to external storage arrays. We'll cover the universal principles that apply regardless of vendor, then walk through a detailed Pure Storage implementation as a reference example.
 
@@ -83,7 +83,7 @@ The first decision is which storage protocol to use. Each has trade-offs:
 - Your storage team has deep FC operational experience
 
 **Choose SMB3 when:**
-- Your storage target supports SMB3 (e.g., Windows-based file servers, NetApp, Dell EMC)
+- Your storage target supports SMB3 (e.g. Windows-based file servers, NetApp, Dell EMC)
 - You want file-level access rather than block-level
 - You're using SMB Direct (RDMA) for high-performance file access
 - Hyper-V VMs will use SMB shares for VM storage (supported configuration)
@@ -122,7 +122,7 @@ Get-NetAdapterAdvancedProperty -Name "vEthernet (Storage)" `
 ping -f -l 8972 10.10.30.100
 ```
 
-> **Important:** Jumbo frames must be configured consistently on every device in the path—host NIC, physical switch ports, and storage array ports. A single device with standard MTU (1500) will cause fragmentation and degrade performance.
+> **Important:** Jumbo frames must be configured consistently on every device in the path, host NIC, physical switch ports, and storage array ports. A single device with standard MTU (1500) will cause fragmentation and degrade performance.
 
 ### 4. Flow Control
 
@@ -508,7 +508,7 @@ In the next post, **[Post 7: Migrating VMs from VMware to Hyper-V](/post/migrati
 ---
 
 **Series Navigation**
-← Previous: [Post 5 — Build and Validate a Cluster-Ready Host](/post/build-validate-cluster-ready-host)
-→ Next: [Post 7 — Migrating VMs from VMware to Hyper-V](/post/migrating-vms-vmware-hyper-v)
+← Previous: [Post 5 ,  Build and Validate a Cluster-Ready Host](/post/build-validate-cluster-ready-host)
+→ Next: [Post 7 ,  Migrating VMs from VMware to Hyper-V](/post/migrating-vms-vmware-hyper-v)
 
 ---

content/post/2026-02-04-welcome-to-the-hyper-v-renaissance.md

@@ -26,7 +26,7 @@ lastmod: 2026-04-05T02:14:44.691Z
 
 You've built the case, validated the hardware, configured the hosts, and connected the storage. Now comes the part everyone's been waiting for (and dreading): actually moving the virtual machines.
 
-VM migration from VMware to Hyper-V is not a single-click operation. Disk formats differ (VMDK vs. VHDX). Virtual hardware differs (VMware paravirtual drivers vs. Hyper-V synthetic drivers). Guest integration tools differ (VMware Tools vs. Hyper-V Integration Services). But the tooling has improved dramatically, and in 2026, you have more options than ever—including a free, Microsoft-supported tool that performs online migration with minimal downtime.
+VM migration from VMware to Hyper-V is not a single-click operation. Disk formats differ (VMDK vs. VHDX). Virtual hardware differs (VMware paravirtual drivers vs. Hyper-V synthetic drivers). Guest integration tools differ (VMware Tools vs. Hyper-V Integration Services). But the tooling has improved dramatically, and in 2026, you have more options than ever, including a free, Microsoft-supported tool that performs online migration with minimal downtime.
 
 In this seventh post of the **Hyper-V Renaissance** series, we'll cover every major migration path, help you choose the right tool for your situation, and walk through the process from pre-migration assessment to post-migration validation.
 
@@ -40,7 +40,7 @@ Let's establish the playing field. Here are the viable tools in 2026:
 
 | Tool | Online Migration | Cost | Scale | Best For |
 |------|-----------------|------|-------|----------|
-| **WAC VM Conversion Extension** | Yes (replication-based) | Free | Batch of 10 VMs | Most migrations — free, Microsoft-supported, online |
+| **WAC VM Conversion Extension** | Yes (replication-based) | Free | Batch of 10 VMs | Most migrations ,  free, Microsoft-supported, online |
 | **SCVMM 2025** | No (offline conversion) | System Center license | Enterprise scale (100+ parallel) | Large-scale migrations with existing SCVMM investment |
 | **StarWind V2V Converter** | Limited (ESXi-to-Hyper-V sync) | Free | Individual VMs | Quick conversions, format flexibility |
 | **Veeam Backup & Replication** | Yes (via restore) | Licensed | Large environments | Organizations already using Veeam |
@@ -86,7 +86,7 @@ Not every VM converts cleanly. Assess each VM against this matrix:
 | Factor | Impact | Action Required |
 |--------|--------|----------------|
 | **BIOS firmware** | Converts to Gen 1 Hyper-V VM | Works as-is; consider converting to Gen 2 post-migration |
-| **UEFI firmware** | Converts to Gen 2 Hyper-V VM | Ideal — enables Secure Boot, larger boot disk support |
+| **UEFI firmware** | Converts to Gen 2 Hyper-V VM | Ideal ,  enables Secure Boot, larger boot disk support |
 | **VMware Paravirtual SCSI** | Must be replaced with standard controller | Tools handle this automatically in most cases |
 | **VMXNET3 NIC** | Must be replaced with Hyper-V synthetic NIC | Tools handle this automatically |
 | **VMware Tools installed** | Must be uninstalled (or removed post-migration) | Uninstall before migration for cleanest conversion |
@@ -121,14 +121,14 @@ The **VM Conversion Extension for Windows Admin Center** is the biggest improvem
 
 ### Why This Is the Recommended Approach
 
-- **Free** — included with Windows Admin Center at no additional cost
-- **Online migration** — the source VM stays running during initial replication; only a brief cutover window is needed
-- **Supports Windows and Linux** — including Ubuntu 20.04/24.04, Debian 11/12, Alma Linux, CentOS, RHEL 9.0
-- **Batch migration** — supports migrating up to 10 VMs simultaneously
-- **Preserves static IP configurations** — reduces post-migration work
-- **Automatic VMware Tools cleanup** — removes VMware Tools from Windows guests post-migration
-- **Secure Boot configuration** — automatically configures Secure Boot based on OS type
-- **Multi-disk support** — migrates all attached virtual disks
+- **Free** ,  included with Windows Admin Center at no additional cost
+- **Online migration** ,  the source VM stays running during initial replication; only a brief cutover window is needed
+- **Supports Windows and Linux** ,  including Ubuntu 20.04/24.04, Debian 11/12, Alma Linux, CentOS, RHEL 9.0
+- **Batch migration** ,  supports migrating up to 10 VMs simultaneously
+- **Preserves static IP configurations** ,  reduces post-migration work
+- **Automatic VMware Tools cleanup** ,  removes VMware Tools from Windows guests post-migration
+- **Secure Boot configuration** ,  automatically configures Secure Boot based on OS type
+- **Multi-disk support** ,  migrates all attached virtual disks
 
 ### Prerequisites
 
@@ -154,9 +154,9 @@ Open the VM Conversion extension and add your vCenter endpoint. You can add mult
 
 Browse your vCenter inventory and select the VMs to migrate. Group them strategically:
 
-- **Application dependency** — VMs that belong to the same application stack
-- **Cluster dependency** — VMs that need to land on nodes within the same cluster
-- **Business boundaries** — separate batches for different business units
+- **Application dependency** ,  VMs that belong to the same application stack
+- **Cluster dependency** ,  VMs that need to land on nodes within the same cluster
+- **Business boundaries** ,  separate batches for different business units
 
 **Step 4: Configure Migration Settings**
 
@@ -201,25 +201,25 @@ lsmod | grep hv_
 
 ## Method 2: SCVMM 2025
 
-System Center Virtual Machine Manager 2025 provides enterprise-scale VMware-to-Hyper-V conversion with enhanced performance—up to four times faster than previous versions. This is the right tool for large-scale migrations where you're converting hundreds of VMs.
+System Center Virtual Machine Manager 2025 provides enterprise-scale VMware-to-Hyper-V conversion with enhanced performance, up to four times faster than previous versions. This is the right tool for large-scale migrations where you're converting hundreds of VMs.
 
 ### How It Works
 
-SCVMM connects directly to your vCenter Server, discovers VMware VMs, and converts them to Hyper-V format. The process is offline—the source VM must be powered off during conversion.
+SCVMM connects directly to your vCenter Server, discovers VMware VMs, and converts them to Hyper-V format. The process is offline, the source VM must be powered off during conversion.
 
 ### SCVMM Conversion Process
 
-1. **Add VMware vCenter to SCVMM fabric** — In the VMM console, under Fabric, add your vCenter Server using a Run As account with administrator privileges.
+1. **Add VMware vCenter to SCVMM fabric** ,  In the VMM console, under Fabric, add your vCenter Server using a Run As account with administrator privileges.
 
-2. **Add ESXi hosts** — After vCenter discovery, add the ESXi hosts that contain the VMs you want to convert.
+2. **Add ESXi hosts** ,  After vCenter discovery, add the ESXi hosts that contain the VMs you want to convert.
 
-3. **Convert VMs** — In VMs and Services, select Create Virtual Machine > Convert Virtual Machine. The wizard walks you through:
+3. **Convert VMs** ,  In VMs and Services, select Create Virtual Machine > Convert Virtual Machine. The wizard walks you through:
    - Selecting the source VMware VM
    - Choosing Generation 1 (BIOS) or Generation 2 (UEFI)
    - Specifying the target Hyper-V host
    - Configuring storage location, network, and VM settings
 
-4. **Monitor conversion** — SCVMM handles disk conversion (VMDK to VHDX), driver injection, and VM registration on the target host.
+4. **Monitor conversion** ,  SCVMM handles disk conversion (VMDK to VHDX), driver injection, and VM registration on the target host.
 
 ### SCVMM Conversion Limitations
 
@@ -278,7 +278,7 @@ StarWind is ideal for:
 - Quick format conversions without infrastructure setup
 - Situations where you need maximum control over the conversion process
 - Converting VMs to test in a lab before production migration
-- Converting between formats not supported by other tools (e.g., QCOW2)
+- Converting between formats not supported by other tools (e.g. QCOW2)
 
 ### Limitations
 
@@ -536,7 +536,7 @@ For production migrations, don't try to convert everything at once. Use a phased
 
 With your VMs migrated to Hyper-V, you've completed the core of the Foundation Building section. But before moving to production architecture, let's tie everything together.
 
-In the next post, **[Post 8: POC Like You Mean It](/post/poc-like-you-mean-it)**, we'll build a complete, functional Hyper-V cluster from scratch in a single afternoon—combining everything from Posts 5, 6, and 7 into a cohesive, reproducible deployment that proves your environment works before you stake production on it.
+In the next post, **[Post 8: POC Like You Mean It](/post/poc-like-you-mean-it)**, we'll build a complete, functional Hyper-V cluster from scratch in a single afternoon, combining everything from Posts 5, 6, and 7 into a cohesive, reproducible deployment that proves your environment works before you stake production on it.
 
 ---
 
@@ -560,7 +560,7 @@ In the next post, **[Post 8: POC Like You Mean It](/post/poc-like-you-mean-it)**
 ---
 
 **Series Navigation**
-← Previous: [Post 6 — Three-Tier Storage Integration](/post/three-tier-storage-integration)
-→ Next: [Post 8 — POC Like You Mean It](/post/poc-like-you-mean-it)
+← Previous: [Post 6 ,  Three-Tier Storage Integration](/post/three-tier-storage-integration)
+→ Next: [Post 8 ,  POC Like You Mean It](/post/poc-like-you-mean-it)
 
 ---