From 5532fd570419f8d7d16b3b9231de2034064ff143 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Tue, 23 Jan 2024 15:04:14 -0700 Subject: [PATCH] Update Scripts/Batch/Robocopy.md --- Scripts/Batch/Robocopy.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Scripts/Batch/Robocopy.md b/Scripts/Batch/Robocopy.md index 09c5274..70d1d74 100644 --- a/Scripts/Batch/Robocopy.md +++ b/Scripts/Batch/Robocopy.md @@ -20,7 +20,8 @@ robocopy "E:\Source" "Z:\Destination" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E !!! tip "Usage of Administrative Shares" Whenever dealing with copying data from one server to another, try to leverage "Administrative Shares", also referred to as "Default Shares". These exist in such a way that, if the server exists in a Windows-based domain, you can type something like `\\SERVER\C$` or `\\SERVER\E$` to access files and bypass most file access restrictions (ACLs). This generally only applies to read-access, write-access may be denied in some circumstances. - An adjusted example can be seen below to account for this usage. **This example assumes you are running robocopy from the destination computer**. + 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. ``` robocopy "\\SERVER\E$\SOURCE" "E:\DESTINATION" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E