Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
7Activity
0 of .
Results for:
No results containing your search query
P. 1
2 Exchange Server 2003 Daily Operations

2 Exchange Server 2003 Daily Operations

Ratings: (0)|Views: 373|Likes:
Published by api-3852474

More info:

Published by: api-3852474 on Oct 19, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

Exchange Server 2003 Daily Operations
Exchange Server 2003 Operations Guide
Exchange Server 2003 Daily Operations
To ensure the availability and reliability of your Microsoft\u00ae Exchange Server 2003 organization, you must
actively monitor the physical platform, the operating system, and all important Exchange Server 2003 services.

Preventive maintenance will help you identify potential errors before any one of these errors cause problems
with the operation of your Exchange organization. Preventive maintenance combined with disaster recovery
planning and regular backups will help minimize problems if they occur. Monitoring your Exchange organization

involves checking for problems with connections, services, server resources, and system resources. You can

also set alerts to notify administrators when problems occur. Microsoft\u00ae Windows Server\u2122 2003 and Exchange
Server 2003 provide you with many monitoring tools and services to ensure that your Exchange Server 2003
organization is running smoothly. The key advantages to daily monitoring are as follows:

\u2022Ensures that the performance requirements of your service level agreements (SLAs) are being met.
\u2022Ensures that specific administrative tasks, such as daily backup operations and checking server health, are
being successfully completed.
\u2022Enables you to detect and address issues, such as bottlenecks in the server performance or need for
additional resources, in your Exchange organization before they affect productivity.

The following daily maintenance tasks let you establish criteria for what is normal for your organization and to
detect any abnormal activity. It is important to implement these daily maintenance tasks so that you can
capture and maintain data about your Exchange organization, such as usage levels, possible performance
bottlenecks, and administrative changes. The following tasks are discussed in detail this topic:

\u2022Performing physical environmental checks
\u2022Performing backups
\u2022Checking disk usage
\u2022Checking the Event Viewer
\u2022Checking connector and server status
\u2022Monitoring server performance
\u2022Checking message paths
\u2022Performing daily database maintenance

http://www.microsoft.com/technet/prodtechnol/exchange/g...Guide/d54a2acb-d932-4ee7-adcb-231a1a44a96e.mspx?pf=true (1 of 26)25/01/2005 10:00:53
Exchange Server 2003 Daily Operations

\u2022Monitoring network performance
\u2022Monitoring Exchange and Windows services
\u2022Monitoring cluster resources
\u2022Enforcing security measures

Performing Physical Environmental Checks

Before you check performance, availability, and functionality of your Exchange organization, you should check the physical environment. For example, the server room temperature might need to be lowered, or a network cable might need to be replaced. You should perform the following physical environmental inspections:

\u2022Physical security measuresPhysical security protection such as locks, doors, and restricted-access rooms
must be secured. Check for any unauthorized and forced entries and signs of equipment damage.
\u2022Temperature and humidityHigh temperature and humidity can cause hardware components to overheat.
Check temperature and humidity to ensure the environmental systems such as heating and air conditioning
can maintain acceptable conditions and function within the hardware manufacturer's specifications.
\u2022Devices and componentsYour Exchange organization relies on a functioning physical network and related
hardware. Check to ensure that routers, switches, hubs, physical cables, and connectors are operational.
Top of page
Monitoring Event View er

You can use Event Viewer to obtain information about service failures, replication errors in the Microsoft Active
Directory\u00ae directory service, and warnings about system resources such as virtual memory and disk space.
Use Event Viewer to view and manage event logs; obtain information about hardware, software, and system

problems that must be resolved; and identify trends that require future action.

Event Viewer maintains logs about application, security, and system events on your computer. Both Exchange
Server and Windows report warnings and error conditions to the event logs. Therefore, make sure that you
review event logs daily. For more information about Event Viewer, see the Windows Server 2003 Help
documentation. You can also use Event Viewer as a troubleshooting tool. For more information about using
Event Viewer as a troubleshooting tool, see Microsoft Knowledge Base article 302542, "How to Diagnose
System Problems with Event Viewer in Windows Server 2000" (http: / / go.microsoft.com/ fwlink/ ?

linkid= 3052&kbid= 302542).
A computer that is running a Windows Server 2003 operating system records events in three types of logs:
\u2022Application logsThe Application log contains events logged by applications or programs. Developers
determine which events to log. For example, a database program might record a file error in the Application
log. Most Exchange Server-related events are in the Application log.
http://www.microsoft.com/technet/prodtechnol/exchange/g...Guide/d54a2acb-d932-4ee7-adcb-231a1a44a96e.mspx?pf=true (2 of 26)25/01/2005 10:00:53
Exchange Server 2003 Daily Operations
\u2022Security logsThe Security log records events such as valid and invalid logon attempts, as well as events
related to resource use such as creating, opening, or deleting files or other objects. For example, if logon
auditing is enabled, attempts to log on to the system are recorded in the Security log.
\u2022System logsThe System log contains events logged by Windows system components. For example, the
failure of a driver or other system component to load during startup is recorded in the System log. The event
types logged by system components are predetermined by the server.
Exchange Server 2003 diagnostic logging records significant events related to authentication, connections, and
user actions. After you enable diagnostic logging, you can view the log entries in Event Viewer.
Note :
Using the maximum logging settings is not recommended unless you are instructed to do this by Microsoft

Product Support Services. Maximum logging drains significant resources and can give many "false positives,"
that is, errors that get logged only at maximum logging but are really expected and are not a cause for
concern. It is also recommended that you do not keep diagnostic logging on permanently. It should be used
only when troubleshooting.

Within each Event Viewer log, Exchange Server records informational, warning, and error events. Monitor these

logs closely to track the types of transactions being conducted on your Exchange servers. You should
periodically archive the logs or use automatic rollover to avoid running out of space. Because log files can
occupy a finite amount of space, increase the log size (for example, to 50 MB) and set it to overwrite, so that

Exchange Server can continue to write new events.
You can also automate event log administration by using tools and technologies such as the Event Comb,
Eventtriggers, and Microsoft Operations Manager (MOM).
\u2022The Event Comb tool lets you gathers specific events from the event logs of several computers to one central
location. It also lets you report on only the event IDs or event sources you specify. For more information
about Event Comb, see the Account Lockout and Management Tools Web site (http: / / go.microsoft.com/
fwlink/ ?linkid= 35607).
\u2022You can also use command-line tools to create and query event logs and associate programs with particular
logged events. Eventtriggers.exe lets you create event triggers that will run programs when specific events
occur. For more information about Eventtriggers, see the Windows Server 2003 documentation.
\u2022You can use Microsoft Operations Manager to monitor the health and use of Exchange servers. Exchange

Server 2003 Management Pack extends Microsoft Operations Manager by providing specialized monitoring for servers that are running Exchange Server 2003. This management pack includes a definition of health for an Exchange 2003 server and will raise an alert message to the administrator if it detects a state that requires intervention. For more information about Exchange 2003 Management Pack, see the Microsoft Operations Manager Web site (http: / / go,microsoft.com/ fwlink/ ?linkid= 16198).

The following section gives you information about the types of events to monitor.
Normal Events
Reviewing event logs daily will help you establish a baseline for typical events for your system. Examine your
event logs for the following application log events (Table 1) on your Exchange servers.
http://www.microsoft.com/technet/prodtechnol/exchange/g...Guide/d54a2acb-d932-4ee7-adcb-231a1a44a96e.mspx?pf=true (3 of 26)25/01/2005 10:00:53

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
ksprakashmca liked this
jontyd liked this
RAJU liked this
Mian liked this
pradeep12001 liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->