Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Secure Copy 7.6.3 - User Guide

Using Secure Copy Setting copy options Running copy jobs Using the command line Managing licenses Running Update Utilities Troubleshooting PowerShell cmdlets

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.
3
To include subdirectories in the path, select Include Subfolders.
4
Specify the source path and target path for the shortcut update or use a .INI file.
To specify a path
a.
Type the path or browse to locate the path of the old target of the shortcut.
b.
Type the path or browse to locate the path of the new target of the shortcut.
To use a .INI file
a.
Select Use Ini File.
b.
Type the path to the .ini file that contains the path update information.
5
To run a test on the update, select Run As a Test.
The test report audit displays the number of shortcuts that will be updated by Shortcut Updater. No shortcuts are actually updated when you run the test report. Specify the number of shortcut files to include in the test. If you leave the box blank, the default is 500 files.
6
Click Run.
Upon completion, the Shortcut Updater creates a log file and a report file in the Tools subfolder (C:\Program Files\Quest\Secure Copy 7\Logs\Tools\Shortcut Updater).
Format for the file name: SU_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 Run as a Test box, and click Run.

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 update links
1
Click Update Utilities In the Navigation Pane, and then click Link Updater.
2
In the Scan Path box, type a path or browse to locate the Microsoft Word, Excel, or PowerPoint files that contain links you want to update.
3
You can specify the source path and target path for the shortcut update or use an .INI file.
NOTE: The link updater verifies that the target folder exists before it updates the links.
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.
Table 25. Update options
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.

Creating a link map .ini file

Information in an .ini file is grouped by section headers, which are names that are enclosed in brackets such as [SectionName]. The section header defines what the section represents. The data to be updated is specified after the [SectionName]. Use the section header [LinkMap] in an .ini file used with the Link Updater.

The .ini file must be saved using ANSI encoding. The file can be edited with a text editor or a word processor that imports ASCII files.

The target path must include the folder in which the files now reside. For example, the .ini file content for remapping the location information for the OLE links in files might look as follows:

[LinkMap]
C:\Corporate\HR Docs = G:\Corporate\HR Docs\Excel
D:\Documents = G:\Documents
 
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

Running Link Updater from the command line

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

You should only run the Link Updater during a time when users do not need to access files on the server or when it is possible for you to lock out all users and prevent them from accessing files on the server. You must run the LU.exe file from the Secure Copy server because of the licensing check the file performs.
IMPORTANT: Do not run Microsoft Office applications on the computer on which the Link Updater is running.

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]
Table 26. Required Parameters
Required Parameter
Meaning

FullFilePath

Location of the Microsoft Word, Excel, or PowerPoint files that contain links you want to update. Enter as the full path name to the directory that contains the files followed by \*.* (which is the default).

•
To update only Microsoft Word files, specify *.doc in the path name.
•
To update only Microsoft Excel files, specify *.xls in the path name.
•
To update only Microsoft PowerPoint files, specify *.ppt in the path name.
NOTE: You can specify the FullFilePath using the UNC convention.

SourcePath

Location of the linked files on the source computer. Path name can be a local path or UNC path.

TargetPath

Location of the linked files on the target computer. Path name can be a local path or UNC path.

NOTE: The link updater verifies that the target folder exists before it updates the links.
Table 27. Optional Parameters
Optional Parameter
Meaning
/r

Search recursively through the folders and subfolders of the paths you have specified.

/t= n

Create a test report that lists the number of files that will be updated. If you specify this option, only the audit report is created. The files are not updated.

If you do not specify a number (=n), then the report includes an unlimited number of files to the maximum number allowed.

NOTE: The maximum number that can be specified using the \t argument is 2147483647.
/c

Use with the /t (test report) option to create a CSV file that lists the files and the links to be updated. This option allows you to review potential changes in a file without updating the links.

If you use the /c option without using /t, you get a CSV file that contains all the file links that were updated.

The CSV file is created in the same directory in which the link updater utility is running. The file uses the following naming convention: LINK_UPDATER_LINKS_FOUND_ddmmyy_hh_mm.csv

/z

Delete previously generated LINK_UPDATER files, including the .log, .csv, and .htm files.

 
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.

Example for specifying path information

You want to update the links for migrated Microsoft Word files located here: C:\Folder1.

The Word files have links to PowerPoint files that were previously located here: D:\Corporate\DivisionB. The PowerPoint files are now located here: D:\Corporate\HR\PP.

LU C:\Folder1\*.doc D:\Corporate\DivisionB D:\Corporate\HR\PP
Identifying all source paths

You can use the test report option to show all source paths. To do this, you enter \\ instead of specifying the source path.

The syntax to produce a test report that shows all source paths is as follows:

LU FullFilePath \\ TargetPath /t

Since you are running the Link Updater in test mode and no links are updated, you can enter a dummy path as the target path. For example, you could enter \\Test as the target path.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation