latest version of Microsoft Robocopy GUI download Use Robocopy to pre-seed files for DFS Replication. This topic explains how to use the command-line tool, Robocopy.exe , to pre-seed files when setting up replication for Distributed File System (DFS) Replication (also known as DFSR or DFS-R) in Windows Server. By pre-seeding files before you set up DFS Replication, add a new replication partner, or replace a server, you can speed up initial synchronization and enable cloning of the DFS Replication database in Windows Server 2012 R2. The Robocopy method is one of several pre-seeding methods; for an overview, see Step 1: pre-seed files for DFS Replication. The Robocopy (Robust File Copy) command-line utility is included with Windows Server. The utility provides extensive options that include copying security, backup API support, retry capabilities, and logging. Later versions include multi-threading and un-buffered I/O support. Robocopy does not copy exclusively locked files. If users tend to lock many files for long periods on your file servers, consider using a different pre-seeding method. pre-seeding does not require a perfect match between file lists on the source and destination servers, but the more files that do not exist when initial synchronization is performed for DFS Replication, the less effective pre-seeding is. To minimize lock conflicts, use Robocopy during non-peak hours for your organization. Always examine the Robocopy logs after pre-seeding to ensure that you understand which files were skipped because of exclusive locks. To use Robocopy to pre-seed files for DFS Replication, follow these steps: Prerequisites. Because pre-seeding does not directly involve DFS Replication, you only need to meet the requirements for performing a file copy with Robocopy. You need an account that's a member of the local Administrators group on both the source and destination servers. Install the most recent version of Robocopy on the server that you will use to copy the files—either the source server or the destination server; you will need to install the most recent version for the operating system version. For instructions, see Step 2: Stabilize files that will be replicated. Unless you are pre-seeding files from a server running Windows Server 2003 R2, you can run Robocopy on either the source or destination server. The destination server, which typically has the more recent operating system version, gives you access to the most recent version of Robocopy. Ensure that sufficient storage space is available on the destination drive. Do not create a folder on the path that you plan to copy to: Robocopy must create the root folder. When you decide how much space to allocate for the pre-seeded files, consider expected data growth over time and storage requirements for DFS Replication. For planning help, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder in Managing DFS Replication. On the source server, optionally install Process Monitor or Process Explorer, which you can use to check for applications that are locking files. For download information, see Process Monitor and Process Explorer. Step 1: Download and install the latest version of Robocopy. Before you use Robocopy to pre-seed files, you should download and install the latest version of Robocopy.exe . This ensures that DFS Replication doesn't skip files because of issues within Robocopy's shipping versions. The source for the latest compatible Robocopy version depends on the version of Windows Server that is running on the server. For information about downloading the hotfix with the most recent version of Robocopy for Windows Server 2008 R2 or Windows Server 2008, see List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2008 and in Windows Server 2008 R2. Alternatively, you can locate and install the latest hotfix for an operating system by taking the following steps. Locate and install the latest version of Robocopy for a specific version of Windows Server. In Search Support , enter the following string, replacing with the appropriate operating system, then press the Enter key: robocopy.exe kbqfe "" For example, enter robocopy.exe kbqfe "Windows Server 2008 R2" . Locate and download the hotfix with the highest ID number (that is, the latest version). Install the hotfix on the server. Step 2: Stabilize files that will be replicated. After you install the latest version of Robocopy on the server, you should prevent locked files from blocking copying by using the methods described in the following table. Most applications do not exclusively lock files. However, during normal operations, a small percentage of files might be locked on file servers. Consider temporarily setting Read-only access on the file shares that will be replicated by using the Windows PowerShell Grant-SmbShareAccess and Close-SmbSession cmdlets. If you set permissions for a common group such as Everyone or Authenticated Users to READ, standard users might be less likely to open files with exclusive locks (if their applications detect the Read-only access when files are opened). Step 3: Copy the replicated files to the destination server. After you minimize locks on the files that will be replicated, you can pre-seed the files from the source server to the destination server. You can run Robocopy on either the source computer or the destination computer. The following procedure describes running Robocopy on the destination server, which typically is running a more recent operating system, to take advantage of any additional Robocopy capabilities that the more recent operating system might provide. pre-seed the replicated files onto the destination server with Robocopy. Sign in to the destination server with an account that's a member of the local Administrators group on both the source and destination servers. Open an elevated command prompt. To pre-seed the files from the source to destination server, run the following command, substituting your own source, destination, and log file paths for the bracketed values: This command copies all contents of the source folder to the destination folder, with the following parameters: For example, the following command replicates files from the source replicated folder, E:\RF01, to data drive D on the destination server: We recommend that you use the parameters described above when you use Robocopy to pre-seed files for DFS Replication. However, you can change some of their values or add additional parameters. For example, you might find out through testing that you have the capacity to set a higher value (thread count) for the /MT parameter. Also, if you'll primarily replicate larger files, you might be able to increase copy performance by adding the /j option for unbuffered I/O. For more information about Robocopy parameters, see the Robocopy command-line reference. To avoid potential data loss when you use Robocopy to pre-seed files for DFS Replication, do not make the following changes to the recommended parameters: Do not use the /mir parameter (that mirrors a directory tree) or the /mov parameter (that moves the files, then deletes them from the source). Do not remove the /e , /b , and /copyall options. After copying completes, examine the log for any errors or skipped files. Use Robocopy to copy any skipped files individually instead of recopying the entire set of files. If files were skipped because of exclusive locks, either try copying individual files with Robocopy later, or accept that those files will require over-the-wire replication by DFS Replication during initial synchronization. Next step. After you complete the initial copy, and use Robocopy to resolve issues with as many skipped files as possible, you will use the Get-DfsrFileHash cmdlet in Windows PowerShell or the Dfsrdiag command to validate the pre-seeded files by comparing file hashes on the source and destination servers. For detailed instructions, see Step 2: Validate pre-seeded Files for DFS Replication. Use Robocopy to Preseed Files for DFS Replication. This topic explains how to use the command-line tool Robocopy.exe to preseed files when setting up replication for Distributed File System (DFS) Replication (also known as DFSR or DFS-R) in Windows Server. By preseeding files before you set up DFS Replication, add a new replication partner, or replace a server, you can speed up initial synchronization and enable cloning of the DFS Replication database in Windows Server 2012 R2. The Robocopy method is one of several preseeding methods; for an overview, see Step 1: Preseed Files for DFS Replication. The Robocopy (Robust File Copy) command-line utility is included with Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, and Windows Server 2008. The utility provides extensive options that include copying security, backup API support, retry capabilities, and logging. Later versions include multi-threading and un-buffered I/O support. Robocopy does not copy exclusively locked files. If users tend to lock many files for long periods on your file servers, consider using a different preseeding method. Preseeding does not require a perfect match between file lists on the source and destination servers, but the more files that do not exist when initial synchronization is performed for DFS Replication, the less effective preseeding is. To minimize lock conflicts, use Robocopy during non-peak hours for your organization. Always examine the Robocopy logs after preseeding to ensure that you understand which files were skipped because of exclusive locks. Preseeding files for DFS Replication by using Robocopy involves the following steps: Prerequisites. Because preseeding does not directly involve DFS Replication, you need only meet the requirements for performing a file copy by using Robocopy: You will need to use an account that is a member of the local Administrators group on both the source server and the destination server. Install the most recent version of Robocopy on the server that you will use to copy the files – either the source server or the destination server; you will need to install the most recent version for the operating system version. For instructions, see Step 2: Stabilize files that will be replicated. Unless you are preseeding files from a server running Windows Server 2003 R2, you can run Robocopy on either the source or destination server. The destination server, which typically has the more recent operating system version, gives you access to the most recent version of Robocopy. Ensure that sufficient storage space is available on the destination drive. Do not create a folder on the path that you plan to copy to: Robocopy must create the root folder. When you decide how much space to allocate for the preseeded files, consider expected data growth over time and storage requirements for DFS Replication. For planning help, see Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder in Managing DFS Replication. On the source server, optionally install Process Monitor or Process Explorer, which you can use to check for applications that are locking files. For download information, see Process Monitor v3.05 and Process Explorer v15.40. Step 1: Download and install the latest version of Robocopy. Before you use Robocopy to preseed files, you should download and install the latest version of Robocopy.exe. This ensures that DFS Replication does not skip files because of issues within the shipping versions of Robocopy. The source for the latest compatible Robocopy version depends on the version of Windows Server that is running on the server. For information about downloading the hotfix with the most recent version of Robocopy for Windows Server 2008 R2 or Windows Server 2008, see article 968429 in the Microsoft Knowledge Base. Alternatively, you can locate and install the latest hotfix for an operating system by taking the following steps. To locate and install the latest version of Robocopy for a specific version of Windows Server. In Search Support , type the following string, replacing < operating system version > with the appropriate operating system, and press ENTER: For example, enter robocopy.exe kbqfe "Windows Server 2008 R2" . Locate and download the hotfix with the highest ID number (that is, the latest version). Install the hotfix on the server. Step 2: Stabilize files that will be replicated. After you install the latest version of Robocopy on the server, you should minimize the chances that locked files will block copying by using methods in the following table. Most applications do not exclusively lock files. However, during normal operations, a small percentage of files might be locked on file servers. Source of the lock. Users remotely open files on shares. Employees connect to a standard file server and edit documents, multimedia content, or other files. Sometimes referred to as the traditional home folder or shared data workloads. Only perform Robocopy operations during off-peak, non-business hours. This minimizes the number of files that Robocopy must skip during preseeding. Consider temporarily setting Read-only access on the file shares that will be replicated by using the Windows PowerShell Grant-SmbShareAccess and Close-SmbSession cmdlets. If you set permissions for a common group such as Everyone or Authenticated Users to READ, standard users might be less likely to open files with exclusive locks (if their applications detect the Read-only access when files are opened). You might also consider setting a temporary firewall rule for SMB port 445 inbound to that server to block access to files or use the Block- SmbShareAccess cmdlet. However, both of these methods are very disruptive to user operations. Applications open files local. Application workloads running on a file server sometimes lock files. Temporarily disable or uninstall the applications that are locking files. You can use Process Monitor or Process Explorer to determine which applications are locking files. To download Process Monitor, open Process Monitor v3.05 and Process Explorer v15.40. Step 3: Copy the replicated files to the destination server. After you minimize locks on the files that will be replicated, you are ready to preseed the files from the source server to the destination server. You can run Robocopy on either the source computer or the destination computer. The following procedure describes running Robocopy on the destination server, which typically is running a more recent operating system, to take advantage of any additional Robocopy capabilities that the more recent operating system might provide. To preseed the replicated files onto the destination server by using Robocopy. Log on to the destination server with an account that is a member of the local Administrators group on both the source server and the destination server. Open an elevated command prompt. To preseed the files from the source to destination server, run the following command, substituting your own source, destination, and log file paths: This command copies all contents of the source folder to the destination folder, with the following parameters: "" Specifies the source folder to preseed on the destination server. "" Specifies the path to the folder that will store the preseeded files. The destination folder must not already exist on the destination server. To get matching file hashes, Robocopy must create the root folder when it preseeds the files. Copies subdirectories and their files, as well as empty subdirectories. Copies files in Backup mode. Copies all file information, including data, attributes, time stamps, the NTFS access control list (ACL), owner information, and auditing information. Retries the operation 6 times when an error occurs. Waits 5 seconds between retries. Copies 64 files simultaneously. Excludes the DfsrPrivate folder. Writes status output to the console window, as well as to the log file. /log Specifies the log file to write. Overwrites the file’s existing contents. (To append the entries to the existing log file, use /log+ .) Produces verbose output that includes skipped files. For example, the following command replicates files from the source replicated folder E:\RF01 to data drive D: on the destination server: We recommend that you use the parameters described above when you use Robocopy to preseed files for DFS Replication. However, you can change some of their values or add additional parameters. For example, you might find out through testing that you have the capacity to set a higher value (thread count) for the /MT parameter. Also, if you will replicate larger files primarily, you might be able to increase copy performance by adding the /j option for unbuffered I/O. For more information about Robocopy parameters, see the Robocopy command-line reference. To avoid potential data loss when you use Robocopy to preseed files for DFS Replication, do not make the following changes to the recommended parameters: Do not use the /mir parameter (which mirrors a directory tree) or the /mov parameter (which moves the files, and then deletes them from the source). Do not remove the /e , /b , and /copyall options. After copying completes, examine the log for any errors or skipped files. Use Robocopy to copy any skipped files individually; do not re-copy the entire set of files. If files were skipped because of exclusive locks, retry copying individual files with Robocopy later, or accept that those files will require over-the-wire replication by DFS Replication during initial synchronization. Next step. After you complete the initial copy, and use Robocopy to resolve issues with as many skipped files as possible, you will use the Get-DfsrFileHash cmdlet in Windows PowerShell or the Dfsrdiag command to validate the preseeded files by comparing file hashes on the source and destination servers. For instructions, see Step 2: Validate Preseeded Files for DFS Replication. Microsoft Robocopy GUI 3.1.2. Microsoft Robocopy GUI это программное обеспечение Shareware в категории (2), разработанная AIT Microsoft® Glossaries Team. Проверяли обновления 63 раз пользователями нашего клиентского приложения UpdateStar в прошлом месяце. Последняя версия Microsoft Robocopy GUI-3.1.2, выпущенный на 29.06.2009. Первоначально он был добавлен в нашу базу данных на 29.10.2007. Microsoft Robocopy GUI работает на следующих операционных системах: Windows. Загружаемый файл имеет размер 1MB. Latest version of Microsoft Robocopy GUI download. I want to use richcopy to include or exclude multiple file wildcards. (ie. include u* and c*) I can only seem to get it to work to include a single wildcard (ie include u*) Does anyone know how to include multuple file name specifications on the file name filter. (I am using richcopy v 4.0.217.0) All replies. RichCopy is provided as-is, and it's not supported by Microsoft. For more information, please refer to the following link. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” Add a Graphical User Interface (GUI) To the Microsoft Robocopy. Robocopy or Robust File Copy is a directory replication command-line tool from Microsoft. It was first released a part of the Windows NT 4.0 Resource Kit and it is available as a part of Windows Vista and Windows 7 as a standard feature. For Windows XP users you need to download the Windows Resource Kit in order to use Robocopy. Robocopy can be used to mirror directories, as well as for any batch or synchronous copy needs. The best feature of Robocopy is that when you mirror directories it can copy NTFS attributes and other file properties as well. It provides features such as multithreading, mirroring, synchronization mode, automatic retry, and the ability to resume the copying process. Robocopy is replacing Xcopy in the newer versions of Windows although you can find both the tools in Windows 10. If you are comfortable using the command line then you can directly run Robocopy commands from the command line using the command syntax and options. But if you’re not comfortable using the command line then don’t worry as you can add a graphical user interface (GUI) to go along with the tool. So let’s see how you can add Graphical User Interface to the Microsoft Robocopy using the below-listed tutorial. Add a Graphical User Interface (GUI) To the Microsoft Robocopy. These are the two tools using which you can add a Graphical User Interface (GUI) to the Microsoft Robocopy command-line tool: RoboMirror RichCopy. Let us discuss how these tools can be used to add Graphical User Interface (GUI) to the Microsoft Robocopy command-line tool one by one. RoboMirror. RoboMirror provides a very simple, clean, and user-centered GUI for Robocopy. RoboMirror allows for easy synchronization of two directory trees, you can perform a robust incremental backup, and it also supports volume shadow copies. In order to add Graphical User Interface (GUI) to the Robocopy command-line tool using RoboMirror, first of all, you need to download RoboMirror. To download RoboMirrror, visit the official website of RoboMirror. After downloading is completed follow the below steps to install RoboMirror: 1.Open the downloaded setup of RoboMirror . 2.Click on the Yes button when asked for confirmation. 3.RoboMirror setup wizard will open, just click on the Next button. 4. Select the folder where you want to install the setup of RoboMirror . It is suggested to install the setup in the default folder. 5.Click on the Next button. 6.Below screen will open up. Again click on the Next button. 7.If you want to create a desktop shortcut for the RoboMirror then checkmark “ Create a desktop icon “. If you do not want to do so then simply uncheck it and click on the Next button. 8.Click on the Install button. 9.When the installation is completed, click on the Finish button and the RoboMirror setup will be installed. To use RoboMirror to add Graphical User Interface to Robocopy command-line tool follow the below steps: 1.Open RoboMirror then click on the Add task option available at the right side of the window. 2. Browse for the Source folder and the Target folder by clicking on the Browse button. 3.Now under “ Copy extended NTFS attributes ” you choose to copy the extended NTFS attributes. 4.You can also choose to delete the extra files and folders in the target folder that are not present in the source folder, just checkmark “Delete extra files and folders” . This gives you an exact copy of the source folder that you are copying. 5.Next, you also have an option to create a volume shadow copy of the source volume during the backup. 6.If you want to exclude the files and folders from backing up then click on the “ Excluded items ” button and then select the files or folders which you wish to exclude. 7.Review all your changes then click OK. 8.On the next screen, you can either perform the backup directly or schedule it to be run at a later time by clicking on the Schedule button. 9. Checkmark the box next to “ Perform automatic backups “. 10.Now from the drop-down menu, choose when you want to schedule backup i.e. Daily, Weekly, or Monthly. 11.Once you have selected then click on the OK button to continue. 12.Finally, click on the Backup button to start the backup if not scheduled for later. 13.Before the backup process begins, the pending changes are displayed so that you can cancel the backup and change the settings for the tasks you need to. 14.You also have the option to view the history of the backup tasks you have performed by clicking on the History button . RichCopy. RichCopy is a discontinued file copy utility program developed by Microsoft Engineer. RichCopy also has a nice & clean GUI but it is more powerful and faster than some other file copying tool available for the Windows operating system. RichCopy can copy several files simultaneously (multi-threaded), it can be invoked either as a command-line utility or via a graphical user interface (GUI). You can also have different backup settings for different backup tasks. Download RichCopy from here. After downloading is completed follow the below steps to install RichCopy: 1.Open the downloaded setup of RichCopy. 2.Click on Yes button when asked for confirmation. 3.Select the folder where you want to unzip the files . It is suggested not to change the default location. 4.After selecting the location. Click on the OK button. 5.Wait for a few seconds and all the files will be unzipped to the selected folder. 6.Open the folder which contains the unzipped files and double click on RichCopySetup.msi. 7.RichCopy setup wizard will open, click on the Next button. 8.Again click on the Next button to continue. 9.On the license agreement dialog box, click on the radio button next to the “ I Agree ” option and then click on the Next button. 10.Select the folder where you want to install the RichCopy. It is suggested not to change the default location. 11.Click on the Next button to proceed. 12. Microsoft RichCopy installation will start. 13.Click on yes button when asked for confirmation. 14.When the installation is completed, click on the Close button. To use RichCopy follow the below steps: 1.Click on the Source button to select multiple files that is available on the right side. 2.Select one or multiple options such as files, folders, or drives that you wish to back up. 3.Select the destination folder by clicking on the Destination button available right below the source option. 4.After selecting the source folder and destination folder, click on the Options button and the below dialog box will open. 5.There are several options that are available which you can set for each backup profile separately or for all the backup profiles. 6.You can also set a timer to schedule backup tasks by checking the checkbox next to Timer. 7.After setting the options for backup. Click on the OK button to save changes. 8.You can also start the Backup manually by clicking on Start button available in the top menu. Recommended: Both RoboCopy and RichCopy are free tools that are good for copying or backing up files in Windows faster than simply using the normal copy command. You can use any of them to add Graphical User Interface (GUI) to Microsoft RoboCopy command-line tool . If you still have any questions regarding this guide then feel free to ask them in the comment section. Aditya Farrad. Aditya is a self-motivated information technology professional and has been a technology writer for the last 7 years. He covers Internet services, mobile, Windows, software, and How-to guides. 1 thought on “Add a Graphical User Interface (GUI) To the Microsoft Robocopy” Sounds good and helpful if it really solves the Robocopy problems , I use a GUI alternative to Robocopy called Gs Richcopy 360, it is easy ,Robust and handle all the issues that Robocopy can’t handle like the long pathname, copying the open files, copying the NTFS/Share permissions…. etc .