Issues do happen! When they do it is important to be able to identify that a problem did occur, the nature of the problem, and what actions need to be taken to remediate the problem. While investigating, it is encouraged to note the steps of your investigation through the PST Flight Deck comment system. This will enable you to easily see when an issue with a file is recurring and the approach being taken will need to be reviewed.
There are many difficulties that can happen in PST migration projects. Being able to identify when a problem is happening at the client vs. the server or which module a failure took place in can expedite the ability to identify the problem and promptly resolve it.
Monitoring the migration is a common way issues are identified. When migration priorities are set for a group of users, a certain expectation of their progress accompanies their enablement. As users or files begin to lag behind the remaining users or files, an Operator will look into why. Frequently this is where issues, the point of their failure, and steps for remediation are identified. Quickly reviewing the appropriate grid can tell you if a user is not logging on, if the upload has completed, if a specific process has failed for a file, or if the user has fully completed their migration. Without monitoring your system, some issues may just not be found.
Most issues log entries in a console under Manage > Events. For most migrations, it is suggested to use this window as a sort of running tally of outstanding areas to investigate in a migration. Most events imply an issue which requires some actionable correction. Acknowledging events whose investigation has completed or have been resolved permits an Operator to have an easy view into what is wrong and what still needs resolution or investigation. Many issues identified by monitoring and review of exceptions can more easily be identified through the Events sub-menu.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
