diff --git a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md
index 28a1dd1..11c47f2 100644
--- a/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md	
+++ b/Servers/Microsoft Exchange/Scripts/DAG/Database Management.md	
@@ -34,4 +34,10 @@ Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02"
 If this fails to cause replication to resume, you can try telling the database to just focus on replication, which tells it to copy the queues and replay them on the replica database, while avoiding interacting with the "**ContentIndexState**" which can be individually fixed in the commands below:
 ```powershell
 Resume-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -ReplicationOnly
-Update-MailboxDatabaseCopy -Identity "DB01\MX-DAG-02" -CatalogOnly -BeginSeed
+```
+
+### If `ContentIndexState` is Unhealthy
+If you see that the "ContentIndexState" is unhappy, you can run the following command to force it to re-seed / rebuild itself.  (This is non-destructive this this is happening on a replica database).
+```powershell
+Update-MailboxDatabaseCopy "DB01\MX05" -CatalogOnly -BeginSeed
+```