Exxhange SQL And IIS- P78 pps

362 Chapter 6 • Managing the Hub Transport Server Role Introduction to the Exchange Mail Flow Troubleshooter Tool If you’re experiencing mail fl ow issues in your organization, you can also give the new Exchange Mail Flow Troubleshooter a try. This diagnostic tool helps perform the following functions: ■ Starting with the mail fl ow symptoms, it moves customers through the correct troubleshooting path. ■ Provides easy access to various data sources that are required to troubleshoot problems with mail fl ow. ■ Automatically diagnoses the retrieved data and presents an analysis of the possible root causes. ■ Suggests corrective actions. ■ Provide guidance to help users manually diagnose the data where and when automation is not possible. In order to launch the Exchange Mail Flow Troubleshooter, perform the following steps: 1. Open the Exchange Management Console. 2. Select the Toolbox work center node. 3. Click the Exchange Mail Flow Troubleshooter icon, and then select Open Tool in the Action pane. When the tool has been launched, it will check to see whether any updates are available on Microsoft.com, and then bring you to the welcome screen. You then need to enter an identifying label for the analysis you’re about to perform, and then specify what symptoms you’re seeing. As you can see in Figure 6.35, you can choose between six different symptoms, and depending on which one you select, the tool will programmatically execute a set of troubleshooting steps to identify the root cause of the mail fl ow issue you’re experiencing. The tool automatically determines what set of data is required to troubleshoot the identifi ed symptoms and collects confi guration data, performance counters, event logs, and live tracing information from an Exchange server and other appropriate sources. The tool analyzes each subsystem to determine individual bottlenecks and component failures, and then aggregates the information to provide root cause analysis. TIP To view or manipulate message queues or individual messages via the Exchange Management Shell, use the Get-Queue and Get-Message cmdlets. Managing the Hub Transport Server Role • Chapter 6 363 Confi guring the Hub Transport Server as an Internet-Facing Transport Server One of the design goals for Exchange 2007 was to be as secure as possible, by default, in the same way that the Hub Transport server is confi gured to only accept messages from internal Exchange users, Exchange servers, and legacy Exchange servers. This means that the Hub Transport server doesn’t accept inbound messages sent from unauthenticated (untrusted) e-mail servers, which typically defi ne external e-mail servers on the Internet. Instead, it expects to receive inbound messages from the Internet via an Edge Transport server in the perimeter network. If you’re an Exchange administrator in a small organization, or if you’re primarily doing Exchange consulting for small shops, chances are IT budgets hinder you from deploying an Edge Transport server in the perimeter network, when transitioning to Exchange Server 2007 Figure 6.35 The Exchange Mail Flow Troubleshooter Tool 364 Chapter 6 • Managing the Hub Transport Server Role (especially if the environment will only consist of a single Exchange 2007 server). Luckily, it’s a pretty simple process to change this behavior since you just need to allow untrusted servers to deliver messages to the Hub Transport server. This is accomplished by enabling Anonymous users under the Permission Groups tab of the Default Receive connector. To get to this property page, you must do the following: 1. Open the Exchange Management Console. 2. Expand the Server Confi guration work center node, and then select Hub Transport. 3. Highlight the respective Hub Transport server in the Result pane, as shown in Figure 6.36. 4. Open the Properties page of the Default <servername> Receive Connector in the Wo r k pane. 5. Click the Permissions Groups tab, check Anonymous users and click OK, as shown in Figure 6.37. Figure 6.36 The Default Receive Connector in the Exchange Management Console Managing the Hub Transport Server Role • Chapter 6 365 Figure 6.37 The Permission Groups Tab on the Default Receive Connector Properties Page Although we haven’t covered the Edge Transport server yet, this server role is also the one that holds all the message hygiene features available in Exchange Server 2007. If you decide not to deploy an Edge Transport server in your perimeter network, you might wonder whether it’s possible to let the Internet-facing Hub Transport server take care of fi ltering out spam and other unwanted e-mail before it reaches your mailbox servers. The answer is yes it is; however, because there are not any anti-spam fi ltering agents installed on a Hub Transport server by default (since the Exchange Product group expects you to deploy an Edge Transport server in the perimeter network), you must do so 366 Chapter 6 • Managing the Hub Transport Server Role manually by running the install-AntispamAgents.ps1 script located in the Exchange 2007 scripts folder. This can be found under C:\Program Files\Microsoft\Exchange Server. To run this script, do the following: 1. Open the Exchange Management Shell. 2. Type CD “program fi les\microsoft\exchange server\scripts” and press Enter. 3. Run the install-AntispamAgents.ps1 script by typing .\install-AntispamAgents.ps1, and then pressing Enter, as shown in Figure 6.38. Figure 6.38 Installing the Anti-Spam Agents on the Hub Transport Server 4. Restart the Microsoft Exchange Transport service. 5. Close and re-open the Exchange Management Console in order for the change to be refl ected in the UI. We now have a new Anti-spam tab under the Hub Transport node beneath the Organization Confi guration work center, as shown in Figure 6.39. As you can see, all the anti-spam fi ltering agents normally found on an Edge Transport server are now listed here. For an explanation of each, see Chapter 7. . troubleshoot the identifi ed symptoms and collects confi guration data, performance counters, event logs, and live tracing information from an Exchange server and other appropriate sources. The. Troubleshooter icon, and then select Open Tool in the Action pane. When the tool has been launched, it will check to see whether any updates are available on Microsoft.com, and then bring you. analysis you’re about to perform, and then specify what symptoms you’re seeing. As you can see in Figure 6.35, you can choose between six different symptoms, and depending on which one you select,