From d53a67c41a76abc7faa988df9b3d015e170d1658 Mon Sep 17 00:00:00 2001 From: illfated Date: Wed, 12 Jun 2019 02:44:57 +0200 Subject: [PATCH] How to Move MBAM 2.5 Databases: file name correction Copy-Paste error correction: The file name "MBAM Recovery Database Data.bak" was incorrectly replaced by "MBAM Compliance Status Database Data.bak" in one line. This commit resolves the issue, making the number of occurrences of those 2 file names equal and appropriate for their separate sections in this article page. Closes #3988 --- mdop/mbam-v25/how-to-move-the-mbam-25-databases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mdop/mbam-v25/how-to-move-the-mbam-25-databases.md b/mdop/mbam-v25/how-to-move-the-mbam-25-databases.md index 590fce21ac..2500ec0e02 100644 --- a/mdop/mbam-v25/how-to-move-the-mbam-25-databases.md +++ b/mdop/mbam-v25/how-to-move-the-mbam-25-databases.md @@ -142,7 +142,7 @@ Stop-Website "Microsoft BitLocker Administration and Monitoring" ### Move the Recovery Database from Server A to Server B -Use Windows Explorer to move the **MBAM Compliance Status Database Data.bak** file from Server A to Server B. +Use Windows Explorer to move the **MBAM Recovery Database Data.bak** file from Server A to Server B. To automate this procedure, you can use Windows PowerShell to run a command that is similar to the following: