Secure Copy 7.6 - User Guide

IMPORTANT: Microsoft Office is required for Link Updater for Access. Do not run Microsoft Office applications on the computer on which the Link Updater for Access is running. If you have Excel open when you run Link Updater for Access, Excel will be forcibly closed with no prompting to save your files.

IMPORTANT: You must create a link map file to use this utility. See Creating a link map .ini file.

To update external table links

Click Update Utilities, and click Link Updater for Access.

Open the Settings tab.

Type the path or browse to locate the Microsoft Access files that contain links you want to update.

Type the path or browse to locate the link map file that maps the old locations of linked files to the new locations.

Set options for the update.

Test Mode (no updates)
By default, the Link Update runs in test mode, which allows you to scan the path and see the updates without making changes to the file.

Enable Debug Logging
Select to see detailed level logging.

Open the Microsoft Access tab.

Set options for Microsoft Access.

Enable Microsoft Access Database Updates
Select to check Microsoft Access files for external table links and hyperlinks.

Update external table links
Select to check and update external table links. The current link types supported are links to other tables in external Microsoft Access files, and links to external Microsoft Excel spreadsheets.

Update Hyperlink fields in table records
Select to scan table records for hyperlink fields. This process may take some time if the table has many records.

Back up Access database file before updating
Select to create a backup copy of the .mdb or .accdb file made to the same location as the existing file. The file will have an extension of .BAK. The backup is made before scanning the Microsoft Access database file for changes. If no changes are made, the backup file is removed.

Open the Scan tab.

Click Scan. The Statistics area updates as the scan progresses.

NOTE: If you selected Test mode on the Settings tab, no files are updated.

To display the log file containing a summary of the actions performed, click View Log.

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

Creating the drive mapping .ini file

The .ini file is used to change the drive mappings in user local and roaming profiles from an old server mapping to a new server mapping.

A template .ini file is available to use to create your own .ini file. The template file is named drivemap.ini and is located in C:\Program Files\Quest\Secure Copy 7\Tools.

Format

;[Values]

;HKEY_CURRENT_USER\Network = ServerMap,Recurse

;

;[ServerMap]

;SourceServer\OldShare = TargetServer\NewShare

;SourceServer = TargetServer

;OldValue = NewValue

The [Values] section identifies the registry keys to search and replace. Drive mappings for a user are stored in the HKEY_CURRENT_USER\Network registry key. You can add the optional Recurse to include subkeys and associated values.

NOTE: If recursion is not set, the Registry Updater searches and replaces only values that are directly under the registry key.

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:

;Example

;[Values]

;HKEY_CURRENT_USER\Network = ServerMap,Recurse

;[ServerMap]

;FS_NT\Sales = FS_2K\UKSales

;FS_NT\Accts = FS_2K\Accounts

;FS_NT = FS_2K