<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='StartPage.xsl'?><!--
//  Copyright (C) 2007 Microsoft Corporation.  All rights reserved.
//  The xml file that describes the content of End-to-End Scenario start page.
//  WARNING: THIS FILE IS SIGNED, ANY CHANGE MADED IN IT WILL BREAK ITS FUNCTIONALITY.
--><startpage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="StartPage.xsd">
  <_locDefinition>
    <_locDefault _loc="locNone"/>
    <_locTag _loc="locData">description</_locTag>
    <_locTag _loc="locData">text</_locTag>
    <_locTag _loc="locData">title</_locTag>
  </_locDefinition>
  <title _locID="TITLE">Exchange Server 2007 End-to-End Scenario</title>
  <groups>
    <!--This is scenarios/features that apply to All Exchange Servers-->
    <group applyOn="">
      <icon>ServerConfiguration</icon>
      <text _locID="G6_TEXT">All Exchange Servers</text>
      <links>
        <!--This link is for Monitoring resources-->
        <link>
          <text _locID="G6_L1_TEXT">Configure Monitoring for your Exchange Servers</text>
          <action>
            <name>ShowHelpTopic</name>
            <argument>exchhelp.chm::/html/88185dec-c376-48d9-b132-99a08d69e41d.htm</argument>
          </action>
          <description _locID="G6_L1_DESCRIPTION">Monitoring the availability, configuration, and performance of your Exchange servers helps you proactively solve problems and minimize the impact to clients.</description>
        </link>
      </links>
    </group>
    <group applyOn="Mailbox">
      <icon>MailboxServer</icon>
      <text _locID="G1_TEXT">Mailbox </text>
      <links>
        <!-- This link is for Disaster Recovery-->
        <link>
          <text _locID="G1_L2_TEXT">Implement Best Practices for Disaster Recovery</text>
          <action>
            <name>ShowHelpTopic</name>
            <argument>exchhelp.chm::/html/e17a4781-19ac-4d87-88d9-fcb58c0b1606.htm</argument>
          </action>
          <description _locID="G1_L2_DESCRIPTION">An important step in creating a disaster recovery strategy is to consider ways that you can avoid, or minimize the impact of, a disaster. You can take several actions to help prevent or minimize the effects of disasters such as hardware failures or power outages.</description>
        </link>
        <!--This is the link for configuring the SCL threshold for the Junk E-mail folder-->
        <link>
          <text _locID="G5_L4_TEXT">Configure the Spam Confidence Level (SCL) for Users' Junk E-mail Folder Threshold</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L4_S1_TEXT">Step 1: Set the global SCL Junk E-mail folder threshold</text>
                <description _locID="G5_L4_S1_DESCRIPTION">The default global SCL threshold for sending e-mail to users’ Junk E-mail folder is 8. For example, if you want to change this default value to "6":</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S1_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S1_SS2_TEXT">2. Run the following command: Set-OrganizationConfig –SCLJunkThreshold:6</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L4_S2_TEXT">Step 2: (Optional) Set per mailbox override thresholds</text>
                <description _locID="G5_L4_S2_DESCRIPTION">The SCL threshold for sending mail to users’ Junk E-mail folder can be set on a per user basis, overriding the organization-wide setting. For example, if you want to set this override on a user’s mailbox to "6":</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S2_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS2_TEXT">2. Run the following command: Set-Mailbox [Username] -SCLJunkThreshold:6 -SCLJunkEnabled:$True</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS3_TEXT">3. Read more about how to configure anti-spam features on a mailbox.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/868d7fd8-e817-46ba-9b67-edf2f50b9494.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L4_DESCRIPTION">You can adjust the global SCL Junk E-mail folder threshold used by the Microsoft Exchange Information Store service to send e-mail to a user's Junk E-mail folder. You can also specify an override on each user's mailbox for the SCL setting.</description>
        </link>
        <!-- This link is for ELC Configuration-->
        <link>
          <text _locID="G1_L1_TEXT">Configure Messaging Records Management (MRM)</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G1_L1_S1_TEXT">Step 1: (Optional) Create a new managed default folder or a new managed custom folder</text>
                <description _locID="G1_L1_S1_DESCRIPTION">Managed folders are mailbox folders that have messaging records management (MRM) enabled. There are two types of managed folders: custom folders (folders that you create for placement in a user's mailbox--for example, a folder named "Legal Documents"), and default folders (folders that are in user's mailbox by default, such as the Inbox folder).</description>
                <substeps>
                  <description _locID="G1_L1_S1_SS_DESCRIPTION">To create managed folders: </description>
                  <substep>
                    <text _locID="G1_L1_S1_SS1_TEXT">1. For managed default folders: Go to Managed Default Folders.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS2_TEXT">Note: A complete set of managed default folders are created when Exchange is installed. You don't have to create additional default folders unless you want multiple copies of a folder, each with different settings (for example, three instances of the Inbox folder, which retain mail for 30, 60, or 90 days).</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS3_TEXT">2. In the action pane, click "New Managed Default Folder".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS4_TEXT">3. For managed custom folders: Go to Managed Custom Folders.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcOrgFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS5_TEXT">4. In the action pane, click "New Managed Custom Folder".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS6_TEXT">5. Complete the New Managed Custom Folder wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L1_S2_TEXT">Step 2: Configure content settings for the managed folder</text>
                <description _locID="G1_L1_S2_DESCRIPTION">The content settings that you apply to a managed folder control retention policies that limit the lifespan of items and allow items to be journaled (copied) to a location outside the mailbox. They also control how long selected items within the managed folder are retained and what happens to those items when they exceed the specified retention period.</description>
                <substeps>
                  <description _locID="G1_L1_S2_SS_DESCRIPTION">To create and apply content settings to a managed folder:</description>
                  <substep>
                    <text _locID="G1_L1_S2_SS1_TEXT">1. For managed default folders: Go to Managed Default Folders.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS2_TEXT">2. For managed custom folders: Go to Managed Custom Folders.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcOrgFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS3_TEXT">3. In the list of folders, right-click the folder for which you want to create and apply managed content settings.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS4_TEXT">4. In the action pane, click "New Managed Content Settings".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS5_TEXT">5. Complete the New Managed Content Settings wizard.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS6_TEXT">Note: To create additional content settings that control other types of items in the folder , you can use the New Managed Content Settings wizard repeatedly.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L1_S3_TEXT">Step 3: Create a managed folder mailbox policy</text>
                <description _locID="G1_L1_S3_DESCRIPTION">Managed folder mailbox policies collect managed folders into logical groupings. When you apply a mailbox policy to a user's mailbox, all the managed folders that are linked to that policy are applied to the user's mailbox in a single step.</description>
                <substeps>
                  <description _locID="G1_L1_S3_SS_DESCRIPTION">To configure a managed folder mailbox policy:</description>
                  <substep>
                    <text _locID="G1_L1_S3_SS1_TEXT">1. Go to Managed Folder Mailbox Policies.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\ElcMailboxPoliciesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S3_SS2_TEXT">2. In the action pane, click "New Managed Folder Mailbox Policy".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S3_SS3_TEXT">3. Complete the New Managed Folder Mailbox Policy wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L1_S4_TEXT">Step 4: Apply the managed folder mailbox policy to a user’s mailbox</text>
                <description _locID="G1_L1_S4_DESCRIPTION">When you apply a managed folder mailbox policy to users' mailboxes, all the managed folders in the policy are applied to those mailboxes at one time.</description>
                <substeps>
                  <description _locID="G1_L1_S4_SS_DESCRIPTION">To apply a managed folder mailbox policy to users' mailboxes:</description>
                  <substep>
                    <text _locID="G1_L1_S4_SS1_TEXT">1. Go to Recipient Configuration.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS2_TEXT">2. Click “Mailbox”.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS3_TEXT">3. In the result pane, select a user to whom you want to apply the policy.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS4_TEXT">4. In the action pane, click "Properties”.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS5_TEXT">5. Click the "Mailbox Settings” tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS6_TEXT">6. Click "Messaging Records Management".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS7_TEXT">7. Click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS8_TEXT">8. Select the "Managed folder mailbox policy" check box.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS9_TEXT">9. Click "Browse," and then select the policy to apply (created in Step 3).</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS10_TEXT">10. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L1_S5_TEXT">Step 5: Schedule the managed folder assistant</text>
                <description _locID="G1_L1_S5_DESCRIPTION">The managed folders, content settings, and policies that you create are applied to users' mailboxes only when the managed folder assistant runs. The managed folder assistant is not enabled by default, and the times that it runs must be scheduled individually on every Mailbox server.</description>
                <substeps>
                  <description _locID="G1_L1_S5_SS_DESCRIPTION">To configure the schedule for the managed folder assistant:</description>
                  <substep>
                    <text _locID="G1_L1_S5_SS1_TEXT">1. Go to Mailbox Server Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS2_TEXT">2. In the result pane, select the server on which you want to schedule the managed folder assistant.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS4_TEXT">4. Click the "Messaging Records Management" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS5_TEXT">5. Click “Customize”.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS6_TEXT">6. Select the times that you want the managed folder assistant to run.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS7_TEXT">7. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L1_DESCRIPTION">Messaging records management (MRM) is the records management technology in Exchange 2007 that helps organizations to reduce the legal risks that are associated with e-mail and other communications. MRM makes it easier to keep messages that are needed to comply with company policy, government regulations, or legal needs, and to remove content that has no legal or business value. </description>
        </link>
      </links>
    </group>
    <group applyOn="ClientAccess">
      <icon>ClientAccessServer</icon>
      <text _locID="G2_TEXT">Client Access</text>
      <links>
        <!-- This link is for Outlook Anywhere-->
        <link>
          <text _locID="G2_L1_TEXT">Enable Outlook Anywhere</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G2_L1_S1_TEXT">Step 1: Install the Windows RPC over HTTP Proxy component</text>
                <description _locID="G2_L1_S1_DESCRIPTION">You must configure RPC over HTTP before Outlook Anywhere can be used.</description>
                <substeps>
                  <description _locID="G2_L1_S1_SS_DESCRIPTION">To install the Windows RPC over HTTP Proxy component:</description>
                  <substep>
                    <text _locID="G2_L1_S1_SS1_TEXT">1. Open Control Panel, and then click “Add or Remove Programs”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS2_TEXT">2. Click “Add/Remove Windows Components”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS3_TEXT">3. Select the “Networking Services” component and select “Details”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS4_TEXT">4. Select the “RPC over HTTP Proxy” check box and then click “OK”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS5_TEXT">5. Complete the Windows Component wizard to add the RPC over HTTP Proxy component.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S2_TEXT">Step 2: Complete the "Configure SSL for your Client Access server" steps on the "Finalize Deployment" tab for Client Access</text>
                <description _locID="G2_L1_S2_DESCRIPTION">Make sure that you have completed the steps listed in the “Configure SSL for your Client Access server” section on the “Finalize Deployment” tab for the “Rpc” virtual directory. For more information, see the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L1_S2_SS1_TEXT">- Managing Client Access Security.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/5341bc72-715a-4489-905e-6daf8ae8a7f5.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S3_TEXT">Step 3: Enable Outlook Anywhere on an Exchange Client Access server</text>
                <description _locID="G2_L1_S3_DESCRIPTION">If you have enabled Outlook Anywhere on a Client Access server, Outlook 2007 users whose mailboxes are located on Exchange 2007 servers that are running the Mailbox server role will be able to use the Windows RPC over HTTP networking technology to connect to Exchange from the Internet.</description>
                <substeps>
                  <description _locID="G2_L1_S3_SS_DESCRIPTION">To enable Outlook Anywhere on the Exchange Client Access server:</description>
                  <substep>
                    <text _locID="G2_L1_S3_SS1_TEXT">1. Go to Exchange Client Access Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ClientAccessNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS2_TEXT">2. Select the Client Access server that you will configure for Outlook Anywhere.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS3_TEXT">3. In the action pane, click “Enable Outlook Anywhere”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS4_TEXT">4. Complete the Enable Outlook Anywhere wizard.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS5_TEXT">5. After you complete the wizard, there may be a delay as long as 15 minutes before your users will be able to use Outlook Anywhere.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S4_TEXT">Step 4: Enable Basic authentication for the Exchange Web Services (EWS) virtual directory</text>
                <description _locID="G2_L1_S4_DESCRIPTION">This will enable Outlook clients outside the firewall to use Basic authentication to access the Availability service for free/busy information. This is required for deployments that do not use ISA Server 2006 or for deployments in which ISA Server 2006 or later versions are not configured to allow NTLM authentication.</description>
                <substeps>
                  <description _locID="G2_L1_S4_SS_DESCRIPTION">To enable Basic authentication for the EWS virtual directory:</description>
                  <substep>
                    <text _locID="G2_L1_S4_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS2_TEXT">2. Run the following command, replacing identity with the actual name of your server and the externalurl with the actual URL: set-webservicesvirtualdirectory -identity "MYSERVER\EWS (Default Web Site)" -externalurl https://exchange.contoso.com/EWS/Exchange.asmx  -BasicAuthentication:$True</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G2_L1_DESCRIPTION">Outlook Anywhere enables clients to connect to Microsoft Exchange from any network that has Internet access.</description>
        </link>
        <!-- This link is for Configuring Exchange 2007 for Internet Access by Outlook 2007-->
        <link>
          <text _locID="G2_L2_TEXT">Configure the Exchange 2007 Autodiscover Service for Internet Access by Outlook 2007</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G2_L2_S1_TEXT">Step 1: Complete the "Configure SSL for your Client Access server" steps on the "Finalize Deployment" tab for Client Access</text>
                <description _locID="G2_L2_S1_DESCRIPTION">When accessing Exchange 2007 over the Internet, Outlook 2007 requires that the certificate that is configured for Secure Sockets Layer (SSL) encryption on either Internet Information Services (IIS) or the ISA Server computer is trusted implicitly or explicitly by the client computer. The easiest way to obtain a trusted certificate is to request one from a third-party certification authority (CA). For more information about how to do this, complete the steps that are listed in the "Configure SSL for your Client Access server" section on the “Finalize Deployment” tab. For more information, see the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S1_SS1_TEXT">- Managing Client Access Security.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/5341bc72-715a-4489-905e-6daf8ae8a7f5.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L2_S2_TEXT">Step 2: Configure the external URLs for Exchange services</text>
                <description _locID="G2_L2_S2_DESCRIPTION">Outlook 2007 retrieves the URLs for the available Microsoft Exchange services from the Autodiscover service. The external URLs must be configured for each component's virtual directory, as follows:</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S2_SS1_TEXT">To configure the Outlook Anywhere external URL, complete the "Enable Outlook Anywhere" steps for Client Access, and then specify an External host name. Alternatively, in the Exchange Management Shell, run the following command, replacing mail.contoso.com with the external URL for your Outlook Anywhere clients: Enable-OutlookAnywhere -Server CAS01 -ExternalHostname "mail.contoso.com" -ExternalAuthenticationMethod "Basic" -SSLOffloading:$False</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS2_TEXT">To configure the Offline Address Book external URL, complete the "Configure Offline Address Book (OAB) Distribution for Outlook 2007 clients” steps for Mailbox on the "Finalize Deployment" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS3_TEXT">To configure the Unified Messaging external URL, do the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS4_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS5_TEXT">2. Run the following command, replacing identity with the actual name of your server and externalurl with the actual URL: set-UMvirtualdirectory -identity "MYSERVER\UnifiedMessaging (Default Web Site)" -externalurl https://exchange.contoso.com/UnifiedMessaging/Service.asmx  -BasicAuthentication:$True</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS6_TEXT">To configure the Exchange Web Services external URL, do the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS7_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS8_TEXT">2. Run the following command, replacing identity with the actual name of your server and externalurl with the actual URL: set-webservicesvirtualdirectory -identity "MYSERVER\EWS (Default Web Site)" -externalurl https://exchange.contoso.com/EWS/Exchange.asmx  -BasicAuthentication:$True</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G2_L2_DESCRIPTION">The Autodiscover service enables users who are running Outlook 2007 and supported mobile devices to locate the profile settings that are required to connect to Microsoft Exchange. The Autodiscover service maintains any profile settings that are required to connect to Exchange 2007.</description>
        </link>
      </links>
    </group>
    <group applyOn="HubTransport">
      <icon>BridgeheadServer</icon>
      <text _locID="G0_TEXT">Hub Transport</text>
      <links>
        <!--This link is for showing Safelist Aggregation Data Help-->
        <link>
          <text _locID="G0_L6_TEXT">Replicate Safelist Aggregation Data</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G0_L6_S1_TEXT">Step 1: Configure safelist aggregation</text>
                <description _locID="G0_L6_S1_DESCRIPTION">The following list shows the high-level steps required to configure safelist aggregation. Detailed information for each step can be found in the topic linked at the end of this step.</description>
                <substeps>
                  <substep>
                    <text _locID="G0_L6_S1_SS1_TEXT">The following two steps must be completed on a computer in the Exchange organization that is connected to the Active Directory directory service:</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS2_TEXT">1. Use the Update-Safelist cmdlet to update safelist information for Outlook users.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS3_TEXT">2. Schedule periodic updates of safelist aggregation to make sure that the most up-to-date safelist aggregation information is in Active Directory.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS4_TEXT">The following two steps must be completed the computer on which the Edge Transport server role is installed:</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS5_TEXT">1. (Optional) Verify that the Microsoft Exchange EdgeSync service is replicating safelist aggregation data to Active Directory Application Mode (ADAM).</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS6_TEXT">2. Verify that content filtering is enabled on the servers where you are running anti-spam features and that safelist aggregation is functioning correctly.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS7_TEXT">For more information about each of these steps, see the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS8_TEXT">- How to Configure Safelist Aggregation.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/5ac17168-f411-4cb7-ae98-ebefb865b210.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G0_L6_S2_TEXT">Step 2: Read more about safelist aggregation</text>
                <description _locID="G0_L6_S2_DESCRIPTION">For more information about safelist aggregation, see the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G0_L6_S2_SS1_TEXT">- Safelist Aggregation.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/f05430a0-0405-4b65-a18d-18c9e86a13c4.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G0_L6_DESCRIPTION">Safelist aggregation refers to a set of anti-spam functionality that is shared across Outlook and Microsoft Exchange. Safelist aggregation can help reduce the instances of false-positives in anti-spam filtering that is performed by the Edge Transport server. </description>
        </link>
        <!--This is the link for configuring E-mail Quarantine-->
        <link>
          <text _locID="G0_L8_TEXT">Configure Spam Quarantine</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G0_L8_S1_TEXT">Step 1: Verify that content filtering is enabled</text>
                <description _locID="G0_L8_S1_DESCRIPTION">You must enable content filtering before you can apply spam quarantine. By default, the Content Filter agent filters all external messages that come through all Receive connectors on the computer on which the Content Filter agent is enabled. This step must be performed on the Edge Transport server.</description>
                <substeps>
                  <description _locID="G0_L8_S1_SS_DESCRIPTION">On the Edge Transport server that will have content filtering enabled:</description>
                  <substep>
                    <text _locID="G0_L8_S1_SS1_TEXT">1. Go to Anti-spam management.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S1_SS2_TEXT">2. Select Content Filtering.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S1_SS3_TEXT">3. Verify that the status is "Enabled".</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S1_SS4_TEXT">4. If it is not enabled, in the action pane, click "Enable".</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G0_L8_S2_TEXT">Step 2: Create a dedicated database for the spam quarantine mailbox</text>
                <description _locID="G0_L8_S2_DESCRIPTION">You must create a spam quarantine mailbox before you can enable the feature. We recommend that you create a dedicated database for the spam quarantine mailbox. The spam quarantine mailbox should have a large database, because if the storage quota limit is reached, messages will be lost. This step must be performed on a computer in the Exchange organization.</description>
                <substeps>
                  <description _locID="G0_L8_S2_SS_DESCRIPTION">On any server role in the Exchange organization or workstation with the console installed, create a dedicated database:</description>
                  <substep>
                    <text _locID="G0_L8_S2_SS1_TEXT">1. Go to Database Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode\StorageGroupsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S2_SS2_TEXT">2. Select the storage group in which you want to create the database.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S2_SS3_TEXT">3. In the action pane, click "New Mailbox Database".</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S2_SS4_TEXT">4. Complete the New Mailbox Database wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G0_L8_S3_TEXT">Step 3: Create the spam quarantine mailbox</text>
                <description _locID="G0_L8_S3_DESCRIPTION">You must create a mailbox that you can use as the spam quarantine mailbox with an appropriate messaging records management policy that includes mailbox size and the number of days that messages will be saved before they are deleted. This step must be performed on a computer in the Exchange organization.</description>
                <substeps>
                  <description _locID="G0_L8_S3_SS_DESCRIPTION">On any server role in the Exchange organization or workstation with the console installed, create a dedicated database:</description>
                  <substep>
                    <text _locID="G0_L8_S3_SS1_TEXT">1. Go to Recipient Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S3_SS2_TEXT">2. In the action pane, click "New Mailbox".</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S3_SS3_TEXT">3. Select the dedicated mailbox database that you created in Step 2 to create the mailbox on.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S3_SS4_TEXT">4. Complete the New Mailbox wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G0_L8_S4_TEXT">Step 4: Configure content filtering to quarantine messages</text>
                <description _locID="G0_L8_S4_DESCRIPTION">You must specify the SCL quarantine threshold and spam quarantine mailbox in the content filtering configuration. This step must be performed on the Edge Transport server.</description>
                <substeps>
                  <description _locID="G0_L8_S4_SS_DESCRIPTION">On the Edge Transport server that will have content filtering enabled:</description>
                  <substep>
                    <text _locID="G0_L8_S4_SS1_TEXT">1. Go to Anti-spam Management.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS2_TEXT">2. Select Content Filtering.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS4_TEXT">4. Select the "Action" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS5_TEXT">5. Select the check box for "Quarantine messages that have a SCL rating greater than or equal to:".</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS6_TEXT">6. Specify the spam quarantine mailbox e-mail address for the spam quarantine mailbox you created in Step 3. Click "OK".</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G0_L8_S5_TEXT">Step 5: Read more about how to configure spam quarantine</text>
                <description _locID="G0_L8_S5_DESCRIPTION">For more information about how to manage the spam quarantine mailbox and how to set the SCL threshold, see the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G0_L8_S5_SS1_TEXT">- Adjusting the Spam Confidence Level Threshold.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/0009b4af-be6d-41d2-98bc-b5487272c74a.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S5_SS2_TEXT">- How to Recover Quarantined Messages from the Spam Quarantine Mailbox.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/7a86bfde-f868-4689-bdec-5f01e52b510d.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G0_L8_DESCRIPTION">When you use anti-spam filters, there is always a chance that the filters will identify false positives. In the context of spam filtering, a false positive exists when a spam filter incorrectly identifies a message from a legitimate sender as spam. In Exchange 2007, you can reduce the risk of false positives and the potential loss of valuable messages if you use the Content Filter agent to quarantine messages that have been identified as potential spam.</description>
        </link>
      </links>
    </group>
    <group applyOn="UnifiedMessaging">
      <icon>UnifiedMessagingServer</icon>
      <text _locID="G4_TEXT">Unified Messaging</text>
      <links>
        <!--This link is for configuring Out Dialing-->
        <link>
          <text _locID="G4_L1_TEXT">Enable Outdialing</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L1_S1_TEXT">Step 1: Create dialing rule groups</text>
                <description _locID="G4_L1_S1_DESCRIPTION">You can create dialing rule groups to specify the kinds of calls that users who are associated with a UM mailbox policy, dial plan, or auto attendant can make. The dialing rule groups are stored on the dial plan that is associated with the UM mailbox policy, dial plan, or auto attendant. You can create two types of dialing rule groups. One is used for in-country/region calls and the other is used for international calls.</description>
                <substeps>
                  <description _locID="G4_L1_S1_SS_DESCRIPTION">To create dialing rule groups:</description>
                  <substep>
                    <text _locID="G4_L1_S1_SS1_TEXT">1. Go to UM Dial Plan Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\DialPlansResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS2_TEXT">2. Select the UM dial plan for which you want to create dialing rule groups.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS3_TEXT">3. Click the “Dialing Rule Groups” tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS4_TEXT">4. To create a new dialing rule entry for an in-country/region dialing rule group, click “Add” under In-Country/Region Rule Groups.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS5_TEXT">5. To create a new dialing rule entry for an International dialing rule group, click “Add” under International Rule Groups.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS6_TEXT">6. Read more about the values to use to create the dialing rule entry.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/29a635b1-059a-4044-bfde-c65bf5c2c0e5.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L1_S2_TEXT">Step 2: Configure dialing restrictions on a UM mailbox policy</text>
                <description _locID="G4_L1_S2_DESCRIPTION">You can select from the list of dialing rule groups that are created in Step 1 and apply them to the UM mailbox policy that you are creating. This lets users who are associated with this UM mailbox policy place calls to people in their own personal contacts or the Microsoft Exchange global address list, or to external phone numbers whose telephone numbers match the patterns defined in the dialing rule group that you selected.</description>
                <substeps>
                  <description _locID="G4_L1_S2_SS_DESCRIPTION">You can configure dialing restrictions on UM dial plans, auto attendants, or UM mailbox policies. To configure dialing restrictions on a UM mailbox policy:</description>
                  <substep>
                    <text _locID="G4_L1_S2_SS1_TEXT">1. Go to UM Mailbox Policy Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\UMMailboxPoliciesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS2_TEXT">2. Select the UM mailbox policy for which you want to configure dialing restrictions.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS4_TEXT">4. Click the "Dialing Restrictions" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS5_TEXT">5. Under "Select allowed in-country/region rule groups from dial plan", click "Add".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS6_TEXT">6. Select one or more of the in-country/region rule groups that you defined on the UM dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS7_TEXT">7. To enable users who are associated with this UM mailbox policy to dial certain international numbers, complete the following three steps:</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS8_TEXT">a. Under "Select allowed international rule groups from dial plan", click "Add".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS9_TEXT">b. Select one or more of the international rule groups that you defined on the UM dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS10_TEXT">c. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L1_DESCRIPTION">You must configure outdialing to allow calls to be transferred to users outside a UM dial plan.</description>
        </link>
        <!--This link is for Enabling Mutual-TLS between gateways/IP-PBXs -->
        <link>
          <text _locID="G4_L2_TEXT">Enable Mutual TLS between IP Gateways or IP PBXs and an Exchange Unified Messaging Server</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L2_S1_TEXT">Step 1: Enable mutual TLS support on both the IP gateways or SIP-enabled IP PBXs and Unified Messaging servers</text>
                <description _locID="G4_L2_S1_DESCRIPTION">Mutual TLS requires that both the IP gateways or SIP-enabled IP PBXs and the Unified Messaging server be issued an X.509 certificate that is signed by a trusted certification authority. To do this, you can use a trusted certificate from a third-party certification authority, a certificate from a public key infrastructure (PKI) certification authority, or a self-signed certificate.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S1_SS1_TEXT">Note: For information about how to configure mutual TLS on an IP gateway or a SIP-enabled IP PBX, see the documentation that is provided by the IP gateway or SIP-enabled IP PBX vendor.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S1_SS2_TEXT">For more information about Unified Messaging VoIP security, see Understanding Unified Messaging VoIP Security.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/a8aac6d2-bf85-4d2e-ba44-f3560e878b52.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S2_TEXT">Step 2: Enable VoIP security on the dial plan</text>
                <description _locID="G4_L2_S2_DESCRIPTION">You must enable the VoIP security setting on an existing UM dial plan. To enable VoIP security, you must use the SIP Secured or Secured setting on the dial plan. If you have not yet created a dial plan, complete the "Configure Unified Messaging" steps on the Finalize Deployment tab before you complete this step.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S2_SS1_TEXT">1. Go to UM Dial Plan Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\DialPlansResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS2_TEXT">2. Select the UM dial plan that will use VoIP security.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS3_TEXT">3. Click "Properties" in the action pane.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS4_TEXT">4. On the “General” tab, click the “VoIP security” drop-down list, and then select SIP Secured or Secured.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS5_TEXT">5. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S3_TEXT">Step 3: Update the UM IP gateway to point to the IP gateway or SIP-enabled IP PBX that will be using VoIP security</text>
                <description _locID="G4_L2_S3_DESCRIPTION">The UM IP gateway must specify the FQDN of the IP gateway or SIP-enabled IP PBX. Therefore, the FQDN must be updated on the existing IP gateway that was linked by using the UM hunt group to the SIP Secured or Secured dial plan in Step 2. If you have not created a UM IP gateway yet, complete the "Configure Unified Messaging" steps on the Finalize Deployment tab before you complete this step.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S3_SS1_TEXT">1. Go to UM IP Gateway Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\umIpGatewaysResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS2_TEXT">2. Select the UM IP gateway that is linked to the dial plan that will be using VoIP security in Step 2.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS3_TEXT">3. In the action pane, click "Properties". </text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS4_TEXT">4. Click the fully qualified domain name (FQDN) option button and specify the FQDN of the IP gateway or SIP-enabled IP PBX.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS5_TEXT">5. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S4_TEXT">Step 4: Verify that the Unified Messaging server is associated with the dial plan that will be using VoIP security</text>
                <description _locID="G4_L2_S4_DESCRIPTION">Each Unified Messaging server can support multiple dial plans and can also be associated with dial plans that are configured with different VoIP security settings.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S4_SS1_TEXT">1. Go to Unified Messaging Server Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>UnifiedMessagingNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS2_TEXT">2. Select the Unified Messaging server that you are associating with the dial plan that is configured to use VoIP security.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS3_TEXT">3. In the action pane, click "Properties". </text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS4_TEXT">4. Click the "UM Settings" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS5_TEXT">5. Verify that this Unified Messaging server is associated with the dial plan that is configured to use VoIP security.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L2_DESCRIPTION">Exchange Unified Messaging supports the use of mutual TLS to authenticate the IP gateways and SIP-enabled IP PBXs and to encrypt SIP only or SIP and RTP traffic. It encrypts the SIP only or SIP and RTP traffic by using the TLS mechanism that is provided by the underlying Windows Server 2003 platform.</description>
        </link>
        <!--This link is for configuring Auto Attendant-->
        <link>
          <text _locID="G4_L3_TEXT">Create and Configure an Auto Attendant</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L3_S1_TEXT">Step 1: Plan how the auto attendants and prompts will be used</text>
                <substeps>
                  <substep>
                    <text _locID="G4_L3_S1_SS1_TEXT">1. Decide on the menu keys or voice files that will be used by callers who access the auto attendant, and the actions that will be associated with the menu keys. For example: Press 1 to transfer to extension 54321, and press 2 to go to a second-level menu or another auto attendant. From the second-level menu, menu key 1 will transfer to extension 54322, and menu key 9 will return the caller to the opening menu.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S1_SS2_TEXT">2. Record the various custom greetings and prompts that callers will hear when they call in to the auto attendant. For example: “Welcome to Contoso.” as a welcome greeting, and “For sales, press 1. For more options, press 2.” for the opening menu prompt. Each recording must be a .wav file that uses the PCM, 8 kilohertz (kHz), 16-bit, monaural format.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S2_TEXT">Step 2: Create the parent or top-level auto attendant</text>
                <description _locID="G4_L3_S2_DESCRIPTION">A top-level auto attendant is one that can be linked to other auto attendants or can be used to transfer a caller to another extension number. It will answer incoming calls to one or more extensions that have been configured.</description>
                <substeps>
                  <description _locID="G4_L3_S2_SS_DESCRIPTION">To create auto attendants:</description>
                  <substep>
                    <text _locID="G4_L3_S2_SS1_TEXT">1. Go to UM Auto Attendant Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\AutoAttendantResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S2_SS2_TEXT">2. In the action pane, click "New UM Auto Attendant".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S2_SS3_TEXT">3. Complete the New UM Auto Attendant wizard. Make sure that you select the "Create auto attendant as enabled" check box.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S3_TEXT">Step 3: Create a child or second-level auto attendant</text>
                <description _locID="G4_L3_S3_DESCRIPTION">Repeat the steps in Step 2 to create a new second-level auto attendant. No extension number is needed. A second-level auto attendant is one that can have no extension configured. If an extension is not configured, callers can only reach it from a menu option that is configured on the parent or top-level auto attendant or on another child auto attendant.</description>
                <substeps>
                  <description _locID="G4_L3_S3_SS_DESCRIPTION">To create a child or second-level auto attendant:</description>
                  <substep>
                    <text _locID="G4_L3_S3_SS1_TEXT">1. Go to UM Auto Attendant Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\AutoAttendantResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S3_SS2_TEXT">2. Repeat the steps in Step 2 to create a second-level auto attendant. An extension number may not be required.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S4_TEXT">Step 4: Configure the parent or top-level auto attendant</text>
                <description _locID="G4_L3_S4_DESCRIPTION">This step and step 5 will result in a pair of auto attendants that together give the caller the interface that was described in the example in step 1. If the language set for the auto attendants is English, you can also speech-enable them. If you do this, callers will also be able to navigate the menu options by using voice inputs. You may want to modify the prompts accordingly. You can add alternative names and phrases for a menu option in its Key Mapping Entry dialog box.</description>
                <substeps>
                  <description _locID="G4_L3_S4_SS_DESCRIPTION">To configure the top-level auto attendant:</description>
                  <substep>
                    <text _locID="G4_L3_S4_SS1_TEXT">1. Go to UM Auto Attendant Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\AutoAttendantResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS2_TEXT">2. Select the top-level auto attendant.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS4_TEXT">4. Click the "Greetings" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS5_TEXT">5. Click "Modify" next to the Business hours greeting, click the "Use custom greeting file" option button, and then click "Browse" to select the .wav file that contains the welcome greeting that was created in step 1.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS6_TEXT">6. Click "OK" to save the Business hours greeting.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS7_TEXT">7. Complete the previous steps for the "Business hours main menu prompt" greeting.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS8_TEXT">8. Click the "Features" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS9_TEXT">9. Specify an "Operator Extension" unless you have already specified the same extension for the dial plan operator.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS10_TEXT">10. Select the "Allow transfer to operator during business hours" check box. This lets callers transfer by pressing 0.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS11_TEXT">11. Click the "Key Mapping" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS12_TEXT">12. Select the "Enable business hours key mapping" check box.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS13_TEXT">13. Click "New" to define the behavior for the 1 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS14_TEXT">14. In the Key Mapping Entry dialog box, click the "Presses this key" option button and enter 1 in the field. Select the "Perform this additional action" check box, click the "Transfer to extension" option button, and then enter the appropriate extension. Click "OK" to save the mapping for the 1 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS15_TEXT">15. Click "New" to define the behavior for the 2 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS16_TEXT">16. In the Key Mapping Entry dialog box, click the "Presses this key" option button and enter 2 in the field. Select the "Perform this additional action" check box, click the "Run auto attendant" option button, and then click "Browse" to select the second-level auto attendant. Click "OK" to save the mapping for the 2 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS17_TEXT">17. Click "OK" to save your changes to the top-level auto attendant.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S5_TEXT">Step 5: Configure a child or second-level auto attendant</text>
                <description _locID="G4_L3_S5_DESCRIPTION">Repeat the steps in step 4 to configure the second-level auto attendant as defined by the plan that was created in step 1.</description>
                <substeps>
                  <description _locID="G4_L3_S5_SS_DESCRIPTION">To configure a second-level auto attendant:</description>
                  <substep>
                    <text _locID="G4_L3_S5_SS1_TEXT">1. Go to UM Auto Attendant Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\AutoAttendantResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S5_SS2_TEXT">2. Repeat the steps in step 4 for the second-level auto attendant. However, change them to make them relevant for the second-level auto attendant to comply with the plan defined in step 1.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L3_DESCRIPTION">The UM auto attendant is a set of voice prompts or .wav files that are played to callers in place of a human operator or receptionist when they call in to an organization that has Exchange 2007 Unified Messaging.</description>
        </link>
      </links>
    </group>
    <group applyOn="Edge">
      <icon>EdgeServerConfiguration</icon>
      <text _locID="G5_TEXT">Edge Transport</text>
      <links>
        <!--This link is for Exchange Anti-Spam Update Service-->
        <link>
          <text _locID="G5_L7_TITLE">Enable the Microsoft Exchange Anti-spam Update Service</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L7_S1_TEXT">Step 1: Enable the Microsoft Exchange Anti-spam Update service</text>
                <description _locID="G5_L7_S1_Desc">To enable the Microsoft Exchange Anti-spam Update service:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L7_S1_SS1_TEXT">1. Go to Anti-spam Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L7_S1_SS2_TEXT">2. Select the server on which the Microsoft Exchange Anti-spam Update service is to be configured.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L7_S1_SS3_TEXT">3. In the action pane, click "Enable Anti-spam Updates".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L7_S1_SS4_TEXT">4. Complete the Enable Anti-spam Updates wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L7_DESC">To make sure that your anti-spam services have the most up-to-date data and signatures, you can install and enable the Microsoft ForeFront Security for Exchange Server update service. This enhanced update service automatically checks Microsoft Update daily and downloads new anti-spam data file updates, IP Reputation Service updates, and anti-spam signature updates. Forefront Security for Exchange Server anti-spam update service is a premium feature that requires the Exchange Enterprise Client Access License (CAL) for each user mailbox, if enabled.</description>
        </link>
        <!--This link is for Configuring the list of internal SMTP Servers-->
        <link>
          <text _locID="G5_L5_TEXT">Configure the List of Internal SMTP Servers</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L5_S1_TEXT">Configure the list of internal SMTP servers</text>
                <description _locID="G5_L5_S1_DESCRIPTION">If your Edge Transport servers are subscribed into the Exchange organization, you must perform the following tasks on a Hub Transport server. The configuration is stored in Active Directory and then the Microsoft Exchange EdgeSync service ensures that the list of internal SMTP servers is propagated to all your subscribed Edge Transport servers.</description>
                <substeps>
                  <description _locID="G5_L5_S1_SS_DESCRIPTION">To configure the list of internal SMTP servers:</description>
                  <substep>
                    <text _locID="G5_L5_S1_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L5_S1_SS2_TEXT">2. To add a single IP address or multiple IP addresses to the list, run the following command: Set-TransportConfig -InternalSMTPServers:"127.0.0.1","127.0.0.2"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L5_S1_SS3_TEXT">3. To add a range of IP addresses to the list, run the following command: Set-TransportConfig -InternalSMTPServers:"127.0.0.1-127.0.0.99"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L5_S1_SS4_TEXT">4. To add a subnet mask to the list, run the following command: Set-TransportConfig -InternalSMTPServers:"127.0.0.1(255.255.0.0)"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L5_S1_SS5_TEXT">5. To add a Classless Interdomain Routing (CIDR) IP address to the list, run the following command: Set-TransportConfig -InternalSMTPServers:"127.0.0.1/24"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L5_S1_SS6_TEXT">6. To display internal SMTP servers setting: "Get-TransportConfig | fl InternalSMTPServers"</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L5_DESCRIPTION">You must configure the list of internal SMTP servers that should be ignored by Sender ID and connection filtering if your Edge Transport server is deployed behind other e-mail servers; . for example, when incoming e-mail is first received by a Sendmail server and then relayed to an Edge Transport server. The following Exchange 2007 anti-spam technologies depend on correct configuration of the list of internal SMTP servers - Sender ID, Connection Filtering, and Sender Reputation.</description>
        </link>
        <!--This link is for showing Safelist Aggregation Data Help-->
        <link>
          <text _locID="G5_L6_TEXT">Replicate Safelist Aggregation Data</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L6_S1_TEXT">Step 1: Configure safelist aggregation</text>
                <description _locID="G5_L6_S1_DESCRIPTION">The following list shows the high-level steps required to configure safelist aggregation. Detailed information for each step can be found in the topic at the end of this step.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L6_S1_SS1_TEXT">The following two steps must be completed on a computer in the Exchange organization that is connected to the Active Directory directory service:</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS2_TEXT">1. Use the Update-Safelist cmdlet to update safelist information for Outlook users.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS3_TEXT">2. Schedule periodic updates of safelist aggregation to verify that the most up-to-date safelist aggregation information is in Active Directory.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS4_TEXT">The following two steps must be completed the computer on which the Edge Transport server role is installed:</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS5_TEXT">1. (Optional) Verify that the Microsoft Exchange EdgeSync service is replicating safelist aggregation data to Active Directory Application Mode (ADAM).</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS6_TEXT">2. Verify that content filtering is enabled on the servers where you are running anti-spam features and that safelist aggregation is functioning correctly.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS7_TEXT">For more information about how to perform each of these steps, see the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS8_TEXT">- How to Configure Safelist Aggregation.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/5ac17168-f411-4cb7-ae98-ebefb865b210.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L6_S2_TEXT">Step 2: Read more about safelist aggregation</text>
                <description _locID="G5_L6_S2_DESCRIPTION">For more information about safelist aggregation, see the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L6_S2_SS1_TEXT">- Safelist Aggregation.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/f05430a0-0405-4b65-a18d-18c9e86a13c4.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L6_DESCRIPTION">Safelist aggregation refers to a set of anti-spam functionality that is shared across Outlook and Microsoft Exchange. This functionality collects data from the anti-spam Safe Recipients Lists or Safe Senders Lists and contact data that Outlook users configure and makes this data available to the anti-spam agents on the Edge Transport server. Safelist aggregation can help reduce the instances of false-positives in anti-spam filtering that is performed by the Edge Transport server. </description>
        </link>
        <!--This is the link for configuring E-mail Quarantine-->
        <link>
          <text _locID="G5_L8_TEXT">Configure Spam Quarantine</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L8_S1_TEXT">Step 1: Verify that content filtering is enabled</text>
                <description _locID="G5_L8_S1_DESCRIPTION">You must enable content filtering before you can apply spam quarantine. By default, the Content Filter agent filters all external messages that come through all Receive connectors on the computer on which the Content Filter agent is enabled. This step must be performed on the Edge Transport server.</description>
                <substeps>
                  <description _locID="G5_L8_S1_SS_DESCRIPTION">On the Edge Transport server that will have content filtering enabled:</description>
                  <substep>
                    <text _locID="G5_L8_S1_SS1_TEXT">1. Go to Anti-spam Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S1_SS2_TEXT">2. Select "Content Filtering".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S1_SS3_TEXT">3. Verify that the status is "Enabled".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S1_SS4_TEXT">4. If it is not enabled, in the action pane, click "Enable".</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L8_S2_TEXT">Step 2: Create a dedicated database for the spam quarantine mailbox</text>
                <description _locID="G5_L8_S2_DESCRIPTION">You must create a spam quarantine mailbox before you can enable the feature. We recommend that you create a dedicated database for the spam quarantine mailbox. The spam quarantine mailbox should have a large database, because if the storage quota limit is reached, messages will be lost. This step must be performed on a computer in the Exchange organization.</description>
                <substeps>
                  <description _locID="G5_L8_S2_SS_DESCRIPTION">On any server role in the Exchange organization or workstation with the console installed, create a dedicated database:</description>
                  <substep>
                    <text _locID="G5_L8_S2_SS1_TEXT">1. Go to Database Management.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S2_SS2_TEXT">2. Select the storage group in which you want to create the database.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S2_SS3_TEXT">3. In the action pane, click "New Mailbox Database".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S2_SS4_TEXT">4. Complete the New Mailbox Database wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L8_S3_TEXT">Step 3: Create the spam quarantine mailbox</text>
                <description _locID="G5_L8_S3_DESCRIPTION">You must create a mailbox that you can use as the spam quarantine mailbox with an appropriate messaging records management policy that includes mailbox size and the number of days that messages will be saved before they are deleted. This step must be performed on a computer in the Exchange organization.</description>
                <substeps>
                  <description _locID="G5_L8_S3_SS_DESCRIPTION">On any server role in the Exchange organization or workstation with the console installed, create a dedicated database:</description>
                  <substep>
                    <text _locID="G5_L8_S3_SS1_TEXT">1. Go to Recipient Management.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S3_SS2_TEXT">2. In the action pane, click "New Mailbox".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S3_SS3_TEXT">3. Select the dedicated mailbox database that you created in Step 2 to create the mailbox on.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S3_SS4_TEXT">4. Complete the New Mailbox wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L8_S4_TEXT">Step 4: Configure content filtering to quarantine messages</text>
                <description _locID="G5_L8_S4_DESCRIPTION">You must specify the SCL quarantine threshold and spam quarantine mailbox in the content filtering configuration. This step must be performed on the Edge Transport server.</description>
                <substeps>
                  <description _locID="G5_L8_S4_SS_DESCRIPTION">On the Edge Transport server that will have content filtering enabled:</description>
                  <substep>
                    <text _locID="G5_L8_S4_SS1_TEXT">1. Go to Anti-spam Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS2_TEXT">2. Select Content Filtering.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS4_TEXT">4. Select the "Action" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS5_TEXT">5. Select the "Quarantine messages that have a SCL rating greater than or equal to:" check box.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS6_TEXT">6. Specify the spam quarantine mailbox e-mail address for the spam quarantine mailbox you created in Step 3. Click "OK".</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L8_S5_TEXT">Step 5: Read more about how to configure spam quarantine</text>
                <description _locID="G5_L8_S5_DESCRIPTION">For more information about how to manage the spam quarantine mailbox and how to set the SCL threshold, see the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L8_S5_SS1_TEXT">- Adjusting the Spam Confidence Level Threshold</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/0009b4af-be6d-41d2-98bc-b5487272c74a.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S5_SS2_TEXT">- How to Recover Quarantined Messages from the Spam Quarantine Mailbox</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/7a86bfde-f868-4689-bdec-5f01e52b510d.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L8_DESCRIPTION">When you use anti-spam filters, there is always a chance that the filters will identify false positives. In the context of spam filtering, a false positive exists when a spam filter incorrectly identifies a message from a legitimate sender as spam. In Exchange 2007, you can reduce the risk of false positives and the potential loss of valuable messages if you use the Content Filter agent to quarantine messages that have been identified as potential spam.</description>
        </link>
      </links>
    </group>
    <!--This is for Exchange resources-->
    <group applyOn="">
      <icon>OWA</icon>
      <text _locID="G8_TEXT">Resources</text>
      <links>
        <!--This link is for EHLO Blog-->
        <link>
          <text _locID="G8_L1_TEXT">Microsoft Exchange Team Blog</text>
          <action>
            <name>ShowUrl</name>
            <argument>http://go.microsoft.com/fwlink/?LinkId=35786</argument>
          </action>
          <description _locID="G8_L1_DESCRIPTION">Read the official blog of the Microsoft Exchange team.</description>
        </link>
        <!--This link is for Exchange TechNet-->
        <link>
          <text _locID="G8_L2_TEXT">Microsoft Exchange Server TechCenter</text>
          <action>
            <name>ShowUrl</name>
            <argument>http://go.microsoft.com/fwlink/?LinkId=34165</argument>
          </action>
          <description _locID="G8_L2_DESCRIPTION">Get the latest technical information and support resources for Microsoft Exchange, including downloads and Knowledge Base articles.</description>
        </link>
        <!--This link is Exchange Feedback-->
        <link>
          <text _locID="G8_L3_TEXT">Submit Feedback on Exchange Server</text>
          <action>
            <name>ShowUrl</name>
            <argument>http://go.microsoft.com/fwlink/?LinkId=71967</argument>
          </action>
          <description _locID="G8_L3_DESCRIPTION">Submit suggestions or report bugs to the Microsoft Exchange team.</description>
        </link>
      </links>
    </group>
  </groups>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/><Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>AFxSIRaoPIaYAwat0fDqyyQNlhY=</DigestValue></Reference></SignedInfo><SignatureValue>
    dC0nXODvgx6+w82aqeZjY9Sdhen35c7Fz/ASwSQcAcJ32I7pLwCrX8wg9wz7IR4c5FBftoQt
    2kak2VIV3Grn+WTffcphtfRp1n1qh1LTlb2d/n+KxdYLmvru7UD0nuED6++Jys5dfVOeyGMN
    EgnRO/wZgkUKwURttmo5VOav1aHh4bHu/1MVw5o7AZklJwpGjhOqtjB8oW5mwlZk+1rR46V0
    +MrQzItcToNw+EX/zgTKVhrZmdFTnOUGVajzpflLQrfckqqmotAFTs7yVPQhokiI/FwaL6pp
    fS2Vm7oygAOCJtwG9WZgBioCePGXnB0UVhYi5rpG02cerDTPNjBZpw==
  </SignatureValue><KeyInfo>
      <KeyValue>
        <RSAKeyValue>
          <Modulus>
            vTCJ+0VyqFNrnolPACPAvtQdPbFZQDjzc5GCJuaWEgBT2RyCDjzOHbu990KNl9T8OBrkufnj
            7NNhA7+g09Z1TVxGqe1e8NLiaVsac+qzHI0EzSlEoGRZLx6YXW7Hqxg5gmXEp7yrdYgZ6oeX
            FCazfyZ2pNQ4OYTjsybVGPkr6dLJFlpUIfKXjYeGKf70SSzmi/gEP33NzZaShg1xA+LQ/gxC
            Nf/XuD/djkUKffbXS61b8HZyHXcjfYk1xBxdslADS0dtB6dViJgGgKaBrVRO2IHW+r9CwDG+
            VQ2Z1VNJEjDr5aWIfF7EeloUhwi0N2mg6zIkjAjr+dQUuuD8zeqkFQ==
          </Modulus>
          <Exponent>AQAB</Exponent>
        </RSAKeyValue>
      </KeyValue>
      <X509Data>
        <X509Certificate>
          MIIEejCCA2KgAwIBAgIKYQHPPgAAAAAADzANBgkqhkiG9w0BAQUFADB5MQswCQYDVQQGEwJV
          UzETMBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWlj
          cm9zb2Z0IENvcnBvcmF0aW9uMSMwIQYDVQQDExpNaWNyb3NvZnQgQ29kZSBTaWduaW5nIFBD
          QTAeFw0wOTEyMDcyMjQwMjlaFw0xMTAzMDcyMjQwMjlaMIGDMQswCQYDVQQGEwJVUzETMBEG
          A1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0
          IENvcnBvcmF0aW9uMQ0wCwYDVQQLEwRNT1BSMR4wHAYDVQQDExVNaWNyb3NvZnQgQ29ycG9y
          YXRpb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC9MIn7RXKoU2ueiU8AI8C+
          1B09sVlAOPNzkYIm5pYSAFPZHIIOPM4du733Qo2X1Pw4GuS5+ePs02EDv6DT1nVNXEap7V7w
          0uJpWxpz6rMcjQTNKUSgZFkvHphdbserGDmCZcSnvKt1iBnqh5cUJrN/Jnak1Dg5hOOzJtUY
          +Svp0skWWlQh8peNh4Yp/vRJLOaL+AQ/fc3NlpKGDXED4tD+DEI1/9e4P92ORQp99tdLrVvw
          dnIddyN9iTXEHF2yUANLR20Hp1WImAaApoGtVE7Ygdb6v0LAMb5VDZnVU0kSMOvlpYh8XsR6
          WhSHCLQ3aaDrMiSMCOv51BS64PzN6qQVAgMBAAGjgfgwgfUwEwYDVR0lBAwwCgYIKwYBBQUH
          AwMwHQYDVR0OBBYEFDh4BXPIGzKbX5KGVa+JusaZsXSOMA4GA1UdDwEB/wQEAwIHgDAfBgNV
          HSMEGDAWgBTMHc52AHBbr/HaxE6aUUQuo0Rj8DBEBgNVHR8EPTA7MDmgN6A1hjNodHRwOi8v
          Y3JsLm1pY3Jvc29mdC5jb20vcGtpL2NybC9wcm9kdWN0cy9DU1BDQS5jcmwwSAYIKwYBBQUH
          AQEEPDA6MDgGCCsGAQUFBzAChixodHRwOi8vd3d3Lm1pY3Jvc29mdC5jb20vcGtpL2NlcnRz
          L0NTUENBLmNydDANBgkqhkiG9w0BAQUFAAOCAQEAKAODqxMN8f4Rb0J22EOruMZC+iRlNK51
          sHEwjpa2g/py5P7NN+c6cJhRIA66cbTJ9NXkiugocHPV7eHCe+7xVjRagILrENdyA+oSTuzd
          DYx7RE8MYXX9bpwH3c4rWhgNObBg/dr/BKoCo9j6jqO7vcFqVDsxX+QsbsvxTSoc8h52e4av
          xofWsSrtrMwOwOSff+jP6IRyVIIYbirInpW0Gh7Bb5PbYqbBS2utye09kuOyL6t6dzlnagB7
          gp0DEN5jlUkmQt6VIsGHC9AUo1/cczJyNh7/yCnFJFJPZkjJHR2pxSY5aVBOp+zCBmwuchvx
          IdptJEiAgRVAfJ/MdDhKTw==
        </X509Certificate>
      </X509Data>
      <X509Data>
        <X509Certificate>
          MIIEEjCCAvqgAwIBAgIPAMEAizw8iBHRPvZj7N9AMA0GCSqGSIb3DQEBBAUAMHAxKzApBgNV
          BAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jv
          c29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4X
          DTk3MDExMDA3MDAwMFoXDTIwMTIzMTA3MDAwMFowcDErMCkGA1UECxMiQ29weXJpZ2h0IChj
          KSAxOTk3IE1pY3Jvc29mdCBDb3JwLjEeMBwGA1UECxMVTWljcm9zb2Z0IENvcnBvcmF0aW9u
          MSEwHwYDVQQDExhNaWNyb3NvZnQgUm9vdCBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQCpAr3BcOY78k4bKJ+XeF4w6qKpjSVf+P6VTKO3/p2iID58UaKboo9g
          MmvRQmR57qx2yVTa8uuchhyPn4Rms8VremIj1h083g8BkuiWxL8tZpqaaCaZ0Dosvwy1WCbB
          RucKPjiWLKkoOajsSYNC44QPu5psVWGsgnyhYC13TOmZtGQ7mlAcMQgkFJ+p55ErGOY9mGMU
          YFgFZZ8dN1KH96fvlALGG9O/VUWziYC/OuxUlE6u/ad6bXROrxjMlgkoIQBXkGBpN7tLEgc8
          Vv9b+6RmCgim0oFWV++2O14WgXcE2va+roCV/rDNf9anGnJcPMq88AijIjCzBoXJsyB3E4Xf
          AgMBAAGjgagwgaUwgaIGA1UdAQSBmjCBl4AQW9Bw72lyniNRfhSyTY7/y6FyMHAxKzApBgNV
          BAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jv
          c29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5gg8A
          wQCLPDyIEdE+9mPs30AwDQYJKoZIhvcNAQEEBQADggEBAJXoC8CN85cYNe24ASTYdxHzXGAy
          n54Lyz4FkYiPyTrmIfLwV5MstaBHyGLv/NfMOztaqTZUaf4kbT/JzKreBXzdMY09nxBwarv+
          Ek8YacD80EPjEVogT+pie6+qGcgrNyUtvmWhEoolD2Oj91Qc+SHJ1hXzUqxuQzIH/YIX+OVn
          bA1R9r3xUse958Qw/CAxCYgdlSkaTdUdAqXxgOADtFv0sd3IV+5lScdSVLa0AygS/5DW8AiP
          friXxas3LOR65Kh343agANBqP8HSNorgQRKoNWobats14dQcBOSoRQTIWjM4bk0cDWK3CqKM
          09VUP0bNHFWmcNsSOoeTdZ+n0qA=
        </X509Certificate>
      </X509Data>
      <X509Data>
        <X509Certificate>
          MIIEYDCCA0ygAwIBAgIKLqsR3FD/XJ3LwDAJBgUrDgMCHQUAMHAxKzApBgNVBAsTIkNvcHly
          aWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jvc29mdCBDb3Jw
          b3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4XDTA3MDgyMjIy
          MzEwMloXDTEyMDgyNTA3MDAwMFoweTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0
          b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEj
          MCEGA1UEAxMaTWljcm9zb2Z0IENvZGUgU2lnbmluZyBQQ0EwggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQC3eX3WXbNFOag0rDHa+SU1SXfA+x+ex0Vx79FG6NSMw2tMUmL0mQLD
          TdhJbC8kPmW/ziO3C0i3f3XdRb2qjw5QxSUr8qDnDSMf0UEk+mKZzxlFpZNKH5nNsy8iw0ot
          fG/ZFR47jDkQOd29KfRmOy0BMv/+J0imtWwBh5z7urJjf4L5XKCBhIWOsPK4lKPPOKZQhRcn
          h07dMPYAPfTG+T2BvobtbDmnLjT2tC6vCn1ikXhmnJhzDYav8sTzILlPEo1jyyzZMkUZ7rtK
          ljtQUxjOZlF5qq2HyFY+n4JQiG4FsTXBeyS9UmY9mU7MK34zboRHBtGe0EqGAm6GAKTAh99T
          AgMBAAGjgfowgfcwEwYDVR0lBAwwCgYIKwYBBQUHAwMwgaIGA1UdAQSBmjCBl4AQW9Bw72ly
          niNRfhSyTY7/y6FyMHAxKzApBgNVBAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQg
          Q29ycC4xHjAcBgNVBAsTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9z
          b2Z0IFJvb3QgQXV0aG9yaXR5gg8AwQCLPDyIEdE+9mPs30AwDwYDVR0TAQH/BAUwAwEB/zAd
          BgNVHQ4EFgQUzB3OdgBwW6/x2sROmlFELqNEY/AwCwYDVR0PBAQDAgGGMAkGBSsOAwIdBQAD
          ggEBAHurrn5KJvLOvE50olgndCp1s4b9q0yUeABN6crrGNxpxQ6ifPMCQ8bKh8z4U8zCn71W
          b/BjRKlEAO6WyJrVHLgLnxkNlNfaHq0pfe/tpnOsj945jj2Yarw4bdKIryP93+nWaQmRiL3+
          4QC7NPP3fPkQEi4F6ymWk0JrKHG3OI/gBw3JXWjNvYBBa2aou7e7jjTK8gMQfHr10uBC33v+
          4eGs/vbf1Q2zcNaS40+2OKJ8LdQ92zQLYjcCn4FqI4n2XGOPsFq7OddgjFWEGjP1O5igggyi
          X4uzLLehpcur2iC2vzAZhSAUDSq8UvRB4F4w45IoaYfBcOLzp6vOgEJydg4=
        </X509Certificate>
      </X509Data>
    </KeyInfo><Object id="ts-countersig"><X509Data><X509Certificate>MIIEqjCCA5KgAwIBAgIKYQWiMAAAAAAACDANBgkqhkiG9w0BAQUFADB5MQswCQYDVQQGEwJVUzET
MBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0
IENvcnBvcmF0aW9uMSMwIQYDVQQDExpNaWNyb3NvZnQgVGltZXN0YW1waW5nIFBDQTAeFw0wODA3
MjUxOTAxMTVaFw0xMzA3MjUxOTExMTVaMIGzMQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGlu
Z3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0aW9uMQ0w
CwYDVQQLEwRNT1BSMScwJQYDVQQLEx5uQ2lwaGVyIERTRSBFU046ODVEMy0zMDVDLTVCQ0YxJTAj
BgNVBAMTHE1pY3Jvc29mdCBUaW1lLVN0YW1wIFNlcnZpY2UwggEiMA0GCSqGSIb3DQEBAQUAA4IB
DwAwggEKAoIBAQDwBC2ylsAagWclsSZisxNLzjC6wBI4/IFlNAfENrIkaPYHBMAHl/S38XseYixG
2UukUTS302ztWju0g6FHPREILjVrRebCPIwCZgKpGGnrSu0nLO48d1uk1HCZS1eEENCvLfiJHebq
KbTnz54GYqdyVMI7xs8/uOGwWBBs5aXXw8J1N730heGB6CjYG/HyrvGCo9bXA6KfFYT7Pfqr4bYy
yKACZPPm/xomcQhTihUC8oMndkmCcafvrTJ4xtdsFk8iZZdiTUYv/yOvheymcL0Dy9rYMgXFK5BA
tp7VLIZst8sTMn2Nxn6uFy8y/Ga7HbBFVfit+i1ng2cpk4TSWqEjAgMBAAGjgfgwgfUwHQYDVR0O
BBYEFOiX9vfvjPHmaeNZaE73mIp63ZsuMB8GA1UdIwQYMBaAFG/oTj+XuTSrS4aPvJzqrDtBQ8bQ
MEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwubWljcm9zb2Z0LmNvbS9wa2kvY3JsL3Byb2R1
Y3RzL3RzcGNhLmNybDBIBggrBgEFBQcBAQQ8MDowOAYIKwYBBQUHMAKGLGh0dHA6Ly93d3cubWlj
cm9zb2Z0LmNvbS9wa2kvY2VydHMvdHNwY2EuY3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMIMA4GA1Ud
DwEB/wQEAwIGwDANBgkqhkiG9w0BAQUFAAOCAQEADT93X5E8vqU1pNsFBYQfVvLvmabHCI0vs80/
cdWGfHcf3esXsr184/mZ8gpFSK0Uu2ks8j5nYlTy7n8nEZI57M7Zh06I92BHI3snFUAIn78NMQSC
2DW2DJwA04uqeGHFtYhBnT423FikJ5s62r0GXRSmsg9MwY48i/Jimfhm7dXzHCiwMtvKMQm8+yJo
Rkz603Mi5ymOIgD7Vr8GroGgFbo0+SiOH0piBaGJ9YFH6Q2RCNdYO48eawlpqcBIfFWCP18AOEOc
Bsw/2C+/T3MJPf26XvTH7DfCZGGgTdQ9cMxbsBOBwdSjMRq9ZNaW0no/KltGUwk8zQP5P1kAzIlT
YQ==</X509Certificate></X509Data><X509Data><X509Certificate>MIIEnTCCA4WgAwIBAgIQaguZT8AAJasR20UfWHpnojANBgkqhkiG9w0BAQUFADBwMSswKQYDVQQL
EyJDb3B5cmlnaHQgKGMpIDE5OTcgTWljcm9zb2Z0IENvcnAuMR4wHAYDVQQLExVNaWNyb3NvZnQg
Q29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jvc29mdCBSb290IEF1dGhvcml0eTAeFw0wNjA5MTYw
MTA0NDdaFw0xOTA5MTUwNzAwMDBaMHkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpXYXNoaW5ndG9u
MRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xIzAhBgNV
BAMTGk1pY3Jvc29mdCBUaW1lc3RhbXBpbmcgUENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA3Ddu+6/IQkpxGMjOSD5TwPqrFLosMrsST1LIg+0+M9lJMZIotpFk4B9QhLrCS9F/Bfjv
db6Lx6jVrmlwZngnZui2t++Fuc3uqv0SpAtZIikvz0DZVgQbdrVtZG1KVNvd8d6/n4PHgN9/TAI3
lPXAnghWHmhHzdnAdlwvfbYlBLRWW2ocY/+AfDzu1QQlTTl3dAddwlzYhjcsdckO6h45CXx2/p1s
bnrg7D6Pl55xDl8qTxhiYDKe0oNOKyJcaEWL3i+EEFCy+bUajWzuJZsT+MsQ14UO9IJ2czbGlXqi
zGAG7AWwhjO3+JRbhEGEWIWUbrAfLEjMb5xD4GrofyaOawIDAQABo4IBKDCCASQwEwYDVR0lBAww
CgYIKwYBBQUHAwgwgaIGA1UdAQSBmjCBl4AQW9Bw72lyniNRfhSyTY7/y6FyMHAxKzApBgNVBAsT
IkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jvc29mdCBD
b3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5gg8AwQCLPDyIEdE+
9mPs30AwEAYJKwYBBAGCNxUBBAMCAQAwHQYDVR0OBBYEFG/oTj+XuTSrS4aPvJzqrDtBQ8bQMBkG
CSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MA0G
CSqGSIb3DQEBBQUAA4IBAQCUTRExwnxQuxGOoWEHAQ6McEWN73NUvT8JBS3/uFFThRztOZG3o1YL
3oy2OxvR+6ynybexUSEbbwhpfmsDoiJG7Wy0bXwiuEbThPOND74HijbB637pcF1Fn5LSzM7djsDh
vyrNfOzJrjLVh7nLY8Q20Rghv3beO5qzG3OeIYjYtLQSVIz0nMJlSpooJpxgig87xxNleEi7z62D
Ok+wYljeMOnpOR3jifLaOYH5EyGMZIBjBgSW8poCQy97Roi6/wLZZflK3toDdJOzBW4MzJ3cKGF8
SPEXnBEhOAIch6wGxZYyuOVAxlM9vamJ3uhmN430IpaczLB3VFE61nJEsiP2</X509Certificate></X509Data><CounterSignature xmlns="http://schemas.microsoft.com/xmldsig/timestamp/2003" ts-format="cms-timestamp-message">MIIGyQYJKoZIhvcNAQcCoIIGujCCBrYCAQMxCTAHBgUrDgMCGjCCARMGCSqGSIb3DQEHAaCCAQQE
ggEAdC0nXODvgx6+w82aqeZjY9Sdhen35c7Fz/ASwSQcAcJ32I7pLwCrX8wg9wz7IR4c5FBftoQt
2kak2VIV3Grn+WTffcphtfRp1n1qh1LTlb2d/n+KxdYLmvru7UD0nuED6++Jys5dfVOeyGMNEgnR
O/wZgkUKwURttmo5VOav1aHh4bHu/1MVw5o7AZklJwpGjhOqtjB8oW5mwlZk+1rR46V0+MrQzItc
ToNw+EX/zgTKVhrZmdFTnOUGVajzpflLQrfckqqmotAFTs7yVPQhokiI/FwaL6ppfS2Vm7oygAOC
JtwG9WZgBioCePGXnB0UVhYi5rpG02cerDTPNjBZp6CCA32hggN5MIICYQIBATCB46GBuaSBtjCB
szELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAc
BgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjENMAsGA1UECxMETU9QUjEnMCUGA1UECxMebkNp
cGhlciBEU0UgRVNOOjg1RDMtMzA1Qy01QkNGMSUwIwYDVQQDExxNaWNyb3NvZnQgVGltZS1TdGFt
cCBTZXJ2aWNloiUKAQEwCQYFKw4DAhoFAAMVAE1vNX8OZDTal7GvxUD7b90OhaifoIHBMIG+pIG7
MIG4MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEe
MBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0aW9uMQwwCgYDVQQLEwNBT0MxJzAlBgNVBAsTHm5D
aXBoZXIgTlRTIEVTTjoyMkExLTIwOEUtODdCMDErMCkGA1UEAxMiTWljcm9zb2Z0IFRpbWUgU291
cmNlIE1hc3RlciBDbG9jazANBgkqhkiG9w0BAQUFAAIFAM+MSogwIhgPMjAxMDA1MDUxOTUwMzJa
GA8yMDEwMDUwNjE5NTAzMloweDA+BgorBgEEAYRZCgQBMTAwLjAKAgUAz4xKiAIBADAKAgEAAgIA
jQIB/zAIAgEAAgMDHMkwCgIFAM+NnAgCAQAwNgYKKwYBBAGEWQoEAjEoMCYwDAYKKwYBBAGEWQoD
AaAKMAgCAQACAw9CQKEKMAgCAQACAwehIDANBgkqhkiG9w0BAQUFAAOCAQEAGknjsWMLm7VOVfLX
6WvrEFmxcWTdJKSDe+/Td4EPf9DuJAO5R+MhYS1ABKQahTnqFW4pQgxc6b64OCGaYbJem1qxGavu
1dzrgaJrgXUkThNWUf201K+UIp5SB/VjahhgoI+aAMZt1yV7G91fkDZ+oN/AnD1v2ucPPd7f3e7j
yFcIBeRPgVtG3xkygpZzCNQZyvmM/Y8JomHawfjnKd5KshSrZgZgnGk8a2F+ZjUtd/3wzWNnZ42t
1njsfbu5FyKqWIRJmeZ2COcLOt935DoF4tmJMinN16ddLWzfqBEBOHarobtLGpW33wep8hJW5Ux+
6lrS9rGHkLE7J3W6Q6BazTGCAgwwggIIAgEBMIGHMHkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpX
YXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRp
b24xIzAhBgNVBAMTGk1pY3Jvc29mdCBUaW1lc3RhbXBpbmcgUENBAgphBaIwAAAAAAAIMAcGBSsO
AwIaoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTAwNTA1MjM1
ODMxWjAjBgkqhkiG9w0BCQQxFgQUVm+GBNSs8Kn9PaCoJX9rF5pZ6powDQYJKoZIhvcNAQEFBQAE
ggEAM77Gk14w0IU0wwKmn/T0zSJroyoLLFAFilrVeWSZgGQvHmSf//qc68a7utkrPmxXHFgGSffF
Ifl8ew2ew+up0u7HotzAw0TSOAWRhYhmdpmLV9K1NrikaXHMHEnvPqQCSn6vfYS6gkI6VyY4Fv3J
aaNIKPO6lROx3zCtwFWsiVD1cTZZRxH5fQfApB2p844FStAdTG+3iWCUvGkI3QLgFGwPya6IfaXo
shrMhHtCzlMyPlHmYbxccuSNsRoizWuV/m4OTtdQuvI3R4XXkxxWv7rovdDsj9Ie1PpNpIQdr4xw
zZ4Yo3r5emh+trSEhN61+QsRZKJcVFdV0FdLTJjtBQ==</CounterSignature></Object></Signature></startpage>