A task is a collection of gathering activities. When you create a task, it is listed in the Tasks node of the navigation tree. When you click the Tasks node, the task appears in the Tasks Summary View.
The Tasks Summary View shows all the tasks created for the MessageStats Scheduler Server. The Tasks Summary view displays the properties of a task, including the task name, credentials, schedule, next occurrence, description, and progress.
The Task Activity view displays detailed properties of the activities that comprise an individual task. These properties include activity descriptions, source, status, progress, runtime gathering dependencies, start and finish time, activity duration, and execution server.
To reduce the impact on resources, built-in gathering rules prevent a task from gathering information more than once within a single (UTC) day. If a task has already successfully completed and you rerun it in the same day, it does not regather the information. Changes do not appear in reports until the task runs the following day.
However, if you have made changes and want to have them immediately reflected in reports that day, you can use the Run Now with Override option to force a task to regather information. For more information, see .
Expand the MessageStats node and select an Exchange organization or an Exchange server.
Right-click and select Create Task.
MessageStats retrieves the server roles for a server from Active Directory, assigns a matching built-in server role value in MessageStats, and identifies the role as “discovered” in the server properties.
Using the server role, MessageStats can determine which server-level gathering tasks can run against a specific Exchange server. For example, if a server does not have the Mailbox role, MessageStats does not allow a Mailbox gathering task to run against the server.
You can include a server in a gathering task even if the task cannot be run against that server due to its server role. When the gathering task is run, it gathers only from servers with the appropriate roles and skips any servers with a role that does not allow the gathering to be run.
You create tasks to collect data from a messaging environment such as Exchange or Lync. The initial gathering task provides immediate information about your Exchange or Lync environment. In a large enterprise, the initial task might be limited to a single group or a local server.
Most organizations add more tasks to collect information from the rest of the Exchange organization and extend gatherings to include additional information. To optimize collection performance, you can create multiple tasks to collect different information on different schedules.
The first task that you create is the Default Gathering task. This is a composite task that includes several gathering tasks and provides the base Exchange information needed to populate the core MessageStats Reports.
Most organizations run the Default Gathering task on a daily schedule to ensure that the MessageStats database is kept up-to-date with the widest range of available data. You can create Default Gathering tasks for Exchange organizations or individual servers.