Added Tags to All Docs

platforms/virtualization/hyper-v/failover-cluster/deploy-failover-cluster-node.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Documentation
+---
+
 **Purpose**: Deploying a Windows Server Node into the Hyper-V Failover Cluster is an essential part of rebuilding and expanding the backbone of my homelab.  The documentation below goes over the process of setting up a bare-metal host from scratch and integrating it into the Hyper-V Failover Cluster.
 
 !!! note "Prerequisites & Assumptions"

platforms/virtualization/hyper-v/failover-cluster/rebuild-failover-cluster-replication.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Documentation
+---
+
 **Purpose**: If you run an environment with multiple Hyper-V: Failover Clusters, for the purpose of Hyper-V: Failover Cluster Replication via a `Hyper-V Replica Broker` role installed on a host within the Failover Cluster, sometimes a GuestVM will fail to replicate itself to the replica cluster, and in those cases, it may not be able to recover on its own.  This guide attempts to outline the process to rebuild replication for GuestVMs on a one-by-one basis.
 
 !!! note "Assumptions"

platforms/virtualization/hyper-v/kerberos-enabled-vm-migration.md

@@ -1,3 +1,8 @@
+---
+tags:
+  - Kerberos
+---
+
 **Purpose**:
 You may find that you want to be able to live-migrate guestVMs on a Hyper-V environment that is not clustered as a Hyper-V Failover Cluster, you will have permission issues.  One way to work around this is to use CredSSP as the authentication mechanism, which is not ideal but useful in a pinch, or you can use Kerberos-based authentication.