SecureCopy 7.6.3 UserGuide
SecureCopy 7.6.3 UserGuide
User Guide
© 2023 Quest Software Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the
written permission of Quest Software Inc.
The information in this document is provided in connection with Quest Software products. No license, express or implied, by
estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest
Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE
AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY
EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE,
SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS,
BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS
DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest
Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this
document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest
Software does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software Inc.
20 Enterprise, Suite 100,
Aliso Viejo, CA 92656
Refer to our Web site (https://www.quest.com) for regional and international office information.
Patents
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most
current information about applicable patents for this product, please visit our website at https://www.quest.com/legal .
Trademarks
Quest, Secure Copy, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc.
For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx. All other trademarks and
registered trademarks are property of their respective owners.
Legend
CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not
followed.
IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.
Troubleshooting ..................................................................................................................... 60
Logging events for Technical Support ..................................................................................... 60
Removing Secure Copy ........................................................................................................... 60
About us .................................................................................................................................. 66
Option Description
Thread count (2-250) Select the number of copy threads for an individual copy job. The
number of threads is equivalent to the number of copy jobs that
can be performed simultaneously. The minimum is 2 and the
maximum is 250.
● When moving a large number of small files, you can
increase the number of threads towards the maximum
number of 250 threads. With more threads per job, large
numbers of files can be moved in the shortest period of
time.
● When moving larger files, using fewer threads is more
effective because the threads are able to focus on moving
a few large files, switching control between few threads in
a fluid process rather than passing control to multiple
threads, which would slow down the copy process.
Batch count (25-1000) Select the maximum number of files in an individual copy job
thread. Batch Count is a limiter based on the number of files a
thread can process at a time. When a job is being processed, a
single thread copies either the maximum number of files in the
batch count or the maximum batch size, whichever is reached
first. The minimum number of files is 25 and the maximum is
1000.
● When processing a large number of small files, it is
preferable to set the batch count to the highest level for
efficiency.
● When processing large files, the batch count can be set
anywhere because the batch size limitation will be met
before the batch count limit is met.
Option Description
Restore application size, position and By default, Secure Copy starts in the state as you left it when
selected content at startup you closed the application. Clear the check box if you want
Secure Copy to start in the state in which it was installed.
Sort job list alphabetically By default, the job list is sorted by creation time. Select this
check box to sort the list alphabetically.
Show job option tooltips By default, tooltips display on the job options pages when you
hover the cursor over an option. Clear the check box to
remove the display of the tooltips.
Turn on splash screen fading By default, the Secure Copy product splash screen fades in
and out when you start Secure Copy. Clear the check box to
remove the animation when the splash screen displays.
Enable Secure Copy context menus Select to display a Secure Copy menu in Windows Explorer
when you right-click a folder, share, or file.
3 Click OK.
Selecting actions
Table 4. Actions for copy jobs
Click To
Run this job now Run the selected copy job. See Starting a copy job.
Test this job Test the selected copy job. See Starting a copy job.
Schedule this job Schedule the selected copy job. See Scheduling jobs.
View job logs Open the Logs and Reports page. See Viewing logs and reports.
6 By default, Secure Copy creates a folder structure on the target that mimics the folder structure in the
source. To ignore the source folder structure, clear the Create initial source folder under target folder
check box.
IMPORTANT: If the Synchronize target contents with source check box is selected on the
Synchronization page, and you copy from multiple source paths, only those files in the last source
file in the list are synchronized with the target. All other files in the target are deleted. See Setting
synchronization.
Setting synchronization
There are several options you can choose to determine how the data is copied from the source to the target.
To set synchronization
1 Click Jobs, and expand the job.
2 Click Synchronization.
3 Set the options to determine how the data is copied.
Option Description
Copy only changed source If the source and target have files with the same name, Secure Copy
files to target compares the file size and time/date stamp. If the file size is different
or the target file is older than the source file, Secure Copy overwrites
the target with the source. The target is not purged; files and folders
that are in the target, but not in the source, remain in the target after
the copy process completes. If the target path is empty, all files and
folders are copied from the source to the target.
Overwrite target files even if Select to overwrite the target file even if the target file is newer than
they are newer than the source the changed source file.
Copy all files from source to If the source and target have files and folders with the same name,
target Secure Copy overwrites the target with the source. The target is not
purged; files and folders that are in the target, but not in the source,
remain in the target after the copy process completes. If the target
path is empty, all files and folders are copied from the source to the
target.
Option Description
Synchronize target contents with Select to purge files during the copy process. For specific examples
source on using this option, see Synchronizing single source path to single
target path.
NOTE: When purging files during the synchronization process, the
source and target machines and paths as defined by the job must
be compared, and then adjusted or purged accordingly. Because
the purge requires the comparison of the source and target
directories and files, the process could extend the duration of the
data migration.
Delete files or folders to the Select to move the deleted target files and folders to the Recycle
Recycle Bin Bin.
NOTE: Only target files and folders on the local computer can be
moved to the Recycle Bin.
Filters Click to include or exclude specified files or folders from the purge.
See Applying filters.
Option Description
Synchronize archive bit on Select to set the archive bit on the target folder or file to be the
source and target same as the source.
Clear archive bit on source after Select to clear the archive bit on the source file after it is copied.
copying Otherwise the archive bit will remain untouched.
Change Read Only attribute on Select to set or clear the Read Only attribute on all copied files.
copied files
Option Description
Reset last accessed date on Copying files and permissions causes the Last Accessed Date to
source files be set to the current date. Select this option to change the Last
Accessed Date to the date last accessed before the copy, which
is useful if you want to later audit your files to see if they need to
be archived or deleted.
Synchronize Last Accessed Date By default, the Last Accessed Date and the Created Date on the
and Created Date on target files target files will be identical to the source.
with source NOTE: If you uncheck this option, the Last Accessed Date and
the Created Date becomes the date the copy occurred.
Option Description
Don’t copy permissions (copy data Copying the permissions on data is not always necessary for
only) every copy job. A user may just want to migrate data from one
drive to another or from one server to another.
Always copy permissions, even on Copies the permissions of source files and folders from the
skipped files source to the target, even if the files and folders are exactly the
same.
This option is helpful in a situation where the permissions were
changed on the source, but the files were not modified. The copy
process skips the files because of the file size and time/date
stamp are identical. If this option is selected, the permissions are
copied even if the file is not.
Filters Specify selected groups or users to exclude or include in the
copy process for permissions.
To create a filter
1. Click Filters.
2. Click Add.
3. Select the groups or users to include or exclude.
4. Select the appropriate option:
• DO NOT copy permissions for selected
groups/users
• Copy permission ONLY for selected groups/users
NOTE: To save the filter to a .csv file, click Save. You can load
the saved filter file at a later time by clicking Load.
Override security on access denied Allows an administrator to perform a copy without changing any
(you must be an administrator) of the permissions or ownership for the objects.
In a traditional copy process, a user must have permissions on a
file or folder to copy it. If the user is denied access, they must
first take ownership of the object, and then set the appropriate
permissions before copying it. Imagine the nightmare scenario of
migrating 10,000 user home and profile directories from one
server to another. These directories would take forever to
repermission and copy.
Block inheritance for root folder(s) Select to block inheritance on root folders. Blocking inheritance
at the root of your target folder is designed to prevent permission
changes made above the root of your target from overwriting any
permission structures you migrate from your source.
NOTE: This check box is unavailable if the Force inheritance
for all target folder(s) check box is selected.
Force inheritance for all target Select to force all the copied folders to keep their original
folder(s) permissions and to inherit the permissions from the target folder
and the parent folder.
Paths
Source Path Target Path Target Result
C:\SOURCE\ \\SRV1\C$\TARGET\ \\SRV1\C$\TARGET\SOURCE\
Result
Because the Create initial source folder under target folder check box is selected, the source folder structure
is duplicated under the target folder. When the copy process is complete:
● Files and folders in the target folder (\\SRV1\C$\TARGET\SOURCE\) that do not also exist in the source
folder (C:\SOURCE\) are purged from the target folder.
Paths
Source Path Target Path Target Result
C:\SOURCE\ \\SRV1\C$\TARGET\ \\SRV1\C$\TARGET\SOURCE\
Result
Because the Create initial source folder under target folder check box is selected, the source folder structure
is duplicated under the target folder. When the copy process is complete:
● Files and folders that do not exist in the source folder (C:\SOURCE\) are not purged from the target
folder (\\SRV1\C$\TARGET\SOURCE\).
● Files and folders that do not exist in the first subfolders of the source folder (C:\SOURCE\subfolder A3\)
and down are purged from the corresponding target folder (\\SRV1\C$\TARGET\SOURCE\sub-folder
A3\).
Paths
Source Path Target Path Target Result
C:\SOURCE\ \\SRV1\C$\ \\SRV1\C$\
Result
Because the Create initial source folder under target folder check box is not selected, the source folder
structure is not duplicated under the target path. When the copy process is complete:
● All files and folders inside the source folder (C:\SOURCE\) are copied to the target folder (\\SVR1\C$\).
● For safety, orphaned files and folders in this scenario are not purged because the system drive would be
purged of all other data.
Figure 3. Orphaned folders and files on the target are not purged
Paths
Source Path Target Path Target Result
C:\SOURCE\ \\SRV1\C$\TARGET\ \\SRV1\C$\TARGET\
The examples included in this section illustrate how these three options work together.
● Scenario 1: Folders with the same name
● Scenario 2: Files with the same name
● Multiple sources example 1
● Multiple sources example 2
● Multiple sources example 3
● Multiple sources example 4
Paths
Source Path Target Path Target Result
C:\folderA\ \\server1\C$\ \\server1\C$\folderA\
C:\folderB\ \\server1\C$\folderB\
Results
Because the Create initial source folder under target folder check box is selected, the source folder structure
is duplicated under the target path during the copy process. When the copy process is complete:
● All files and folders inside the source folders (C:\folderA\ and C:\folderB) are copied to the target folder
(\\SVR1\C$\).
● Files and folders that do not exist in the source folders (C:\folderA\) and (C:\folderB\) are purged from the
target folders (\\server1\C$\folderA\) and (\\server1\C$\folderB\).
IMPORTANT: When copying multiple source paths to a single target path, any file or folder with the same
name located on the root of the source paths is overwritten by the file or folder of the same name in the
last source path. See Scenario 1: Folders with the same name and Scenario 2: Files with the same name.
Paths
Source Path Target Path Target Result
C:\folderA\ \\server1\C$\ \\server1\C$\folderA\
C:\folderB\ \\server1\C$\folderB\
Results
Because the Create initial source folder under target folder check box is selected, the source folder structure
is duplicated under the target path during the copy process. When the copy process is complete:
● All files and folders inside the source folders (C:\folderA\ and C:\folderB) are copied to their respective
target folders (\\server1\C$\folderA\) and (\\server1\C$\folderB\).
● Files and folders that do not exist in the root of the source folders (C:\folderA\) and (C:\folderB\) are not
purged from their respective target folders (\\server1\C$\folderA\) and (\\server1\C$\folderB\).
● Files and folders that do not exist in the subfolders of the source folders (C:\folderA\sub-folderA1\) and
(C:\folderB\subfolderB1\) and down are purged from their respective target folders
(\\server1\C$\folderA\folderA sub1\) and (\\server1\C$\folderB\sub-folderB1\).
Figure 8. Orphaned folders and files in subfolders on the target are purged
Paths
Source Path Target Path Target Result
C:\folderA\ \\server1\C$\ \\server1\C$\
C:\folderB\
Result
Because the Create initial source folder under target folder check box is not selected, the source parent
folder is not duplicated under the target path during the copy process, but the source subfolders are duplicated.
When the copy process is complete:
● All files and folders inside the source folders (C:\folderA\ and C:\folderB) are copied to the target folder
(\\SVR1\C$\).
● For safety, files and folders that do not exist in the root of the source folders (C:\folderA\) and
(C:\folderB\) are not purged from the target folder (\\SVR1\C$\), because the system drive would be
purged of all other data.
Figure 9. Orphaned files and folders on the target are not purged
IMPORTANT: When copying multiple source paths to a single target path, any file or folder with the same
name located on the root of the source paths is overwritten by the file or folder of the same name in the
last source path. See Scenario 1: Folders with the same name and Scenario 2: Files with the same name.
Paths
Source Path Target Path Target Result
C:\folderA\ \\server1\C$\ \\server1\C$\
C:\folderB\
Result
Because the Create initial source folder under target folder check box is not selected, the source parent
folder is not duplicated under the target path during the copy process, but the source subfolders are duplicated.
When the copy process is complete:
● Files and folders from all source paths are copied to the target folder (\\server1\C$\).
● Files and folders that do not exist in the first subfolders of the source folders (C:\folderA\sub-folder A1\)
and (C:\folderB\sub-folder B1\) and down are purged from their respective target folders.
● For safety, files and folders that do not exist in the root of the source folders (C:\folderA\) and
(C:\folderB\) are not purged from the root of the target folder (\\server1\C$\).
IMPORTANT: When copying multiple source paths to a single target path, any file or folder with the same
name located on the root of the source paths is overwritten by the file or folder of the same name in the
last source path. See Scenario 1: Folders with the same name and Scenario 2: Files with the same name.
Filtering files
You can filter files by file name or extension. You can create multiple filters, but you must add filters one at a
time. In the following example, any files with the listed extensions are excluded from the copy job.
Filtering folders
In adding to filtering files, you can add a filter for folders. You can create multiple filters, but you must add filters
one at a time. The asterisk wildcard is supported (New* would filter a folder named New Folder). During a
migration this might be helpful for the elimination of folders that are not necessary and can be recreated later.
Some examples are temp folders and Temporary Internet Files folders.
Enabling logging
You can set logging for an individual copy job. Two logging levels are available: Full and Errors only. Selecting
Full automatically enables the Logging Status option where you can customize your logs by copying status.
To enable logging
1 Click Jobs, and expand the job.
2 Click Performance.
3 Select Enable logging.
4 Select the logging level, and logging status (when available).
Option Description
Thread count Select the number of copy threads for an individual copy job
The number of threads is equivalent to the number of copy jobs that can be
performed simultaneously. By increasing the thread count, you are adding more
threads that copy batches of files. Each of the file threads deals with one batch
of files at a time.
In normal operation, the default settings should be adequate. However, if you
have a large number of small files and many batches, you might start by
creating at least 10 threads, and then monitoring network card utilization.
IMPORTANT: Setting the thread count too high can result in poor performance.
We recommend using a value less than 20 if using normal server hardware.
• When moving a large number of small files, you can increase the number
of threads towards the maximum number of 250 threads. With more
threads per job, large numbers of files can be moved in the shortest
period of time.
• When moving larger files, using fewer threads is more effective because
the threads are able to focus on moving a few large files, switching control
between few threads in a fluid process rather than passing control to
multiple threads, which would slow down the copy process.
Batch count Select the maximum number of files in an individual copy job thread
Batch Count is a limiter based on the number of files a thread can process at a
time. When a job is being processed, a single thread copies either the maximum
number of files in the batch count or the maximum batch size, whichever is
reached first. The minimum number of files is 25 and the maximum is 1000.
IMPORTANT: In most cases, the default values are optimal. Changing these
values incorrectly can lead to performance degradation.
• When processing a large number of small files, it is preferable to set the
batch count to the highest level for efficiency.
• When processing large files, the batch count can be set anywhere
because the batch size limitation will be met before the batch count limit is
met.
Batch size Select the maximum number of bytes in an individual copy job thread.
Batch Size is a limiter based on the size of the files a thread can process at a
time. When a job is being processed, a single thread copies either the maximum
size of files or the maximum number of files, whichever is reached first. The
minimum is 1MB and the maximum is 100MB.
IMPORTANT: In most cases, the default values are optimal. Changing these
values incorrectly can lead to performance degradation.
• When processing a large number of small files, it is preferable to set the
batch size to the highest level for efficiency.
• When processing large files, the batch size can be set anywhere because
the batch size limitation will be met prior to meeting the limit of the batch
count.
Inter-Packet Gap Select the time span to wait between packets of data being copied.
The Inter-Packet Gap (IPG), which is also referred to as an Interframe Gap
(IFG), slows down the copy process, which reduces the bandwidth usage over
the network. As a file is copied, it is copied 64 kilobytes at a time. The Inter-
Packet Gap is a time span in milliseconds (ms) to wait before sending the next
64 kilobytes.
NOTE: Due to factors, such as the volume of other traffic on the network, you
may need to experiment with the time span to achieve a desired bandwidth.
Option Description
Local groups Migrates local groups from the source to the target.
Local users Migrates local users from the source to the target.
Copy only local groups Migrates only local groups and users accounts. Files are not migrated.
and users not files NOTE: Only local groups and users who already have permissions on the
source data will be migrated.
Set password for Set a new password for the migrated user accounts. Type the new
migrated user accounts password in the box.
Option Description
Target server Migrates local groups and users from the source server to the target
server that is indicated on the Copy Locations page.
Active directory Migrates local groups and users from the source server to an Active
Directory® Organizational Unit (OU). Type a path using standard LDAP
format in the box, or click Browse to browse for an OU.
Always perform the To avoid conflicts, add a prefix or suffix to the migrated groups/users.
following action Adding a prefix or suffix allows administrators to enforce a standard
naming convention, or to differentiate the migrated groups and users
from their already existing counterparts.
Option Description
Use the existing group/user If a local group/user name already exists on the target, Secure
Copy applies those permissions to the migrated data.
Add members of the source Migrates the users of a group on the source server to the group with
group to existing group the same name on the target server.
Synchronize target members If a local group/user already exists on the target, the source local
with source members group/user overwrites the target.
Add the Prefix In cases where there may be multiple local groups/users of the
Add the Suffix same name and manually renaming the local groups/users when
prompted may be unfeasible, such as in the case of a scheduled
job, you can have Secure Copy add a prefix or a suffix to the new
local group/user name. This gives a uniform naming convention to
the new local groups/users and prevents unnecessary user
intervention.
7 To prevent Secure Copy from appending members to the target server’s BUILTIN Groups, select Don’t
append members to target server’s BUILTIN groups.
8 To use a map file to migrate local groups and users, see Using map files to migrate local groups and
users.
Option Description
Skip It (Ignore) If a share already exists on the target, Secure Copy does not create
the share on the target.
Overwrite (Remove old share, If a share already exists on the target, Secure Copy unshares the
create new one) share on the target, and then writes over it with the source share.
Add the Prefix Type the prefix or suffix to add to the new file share name.
Add the Suffix In cases where there may be multiple shares of the same name and
you want to recreate the shares using the new folders from the
source, but manually renaming the shares when prompted may be
unfeasible, such as in the case of a scheduled job, you can have
Secure Copy add a prefix or a suffix to the new share name. This
gives a uniform naming convention to the new shares and prevents
unnecessary user intervention.
5 If the source contains a root share folder, such as \\server\sharename, and you want to create that root
share folder on the target, select Create root share folder on target. Otherwise, the root share folder is
not created on the target.
6 If Source is File share, Create source root share folder on target check box on File shares page is not
selected, the purge will not occur.
Formatting Rules
● Source and target directory must be on different computers, copying from one location to another on the
same computer (even if the source and target are on different volumes) prevents the folders from being
mapped.
● The full path for the source and target folders must be entered into the map file.
● For folders, the source and target path in the map file must have a trailing backslash (not necessary for
files).
● The target directory does not need to be created ahead of time. If the folder on the target directory does
not exist prior to running the copy job, Secure Copy creates the target folder and copies the contents of
the source folder into the new target folder.
Examples
● To copy a file: C:\test\testfile.txt=\\targetserver\test\testfile.txt
● To copy folders: C:\source\=\\ad3\e$\scy test\target\
● To rename a file: C:\test\testfile.txt=\\targetserver\test\newtestfile.txt
● To divert a file: C:\test\testfile.txt=\\targetserver\newDir\testfile.txt
● To rename a folder: C:\test\=\\targetserver\C$\newfolder\
Using compression
NOTE: Compression is not performed by Secure Copy; it is performed by the operating system. The
compression function is performed at the same time as the write function, which could extend the write
time of the file and thus extend the duration of data migration.
To use compression
1 Click Jobs, and expand the job.
2 Click Other File Options.
3 Select how to handle compression.
Option Description
Never compress target files Disregards any file or folder compression that may exist on the
source or target. Copies all files and folders uncompressed. This
option offers the greatest speed for the copy process, and is
recommended if there is not a space requirement on the target.
Option Description
Update ACLS which use SID Select to update ACLs that use SID history, and type a Lightweight
history Directory Access Protocol (LDAP) domain path.
During a migration, the SIDs of the objects being migrated are
checked against the SID History specified in the LDAP domain path
box. If the SIDs of the objects being migrated are on the list, the
ACLs are updated with new SIDs for the migrated objects and their
SID history is cleared.
Copy SACL Select to copy security information.
Remove Orphaned SIDs Select to remove orphaned SIDS.
Map SIDs Using Quest If you created a map file using Quest™ Migration Manager, select the
Migration Manager for AD map check box, and click Browse to locate the map file.
file • To view the contents of the map file, click View.
• By default, source permissions on the target are retained. If
you do not want to retain the permissions, clear the Leave
source accounts permissions on target check box.
• If you want to copy only permissions for accounts that are
included in the Migration Manager INI map file and ignore all
other permissions from the source, select Translate only
accounts found in the map file.
NOTE: If you select Translate only accounts found in the map
file, the Leave source accounts permissions on target check box
is cleared and vice versa. Both checkboxes cannot be selected at the
same time.
Option Description
Run a Pre-Migration Task Select to run a task before the migration begins. Click Browse to
locate an executable (*.exe or *.cmd) or type the path into the
box.
Run a Post-Migration Task Select to run a task after the migration completes. Click Browse
to locate an executable (*.exe or *.cmd) or type the path into the
box.
If a fatal error occurs, cancel all Select to cancel all pending tasks and the migration if a fatal
tasks including the migration. error occurs during the execution of a task or the migration.
Option Description
When job completes Select to send an email to the specified recipients when the
copy job completes successfully.
If job has not completed by Select to send an email to the specified recipients only if the
copy job has not completed by the date and time specified.
To change the date and time, click an item in the box, and
then use the arrow keys to change the value.
If job is not completed within Select to send an email to the specified recipients only if the
hh:mm:ss copy job has not completed within the time period specified.
To change the time period, click an item in the box, and then
use the arrow keys to change the value.
If job fails Select to send an email to the specified recipients if the job
fails.
5 To add recipients, click Add, type the name of the recipient, and click OK. Repeat for each recipient.
6 Type the text to appear in the subject line of the email.
Importing a job
You can create a new job quickly by using the options set for a current job and then importing a .csv file with the
job name, source path, and target path.
Scheduling jobs
Secure Copy includes the ability to schedule copy jobs to occur when they are convenient to personnel, without
interfering with business practices. The best time for data migration is during hours of non-operation or non-peak
usage. Quite often this is not feasible for the average 9 to 5 administrator. Secure Copy uses the features of the
Microsoft Task Scheduler service to handle all functions of job scheduling.
2 Select a log file from the Logs and Reports pane. The Dashboard tab displays a summary of the
selected job.
Button Description
Level Filter the displayed results by the value in the Level column: All, Debug, Error, Fatal, Info,
or Warn
Status Filter the displayed results by the value in the Status column: All, Copied, Error, Info,
Purged, or Stopped
Type Filter the displayed results by the value in the Type column: All, dll, exe, htm, or wav
Group By Group the displayed results by the values in the Level, Logger, or Status columns
Refresh Reload the values from the log file
Clear Clear all values from the display
Reset Remove all groupings and filters from the displayed results
Export Export log results to a CSV or XML file
Exporting logs
You can export a log to a .CSV or .XML file.
Running reports
You can run reports about the selected copy job.
To run a report
1 Click Logs and Reports.
2 Select a log file from the Logs and Reports pane.
3 Open the Reports tab and select a report.
NOTE: For those reports that can be sorted by Message or Source, select the desired option before
running the report.
Report Description
Summary Report Lists job summary information.
Copied Files Report Lists copied files, sorted by Message, Source, or File Type.
NOTE: Select the method of sorting prior to running the report.
Skipped Files Report Lists skipped files, sorted by Message, Source, or File Type.
NOTE: Select the method of sorting prior to running the report.
Purged Files and Folders Report Lists purged files and folders, sorted by Message, Source, or File
Type.
NOTE: Select the method of sorting prior to running the report.
Local Groups and Users Report Lists migrated local groups and users.
Failed Job Report Lists fatal errors that prevented the copy job from completing.
Errors Report Lists errors, sorted by Message, Source, or File Type. Select the
method of sorting prior to running the report.
File Verification Report Lists any differences in the SHA512 checksum comparisons of
file verification, if Verify File Copy is selected on the Performance
page. See Verifying file copy.
License Information Report Lists licensed servers.
Console’s Server List Report Lists the server licenses used by this console.
Verbose Report Displays the contents of the Log Viewer tab as a report.
Analysis Report Displays the post-migration analysis.
Using SecureCopyCmd.exe
You can run Secure Copy from the command line by using SecureCopyCmd.exe. You can run the File System
Statistics Analyzer from the command line using FileSystemStatistics.exe.
SecureCopyCmd.exe is the engine that Secure Copy uses for copy processes and it uses all of the features that
are available in Secure Copy. SecureCopyCmd.exe runs from the command line, but offers only limited options to
script, because it references the features of a saved job by using the name of that job.
NOTE: You must use SecureCopyCmd.exe from a computer that has a fully licensed version of Secure
Copy 7 installed. You cannot copy SecureCopyCmd.exe from computer to computer.
Usage
SecureCopyCmd.exe
Parameter Meaning
/DB Specify jobs database (.ssd file)
/Name=<Name> Specify job using Job Name
/Source=<SourcePath> Define a new source path.
IMPORTANT: If you add /source to the command, it overrides
the source(s) specified in the copy job identified by the job id
or name.
/Target=<TargetPath> Define a new target path.
IMPORTANT: If you add /target to the command, it overrides
the target(s) specified in the copy job identified by the job id or
name.
/CopySubFolders=<True/False> Specify true or false.
/Test Test the job.
/Delete Delete the job.
/Quiet Runs job without user interface.
Usage
The File System Statistics Tool (FileSystemStatistics.exe) is located in the Secure Copy installation folder:
C:\Program Files\Quest\Secure Copy 7.
FileSystemStatistics /roots <roots> | /server <server> /out <filename> [/threads
<count>] [/security] [/nobackup] [/nostatus]
If neither /roots or /server are specified, the application will enumerate all fixed drives on the local computer, and
process them.
Managing licenses
● Viewing licenses
● Viewing licensed servers
● Applying a new license file
● Checking for product updates
Viewing licenses
Secure Copy is licensed per server or per user. When you create a copy job, Secure Copy checks the license
status to verify that the selected servers are on the list of licensed servers or if you have an available license to
add the server. Use the options on the Help menu to monitor your license.
License details include the license number, license type, expiration date, and the number of licensed servers and
users. To see how many of the licensed servers are being used, check the list of licensed servers.
d. Click Add.
e. Click Next.
f. Map the source servers to the new target servers that will replace the source servers in the users’
home directory paths.
The Home drive mappings page lists all of the servers on which the selected users have their
home drives: these are the source servers. You can map each source computer to a different
target computer or you can map multiple source computers to a single target computer.
g. Click the row that contains the source computer to be mapped.
h. Browse to select a target computer.
i. Repeat for each source computer to be mapped to a new target computer.
j. Click Next.
6 View the details for the user home paths that you are updating and make individual changes to the new
home path information, if necessary.
■ To edit specific information, click the entry under the New Home Dir heading that you want to
change, and enter in the changes.
■ To make changes for several users at a time, click Replace All and enter the information to be
changed and the new information that replaces it.
7 Export the user home path mapping details to a file, if desired. The file that is created is in .csv (comma-
separated values) file format.
A .csv file is a method to collect data so that it can be used as input for a table-oriented application such
as a spreadsheet. Microsoft Excel can read .csv files. By editing the .csv file, you can make bulk changes
to the user information using search and replace options.
To export the file
a. Click Export to create a file.
b. Enter the name for the file and the location in which it should be saved.
c. Click Save.
After you have created the file, you can import it into a program such as Microsoft Excel and make bulk
changes to the user information using search and replace options. You can then import the file into this
wizard and update the user home paths on the specified servers.
After you import the file into a program such as a spreadsheet application, you can see that the file follows
certain conventions that must be maintained as you edit the file:
■ The first column and row must contain the domain name.
■ The subsequent rows that contain the user home path details must be in the following format:
user name current user home path new user home path drive letter
8 Click Next.
10 Review the final information for the user home path updates.
11 Click Finish.
While the update is running, the User Home Path Updater displays a dialog box that shows the statistics
for the update, such as the elapsed time and the estimated time remaining. You can also use this dialog
box to stop the update.
For an easy way to verify that the user home paths have been updated, run the User Home Path Updater
again and select the target server from the previous update on the Select Users page of the wizard. All of
the users that you updated are now listed under the target server. Once you have viewed the list, close
the wizard.
Quest Secure Copy 7.6.3
Running Update Utilities 50
Profile Path Updater
The User Profile Path Updater allows you to view roaming user profiles on a server within a specified domain and
to update the paths after you have migrated data to a new server. A roaming user profile is stored on a server
and is available every time an end user logs on to any computer on the network. Any change made to the
roaming user profile is updated on the server.
IMPORTANT: Your logon account must have administrative rights for the domain in which the user
accounts exist.
IMPORTANT: Home Path Updater and Profile Path Updater require that Active Directory® Users have
Home Paths and Profile Paths configured in Active Directory, otherwise when the domain is scanned the
Server drop-down list will be empty.
d. Click Add.
e. Click Next.
f. Map the source servers to the new target servers that will replace the source servers in the users’
home directory paths.
The Home drive mappings page lists all of the servers on which the selected users have their
home drives: these are the source servers. You can map each source computer to a different
target computer or you can map multiple source computers to a single target computer.
g. Click the row that contains the source computer to be mapped.
h. Browse to select a target computer.
i. Repeat for each source computer to be mapped to a new target computer.
j. Click Next.
5 View the details for the user profile paths that you are updating and make individual changes to the new
profile path information, if necessary.
■ To edit specific information, click the entry under the New Profile Path heading that you want to
change and enter in the changes.
7 Click Next.
9 Review the final information for the profile path updates on the Confirmation page.
10 Click Finish.
While the update is running, the User Profile Path Updater displays a dialog box that shows the statistics
for the update, such as the elapsed time and the estimated time remaining. You can also use this dialog
box to stop the update.
For an easy way to verify that the user profile paths have been updated, run the User Profile Path Updater
again and select the target server from the previous update on the Select Users page of the wizard. All of
the users that you updated are now listed under the target server. Once you have viewed the list, close
the wizard.
Shortcut Updater
Use the Shortcut Updater to update shortcuts to point to the new location after data is migrated to a new server.
When you run the Shortcut Updater, the shortcut files (.lnk) that contain the shortcut paths to the source
computer are updated to point to the new target path location.
You can specify the old and new target path of the shortcut or use a .INI file. The .ini file must be saved in ANSI-
encoded format.
Example
You migrated data from server CORP1_NT to server CORP1_2K. During the migration, you renamed Accts to
Accounts and Sales to UKSales. The .ini file to update those shortcuts that map to files and folders on the old
server is:
[ServerMap]
\\CORP1_NT\Sales = \\CORP1_2K\UKSales
\\CORP1_NT\Accts = \\CORP1_2K\Accounts
\\CORP1_NT = \\CORP1_2K
To update shortcuts
1 Click Update Utilities, and click Shortcut Updater.
2 Type the path or browse to locate the path of the shortcut files to update.
Link Updater
IMPORTANT: Microsoft Office is required for Link Updater. Do not run Microsoft Office applications on
the computer on which the Link Updater is running. If you have Excel open when you run Link Updater,
Excel will be forcibly closed with no prompting to save your files.
You can use the Link Updater (LU.exe) to update OLE (Object Linking and Embedding) links and hyperlinks in
Microsoft Word, Excel, and PowerPoint files that have been migrated to a new server.
NOTE: The Link Updater cannot update the links in files that are password protected or to which access
is denied and files that are in use.
The OLE links and hyperlinks can use either UNC (Universal Naming Convention) paths or explicit local paths.
The utility can update the existing links in a document to new local paths or UNC paths as necessary.
In a network, the Universal Naming Convention (UNC) is used to identify a shared file in a computer without
having to specify the specific storage device on which it is located. In Windows® operating systems, the UNC can
be used instead of the local naming system. The UNC name format is as follows:
\\servername\sharename\path\filename
A UNC path cannot contain any folder names or subfolder names since the file name could already exist directly
under the share name.
Prerequisites
Before you update the link information, verify that the following prerequisites are met:
● Microsoft Word, Excel, and PowerPoint must be installed on the computer on which the Link Updater is
run.
● •You must be logged on with an account that has administrative rights since you need access to the files.
To specify a path
a. In the Source Link box, type a path or browse to locate the linked files on the source
computer. The path name can be a local path or UNC path.
b. In the Target Link box, type a path or browse to locate the linked files on the target computer.
The path name can be a local path or UNC path.
To use a map file
a. Select Use Map File.
b. Type a path or browse to locate the link map .ini file that maps the old locations of linked files to
the new locations. See Creating a link map .ini file.
c. Click Open.
4 Set options for the update.
Option Description
Recursive Search and Update Select to search recursively through the folders and subfolders of
the paths you have specified.
Turn on output to CSV file Select to save detailed information from the test report in a CSV
(comma separated values) file.
Log detailed info Select to save detailed information from the update in a log file.
5 To perform a test report audit to see the number of files that will be updated by Link Updater, select Test
Mode, and specify the number of files you want to test. No files are actually updated when you run the
test report.
6 Click Run.
Upon completion, the Link Updater creates a log file and a report file in the Tools subfolder (C:\Program
Files\Quest\Secure Copy 7\Logs\Tools\Link Updater).
Format for the file name: LU_ddmmyy_hh_mm_ss.*
To view the report in a web browser
■ Click Report. You also can open the report from the Navigation pane by double-clicking the report
file name.
To view the log
■ Click Log. You also can open the report from the Navigation pane by double-clicking the log file
name.
7 When you are ready to perform the update, clear the Test Mode check box, and click Run.
NOTE: Do not enclose any file or folder names that contain spaces in quotation marks in an .ini file. You
only use enclose variables in quotation marks in the command line.
Example
You have a Microsoft Word file with links to different types of files in several different folders. You have created
an .ini file that maps the old locations of the linked files to the new locations. The name of the.ini file is remap.ini
and is located in C:\Migration.
LU "\\ServerA\Sales 2005\Company X RFP.doc" /F=C:\Migration\remap.ini
Use the following syntax to run Link Updater from the command line and manually specify the paths to be
updated:
LU FullFilePath SourcePath TargetPath [/r] [/t= n] [/c] [/z]
NOTE: Any file or folder names that contain spaces must be enclosed in quotation marks ("). You must
enter the source and target paths using a balanced syntax.
Correct
LU *.doc C:\SourceFolder\ D:TargetFolder\
Incorrect
LU *.doc C:\SourceFolder\ D:TargetFolder
Since the incorrect example has \ after SourceFolder but not after TargetFolder, the Link Updater replaces
C:\SourceFolder\ with D:\TargetFolder. So, in effect, the TargetFolder name is incorrect as a prefix to the updated
file links. The Link Updater would determine that the target path does not exist and the files are not updated.
Registry Updater
You can use the Registry Updater (RegTool.exe) to search and replace registry entries on client computers after
a migration. The Registry Updater updates the registry based on an .ini file that contains the specified registry
entries that are used to update the client computers.
For example, after a data migration you may need to update drive mappings in user local and roaming profiles.
The Registry Updater replaces outdated links with links to the new server, so the computers can identify the new
location of the data.
NOTE: Before you run the Registry Updater, you must create an .ini file for the drive mappings.
Topics:
● Creating the drive mapping .ini file
● Running the Registry Updater
● Running Registry Updater from the command line
● Using the Registry Updater in a logon script
The [ServerMap] section defines a mapping of old server to new server. You can map a server to a share on
another server and you can map a share on a server to a new share on a server.
IMPORTANT: Only one mapping rule is applied and the rules are processed in order. This allows you to
map old shares to new shares with different names.
Example
You migrated data from server FS_NT to server FS_2K. Several shares were migrated and you renamed some
of the shares because of conflicts on the target server or because of new naming conventions. You migrated
shares named Software, Public, Accts, and Sales. During the migration, you renamed Accts to Accounts and
Sales to UKSales. The .ini file to update those users that still have drive mappings to the old server and old
shares might look as follows:
;[ServerMap]
;FS_NT\Sales = FS_2K\UKSales
;FS_NT\Accts = FS_2K\Accounts
;FS_NT = FS_2K
Format
RegTool /i=INIFile [/c=ComputerName] [/a=AuditFile]
INIFile is the name and path of the .ini file that you created.
ComputerName is the computer where the Registry Updater will update the registry. If you do not specify this
argument, the update is run on the local computer.
AuditFile is the path to the file that saves the information about the registry keys that were updated and those that
could not be updated. (Optional)
Examples
RegTool /i=C:\RegTool\updates.ini /c=USERCOMP01 /a=C:\RegTool\audit.log
RegTool /i=\\FILSRV1\RegToolShare\updates.ini /c=USERCOMP01 /a=C:\RegTool\audit.log
Troubleshooting
Secure Copy has several tools that you can use to help troubleshoot your copy jobs. Quest Technical Support is
also available to help you. You can access the Quest Support Portal at https://support.quest.com.
Topics:
● Logging events for Technical Support
● Removing Secure Copy
PowerShell cmdlets
Microsoft® Windows PowerShell® is a Windows® command-line shell and scripting language designed specifically
for system administrators and built on top of the Microsoft .NET Framework. Secure Copy® supports the use of
PowerShell cmdlets.
Topics:
● What are cmdlets?
● Using the PowerShell cmdlets
● Managing copy jobs
● Running the File System Statistics Analyzer
Table 28. Secure Copy cmdlets for use with Windows PowerShell
NOTE: All cmdlets should be run while logged on as an Administrator. The Secure Copy cmdlets should
be used only by those familiar with Windows PowerShell.
Parameter Description
-Database <string> Specify the jobs database (.ssd file).
-JobName <string> Specify the job using Job Name.
-Source <string> Define a new source path.
IMPORTANT: If you add /source to the command, it overrides
the source(s) specified in the copy job identified by the job ID or
name.
-Target <string> Define a new target path.
IMPORTANT: If you add /target to the command, it overrides
the target(s) specified in the copy job identified by the job ID or
name.
-CopySubFolders <bool> Specify true or false.
Parameter Description
-Database <string> Specify the jobs database (.ssd file).
-JobName <string> Specify the job using Job Name.
Example
This example removes the TestJob copy job.
Remove-SecureCopyJob -Database "C:\Program Files\Quest\Secure Copy
7\SecureCopy.ssd" -JobName TestJob
Syntax
Start-FileSystemStatistics [[-Roots] <string>] [[-Server] <string>] [-Out] <string>
[[-Threads] <int>] [[-NoBackup] <bool>] [[-Security] <bool>] [[-NoStatus] <bool>]
[<CommonParameters>]
Parameter Description
-roots <string> List of paths to scan. Separate each path with a semi-colon.
NOTE: This parameter must be specified. If there are any spaces in the
paths, the entire list should be in quotes.
-server <string> Name of the server to process.
When specified, all normal <non administrator, non IPC> shares are
enumerated and used as roots.
Examples
This example retrieves information for all shares.
Start-FileSystemStatistics -server SERVERNAME -out ServerName-outputfile.csv
This example retrieves information for a set of shares.
Start-FileSystemStatistics -roots “\\SERVERNAME\Share1;\\SERVERNAME\Share Number 2”
-out ServerName-outputfile.csv
Quest provides software solutions for the rapidly-changing world of enterprise IT. We help simplify the challenges
caused by data explosion, cloud expansion, hybrid datacenters, security threats, and regulatory requirements.
We are a global provider to 130,000 companies across 100 countries, including 95% of the Fortune 500 and 90%
of the Global 1000. Since 1987, we have built a portfolio of solutions that now includes database management,
data protection, identity and access management, Microsoft platform management, and unified endpoint
management. With Quest, organizations spend less time on IT administration and more time on business
innovation. For more information, visit www.quest.com.