In some environments directory and other resource processing tasks may take a very long time to complete. Under certain circumstances the processing may take more then 24 hours to complete and it becomes very hard to monitor the status of the job to tell if it is still running successfully or there is a problem. The Information Tab for the task may not update in a timely manner. What are the recommendations for monitoring such processing jobs?
1. Every task is represented by its process that can be tracked in Tasks Manager on QMM console:
ADPW.exe - ADPW (Active Directory Processing Wizard) (adp.ini)
E2kPW.exe - Exchange 2000/2003 Processing Wizard (exchange2k.ini)
E55PW.exe - Exchange 5.5 Processing Wizard (exchange55.ini)
SMSWizard.exe - SMS Processing Wizard (smswizard.ini)
SQLWizard.exe - SQL Processing Wizard (sqlwizard.ini)
These processes can be monitored to ensure the job is still running and has not been interrupted.
2. Each task can be executed in standalone mode when it is launched independently from the project manager GUI and has its own window opened with the progress bar. This can provide a better indication of successfully running job. In order to run it in standalone mode please double click on the corresponding .exe file directly under %Program Files%\Common Files\Aelita Shared\Migration Tools. Task will not run without ini file located at the same folder. It could be already generated if the task was previously configured from the GUI or exported from QMM Project Manager under Tools - Export to - INI File ...
3. Standalone task package can be created and executed directly on the Domain Controller, Exchange server, SQL or SMS servers in the domain where particular resources need to be updated. This can decrease total time required for the resource updating job since it is executed locally and there is no dependency on the network connectivity. Please refer to this article for the step by step instructions:
A) SQL Processing Task connected to ADAM (KB 15866):
B) SQL Processing Task based on SQLWizard.ini file generated at the time of task creation (KB 15262):
NOTE:E2kpw log is created when processing wizard was started in standalone mode (directly clicking on EXE). To view log in console mode select History -> right click on specified processing job -> View log