About the information in the Computer Status reports and logs

The Computer Status log contains information about the real-time operational status of the
computers in the network. Information available includes the computer name and IP address,
last check-in time, definitions date, infected status, Auto-Protect status, server, group,
domain, and user name. Filters for Computer Status reports have both standard
configuration options and compliance-specific options.

The table below describes some typical uses for the kind of information that you can get from
Computer Status reports and logs.

Report or log Typical uses

Virus Definitions Use this report to make sure that all the groups, domains, or servers in your network
Distribution use up-to-date virus definitions files versions.
Computers Not Use this report to find the computers that have not checked in with a server and
Checked into Server therefore might be lost or missing.
Symantec Endpoint Use this report to check the versions of product software, virus definitions, IPS
Protection Product signatures, and proactive protection content in use in your network. With this
Versions information you can pinpoint the computers that need an update.
Intrusion Prevention Use this report to make sure that all the groups your network use up-to-date intrusion
Signature Distribution prevention signatures. You can also see which domains or servers are out-of-date.
Client Inventory Use this report to see the number and percentage of computers that fall into certain
hardware and software categories. Available information includes the computers'
operating system, total memory, free memory, total disk space, free disk space, and
processor type. For example, from the Client Inventory report, you might see that 22%
of your computers have less than 1 GB of free disk space.
Compliance Status Use this report to see which groups or subnets have the largest percentage of
Distribution computers out of compliance. You may want to investigate if certain groups seem to
have a lot more compliance problems than others.
Client Online Status Use this report to see which groups or subnets have the largest percentage of clients
online. You may want to investigate why some groups or subnets currently experience
more problems than others.
Clients With Latest Use this report to see which groups or subnets have the largest percentage of
Policy computers that don't have the latest policy on them.
Client Count by Group Use this report to see the total number of clients and users, by group.
Security Status Use this report to quickly see the total number of computers that have the
Summary following problems:
 Auto-Protect is disabled
 The antivirus engine is turned off
 Tamper Protection is turned off
 The computer needs to be restarted
 The computer failed a host integrity check
 Network Threat Protection is turned off
These computers may continue to be at risk unless you intervene.
Protection Content Use this report to check the versions of Proactive Protection content in use in your
Versions network, to pinpoint any computers that need an update.
Client Migration Use this report to see the migration status of clients by domain, group, and server. You
can quickly identify clients where migration has failed or has not yet started.
Clients Online/ Offline Use this report to pinpoint the clients that don't connect to the network frequently
Over Time enough. This report is available only as a scheduled report.
(Snapshots)
Clients With Latest Use this report to pinpoint the clients that don't get policy updates frequently enough.
Policy over Time This report is available only as a scheduled report.
(Snapshots)
Client Software Rollout Use this report to pinpoint the clients that don't have the latest software version
(Snapshots) deployed. This report is available only as a scheduled report.
Non-compliant Clients Use this report to pinpoint the clients that frequently fail host integrity checks. This
Over Time report is available only as a scheduled report.
(Snapshots)
Virus Definitions Use this report to check to see the definitions versions that clients have. This report is
Rollout (Snapshots) available only as a scheduled report.
Computer Status log Check the Computer Status log if you need more details about any of the areas that the
reports cover.

<Insert Project Name>

Status Report
Reporting Period: day.month.year to day.month.year

1. ACHIEVEMENTS THIS PERIOD

Instructions:

This section lists work completed this period and other notable accomplishments.

2. DECISIONS THIS PERIOD

Instructions:

This section lists all significant decisions made this reporting period. These decisions can be made by
the Project Sponsor, Steering Committee, or Project Manager.

3. PRIORITIES NEXT PERIOD

Instructions:

This section lists high priority items for the next reporting period. This list may include:

Deliverables that will be finished next period

Activities that will start or finish next period

Required decisions, including approvals, next period

4. PROGRESS OF DELIVERABLES
Instructions:

The table in this section provides information on the progress of deliverables:

When producing the first Status Report:

List all project deliverables in the left hand column. Take deliverable names from the Deliverables
section of the Project Plan if one was written.

Provide the planned completion date for the deliverable in the next column. These dates should be
taken from the Project Schedule if one was written.

When updating the Status Report each period:

Enter the actual completion date for completed deliverables.

Update status for all deliverables – started, not started, complete.

Highlight deliverables that are late (suggest a different color font).

Tips:

It is not accepted practice to change the “Planned Finish Date” for a late deliverable. The purpose of
listing planned finish dates and actual finish dates separately is to detect variances, and planned finish
dates should only change if the schedule has changed with permission of the Project Sponsor.

The “Actual Finish Date” column should be empty until the deliverable is complete.

Towards the end of the project, it may be useful to delete rows for deliverables that have been
completed for several weeks to make the report shorter and avoid repeatedly reporting that the
deliverable is complete.

It is often useful to list deliverable completion and deliverable approval as separate deliverables.

Status Report – Preparation Guidelines Page 1

 If earned value is being calculated for the project, updates to the “started, not started, complete” are
important inputs for an updated earned value calculations.

Example table with instructions:

Actual
Planned Status
Finish
Deliverables Finish Date Not Started / Started / Notes
Date
mm.dd.yy Complete
mm.dd.yy

<Enter due <Enter <Here note variance or

<Indicate if work on
<Enter name of deliverable date (find in date other items of interest
deliverable has started
(find in Project Plan)> Project actually related to this
and if it is complete>
Schedule)> finished> deliverable>

Examples

Website conceptual design

06.02.06 06.01.06 complete
document written

Website conceptual design

06.08.06 06.06.06 complete
document approved

Website detailed design

06.15.06 not started Late
document written

Website detailed design

06.22.06 not started Late
document approved

Website prototypes built May be late as design is

07.20.06 not started
late

5. PROJECT ISSUES
Instructions:
This section lists all active project issues and provides recommended actions. Issues are things that are
happening right now that need to be resolved in order for the project to proceed successfully. Note that not
all project issues are listed here: issues that are resolved are stored in a separate Issue Log.

When producing the first Status Report:

List all issues in the Issues section of the Project Plan if one was written if these are still active.
Add any new issues identified since the Project Plan was written.

When updating the Status Report:

Remove any resolved issues and add newly identified ones along with updates to recommended
actions

Tips:

The number that appears in the left-hand column should be a unique identifier for the issue and
should be identical to the issue number listed in the issue log. It will be common, therefore, for the
numbers in the left-hand column not to be sequential.

o. Issues Recommended Action

Status Report – Preparation Guidelines Page 2

6. PROJECT RISKS
This section lists all active project risks and provides recommended actions. Risks are things that may
or may not happen in the future that may have an impact on the success of the project. Note that not all
project risks are listed here: risks that are closed are stored in a Risk Log.

When producing the first Status Report:

List all risks in the Risk section of the Project Plan if one was written if these are still
active. Add any new risks identified since the Project Plan was written.

Instructions:

Remove any risks that have passed and add newly identified ones along with updates to
recommended actions.

Tips:

The number that appears in the left-hand column should be a unique identifier for the risk and
should be identical to the risk number listed in the Risk Log. It will be common, therefore, for
the numbers in the left-hand column not to be sequential.

A good risk event statement includes what might happen and its effect on a project. For
example, “weather” is not a risk event statement. “Bad weath er may delay project
completion” is a risk event statement.

No. Risk Event Statement Risk Mitigation Actions

3
7. CHANGE REQUESTS
This section lists all new and unresolved change requests. Change requests are requests to change an
aspect of the project – usually scope, deliverables, the schedule, or the budget.

Tips:

The number that appears in the left-hand column should be a unique identifier for the change
request and should be identical to the change number listed in the Change Log. It will be
common, therefore, for the numbers in the left-hand column not to be sequential.

No. Requestor and Request Impact Resolution

8. BUDGET
This section provides information on whether or not the project is on budget.