diff --git a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md
index 048333f..31d2e3a 100644
--- a/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md	
+++ b/Virtualization/Hyper-V/Failover Cluster/Rebuild Failover Cluster Replication.md	
@@ -57,5 +57,12 @@ Now we need to clean up the storage left behind by the replication cluster.
     - Delete the entire GUID folder noted in the previous steps. `e.g. 020C9A30-EB02-41F3-8D8B-3561C4521182`
 
 ## Production Cluster - CLUSTER-01
-### Enable Replication on GuestVM in Cluster-01 (Production Cluster)
-PLACEHOLDER
\ No newline at end of file
+### Re-Enable Replication on GuestVM in Cluster-01 (Production Cluster)
+At this point, we have disabled replication for the GuestVM and cleaned up traces of it in the replication cluster.  Now we need to re-enable replication on the GuestVM back in the production cluster.
+
+- Within a node of the production Hyper-V: Failover Cluster Manager
+    - Right-Click the GuestVM
+    - Navigate to "**Replication > Enable Replication...**"
+    - Click "Next"
+    - For the "**Replica Server**", enter the name of the role of the Hyper-V Replica Broker role in the Failover Cluster. `e.g. CLUSTER-01-REPL`
+    - **PLACEHOLDER - UNDER CONSTRUCTION - PLACEHOLDER**
\ No newline at end of file