How to migrate and synchronize user folders when the source and target path names are different (4267005)

How to migrate and synchronize user folders when the source and target path names are different, but the folder names remain the same.

Migrating selected user folders from one file server to another is normally a simple process, however, browsing and manually selecting the desired user from a lengthy folder browser list is less than desirable. In addition, if the source path and target paths names are different, synchronization will not work correctly.

A Vbscript is used to create and import a .csv file from a text file containing a list of desired user folders. The import file it then used to create a new Secure Copy job, which simplifies the process of selecting the user folders for the copy job. The script also creates a map file that allows synchronization to work correctly when the source and target path names are different.

Create a text file with the list of folders names, in this example it is a list of user folders, (figure1).

Figure 1

The Vbscript is called “SCYSourceImport.vbs” and may be obtained by contacting Quest Software Support if it is not already attached to this document. More detailed documentation of the script process may be provided on request.

NOTE: The script is provided as an example and should not be implemented in production without adequate testing. Quest Software does not provide support and assumes no liability for problems that arise from improper use of this script. 

The Vbscript contains a “Script Variables” section that should be customized with values unique to the environment in which it will be executed, (figure 2).

Figure 2

The top of the script explains the required value of each variable, (figure 3).

Figure 3

In Windows XP and Server 2003 double click on the script to run it. In Windows 7 and Server 2008 run the command prompt as Administrator and execute the script. The map file and the import file will be created when the script completes.

In this example the job name is “UserMigrate” (yellow) and the import file is called “SCYJobImportFile.csv”, (figure 4).

Figure 4

A map file called “SCYMapFile.txt” was also created in this example, (figure 5). The map file will show the same names for the target folders as the original source folders, so it is necessary to modify the target folder names to reflect the desired names. The map file may be created manually but ensure that a backslash is at the end of each path.

Figure 5

To create a job from the import file run Secure Copy and select “File” | “Import” from the main Menu, (figure 6).

Figure 6

Select the current job to use as the template for the new job from the drop down list, then browse for the import file created by the Vbscript. In this example it is called “SCYSourceImport.vbs”, (figure 7).

Figure 7

In this example a new job called “UserMigrate” was created from the SCYJobImportfile.csv file, (figure 8).

Figure 8

Select the “Other File Options” node in the new job, check “Map folders and files” and browse for the “SCYMapFile.txt” map file created by the Vbscript, (figure 9). The Map file is only required for Synchronization if the source and target path names are different.\

Figure 9

On the second run, the job in this example copied one new file and purged another, (figure 10).

Figure 10