Get Live Help
When discussing details about an issue, a common area of interest is the point of failure. This is the exact point in time that the issue occurs, where it occurs, and under what conditions. The idea of determining the point of failure is to ultimately find a means by which to reproduce the issue being observed. Once any issue can be reproduced on demand, it is infinitely easier to work towards a solution. For troubleshooting, the identification of a point of failure means that we are able to reproduce the issue, collect applicable logs, sample items, and make assessments on if the issue is environmental or not. In most instances, we can collect samples that are provided to our Support team for analysis. This frequently expedites the troubleshooting of an issue and results in a drastically shortened time to resolution.
PST Flight Deck has very robust logging features that enable administrators to effectively troubleshoot problems. There are two categories of logs agent logs and server logs. Agent logs are generated by the Migration Agent and are stored on a users computer. Agent logging is enabled by default. Server logs are generated by the various PST Flight Deck modules and the Core. Server logging is disabled by default. To learn how to enable logging in PST Flight Deck please visit use this on the topic.
The Windows Migration Agent has two components, the discovery agent and the migration agent, and both components generate logs. The logs are stored in %temp%\Quadrotech\. Both logs can be retrieved from a workstation using the Request Client Logs feature in the Admin Console. If enabled, a user can elect to send logs to the server using the Send Log feature of the Migration Agent.
The Discovery Agent log is written to a file named FileScanner_hostname.log. The log will not be created if there are no warning levels. There is rarely a need to change the logging level but you may be directed by Quadrotech support to change it for troubleshooting.