During resource processing there are sometimes minor issues with the profile not being properly re-permissioned. The regular logging level may not have enough information to resolve the issue, is there a possibility to increase the logging level for QMM Consolidated Log so it shows more information?
After 8.3 it is no longer possible to enable extended logging via GUI interface and can only be accomplished by directly modifying INI file or via the registry as per the instructions below. Change Request 67332 is currently considered to place this back into GUI for the future product releases.
I. VMOVER LOG:
Extended logging can be enabled directly on DMW/QMM console in Agent Manager (RUM): Tools - Options - Logging and select "Extended Logging", it will set the "LogMask=31" in Vmover.ini and this setting should suffice.
QMM 8.6 and above
1. Create new String value ProcessingLogLevel=Full under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Aelita\Migration Tools\CurrentVersion\Resource Updating Manager
2. ProcessingLogLevel can also be set to "None" and "Default"
WARNING: Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 â€Description of the Microsoft Windows registryyâ€: http://support.microsoft.com/default.aspx?kbid=256986.
QMM all versions:
There is also a switch for Vmover.ini to enable extended logging, it can be done by changing the "LogMask" parameter in the Vmover.ini from 15 to -1.
Important: Every time you click on start QMM creates a new Vmover.ini and this Vmover.ini is copied to each workstation so if you modify the Vmover.ini manually then it will be overwritten again. It will only work if you use another approach, e.g. change the LogMask parameter in the Vmover.ini from 15 to -1. and then in Agent Manager (RUM) select "Process as specified in the exported INI settings file".
Note: Enabling extended logging is sometimes required for development when troubleshooting, it creates big log files and slows down the process, especially on file servers because it is logging each step. Enabling extended logging in Agent Manager (RUM) is sufficient in most scenarios and only when additional extensive troubleshooting is needed the LogMask parameter in the Vmover.ini should be changed from 15 to -1 for individual workstations, in this case it is a good idea to execute the Vmover.exe locally from command line. Please also ensure that in Agent Manager (RUM) the setting "Limit logged errors" is not selected, by default it is set to 10 errors and this might reduce the number of logged errors.
II. RUM CONTROLLER LOG:
(only applicable to QMM 8.4 and up)
Extended logging can be enabled via Registry modification for RUM Controller log:
1. Create new key Config under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QsRUMController so it will be HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QsRUMController\Config
2. Create String value LogLevel=Full
The value can also be set to "None" and "Default"
WARNING: Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 â€Description of the Microsoft Windows registryyâ€: http://support.microsoft.com/default.aspx?kbid=256986.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center