How is the Altiris Profiler (new to NS 6.0 SP3) setup to run, and what files are needed when the profiler has been run so that they can be analyzed by the support group?
There are 2 ways to run the profiler, by using the Wizard or simply running it directly.
1. Using the Wizard.
The profiler can be run to collect or not to collect the SQL and/or Code traces. It is setup through the wizard that will normally show up when the profiler is run. It can be turned off so that it doesn't run automatically but can be run again from the main menu of the profiler.
The following steps are used to get a profiler trace. Step 3 shows the images through the setup wizard on how the options should be chosen.
The profile should be done. The next thing needed is to collect the profiler files for support. They will normally be found in the same directory from which the profiler.exe was run. The following are the files that are generated during the course of the profile:
These are the two .buffer files which support directly needs. There are also two reports that the profiler can generate. They are .htm files and give some general information gathered during the profile and regarding some performance of the server on which the profile was run. Here are the names of these two files:
"Executive Summary Report-<today's date>.htm"
"Performance Report-<today's date>.htm"
They should be collected and sent in to the support group with the two .buffer files.
2. Running the Profiler directly
Work through the following steps to capture the Altiris Profiler Trace Data:
The process includes;
The files that are generated by the profiler can become quite large. Be sure to follow the steps above to disable the profiler when finished to avoid a situation where you run out of available disk resources.
After collecting the requested files and sending them in to support, you may safely delete these files to recover the used disk space.