Troubleshooting ADMT Log File Issues
Updated: June 21, 2010
Applies To: Windows Server 2008, Windows Server 2008 R2
Applies to: Active Directory Migration Tool 3.1 (ADMT 3.1) and ADMT 3.2
This section describes a known issue related to the Active Directory Migration Tool (ADMT) log files.
I cannot find the ADMT log files.
Solution: All the ADMT log files are stored in the ADMT database. However, the last 20 migration logs are also stored in the Logs folder under the ADMT folder on the computer on which ADMT is installed. You can access all ADMT logs in the database by using the admt task command at a command line.
I cannot read the event log entries for the ADMT agent.
Cause: You are not on a computer on which ADMT has been installed.
Solution: The agent may write event log entries to the computer on which it runs. However, the agent software is removed when the agent's task is finished. You can view the event log entries on the computer to which the agent was dispatched by running Event Viewer from the computer on which ADMT is installed.
I need more information from the ADMT logs.
Cause: Incorrect logging level setting.
By default, ADMT writes summary information to its log files. You can increase the level of detail by changing the registry entry that controls the logging level.
Solution: On the computer on which ADMT is installed, set the value of the HKEY_LOCAL_MACHINE\Software\Microsoft\ADMT\TranslationLogLevel registry key to 7.
You can use verbose logging mode for problem diagnosis and troubleshooting. Verbose logging mode can create very large log files, particularly in cases where large numbers of files, or other objects whose access control lists (ACLs) must be updated, exist on the target computer. Because the agent logs are written to the folder that is specified by the %TEMP% environment variable, the volume to which that environment variable points should have ample disk space. When you log in with verbose mode, you may have to change the value of the %TEMP% environment variable before you dispatch an agent.
Generated reports do not show up in the ADMT.
Cause: When ADMT generates reports, it does not update the console automatically.
Solution: To view the reports, close and then reopen ADMT.
Running multiple instances of ADMT in multiple languages
When you run multiple instances of ADMT where different instances are using different languages, the log files are generated in the language that the instance is being run in. This does not affect the functionality of ADMT in any way. However, we recommend that you use a unified language when you run multiple instances of ADMT.