Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Microsoft Exchange 2000
Summary of Contents for Microsoft Exchange 2000
- Page 1 Exchange 2000 Operations Guide Version 1.0...
- Page 2 Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
-
Page 3: Table Of Contents
Microsoft Operations Framework (MOF) ........ - Page 4 System Monitor ..........54 Exchange 2000 Objects and Counters to Monitor ......55 Windows 2000 Objects and Counters to Monitor .
- Page 5 Contents Chapter 5 Protection Introduction ............71 Chapter Start Point .
- Page 7 Paul Slater – ContentMaster Kent Sarff – Microsoft Consulting Services Sasha Frljanic – Microsoft Consulting Services Reviewers Jon LeCroy – Microsoft ITG Thomas Applegate – Microsoft ITG Erik Ashby – Microsoft Exchange 2000 Product Group Chase Carpenter – Microsoft Consulting Services...
-
Page 9: Introduction
Introduction Introduction Welcome to the Microsoft® Exchange 2000 Server Operations Guide. This guide is designed to give you the best information available on managing operations within an Exchange 2000 environment. To manage Exchange in a day-to-day environment, an operations team needs to perform a wide variety of procedures, including server monitoring, backup, verification of scheduled events, protection against attack, and user support. - Page 10 Review Figure 1.1 MOF Process Model multiple data centers. In this case, you will be using MOF in the context of Exchange 2000 operations. The process model is supported by 20 service management functions (SMFs) and an integrated team model and risk model. Each quadrant is supported with a corresponding ding operations management review (also known as review milestone), during which the effectiveness of that quadrant’s SMFs are assessed.
-
Page 11: How To Use This Guide
The wide variety of tasks that constitute Exchange 2000 operations can be divided into three broadly overlap- ping groups. Figure 1.2 on the next page shows these groups and how the operations fit... - Page 12 Microsoft Exchange 2000 Operations Guide — Version 1.0 Efficiency Continuity Storage Management are Upgra es Performance Performance Tuning Monitoring Exchange System Recovery Testing Policies Availability Monitoring Capacity Management Availablity Management isaster Recovery Support Anti irus Event Monitoring Change Management roup Policies...
-
Page 13: Chapter Outlines
Configuration management (including use of Exchange system policies) Chapter 4 – Enterprise Monitoring To track any problems and to ensure that your Exchange 2000 Server is running efficiently, you need to monitor it effectively. Monitoring is not something that should occur only when there are problems, but should be a continuous part of your maintenance program. -
Page 14: Planning And Deployment
Problem management Planning and Deployment To make the most out of your Exchange 2000 environment, you should make sure that your operations are carefully planned and structured. The best way of ensuring that your operations are efficient is to have operations intrinsically involved in the planning and deployment phases of Exchange 2000, providing valuable input into those processes. -
Page 15: Service Level Agreements
(and in some cases the deployment phase) to test procedures that are defined, such as those for disaster recovery. Planning and deployment are covered in more detail as part of the Exchange 2000 Upgrade Series. You will find this at the following Web site: http://www.microsoft.com/technet/exchange/guide/default.asp... -
Page 16: Performance
Microsoft Exchange 2000 Operations Guide — Version 1.0 Performance Here you show the performance you would expect from each of the previously mentioned features. This would include some or all of the following: Service availability (this may be given across all services or on a service-by-service... -
Page 17: Summary
Supporting chapter first, you should go back and read the other chapters as well. Related Topics The Microsoft Operations Framework provides technical guidance and industry best practices that encompasses the complete IT Service Management environment, including capacity management, availability management, configuration management, service monitoring and control, service level management, and their inter-relationships. -
Page 19: Capacity And Availability Management
Management Introduction In the vast majority of cases, the load on your Exchange 2000 Server computers will increase over time. Companies increase in size, and as they do, the number of Exchange users increases. Existing users tend to use the messaging environment more over time, not only for traditional e-mail, but also for other collaborative purposes (for example, voicemail, fax, instant messaging, video conferencing). -
Page 20: Chapter Sections
Of course, whether an individual server reaches its SLA targets will depend greatly upon the functions of that server. In Exchange 2000, servers can have a number of different functions, so you will need to ensure that you categorize servers according to the functions they perform and treat each category of server as an individual case. - Page 21 To ensure that you manage capacity appropriately for your Exchange 2000 server, you need a great deal of information about current and projected usage of your server running Exchange.
- Page 22 However, keeping an eye on the size of your Exchange 2000 databases is still important. In a large enterprise, it is typical for users to be moved from one server to another quite often, and for users to be deleted.
-
Page 23: Availability Management
One of the main aims of Exchange 2000 operations is to ensure that Exchange is avail- able as much as possible and that both planned and unplanned interruptions to service are minimized. -
Page 24: Service Availability
Exchange, which would result in the databases shutting down and in users losing a number of services. Minimizing System Failures To minimize the frequency of failure in Exchange 2000, you need do the following: Decrease single points of failure Increase the reliability of Exchange 2000 itself. - Page 25 Exchange can fail over correctly to the other node. With Service Pack 1 of Exchange 2000 and Windows 2000 Datacenter server, you can have four nodes in your cluster. In this implementation consider active/active/active/passive clustering.
- Page 26 Exchange 2000 in Chapter 3. Increasing the Reliability of Exchange 2000 While Exchange 2000 is a very robust messaging system, like any product, there are configurations that in particular cases could result in a loss of reliability. In an Enterprise environment, it is important to guard against these difficulties by continually monitoring Exchange.
-
Page 27: Minimizing System Recovery Time
Chapter 3. Minimizing System Recovery Time To recover from failure in an Exchange 2000 environment as quickly as possible, you need to be thoroughly prepared. You will need the following:... -
Page 28: Making Changes To The Registry
Microsoft Exchange 2000 Operations — Version 1.0 While obtaining the best performance from your Exchange 2000 computers is always an important goal, it is crucial to be cautious in your tuning changes. You should track all alterations in case you make a change that inadvertently reduces performance. Making one change at a time makes it easy to identify which change needs to be reversed. -
Page 29: No Performance Optimizer
“Edit Registry Information” Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running the Microsoft Windows NT® or Microsoft Windows® 2000 operating system, you should also update your emergency repair disk (ERD). -
Page 30: Tuning Considerations
Exchange 5.5, it is best to start from scratch in evaluating the optimization of Exchange 2000. It is useful in this process to know your Exchange 5.5 settings before upgrading to Exchange 2000. The text file WINNT\System32\perfopt.log provides a record of those registry keys and disk assignments changed by PerfWiz. -
Page 31: Tuning Smtp Transport
Exchsrvr\mailroot directory (the default location for this directory is \Program Files\Exchsrvr\mailroot) Note: If you perform the following step on a clustered Exchange 2000 server, you will need to first start Cluster Administrator and set the Exchange group to offline. - Page 32 16. Restart the Exchange 2000 computer. SMTP File Handles When the Exchange 2000 SMTP stack receives a new message, it writes the contents to a file on an NTFS partition. While the message is being processed (that is, waiting for the next hop or delivery point) a file handle is held open by the operating system.
- Page 33 Chapter 2: Capacity and Availability Management your server becomes low on kernel memory, your system becomes unresponsive. To regain control of your server, you must restart it to free up the kernel memory. Table 2.1 shows the registry parameters you might need to alter if you are to make perfor- mance gains on servers with more than 1 GB RAM.
-
Page 34: Store And Ese Tuning
10,000, SMTP will refuse any inbound mail after the queue reaches 10,000 messages. You may need to alter the following registry entry if the Exchange 2000 computer is running out of memory because the number of incoming messages is too great for the server to process: Location. - Page 35 If Exchange 2000 is installed in a global data center, serving customers from multiple time zones, the default online maintenance time could become an issue. The effect that online maintenance has on Active Directory is proportional to the number of users in each of the server’s databases.
- Page 36 On the next page is an example of an online store maintenance schedule for a corporate Exchange 2000 mailbox server that hosts users who are in a single time zone. First Storage Group Database One Online maintenance runs between 9:00 P.M.
- Page 37 Chapter 2: Capacity and Availability Management Extensible Storage Engine (ESE) Heaps When Exchange 2000 is installed on servers with more than four processors, you might notice high virtual memory usage by the Extensible Storage Engine (ESE) multi-heap. This can lead to performance problems, especially when the server has more than one GB of memory, and many databases and storage groups have been configured.
-
Page 38: Tuning Active Directory Integration
Microsoft Exchange 2000 Operations — Version 1.0 Factors which affect the virtual address-space size in the Store.exe process include the following: Initial allocation on start-up Number of storage groups and databases on the server Number of threads running Size of the store-database cache Prior to increasing the maximum cache size, it is recommended that you use the Windows 2000 performance monitor to monitor the memory of the server under normal load. - Page 39 LDAP queries until the active number drops below 20. Twenty is generally sufficient for most Active Directory servers, but it is necessary to increase this value when you are running Exchange 2000 on six- or eight-processor servers, or if the preceding error message is logged.
- Page 40 Note: This setting will be replicated to all Active Directory servers within the forest. You do not have to restart domain controllers or Global Catalog servers for this to take effect. Under normal circumstances, Exchange 2000 will access Global Catalog servers and the user partition of domain controllers by consulting a dynamically created list of available servers.
-
Page 41: Tuning Outlook Web Access (Owa)
In environments where many users will use Outlook Web Access as their client, traffic and resources on the Exchange 2000 server—as well as latencies apparent to the user—can all be reduced by increasing the time until expiration of static files from the \Program Files\ Exchsrvr\Exchweb\Controls and \Img directories. - Page 42 Tools, and select Internet Services Manager. 2. Expand the server icon. Note: If you are performing this procedure on an Exchange 2000 Server cluster, expand the Exchange Virtual Server instead of the Default Web Site in the following step.
-
Page 43: Hardware Upgrades
This allows you to keep your hardware consistent across each Exchange 2000 role and therefore reduce support costs for the new environment. Always ensure that you test Exchange and Windows 2000 thoroughly on the new hardware to ensure that there are no unforeseen anomalies. -
Page 45: Change And Configuration Management
Management Introduction Exchange 2000 Server is highly configurable and has the potential for huge variation in hardware and software configuration. It is also likely to be one of the most important elements of your IT environment. For Exchange to run as smoothly as you hope, providing the best possible service to users, you need to make sure that your environment is carefully managed. -
Page 46: Prerequisites
Microsoft Exchange 2000 Operations Guide — Version 1.0 Prerequisites By now you have defined a set of acceptable service level agreements for your Exchange environment and you understand the concepts of availability management that were discussed in Chapter 2, “Capacity and Availability Management.”... - Page 47 Change can be broadly categorized into four groups, each requiring its own style of management. The groups are: Major change. Significantly impacts the IT environment, and requires major resources to plan, build, and implement (for example, upgrading all Exchange 2000 Server hardware). Significant change. Requires substantial resources to plan, build and implement (for example, upgrading to a new Service Pack).
- Page 48 Microsoft Exchange 2000 Operations Guide — Version 1.0 Step 2 – Change Manager Assesses the RFC The change manager receives the RFC and records it in the change management log. The manager examines the RFC, checking to see if it is a complete and practical proposal. If in...
- Page 49 Chapter 3: Change and Configuration Management change. In this case, expertise with Exchange and hardware is very important. In fact, the change manager may decide to appoint an OEM vendor representative to the change advisory board. The change advisory board determines the hardware upgrade schedule, according to IT executive committee recommendations.
- Page 50 Microsoft Exchange 2000 Operations Guide — Version 1.0 Figure 3.1 The Change Management Process Minor and Standard Changes The advantage of minor and standard changes is that individuals with less authority can be pre-assigned the permissions to perform them. This is perfectly fine, because the changes themselves are not likely to cause significant problems when implemented.
-
Page 51: Security
Chapter 3: Change and Configuration Management the user in the appropriate Windows 2000 groups and create the Exchange 2000 mailbox with the appropriate settings for that user. Over time, your team will build a set of custom tools that are used frequently to administer standard changes. -
Page 52: Configuration Management
By implementing Exchange 2000, you will already have many of the tools to create a good knowledge management system! RFCs can be easily submitted via Microsoft Outlook ®... -
Page 53: Tools For Configuration Management
“picture” of the environment is always available. Configuration Items Configuration items are objects that fall under the category of change management, and are therefore subject to change. In Exchange 2000, configuration items include the following: Exchange Server hardware Domain controller hardware... - Page 54 Exchange software. It will have the following attributes associated with it: A software identifier The RFC identifier that led to the current software version The name of the application (for example, Exchange 2000 or Exchange 2000 Server Enterprise Edition) The version number of the software...
- Page 55 Here the server itself is obviously hardware, but it also represents the software that is to installed on it. These elements depend on each other. If there was no hardware, Exchange would have nothing to be installed on, and if there is no Exchange 2000 software, there is little point in having the hardware.
- Page 56 Microsoft Exchange 2000 Operations Guide — Version 1.0 Here, the printer is related to the server because it is connected to it. Exchange 2000 Server is licensed to the server hardware. The hot fix is another configuration item, but one that clearly has a relationship to the server running Exchange on which it is installed.
-
Page 57: Maintaining The Configuration Management Database
Chapter 3: Change and Configuration Management Defining Configuration Items When defining configuration items you need to decide how deeply you want to go in recording the them. Too many configuration items makes the relationships too difficult to manage and costs start to increase. There are strong benefits to making the configuration management database as simple as possible to actively reflect the environment in which it is working, then adding in additional configuration items as and when they are required. - Page 58 Microsoft Exchange 2000 Operations Guide — Version 1.0 which connectors will be affected by taking a server running Exchange offline for mainte- nance, only to find when they actually examine the servers that different connectors are present. The configuration management database is initially populated by an inventory of your existing hardware, software, tools, and processes.
-
Page 59: Exchange System Policies
Administering System Policies One of the main advantages of Exchange 2000 system policies is that it allows you to centralize administrative control easily. The administrative model you follow determines how you should implement system policies. -
Page 60: Summary
If you do not have change and configuration management in your organization currently, you can still implement it for your Exchange 2000 Server environment. It is very likely that doing so will considerably improve the efficiency and the reliability of your operations. -
Page 61: Enterprise Monitoring
(covered in Chapter 1, “Introduction”). Chapter Sections This chapter covers the following procedures: Performance monitoring Event monitoring Availability monitoring Client monitoring Operation personnel notification At the end of this chapter, you will be able to monitor your Exchange 2000 Server environ- ment effectively. -
Page 62: Performance Monitoring
The Windows 2000 operating system includes System Monitor (which consists of Perfor- mance Monitor and Network Monitor) for analyzing the performance of your system. When you install Exchange 2000 Server, a large number of objects are installed and counters are associated with those objects. -
Page 63: Exchange 2000 Objects And Counters To Monitor
Chapter 4: Enterprise Monitoring Exchange 2000 Objects and Counters to Monitor Every Exchange 2000 performance object has at least one counter associated with it. For information on particular counters, in Performance Monitor, click Select Counters from List, select a counter, and then click Explain. - Page 64 Microsoft Exchange 2000 Operations Guide — Version 1.0 Service or Resource Performance Object Lotus CC Mail MSExchangeCCMC Lotus Notes Message Center MSExchangeNMC Service or Resource Performance Object Message Transfer Agent MSExchangeMTA Message Transfer Agent Connections MSExchangeMTA Connections MS Mail Connector Interchange...
- Page 65 SMTP traffic can be from SMTP Servers, such as other servers running Exchange, or it can be from POP3 or IMAP4 Clients such as Microsoft Outlook Express. When monitoring SMTP parameters, remember that your client base will affect these figures: Local Queue Length –...
- Page 66 Work Queue Length of the MSExchangeMTA object and the Queue Length of the MSExchangeMTAConnections object. In Exchange 2000 Server, you may find the Message Transfer Agent (MTA) shutting down fairly frequently, especially if it cannot find a domain controller temporarily. To resolve this problem, you may want to use the recovery actions option in services to restart the service in the event of it being stopped.
-
Page 67: Windows 2000 Objects And Counters To Monitor
Windows 2000 Objects and Counters to Monitor A heavily used Exchange 2000 server may have a number of bottlenecks. Simply monitor- ing Exchange 2000 Server performance objects and counters in isolation will not give you information about the condition of the server itself. - Page 68 Microsoft Exchange 2000 Operations Guide — Version 1.0 Table 4.2 Subjects and Associated Objects and Counters Subsystem Object Counter Exchange Comments Disk Logical Disk % Free Disk Space Physical Disk % Disk Time Usually unreliable for RAID systems, so rarely applicable...
- Page 69 Chapter 4: Enterprise Monitoring Subsystem Object Counter Exchange Comments Processor Processor Interrupts/sec Processor %Processor Time The creation of indexes by Full Text Indexing generally uses a great deal of processor time. However, a low priority thread is used, so it does not necessarily cause performance issues.
-
Page 70: Centralized Monitoring
Exchange. An example of a centralized monitoring tool for Exchange 2000 Server is AppManager from NetIQ. AppManager consists of four components: Console –... -
Page 71: Event Monitoring
Chapter 4: Enterprise Monitoring Event Monitoring When Exchange 2000 Server is running smoothly, event monitoring does not seem espe- cially important. However, when performance is poor, you will quickly see the benefits of event monitoring. Event Viewer is a useful source of information about Exchange 2000 Server, along with log files that you may choose to generate. -
Page 72: Log Files
One of the main problems with event viewing in Exchange 2000 Server is the sheer volume of information Exchange produces when you increase the logging level. It is often benefi- cial to use filters in the Event Log to produce only warning and critical events, or to use utilities that only display the more significant events. -
Page 73: Availability Monitoring
Simple Mail Transport Protocol World Wide Web Publishing Service If any of these services are not running, Exchange 2000 logs a critical state warning in Event Viewer. Note: The Monitoring and Status tool does not notify you if a store has become dismounted. - Page 74 Microsoft Exchange 2000 Operations Guide — Version 1.0 have other Exchange services that are vital to the user experience in your environment (for example, if Instant Messaging is used heavily in your organization). Monitoring Resources You can monitor other resources using the Monitoring and Status tool. To do so, click Add on the Monitoring tab and select the resources you want to monitor.
-
Page 75: Centralized Availability Monitoring
Chapter 4: Enterprise Monitoring Status The details pane of the Status container allows you to view the status of servers and connectors in your organization. The Status container shows the following server states: Available – This shows that the server is online and all the main services are running normally. -
Page 76: Client Monitoring
(It is important not to confuse a loss of service on the client due to Exchange 2000 Server issues with loss of service on the client due to user error.) -
Page 77: Summary
Chapter 4: Enterprise Monitoring Summary It is impossible to operate servers running Exchange efficiently if you do not know what they are doing. It is very important to ensure that you always have enough information about your Exchange environment to predict problems and to verify that you are meeting your service level agreements. -
Page 79: Protection
Protection Introduction By its very nature, Exchange 2000 Server has a public face. You will be offering e-mail and other functionality to a large number of users. In many cases those users will not only be able to collaborate with other users in their own company, but also with others across the Internet. -
Page 80: Chapter Sections
Microsoft Exchange 2000 Operations Guide — Version 1.0 Chapter Sections This chapter covers the following procedures: Protection against hacking Anti-virus measures Disaster recovery procedures Recovery testing Backup Restore Protection Against Hacking Whenever you consider protecting your organization against malicious attack, it is worth recalling one of the golden (and most disillusioning) rules of security: the majority of attacks on a network security come from inside. -
Page 81: Firewall Operations
Your Exchange operations department should ensure that it receives security bulletins from Microsoft. To receive these bulletins, visit the following Web site: http://www.microsoft.com/technet/security/notify.asp In cases where a security breach has been exposed and a new hot fix needs to be applied, the change should generally be considered urgent and should travel through the change configuration process accordingly. - Page 82 Microsoft Exchange 2000 Operations Guide — Version 1.0 operating. In a multi-firewall environment, the firewalls are generally manufactured by a number of different vendors, which can make management issues even more complex. The responsibilities of the operations department in these circumstances will include the...
-
Page 83: Anti-Virus Measures
Anti-Virus Measures As part of your planning and deployment of Exchange 2000, you will have put in place appropriate measures against virus attack. However, regardless of how much protection you put in place, it is quite possible that viruses may affect Exchange. -
Page 84: Staying Current
If there is a store-related incident on a server with this product, Microsoft Product Support Services (PSS) will recommend that the anti-virus software be disabled early in troubleshooting. -
Page 85: Dealing With Virus Infection
Chapter 5: Protection In some cases you will receive a warning about a new virus before an update to your anti- virus software is proposed. The first thing to do here is to verify that the virus is genuine. Many problems are in fact caused by hoax virus notifications. Ensure that the virus is a genuine problem by checking with your anti-virus vendors. -
Page 86: Blocking Attachments At The Client
Attachments may be blocked at the server level, but they may also be blocked at the client. You can install a security patch on Microsoft Outlook 98 and Outlook 2000. This patch is built into Outlook 2000 Service Release 2 and Outlook 2002 (a component of Microsoft Office XP). - Page 87 VBscript file Note: Not all attachments considered to be dangerous are blocked by this patch. For example, the Microsoft Access file types .mda and .mdz are not blocked, nor are zipped versions of any of the above files. It is good practice to quarantine all suspect content, where it can be examined individually before deciding whether it can be safely passed on or not.
-
Page 88: Disaster Recovery Procedures
Another alternative is real-time byte level replication. You will find a list of third party vendors offering backup solutions for Exchange 2000 at the following Web site: http://www.microsoft.com/exchange/thirdparty/E2Ksolutions.htm#backup... - Page 89 In Exchange System Manager, when you make configuration changes for a server in the Protocols container, most of those changes are written to the Microsoft Internet Informa- tion Services (IIS) metabase (some of the same information is also kept in Active Direc- tory.) So as well as backing up Active Directory, you should also back up the IIS metabase...
- Page 90 Exchange server if an online backup does not work as it should. Each Exchange 2000 store consists of an .edb file and an .stm file. With up to 20 stores, public and private, on a server, you need to back up, up to 40 files per server. When you shut down the information store correctly, all the log file information is written to the corresponding .edb and .stm databases, so you do not need to back up the log files when...
-
Page 91: Restoring
Active Directory). Recovering Individual Messages Exchange 2000 has a setting to allow deleted item retention time. By default, this is set to zero. The easiest way of allowing the recovery of individual messages is to increase this value. - Page 92 Microsoft Exchange 2000 Operations Guide — Version 1.0 Once again, you would be advised to define your SLAs so that mailbox recovery is not possible outside the period of time you specified in the Administrator program. While mailbox recovery is possible outside of this time span, dependent upon your backup software, you may have to restore an entire Exchange database to a server in a different Windows 2000 forest to get the appropriate missing mailbox.
- Page 93 One of your main concerns in operations should be to ensure that this never happens. As you will have already noticed, Exchange 2000 is completely dependent on Active Direc- tory. If you are to fully protect your Exchange environment, you should do all you can to...
-
Page 94: Recovery Testing
Microsoft Exchange 2000 Operations Guide — Version 1.0 However, this does not mean that an Active Directory failure makes Exchange 2000 completely unusable. You should be able to recover an Exchange Organization, pro- vided you have access to information about the Exchange configuration, including the Exchange storage group and store names for each server, plus a key item, known as the legacyExchangeDN attribute for each administrative group. -
Page 95: Summary
Chapter 5: Protection In training your staff, you should note that restoring to another online server while the first is online is a very difficult procedure to the majority of disaster recovery procedures, because you have to recover to a different forest under those circumstances. The best way to simulate the type of restore you may have to perform in an emergency is using a test network that is completely separate from the main network. -
Page 97: Support
Support Introduction The more you can do with a product, the more you can do wrong. Exchange 2000 Server is an extremely diverse and complex product. If you use Exchange to its full potential, you will be exposing more functionality to your users than ever before, thus creating more and tougher challenges for the support environment than ever before. -
Page 98: Providing Support For End Users
Your Exchange 2000 Server environment may be one of the most complicated and diverse of your IT infrastructure. You may have a wide range of different clients, including the... - Page 99 Chapter 6: Support Server hardware problems (servers running Exchange or domain controllers) Server connectivity problems (to domain controllers, other servers running Exchange or the Internet) Educating your users is one of the key ways to reduce support costs. If users know how to use their clients efficiently and effectively, they will need to contact the Service Desk much less frequently.
- Page 100 Microsoft Exchange 2000 Operations Guide — Version 1.0 number of protocols supported. For example, you may choose to only support OWA as the means of access outside the firewall. Not all of these problems are necessarily client issues. End users will be directly affected by problems at the server level.
- Page 101 Chapter 6: Support Dealing with User Problems You must have a mechanism for dealing with user problems once they are reported. The first step in this process is to determine the scope of the problem. In doing so, you should consider the following: How many users are affected by the problem? (Does it affect a single user, all users on a server, all users in a region, and so on?
-
Page 102: Exchange Problem Management
Exchange problem is not an Exchange problem at all, but is caused by the failure of a related technology. The key to good problem management for Exchange 2000 Server is a good understanding of the interdependencies Exchange has, and good knowledge management in your support environment. - Page 103 Chapter 6: Support To help you with Exchange problem management, you should create dependency charts for a number of scenarios. Examples include the following: A chart for MAPI client connectivity that lists all dependencies, for example, DNS, WINS, Exchange, Active Directory, and so on A chart for POP and IMAP client connectivity that lists all dependencies, for example, DNS, WINS, Exchange, Active Directory, SMTP relay, and so on A chart for OWA client connectivity that lists all dependencies, for example, DNS,...
-
Page 104: Summary
You should ensure that your support staff has a complete picture of Exchange and its interdependencies. For most organizations, it is not economically sound to have all Exchange 2000 Server expertise directly employed within the company. Normally the higher levels of support are contracted out. -
Page 105: Glossary
Active Directory. Replicated objects include mailboxes, custom recipients, distribution lists, and site configuration information. ADC uses Connection Agreements (CAs) to define individual configurations for replication. The Exchange 2000 ADC is also used to allow Exchange 5.x and Exchange 2000 servers to coexist within the same Exchange site. - Page 106 Exchange 2000 store, or a SQL database. Administration group A collection of servers running Exchange 2000 that can be administered as a single unit. An administration group can include zero or more policies, routing groups, public folder trees, monitors, servers, conferencing services, and chat networks. When security settings (permissions) are applied to an administration group, all child objects in the DS tree inherit the same Access Control Lists (ACLs) as the administration group node.
- Page 107 (CDO) for Exchange 2000 CDO for Exchange 2000 is included with Exchange 2000 and its services are supplied from the CDOEX.DLL file. CDO for System Management (formerly known as Exchange Management Objects – EMO) An API that allows administrators to programmatically access management information on an Exchange 2000 server, including databases and mailboxes.
- Page 108 Microsoft Exchange 2000 Operations Guide — Version 1.0 Conferencing Management Service – CMS The network service that coordinates the booking of virtual resources for online meetings in the Exchange Conference Service. Each site (not domain) normally has an active Conferencing Management Service to allow fast connection for data conferencing users.
- Page 109 Client requests use the DSProxy service for directory access. DSProxy The Exchange 2000 component that can proxy (and refer) Messaging Application Pro- gramming Interface (MAPI) directory service requests from Outlook clients to Active Directory for Address Book lookup and name resolution.
- Page 110 A piece of code that is activated by a defined trigger, such as the reception of a new message. The code is normally written in any COM-compatible programming language such as Visual Basic, VBScript, JavaScript, C, or C++. Exchange 2000 supports the fol- lowing event sinks:...
- Page 111 Exchange Server 5.5 incorporated protocols such as Network News Transfer Protocol (NNTP), Post Office Protocol 3 (POP3), and Internet Messaging Access Protocol (IMAP) directly into the Store.exe process, so data transfer was very efficient. The Exchange 2000 architecture separates the protocols from the database for ease of management and to support future architectures.
- Page 112 Installable File System – IFS See Web Storage System Instant Messaging – IM The Exchange 2000 service that allows for real-time messaging and collaboration between users. Clients generally use the MSN Messenger client to log on to Instant Messaging and subscribe to other users.
- Page 113 A standard-based protocol for accessing mailbox information. IMAP4 is considered to be more advanced than POP3 because it supports basic online capabilities and access to folders other than the Inbox. Exchange Server 5.x and Exchange 2000 both support IMAP4. Joint Engine Technology – JET Defines the low-level access to underlying database structures in Exchange Server 4.0 and...
- Page 114 Metaedit. Metabase update service A component in Exchange 2000 that reads data from Active Directory and transposes it into the local IIS metabase. The metabase update service allows the administrator to make remote configuration changes to virtual servers without a permanent connection to each system.
- Page 115 C and C++ to access dissimilar data stores through a common query language. OLE DB is seen as the replacement for Open Database Connectivity (ODBC). Data stores such as those in Exchange 2000 and SQL Server allow for OLE DB access, which makes appli- cation development easier and faster.
- Page 116 Exchange server used only a single tree (called: All Public Folders), whereas multiple trees can be defined in Exchange 2000. Each tree is a unit of hierarchy replication and can be replicated to one or more Public MDBs. A Public MDB can host only one tree.
- Page 117 Additionally, a routing group defines the boundary for public folder access. Routing Group Connector – RGC A connector in Exchange 2000 that connects routing groups to one another. An RGC is uni-directional and can have separate configuration properties (such as allowable message types over the connection).
- Page 118 Microsoft Exchange 2000 Operations Guide — Version 1.0 SASL Simple Authentication and Security Layer. Defined in RFC2222. Schema The metadata (data about data) that describes the use of objects within a given structure. In Active Directory, the schema governs the type of objects that can exist and the mandatory and optional attributes of each object.
- Page 119 Exchange 5.x Directory Service. Storage group A collection of Exchange databases on a server running Exchange 2000 that share the same Extensible Storage Engine (ESE) instance and transaction log. Individual databases within a storage group can be mounted and dismounted. Each server running Exchange 2000 can architecturally host up to 16 storage groups, although only four can be defined through the Exchange System Manager.
- Page 120 Microsoft Exchange 2000 Operations Guide — Version 1.0 System attendant One of the core Exchange 2000 services that performs miscellaneous functions (usually related to directory information) such as generation of address lists, offline Address Books, and directory lookup facilities. T.120 A standards-based protocol used with Exchange Data Conferencing.
- Page 121 Web Storage System The database architecture in Exchange 2000. Previous releases of Exchange only exposed data such as public folders through MAPI, whereas Exchange 2000 exposes all of its data through MAPI, HTTP, OLE DB and Win32 layers. This means that an object stored in a public folder can be retrieved and manipulated through a Web browser or a standard client with a network redirector.