From b7d2cf2a58956b6ae81fd2164bcc2ba8f311f901 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Mon, 14 Apr 2025 20:46:33 -0600 Subject: [PATCH] Update Scripts/Batch/Robocopy.md --- Scripts/Batch/Robocopy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Scripts/Batch/Robocopy.md b/Scripts/Batch/Robocopy.md index 70d1d74..373cf02 100644 --- a/Scripts/Batch/Robocopy.md +++ b/Scripts/Batch/Robocopy.md @@ -4,7 +4,7 @@ Robocopy is a useful tool that can be leveraged to copy files and folders from o When you run Robocopy, especially when transferring data across the network to another remote server, you need to be sure to run the command prompt under the session of a domain admin. Secondly, it needs to be ran as an administrator to ensure the command is successful. This can be done by going to the start menu and typing "**Command Prompt**" > **Right Clicking** > "**Run as Administrator**" while logged in as a domain administrator. An example of using Robocopy is below, with a full breakdown: -``` +```powershell robocopy "E:\Source" "Z:\Destination" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E ``` @@ -22,7 +22,7 @@ robocopy "E:\Source" "Z:\Destination" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E An adjusted example can be seen below to account for this usage. **This example assumes you are running robocopy from the destination computer**. - **Remember**: You are always **PULLING** data with administrative shares, not pushing it, the source should be the administrative share, and the destination should always be local. - ``` + **Remember**: You are always **PULLING** data with administrative shares, not pushing it, the source should be the administrative share, and the destination should be local (in this example). There are scenarios where you can move data between two network shares, but its best (and cleaner) to always have a remote/local relationship in the transfer. + ```powershell robocopy "\\SERVER\E$\SOURCE" "E:\DESTINATION" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E ``` \ No newline at end of file