Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Secure Copy 7.5.1 - User Guide

Table of Contents

Using Secure Copy

About Secure Copy Starting Secure Copy Examining the main window Setting default performance settings Setting SMTP settings Setting general preferences Setting logging settings Creating a basic job

Changing basic copy job settings Selecting actions

Setting copy options

About copy options Setting copy locations Setting synchronization

Synchronizing single source path to single target path

Single source example 1 Single source example 2 Single source example 3 Single source example 4

Synchronizing multiple source paths to single target path

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

Applying filters

Filtering files Filtering folders Copying folder structures without files

Setting performance options

Verifying file copy Enabling logging Maximizing copy performance Copying locked files Closing the Jobs Progress window

Migrating local groups and users

Using map files to migrate local groups and users

Migrating file shares Setting other file options

Using map files to copy files and folders Copying encrypted files Copying off-line/stub files Copying recently modified files Using compression Copying ACL information Running pre and post migration tasks

Sending email notifications

Running copy jobs

Starting a copy job Restarting a copy job Importing a job Restoring job settings Scheduling jobs Managing scheduled jobs Viewing job status Viewing logs and reports Viewing copy job statistics Viewing log file contents

Filtering log file contents

Exporting logs Deleting logs Running reports Analyzing file systems statistics

Using the command line

Using SecureCopyCmd.exe Using Analyzer from the command line

Managing licenses

Viewing licenses Viewing licensed servers Applying a new license file Checking for product updates

Running Update Utilities

Home Path Updater Profile Path Updater Shortcut Updater Link Updater

Creating a link map .ini file Running Link Updater from the command line Using a .ini file from the command line

Link Updater for Access Registry Updater

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

Troubleshooting

Logging events for Technical Support Removing Secure Copy

PowerShell cmdlets

What are cmdlets? Using the PowerShell cmdlets Managing copy jobs

Starting a copy job Removing a copy job

Running the File System Statistics Analyzer

Running the Registry Updater

1

Click Update Utilities, and click Registry Updater.

2

Type the path or browse to locate the .ini file that you created.

3

Type the name of the computer where the Registry Updater will update the registry.

4

You can run the Registry Updater through the Registry Tool dialog box or you can run it from the Command Line.

•

Click to Run the specified .ini file with the specified arguments.

•

Click Launch cmd.exe to run the Registry Updater from the command line.

Running Registry Updater from the command line

The Registry Updater (ToolsRegTool.exe) is located in: C:\Program Files\Quest\Secure Copy 7\Tools.

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)

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

Using the Registry Updater in a logon script

The Registry Updater is typically distributed through logon scripts that run when users first log on to their computers after the migration. When you create the logon script, be aware of the following two points:

•

The logon script should only run once.

•

After the script has run, the user must log off and then log on for the changes to take effect.

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.

•

Logging events for Technical Support

•

Removing Secure Copy

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center