Format of the RegWalker Log File
Format of the RegWalker Log File
The log file contains tab-delimited text records that represent information on work results and errors description. The number and the names of log files depend on the RegWalker start mode.
In command prompt start mode, RegWalker logs its activities into one log file, regwalker.log.
In logon script start mode, a separate log file is created for each processed user. The name of each log consists of the domain name, computer name, and user name, delimited by semicolons.
Each record in the log contains the following tab-delimited data:
- Date
- Time
- Computer name
- Record type (Information/Error)
- Path to the registry key that caused the error
- Error code
- Error description
RegWalker Usage Examples
RegWalker Usage Examples
The following are several RegWalker usage examples.
Example 1
RegWalker can be used to automate the post-migration update of Microsoft Client for Netware settings on the user desktop computers.
The Microsoft Client for Netware settings are stored in the following registry key under the user SID:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NWCWorkstation\Parameters\Option\<SID>
When users are migrated, their SIDs change; therefore the users do not have access to these settings. Regwalker creates the appropriate Novell NDS Tree and Context registry settings on selected users’ computers for the migrated users enumerated in the migrated users map file generated by DMW (default name vmover.ini).
In this example RegWalker is started from the command prompt. To use RegWalker:
- In a text editor such as Notepad, create a parameter file for RegWalker. In the file specify the paths to the migrated user map file (the default name is vmover.ini) and the RegWalker task file:
[RegWalker]
TaskFile="Novell Settings Registry Update.xml"
OutputPath=Reports
MapFile=vmover.ini
Save the file under the name regwalker.ini.
- In a text editor, create a task file. You can copy the provided example directly to the file and save it as Novell Settings Registry Update.xml.
Task file example:
<!--
The following Novell Settings Registry file tells RegWalker to the Microsoft Client for Netware settings on the user computers in the following registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\NWCWorkstation\Parameters\Option\<SID>
-->
<os type="winnt">
<basekey name="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\NWCWorkstation\Parameters\Option" subkeys="0" >
<find string="{SrcDomainSid}-{SrcUserRid}" keys="1" wholestring="1" >
<copy src="{FoundKey}" dest="{BaseKey}\{DomainSid}-{UserRid}" />
<output string="{ComputerName}	{UserName}	Novell settings have been moved." />
</find>
</basekey>
</os>
- Run RegWalker.exe from a command prompt, specifying the path to the ini file you created:
RegWalker.exe regwalker.ini
RegWalker will process the registries on the selected computers and copy the necessary settings from the source user profiles to the corresponding target user profiles.
|
|
|
Example 2
In this example RegWalker is started from the command prompt and used to update the print server name in the users’ profiles. Take the following steps:
- In a text editor such as Notepad, create a parameter file for RegWalker. In the file specify the paths to the RegWalker task file and the output path, and define two variables:
[RegWalker]
TaskFile = task2.xml
OutputPath = Results
ComputerListFile = domaincomputers.lst
{OldPrintServer}="\\PrintServer"
{NewPrintServer}="\\PrintServer2"
Save the file under the name regwalker.ini.
- In a text editor, create a task file. You can copy the provided example directly to the file and save it as task2.xml.
Task file example:
<!--
The following task file tells RegWalker to change the name of the print server in the user profile. RegWalker will change Server key value from {OldPrintServer} to {NewPrintServer} in the following registry key
HKEY_USERS\"SID"\Printers\Connections\"*"\
-->
<os type="winnt">
<basekey name="HKEY_USERS\{DomainSID}-{UserRID}\Printers" SubKeys="1" >
<group>
<find string="Connections" keys="1" WholeString="1" />
<find string="Server" values="1" WholeString="1" />
<replace string="{OldPrintServer}" with="{NewPrintServer}" WholeString="1" >
<output string="{Data}	{Time}	{ComputerName}	Chanage printer setting for user {UserName} rename server from server replaced from {OldPrintServer} to {NewPrintServer}" />
</replace>
</group>
</basekey>
</os>
- In a text editor, create a file with a list of computers to process and save the file as domaincomputers.lst. For example:
ALEX;RESEARCH\Alex
EDITOR;RESEARCH\Betty
MARTIN;RESEARCH\Martin
SERVER;RESEARCH\Serge
- Run RegWalker.exe from a command prompt, specifying a path to the ini file you created:
RegWalker.exe regwalker.ini
RegWalker will process registries on the users’ computers and change the old print server name to the new one in the users’ profiles.
GetRsl
Every computer has a Registry Size Limit (RSL) set for it. It is a universal maximum for registry space that prevents an application from filling the paged pool with registry data. The total amount of space that can be consumed by registry data (hives) is restricted by the registry size limit.
When the registry size gets close to the limit, the operating system may prevent applications from modifying the registry. This may prevent Resource Updating Manager and VMover from updating profiles and registries on remote computers.
GetRsl displays the current registry size and the registry size limit for a remote computer. If the registry size is close to the limit, this might be the cause of some problems you experience. In this case, modify the computer’s RSL and retry updating the computer.
Using GetRsl
Using GetRsl
GetRsl uses the following command line syntax:
GetRsl.exe ComputerName
where ComputerName is the name of the remote computer.
The utility produces output in the following format:
ComputerName RegistrySize RSL
The numbers are reported in megabytes, for example:
> GetRsl.exe Setanta
Setanta 24.3 69.3