Microsoft Press 70 284 training kit exchange server 2003 phần 10 ppt

14-10 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 Sometimes an X.400 connector is the solution rather than the problem. By default, Exchange Server 2003 routing groups are connected by routing connectors. If, how- ever, the connection is unreliable or non-persistent (a demand-dial connection, for example), then transfer reliability can be improved by using an X.400 connection, which uses message-based data transfer rather than remote procedure call (RPC). You also need to take care how you specify encoding formats for your POP3 and Inter- net Message Protocol version 4 (IMAP4) clients on the relevant virtual servers. This was discussed in Chapter 9, “Virtual Servers.” If your clients use UNIX to UNIX encoding (uuencode), then your virtual servers need to be set up appropriately. For Macintosh clients, you need to specify uuencode and then select BinHex for Macintosh. Microsoft Outlook users tend to take calendaring for granted because it is a built-in Outlook function. However, the Calendar Connector’s properties are set not to syn- chronize calendar data by default. Thus when Outlook users attempt to view the schedules of users on foreign systems, for example Lotus Notes, the information could be out of date. Exam Tip If you get a question about interaction with a foreign system, read it carefully to determine if you are getting no communication with the foreign system, in which case a con- nector is down or a virtual server has failed. If, on the other hand, you are getting a connec- tion but the messages are garbled, then the encoding format may be specified incorrectly. Practice: Using the Netdiag and Dcdiag Command-Line Utilities The netdiag utility tests network connectivity. The tool lets you specify a number of optional parameters, such as /test: to run a specific test and /d: to specify a domain. However, it is typically run either with no parameters or with the /fix switch to repair minor errors and the /debug switch to give detailed output. The output from the tool can be redirected to a text file for analysis. The dcdiag utility is mainly used to test domain controller operation, but it also tests DNS availability. If there is a problem with your Active Directory domain or your DNS server, then Exchange Server 2003 will not install and dcdiag can help troubleshoot the failure. The utility has a number of parameters, all of which are optional. You can use the /s: switch to specify a domain controller, the /u: switch to specify a user (by user- name and domain name), and the /p: switch to specify a password. If you do not sup- ply any of these parameters, then the utility will test the host on which it is run in the context of the logged in user. The /fix switch fixes the Service Principal Names (SPNs) on the specified domain controller, and the /test: switch allows you to specify particu- lar tests. All tests except DcPromo and RegisterInDNS must be run on a domain controller. ! Lesson 1 Troubleshooting Exchange Server 2003 Server Migration and Interoperability 14-11 See Also Details of the netdiag and dcdiag tests and parameters may be obtained from the Windows Server 2003 help files. Search under “Support Tools.” In this practice, you create files to hold the output of the tests, run the netdiag tests on a normal system and on a faulty system, compare the outputs, and then do the same with the dcdiag tests. Exercise 1: Create Files to Hold the Test Output To create files to hold the test output, perform the following steps: 1. On Server01, create a new folder named C:\Tests. 2. In the C:\Tests folder, create the following empty text files: ❑ Netdiag1.txt ❑ Netdiag2.txt ❑ Dcdiag1.txt ❑ Dcdiag2.txt Note Some administrators do not create the required folder and files before using command-line utilities such as netdiag and dcdiag, because the utilities create them automatically. However, not all command-line utilities do this. Arguably, it is good practice to create files before you run any utility that uses them. Exercise 2: Use Netdiag to Check Network Connectivity To use netdiag to test network connectivity on Server01, perform the following steps: 1. On Server01, open the Command console. 2. Enter netdiag /debug /fix > c:\tests\netdiag1.txt. 3. Open the Netdiag1.txt file using Microsoft Notepad. 4. Read the test output. Use the search function to find “Errors,” “Warning,” or “Failed.” A section of the test output is shown in Figure 14-1. 14-12 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 F14es01 Figure 14-1 Netdiag output Exercise 3: Use Netdiag to Find a Connection Fault To create a connection fault on Server01 and use netdiag to diagnose the fault, perform the following steps: 1. On Server01, unplug the connector from Local Area Connection. 2. Open the Command console. 3. Enter netdiag /debug /fix > c:\tests\netdiag2.txt. 4. Open the Netdiag2.txt file using Notepad. 5. Read the test output. Use the search function to find “Fatal.” The relevant section of the test output is shown in Figure 14-2. F14es02 Figure 14-2 Netdiag output showing a fatal error 6. Replace the network connector for Local Area Connection. Test the connection by pinging Server02. Lesson 1 Troubleshooting Exchange Server 2003 Server Migration and Interoperability 14-13 Exercise 4: Use Dcdiag to Test Server02 In this exercise, you run dcdiag from Server01 to test Server02. If Server02 is not a domain controller on your test network, then test Server01 instead. To test Server02 using dcdiag, perform the following steps: 1. On Server01, open the Command console. 2. Enter dcdiag /s:server02 /n:contoso.com /u:contoso.com\administrator /p:* /v /f:c:\tests\dcdiag1.txt /fix. 3. Enter the password for the contoso.com administrator when prompted. The test completes as shown in Figure 14-3. F14es03 Figure 14-3 Running dcdiag on Server02 4. Open the Dcdiag1.txt file using Notepad and read the results. A section of the test output is shown in Figure 14-4. F14es04 Figure 14-4 Output of dcdiag test on Server02 Exercise 5: Use Dcdiag to Detect a Fault on Server02 In this exercise, you stop the DNS service on Server02 and then run dcdiag from Server01 to test Server02. To use dcdiag to detect a fault on Server02, perform the fol- lowing steps: 14-14 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 1. On Server02, open the DNS console, right-click SERVER02, and then click Stop. 2. On Server01, open the Command console. 3. Enter dcdiag /s:server02 /n:contoso.com /u:contoso.com\administrator /p:* /v /f:c:\tests\dcdiag2.txt /fix. 4. Enter the password for the contoso.com administrator when prompted. 5. Open the Dcdiag2.txt file using Notepad and read the results. The relevant section of the test output is shown in Figure 14-5. F14es05 Figure 14-5 Dcdiag failure notification on Server02 6. Start the DNS service on Server02. Lesson Review The following questions are intended to reinforce key information presented in this lesson. If you are unable to answer a question, review the lesson materials and then try the question again. You can find answers to the questions in the “Questions and Answers” section at the end of this chapter. 1. You are installing Exchange Server 2003, Enterprise Edition, on a standalone server. The server meets the recommended hardware requirements and Windows Server 2003, Enterprise Edition, is installed. You have installed and enabled SMTP, NNTP, the World Wide Web service, and ASP.NET. The server is a standard primary DNS server. Will the installation succeed? If not, why not? 2. You migrate an Exchange Server 5.5 organization to Exchange Server 2003. You use the Active Directory Migration Tool to migrate the mailboxes. You find that the mailboxes have migrated with all the user permissions intact, but user passwords have not migrated. What is the probable reason? Lesson 1 Troubleshooting Exchange Server 2003 Server Migration and Interoperability 14-15 3. Your Exchange Server 2003 organization connects to a UNIX e-mail system over an X.400 connector. You establish connectivity with the system, but e-mail mes- sages are garbled. How do you solve the problem? Lesson Summary ■ Exchange Server 2003 will fail to install if your hardware resources are inadequate, if your member server does not have the appropriate operating system, or if Active Directory or DNS are not accessible. ■ Other reasons for installation failure are that SMTP, NNTP, and the World Wide Web service are not installed and running and that POP3 is installed. When install- ing on a Windows Server 2003 member server, you also need to install and enable ASP.NET. ■ Migration from Exchange systems requires that mailboxes be migrated. When migrating to Exchange Server 2003 you should use version 2 of the Active Direc- tory Migration Tool, which will migrate mailboxes that are associated with user accounts and will also migrate passwords. You need to configure an SMTP virtual server to replace the Internet Mail connector used by Exchange Server 5.5 and configure DNS accordingly. ■ When you need to coexist with foreign e-mail systems, it is important to check your encoding. Exchange Server 2003 defaults are not always suitable for this coexistence. ■ You can use support tools such as netdiag and dcdiag to check network connec- tivity and DNS and Active Directory operation. 14-16 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 Lesson 2: Troubleshooting Exchange Server 2003 Servers The performance of an Exchange Server 2003 server depends upon the efficiency of general server processes, such as memory and processor operation, in addition to the processes specific to Exchange. Troubleshooting server health involves interpreting the values of the appropriate counters recorded in a performance log and taking action as required. If you suspect that a fault is occurring that could result in an unusually high or low counter reading, you can set thresholds to trigger an alert. The alert could in turn initiate logging of other counters. Loss of data is a very serious matter in an Exchange organization, and you need to be proactive in troubleshooting data storage to prevent a disaster. If a disaster does occur, you need to have confidence that your data recovery process is operating correctly. If your servers are clustered to provide failover or load sharing, then you need to have procedures in place to ensure that those clusters are operating correctly and to repair any failures before they affect your users. After this lesson, you will be able to ■ Interpret a Windows Server 2003 server performance log and take action, as appropriate ■ Troubleshoot data storage and ensure that disk performance and failover protection are maintained ■ Troubleshoot Exchange Server 2003 server clusters ■ Troubleshoot backup and recovery operations Estimated lesson time: 90 minutes Troubleshooting Server Health Chapter 13 described how you can configure a performance log and diagnostic logging in order to monitor counters and resources on an Exchange Server 2003 server. In this lesson, you learn the significance of the results obtained and the action that you can take when these results indicate a problem. You can also set up alerts to indicate when resource usage or a performance counter exceeds a critical limit. There are many counters and instances of counters in an Exchange Server 2003 server. The following are among the most commonly used to diagnose problems with server health: ■ Memory\Pages/sec This counter indicates the rate at which pages are read from or written to disk to resolve hard page faults. It is the sum of Memory\Pages Input/sec and Memory\Pages Output/sec, and indicates the type of faults that cause system-wide delays. It includes pages retrieved to satisfy faults in the file Lesson 2 Troubleshooting Exchange Server 2003 Servers 14-17 system cache (usually requested by applications) and non-cached mapped mem- ory files. If the counter value increases over time, it could indicate that memory is becoming a bottleneck. It can also indicate “leaky” applications that use memory when running but do not release it when they stop. Typically, the counter value should not exceed five. A value of 20 or more indicates a problem. ■ Processor\% Processor Time This is the percentage of elapsed time that the processor spends to execute a non-idle thread. The counter is the primary indica- tor of processor activity and displays the average percentage of busy time observed during the sample interval. It is quite normal for this counter to reach 100 percent. However, a value in excess of 80 percent averaged over a period of time indicates that the processor may be overloaded. If you have a symmetrical microprocessor (SMP) computer, then each processor is monitored as an instance of this counter. If you discover high readings for one processor and low readings for another, then you should use Task Manager to discover what processes have a hard affinity to the first processor. ■ Process\% Processor Time This indicates the percentage of elapsed time for which all of the threads of a process used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Because there are many processes created in an Exchange Server 2003 server (or any server), there are many instances of this counter (for example, store). Use the counter instances to keep track of key processes. There is no “correct” value for this counter. You need to establish a baseline for normal operation and compare your current readings against this. If the processor time used by a particular pro- cess increases over time, you need to judge whether there is a problem with the process or whether this is normal behavior that indicates that you may eventually need to upgrade the processor. ■ MSExchangeIS\RPC Requests The MSExchangeIS object represents the ser- vice that allows access to mailbox and public folder stores. Remote Procedure Call (RPC) Requests is the number of client requests that are currently being processed by the information store. The RPC protocol is used to transfer messages between computers and across connectors. You need to look at the value of this counter, together with the readings for MSExchangeIS\RPC Packets/sec (the rate that RPC packets are processed) and MSExchangeIS\RPC Operations/sec (the rate that RPC operations occur) to determine whether there is a bottleneck in the system. ■ PhysicalDisk\Disk Transfers/sec The value in this counter indicates the rate of read and write operations on a physical disk. A physical disk can contain sev- eral logical disks or volumes. Conversely, if disk arrays are used, a logical disk can contain several physical disks. You can add this counter to a performance log, but you will get a value of zero unless the disk counters are enabled using the diskperf command-line utility. Do not enable disk counters unless you have a problem that 14-18 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 you need to solve, and do not enable them for any longer than you must. Enabling disk counters can seriously degrade server performance. ■ SMTP Server\Local Queue Length This indicates the number of messages in the local queue on an SMTP server. You can get the same information from Queue Viewer, but a performance log lets you view a report over time and track trends. You should look at this counter in conjunction with the SMTP Server\Messages Delivered/sec counter, which indicates the rate at which messages are delivered to local mailboxes. It is possible that there are a lot of messages in a queue, but the queue is being processed at a rate sufficient to ensure that the messages are deliv- ered promptly. You can also set alerts on counters such as SMTP Server\Bad- mailed Messages (No Recipient) so that you are warned if an excessive amount of anonymous mail is delivered, possibly indicating spamming or a Denial of Service (DoS) attack. ■ MSExchangeIS Mailbox\Local Delivery Rate This is the rate at which mes- sages are delivered locally. The MSExchangeIS Mailbox object counters specifi- cally measure mailbox, as opposed to both mailbox and public folder, traffic. Other counters that you might need to monitor are MSExchangeIS Mailbox\Folder Opens/sec, which is the rate that requests to open folders are submitted to the Information Store, and MSExchangeIS Mailbox\Message, which is the rate that requests to open messages are submitted to the information store. You need to compare these counter values against performance baselines to determine whether a bottleneck exists and to track trends over time. Troubleshooting Data Storage Chapter 12 discussed the various redundant array of independent drives (RAID) con- figurations that can be used to store Exchange Server 2003 server databases and trans- action logs. We saw in that chapter that recovery to the point of failure is possible only if circular logging is disabled (the default) and transaction logs are stored on separate disks or disk arrays from databases. We also saw that a well-designed backup strategy could prevent disks from being filled with an excessive number of transaction logs. With the exception of RAID-0, the failure of a disk in an array is not always immedi- ately obvious. It is possible to generate an alert if a counter such as Physical\Disk Transfers/sec drops to zero, but this would necessitate having the disk counters enabled (and may be a good reason for enabling these counters). You can also config- ure Monitoring And Status in Exchange System Manager to write an event to the appli- cation log in Event Viewer if free disk space in the array falls below a predefined limit, and you can configure Notifications in the Monitoring And Status tool to notify you by e-mail or by some other method specified in a script file when the event occurs. This will alert you if there are capacity problems, but will not indicate a disk failure in an array because the loss of a spindle in an array does not affect free disk space. Lesson 2 Troubleshooting Exchange Server 2003 Servers 14-19 However, it is important that you deal with a disk failure immediately because your array is no longer fault-tolerant. If you are using RAID-5, then the loss of a spindle will result in noticeable performance degradation; basically everything slows down. In RAID-1 and RAID-0+1 arrays, however, the degradation in read performance may not be immediately noticeable, especially during quiet periods. Commercial hardware RAID systems can generate visual and audible warnings of disk failure, and you should take this functionality into account when choosing a system. Mailbox and Public Store Policies You can create mailbox and public store policies for any administrative group by expanding the administrative group in Exchange System Manager, right-clicking Sys- tem Policies, and then specifying either a new mailbox or a new public store policy. Chapter 7, “Managing Recipient Objects and Address Lists,” and Chapter 8, “Public Folders,” discuss policies in detail. From a troubleshooting viewpoint, limiting the size of public and mailbox stores, specifying a retention policy for deleted items, and not permanently deleting mailboxes until the store has been backed up are the most useful components of these policies. In Chapter 13, you learned how to monitor mailbox sizes and start the mailbox management process. These procedures help to troubleshoot storage, because problems can occur when databases grow too large. Enforcing mailbox limits can prevent such problems. Proac- tive troubleshooting—that is, preventing problems from occurring—is the hallmark of the efficient administrator. Real World But There’s Hardly Anything in My Mailbox! Not all users will see mailbox limits as good proactive troubleshooting. They will assure you that they regularly read and delete items and download extensions to their local disk. You need to explain that unless an e-mail message with a large extension is deleted, it will remain in the mailbox, and that deleted items are kept in mailboxes until they are backed up. Carefully note details of any issues that a user has with your policies. The information can be very useful when the same user asks you to retrieve a message that he or she deleted six months ago. Troubleshooting Clusters When a cluster node goes down and failover occurs, it is not always immediately obvi- ous that you have a problem. You need to use Cluster Administrator on a daily basis to check the health of your clusters. One of the main problems when using clusters is virtual memory fragmentation. You need to monitor the following virtual memory counters for each node in the cluster to determine when an Exchange virtual server must be restarted due to this fragmentation: [...]... restore 14-26 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 Lesson 3: Troubleshooting the Exchange Server 2003 Organization While some faults are restricted to specific Exchange Server 2003 servers, others affect the entire Exchange Server 2003 organization Problems with public folders can affect everyone in your organization, as can problems with virtual servers If you use a backend/front-end... Microsoft Exchange Server 2003 Security,” and is important enough to reproduce in this chapter These are the ports that Exchange Server 2003 server might need Open as few of them as possible Table 14-1 Exchange Server 2003 Ports and Services Port Service 25 SMTP 80 HTTP 88 Kerberos 102 Message Transfer Agent (MTA)-X.400 connector over TCP/IP 110 POP3 119 NNTP 135 Client /server communication RPC Exchange. .. Support Exchange Server 2003 14-45 Lesson 5: Troubleshooting Technologies That Support Exchange Server 2003 In this lesson, you learn about Windows Server 2003 technologies that operate in the background, supporting the Exchange Server 2003 organization Although these technologies are not directly concerned with e-mail, public stores, or newsgroups, Exchange Server 2003 needs them in order to work If Exchange. .. specialized storage group that can exist alongside the regular storage groups in an Exchange Server 2003 server (even if the server already has four normal storage groups) You can restore mailbox stores from any normal Exchange Server 2003 storage group to the recovery group You can then, if Lesson 2 Troubleshooting Exchange Server 2003 Servers 14-21 appropriate, use the exmerge command-line utility to move the... between server roles On front-end servers, IMAP4 and POP3 virtual 14-30 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 servers use basic authentication, and this cannot be changed On POP3 and IMAP4 virtual servers on back-end servers, you can select basic authentication or Integrated Windows Authentication Integrated Windows Authentication cannot be specified on front-end HTTP virtual servers...14-20 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 ■ MSExchangeIS\V Largest Block Size When this counter drops below 32 MB, Exchange Server 2003 logs a warning in the Event Viewer application log (Event ID=9582) It logs an error if the counter drops below 16 MB ■ MSExchangeIS\VM Total 16MB Free Blocks You should monitor the trend on this counter... is working properly and that MX and A (host) records exist for a particular Exchange Server 2003 server or for all such servers in a domain You can, for example, use the nslookup – querytype=mx tailspintoys.com command to return all the MX records for the tailspintoys.com domain Lesson 3 Troubleshooting the Exchange Server 2003 Organization 14-31 Practice: Limiting Write and Delete Permissions to Public... other users Lesson 3 Troubleshooting the Exchange Server 2003 Organization 14-33 To configure permissions on a public folder store, perform the following actions: 1 Start Exchange System Manager 2 Navigate to Administrative Groups\First Administrative Group\Servers \Server0 1 \First Storage Group\Public Folder Store (Server0 1) 3 Right-click Public Folder Store (Server0 1), and then click Properties 4 On... access, DNS access, and the general health and interoperability of your Exchange Server 2003 organization 14-36 Chapter 14 Troubleshooting Microsoft Exchange Server 2003 Lesson 4: Troubleshooting Security Security troubleshooting can be a complex and difficult process Traffic can be filtered at a firewall, at a router, or at a virtual server If a particular type of traffic or traffic from a particular... lists ■ MSExchangeDSAccess This service allows Exchange access to Active Directory ■ MSExchangeIS This service allows access to the Information Store ■ MSExchangeMTA This service allows X.400 connectors to access the message transfer agent (MTA) ■ MSExchangeMU This service replicates Exchange configuration information changes to the IIS metabase ■ MSExchangeSA This counter records an entry when Exchange . Troubleshooting Microsoft Exchange Server 2003 Lesson 2: Troubleshooting Exchange Server 2003 Servers The performance of an Exchange Server 2003 server depends upon the efficiency of general server processes,. Troubleshooting Microsoft Exchange Server 2003 Lesson 3: Troubleshooting the Exchange Server 2003 Organization While some faults are restricted to specific Exchange Server 2003 servers, others. virtual server. Diagnostic Logging Diagnostic logging can assist in troubleshooting both virtual servers and the general health of an Exchange Server 2003 server and of the Exchange Server 2003