The Migration Manager console log file, EMWMigration.log, located by default in %Program Files%\Quest Software\Migration Manager\Exchange Data folder, is recreated each time the Project Manager starts. This means that some information that may be valuable for troubleshooting could be overwritten and lost. How can this behavior be changed?
This behavior is by design. Please refer to the resolution section for the workaround.
To set up automatic archiving of the Migration Manager console log, complete the following steps:
1. On the console computer add the following registry key value:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Aelita\Migration Manager\CurrentVersion\Exchange Data
Value: LogWithProcessID = 1
A new log will be still created each time Project Manager starts, but the process ID will be appended to its name. That is, the log file name will be in the following format: EMWMigration<processID>.log.
2. Copy the ArchiveLogs.cmd and ArchiveLogs.js files to any folder on the console computer. (If you copy it to the same folder where the log resides /path parameter is not required).
3. If needed, modify the parameters specified in the ArchiveLogs.cmd file. By default, all files in the same folder where script is located that have a *.LOG extension and that are bigger than 1024 KB and older than one day are archived.
4. Schedule ArchiveLogs.cmd to run daily using the built-in Windows Scheduler.
The archived log files will be compressed and put into the %Program Files%\Quest Software\Migration Manager\Exchange Data\Logs folder each time ArchiveLogs.cmd runs. Each compressed file (*.GZ) will contain the creation date and time in its name.