Registry Updater
Previous
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
Previous
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
Running the Registry Updater
Previous
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
Previous
The Registry Updater (ToolsRegTool.exe) is located in: C:\Program Files\Quest\Secure Copy 7\Tools.
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