<?xml version="1.0"?><?xml-stylesheet type='text/xsl' href='StartPage.xsl'?><!--
//  Copyright (C) 2006 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>ShowUrl</name>
            <argument>http://go.microsoft.com/fwlink/?LinkID=73665</argument>
          </action>
          <description _locID="G6_L1_DESCRIPTION">Monitoring the availability, configuration, and performance of your Exchange servers allows you to 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 in which you can avoid or minimize the impact of a disaster. There are many different preventive measures you can take to help prevent or minimize the effects of disasters such as hardware failure 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">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S1_SS2_TEXT">Run the following command: Set-OrganizationConfig –SCLJunkThreshold:6</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L4_S2_TEXT">Step 2: Set per mailbox override thresholds (optional)</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, over-riding the organization-wide setting. For example, if you want to set this override on a user’s mailbox (in this example to "6"):</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S2_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS2_TEXT">Run the following command: Set-Mailbox [Username] -SCLJunkThreshold:6 -SCLJunkEnabled:$True</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS3_TEXT">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 over-ride 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: Create a new managed default folder or a new managed custom folder (optional)</text>
                <description _locID="G1_L1_S1_DESCRIPTION">Managed folders are mailbox folders that have messaging records management enabled. There are two types of managed folders: custom folders (folders that you create for placement in user's mailbox--for example, a folder named "Legal Documents"), and default folders (the 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">For Managed Default Folders:  Go to Managed Default Folder Management</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. It is not necessary 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">Select "New Managed Default Folder" in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS4_TEXT">For Managed Custom Folders:  Go to Managed Custom Folder Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcOrgFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS5_TEXT">Select "New Managed Custom Folder" in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS6_TEXT">Complete the specified 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 it 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">For Managed Default Folders:  Go to Managed Default Folder Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS2_TEXT">For Managed Custom Folders:  Go to Managed Custom Folder Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\elcOrgFoldersResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS3_TEXT">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">Select "New Managed Content Settings" in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS5_TEXT">Complete the New Managed Content Settings Wizard</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S2_SS6_TEXT">Note: You can use the New Managed Content Settings wizard repeatedly to create additional content settings to control other types of items in the folder.</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">Go to Managed Folder Mailbox Policy Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\ElcMailboxPoliciesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S3_SS2_TEXT">Select "New Managed Folder Mailbox Policy" in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S3_SS3_TEXT">Complete the New Managed Folder Mailbox Policy Wizard</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L1_S4_TEXT">Step 4: Configure the schedule for the managed folder mailbox assistant</text>
                <description _locID="G1_L1_S4_DESCRIPTION">The managed folders, content settings, and policies that you create are applied to users' mailboxes only when the Managed Folder Mailbox Assistant runs. The Managed Folder Mailbox 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_S4_SS_DESCRIPTION">To configure the schedule for the Managed Folder Assistant:</description>
                  <substep>
                    <text _locID="G1_L1_S4_SS1_TEXT">Go to Mailbox Server Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS2_TEXT">Select the server to enable the Managed Folder Assistant on</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS3_TEXT">Select "Properties" in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS4_TEXT">Select the "Messaging Records Management" tab</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS5_TEXT">Select a time to have the assistant run in the "Schedule the Managed Folder Assistant" box</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S4_SS6_TEXT">Click "OK" to save changes</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L1_S5_TEXT">Step 5: Apply the managed folder mailbox policy to a users' mailboxes</text>
                <description _locID="G1_L1_S5_DESCRIPTION">When you apply a managed folder mailbox policy to users' mailboxes, all of the managed folders in the policy are applied to those mailboxes at one time.</description>
                <substeps>
                  <description _locID="G1_L1_S5_SS_DESCRIPTION">To apply a managed folder mailbox policy to users' mailboxes:</description>
                  <substep>
                    <text _locID="G1_L1_S5_SS1_TEXT">Go to Recipient Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS2_TEXT">Select the user to apply the policy to</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS3_TEXT">Select "Properties" in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS4_TEXT">Select the "Mailbox Settings" Tab</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS5_TEXT">Select "Messaging Records Management"</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS6_TEXT">Click the "Properties" button</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS7_TEXT">Click the "Browse" button and select the policy to apply (created in step 3) </text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S5_SS8_TEXT">Click "OK" to save changes</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L1_DESCRIPTION">Messaging management policies help organizations to comply with legal requirements and conserve information technology (IT) resources.</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">Open the Control Panel, and then click “Add or Remove Programs”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS2_TEXT">Click “Add/Remove Windows Components”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS3_TEXT">Select the “Networking Services” component and choose “Details”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS4_TEXT">Select the “RPC over HTTP Proxy” checkbox and then click “OK”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S1_SS5_TEXT">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" page 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” page for the “Rpc” virtual directory.  For more information read 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, users whose mailboxes are located on Exchange 2007 servers that are running the mailbox server role will be able to use RPC over HTTP to connect to their Microsoft Exchange mailbox.</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">Go to Exchange Client Access Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ClientAccessNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS2_TEXT">Select the Client Access server that you will configure for Outlook Anywhere.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS3_TEXT">In the action pane, click the “Enable Outlook Anywhere” link.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS4_TEXT">Complete the Enable Outlook Anywhere wizard.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS5_TEXT">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 Web Service for free/busy information. This is required for deployments that do not use ISA Server 2006 or for deployments where ISA Server 2006 or later versions are not configured to allow NTLM.</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">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS2_TEXT">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">Configuring 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" page for Client Access</text>
                <description _locID="G2_L2_S1_DESCRIPTION">When accessing Exchange 2007 over the Internet, Microsoft Office Outlook 2007 requires that the certificate configured for 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 by using IIS, complete the steps that are listed in the "Configure SSL for your Client Access server" section on the “Finalize Deployment” page for the “Autodiscover” virtual directory. For more information, read 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 URL</text>
                <description _locID="G2_L2_S2_DESCRIPTION">Outlook 2007 gets URLs to Exchange components when it calls 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 on the End-to-End Scenario page for Client Access</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 on the Finalize Deployment page for Mailbox.</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">Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS5_TEXT">Run the following command, replacing identity with the actual name of your server and the 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 Service's external URL do the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS7_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS8_TEXT">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_L2_DESCRIPTION">The Autodiscover service enables users who are running Outlook 2007 to locate the profile settings that are required to connect to Microsoft Exchange the first time. By locating these settings, the Autodiscover service can repair any Exchange connection settings after a change in connectivity or to the Microsoft Exchange messaging infrastructure.</description>
        </link>
      </links>
    </group>
    <group applyOn="HubTransport">
      <icon>BridgeheadServer</icon>
      <text _locID="G0_TEXT">Hub Transport</text>
      <links>
        <!--This link is for Forefront AntiVirus-->
        <link>
          <text _locID="G0_L5_TEXT">Protect your Exchange Servers from viruses, worms and other malware</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G0_L5_S1_TEXT">Step 1: Learn about Forefront Security for Exchange Server</text>
                <description _locID="G0_L5_S1_DESCRIPTION">Learn more about how Microsoft Forefront Security for Exchange Server can help protect your Exchange servers from viruses, worms, and other malware.</description>
                <substeps>
                  <substep>
                    <text _locID="G0_L5_S1_SS1_TEXT">Read about Microsoft Forefront Security for Exchange Server</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?linkid=68589</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G0_L5_S2_TEXT">Step 2: Install Forefront Security for Exchange Server</text>
                <description _locID="G0_L5_S2_DESCRIPTION">To install Forefront Security for Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G0_L5_S2_SS1_TEXT">Insert the Exchange DVD in your DVD drive and select “Install Microsoft Forefront Security for Exchange Server” from the first screen</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L5_S2_SS2_TEXT">OR</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L5_S2_SS3_TEXT">Download Forefront Security for Exchange Server</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?linkid=68582</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G0_L5_DESCRIPTION">Microsoft Exchange Forefront Security for Exchange Server helps protect your Exchange servers from viruses, worms and other malware.</description>
        </link>
        <!--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">Use the Update-Safelist cmdlet to update safelist information for Microsoft Office Outlook users.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS3_TEXT">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">Verify that the Microsoft Exchange EdgeSync service is replicating safelist aggregation data to Active Directory Application Mode (ADAM). (optional)</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L6_S1_SS6_TEXT">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">Read additional details for performing each of these steps:</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 additional information about safelist aggregation:</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 Microsoft Office 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 is going to have content filtering enabled:</description>
                  <substep>
                    <text _locID="G0_L8_S1_SS1_TEXT">Go to Anti-spam management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S1_SS2_TEXT">Select Content Filtering</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S1_SS3_TEXT">Verify that the status is "Enabled"</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S1_SS4_TEXT">If it is not enabled, click "Enable" in the action pane</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">Go to database management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode\StorageGroupsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S2_SS2_TEXT">Select the storage group that you want to create the database in</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S2_SS3_TEXT">In the action pane, click the "New Mailbox Database"</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S2_SS4_TEXT">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">Go to Recipient Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S3_SS2_TEXT">In the action pane, click "New Mailbox"</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S3_SS3_TEXT">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">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 is going to have content filtering enabled:</description>
                  <substep>
                    <text _locID="G0_L8_S4_SS1_TEXT">Go to Anti-spam management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS2_TEXT">Select Content Filtering</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS3_TEXT">In the action pane, click "Properties"</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS4_TEXT">Select the "Action" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS5_TEXT">Select the checkbox for "Quarantine messages that have a SCL rating greater than or equal to:".</text>
                  </substep>
                  <substep>
                    <text _locID="G0_L8_S4_SS6_TEXT">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">Additional information about how to manage the spam quarantine mailbox and how to set the SCL threshold should be reviewed.</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 Out Dialing</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 calls that users who are associated with a UM mailbox policy can make. The dialing rule groups are stored on the dial plan that is associated with the UM mailbox policy. You can create two types of dialing rule groups.  One is used for in-country/region groups and the other that is used for international groups.</description>
                <substeps>
                  <description _locID="G4_L1_S1_SS_DESCRIPTION">To create dialing rule groups:</description>
                  <substep>
                    <text _locID="G4_L1_S1_SS1_TEXT">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">Select the UM dial plan for which you want to create dialing rule groups.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS3_TEXT">Click the “Dialing Rule Groups” tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS4_TEXT">To create a new dialing rule entry for In-Country/Region dialing rule groups, click “Add…” under the In-Country/Region Rule Groups.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS5_TEXT">To create a new dialing rule entry for International dialing rule groups, click “Add…” under the International Rule Groups.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS6_TEXT">For more information about the values to use to create the dialing rule entry, read the following:</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 specified UM mailbox policy. This allows users who are associated with this UM mailbox policy to place calls to people from their own personal contacts or the Exchange global address list, or to external phone numbers whose telephone numbers match the patterns defined in the selected dialing rule group.</description>
                <substeps>
                  <description _locID="G4_L1_S2_SS_DESCRIPTION">To configure dialing restrictions on the UM mailbox policy:</description>
                  <substep>
                    <text _locID="G4_L1_S2_SS1_TEXT">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">Select the UM mailbox policy for which you want to configure dialing restrictions.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS3_TEXT">In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS4_TEXT">Click the "Dialing Restrictions" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS5_TEXT">Under "Select allowed in-country/region rule groups from dial plan", click "Add".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS6_TEXT">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">To allow 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">Under "Select allowed international rule groups from dial plan", click "Add".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS9_TEXT">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">Click "OK" to save changes.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L1_DESCRIPTION">To allow calls to be transferred to users outside a UM dial plan you must configure out dialing.</description>
        </link>
        <!--This link is for Enabling Mutual-TLS between gateways/IP-PBXs -->
        <link>
          <text _locID="G4_L2_TEXT">Enable Mutual-TLS (MTLS) between IP/VoIP gateways or IP/PBXs and an Exchange UM server</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L2_S1_TEXT">Step 1: Turn on MTLS support on both the Session Initiation Protocol (SIP) endpoints and the Windows Server 2003 server</text>
                <description _locID="G4_L2_S1_DESCRIPTION">MTLS requires that both the SIP endpoint and Windows server be issued an X.509 certificate signed by a trusted certification authority. To do this, you can use the PKI infrastructure of your existing organization and the ExchangeCertificate cmdlets. Alternatively, you can configure them to use self-signed certificates.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S1_SS1_TEXT">For information about how to configure MTLS on the SIP endpoint, see the documentation that is provided by the SIP endpoint vendor.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S1_SS2_TEXT">For more information about UM 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 the MTLS setting on the dial plan</text>
                <description _locID="G4_L2_S2_DESCRIPTION">You must enable the MTLS setting on an existing dial plan.  If you have not yet created a dial plan, complete the "Configure Unified Messaging" steps on the Finalize Deployment page before completing this step.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S2_SS1_TEXT">Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS2_TEXT">Run the following command: set-umdialplan -identity "Name of UM Dial Plan" -VOIPSecurity SIPSecured</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S3_TEXT">Step 3: Update the UM IP Gateway to point to the SIP endpoint</text>
                <description _locID="G4_L2_S3_DESCRIPTION">The UM IP gateway must specify the FQDN of the SIP endpoint. Therefore, the FQDN must be updated on the existing IP Gateway that was linked via the hunt group to the MTLS-enabled dial plan in Step 2. If you have not created an IP gateway yet, complete the "Configure Unified Messaging" steps on the Finalize Deployment page before completing this step.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S3_SS1_TEXT">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">Select the IP gateway that is linked to the MTLS-enabled dial plan in Step 2</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS3_TEXT">Click "Properties" in the action pane</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS4_TEXT">Click the fully qualified domain name (FQDN) radio button and specify the FQDN of the SIP endpoint</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS5_TEXT">Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S4_TEXT">Step 4: Verify that all dial plans associated with the UM server are MTLS-enabled</text>
                <description _locID="G4_L2_S4_DESCRIPTION">Each UM server can support multiple dial plans. However, a single UM server can operate only in secure or unsecure mode. Therefore, all the dial plans associated with this UM server must have the same security setting (i.e., same values for VoipSecurity).</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S4_SS1_TEXT">Go to UM Server Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>UnifiedMessagingNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS2_TEXT">Select the UM server that you are associating the MTLS-enabled dial plan to.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS3_TEXT">Click "Properties" in the action pane.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS4_TEXT">Click the "UM Settings" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS5_TEXT">Verify that this UM server is associated with the MTLS-enabled dial plan and is the only dial plan with which the server is associated.  If other dial plans that are not MTLS-enabled are associated with the UM server, you must remove the dial plans and then repeat steps 2 and 3 for the other associated dial plans and add them back to the UM server.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S5_TEXT">Step 5: Restart the Microsoft Exchange Unified Messaging service to start using MTLS</text>
                <description _locID="G4_L2_S5_DESCRIPTION">The Microsoft Exchange Unified Messaging service must be restarted for the MTLS settings take effect.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S5_SS1_TEXT">Open the Windows Component Services administrative tool.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S5_SS2_TEXT">Click the "Microsoft Exchange Unified Messaging" service</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S5_SS3_TEXT">Right-click and choose "Restart"</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S5_SS4_TEXT">To verify that the UM service started in secure mode check the application event log for an information event number 1114 and 1112 logged by the UMService.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L2_DESCRIPTION">Exchange Unified Messaging supports the use of Mutual-TLS (MTLS) to authenticate the SIP endpoints (including the IP/VoIP gateways and IP/PBXs) and to encrypt the SIP traffic. It encrypts the SIP traffic by using the TLS mechanism provided by the underlying Windows Server 2003 platform.</description>
        </link>
        <!--This link is for configuring Auto Attendant-->
        <link>
          <text _locID="G4_L3_TEXT">Configuring the Auto Attendant</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L3_S1_TEXT">Step 1: Plan the Auto Attendants and Prompts</text>
                <description _locID="G4_L3_S1_DESCRIPTION">Decide on menu keys and recorded greetings and prompts that will be used by the auto attendant.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L3_S1_SS1_TEXT">Decide on the menu keys that will be used by callers who access the auto attendant, and the actions that will be associated with these keys. For example: Press 1 to transfer to extension 54321, and press 2 to go to a second-level menu. 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">Record the various greetings and prompts that callers will hear when they interact with the auto attendants. 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 top-level auto attendant</text>
                <description _locID="G4_L3_S2_DESCRIPTION">A top-level auto attendant is one that has one or more extensions configured. It will answer incoming calls to one or more extension(s).</description>
                <substeps>
                  <description _locID="G4_L3_S2_SS_DESCRIPTION">To create Auto Attendants:</description>
                  <substep>
                    <text _locID="G4_L3_S2_SS1_TEXT">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">Click the "New UM Auto Attendant" link in the action pane.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S2_SS3_TEXT">Complete the New UM Auto Attendant wizard, make sure to select the "Create auto attendant as enabled" checkbox.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S3_TEXT">Step 3: Create the 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 has no extension configured. Therefore, callers can only reach it from a menu option that is configured on another auto attendant.</description>
                <substeps>
                  <description _locID="G4_L3_S3_SS_DESCRIPTION">To create a second-level auto attendants:</description>
                  <substep>
                    <text _locID="G4_L3_S3_SS1_TEXT">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">Repeat the steps in Step 2 to create the second-level auto attendant.  However, an extension number is not required</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S4_TEXT">Step 4: Configure the 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 combine together to give the caller the interface 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">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">Select the “top level” auto attendant.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS3_TEXT">Click "Properties" in the action pane.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS4_TEXT">Click the "Greetings" tab</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS5_TEXT">Click "Modify…" next to the Business hours greeting, click the "Use custom greeting file" radio button and click "Browse…" to select the .wav file containing the welcome greeting created in Step 1.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS6_TEXT">Click "OK" on the dialog to save the Business hours greeting</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS7_TEXT">Complete the above steps for the "Business hours main menu prompt" greeting.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS8_TEXT">Click the "Features" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS9_TEXT">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">Select the "Allow transfer to operator during business hours" checkbox.  This allows callers to be able to transfer by pressing 0.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS11_TEXT">Click on the "Key Mapping" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS12_TEXT">Select the "Enable business hours key mapping" checkbox.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS13_TEXT">Click the "New…" button to define the behavior for the 1 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS14_TEXT">In the Key Mapping Entry dialog box, select the "Presses this key:" radio button and enter 1 in the field. Check the "Perform this additional action:" checkbox and select the "Transfer to extension" radio button and then enter the appropriate extension. Click on "OK" to save the mapping for the 1 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS15_TEXT">Click the "New…" button to define the behavior for the 2 key.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L3_S4_SS16_TEXT">In the Key Mapping Entry dialog box, click the "Presses this key:" radio button and enter 2 in the field. Check the "Perform this additional action:" checkbox and select the "Run auto attendant" radio button choosing the "Browse" button to select the 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">Click "OK" to save the changes to the top-level auto attendant.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L3_S5_TEXT">Step 5: Configure the 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">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">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 in accordance 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 and .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 Forefront AntiVirus-->
        <link>
          <text _locID="G5_L1_TEXT">Protect your Exchange Servers from viruses, worms and other malware</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L1_S1_TEXT">Step 1: Learn about Forefront Security for Exchange Server</text>
                <description _locID="G5_L1_S1_DESCRIPTION">Learn more about how Microsoft Forefront Security for Exchange Server can help protect your Exchange servers from viruses, worms, and other malware.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S1_SS1_TEXT">Read about Microsoft Forefront Security for Exchange Server</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?linkid=68589</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S2_TEXT">Step 2: Install Forefront Security for Exchange Server</text>
                <description _locID="G5_L1_S2_DESCRIPTION">To install Forefront Security for Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S2_SS1_TEXT">Insert the Exchange DVD in your DVD drive and select “Install Microsoft Forefront Security for Exchange Server” from the first screen</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S2_SS2_TEXT">OR</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S2_SS3_TEXT">Download Forefront Security for Exchange Server</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?linkid=68582</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L1_DESCRIPTION">Microsoft Exchange Forefront Security for Exchange Server helps protect your Exchange servers from viruses, worms and other malware.</description>
        </link>
        <!--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">Go to Anti-spam management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L7_S1_SS2_TEXT">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">In the action pane, click "Enable Anti-spam Updates"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L7_S1_SS4_TEXT">Complete the Enable Anti-spam Updates wizard</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L7_DESC">To ensure 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">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L5_S1_SS2_TEXT">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">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">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">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">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 linked 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">Use the Update-Safelist cmdlet to update safelist information for Microsoft Office Outlook users.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS3_TEXT">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="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">Verify that the Microsoft Exchange EdgeSync service is replicating safelist aggregation data to Active Directory Application Mode (ADAM). (optional)</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L6_S1_SS6_TEXT">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">Read additional details for performing each of these steps:</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 additional information about safelist aggregation:</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 Microsoft Office 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 is going to have content filtering enabled:</description>
                  <substep>
                    <text _locID="G5_L8_S1_SS1_TEXT">Go to Anti-spam management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S1_SS2_TEXT">Select Content Filtering</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S1_SS3_TEXT">Verify that the status is "Enabled"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S1_SS4_TEXT">If it is not enabled, click "Enable" in the action pane</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">Go to database management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode\StorageGroupsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S2_SS2_TEXT">Select the storage group that you want to create the database in</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S2_SS3_TEXT">In the action pane, click the "New Mailbox Database"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S2_SS4_TEXT">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">Go to Recipient Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S3_SS2_TEXT">In the action pane, click "New Mailbox"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S3_SS3_TEXT">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">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 is going to have content filtering enabled:</description>
                  <substep>
                    <text _locID="G5_L8_S4_SS1_TEXT">Go to Anti-spam management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode\JunkEmailFeaturesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS2_TEXT">Select Content Filtering</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS3_TEXT">In the action pane, click "Properties"</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS4_TEXT">Select the "Action" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS5_TEXT">Select the checkbox for "Quarantine messages that have a SCL rating greater than or equal to:".</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L8_S4_SS6_TEXT">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">Additional information about how to manage the spam quarantine mailbox and how to set the SCL threshold should be reviewed.</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 Exchange product 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</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 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>UcnuLgPqTUDXMR0DWPy8hJdHzBk=</DigestValue></Reference></SignedInfo><SignatureValue>
    IZLe2oN4XJPIbUZNoG4Z8Xr8nKptzbBNaaxDIsV+IPb0+AcoJ81rUOtXaTwVgPwGPXo8Qa95
    xyOS0VDf+EhAV1S/YRARIVld8MwxzpYOTgvAx7TjKBEpCFetA8n2ovpyALjTNwLr62LX7WP1
    gfM90KdV13WEeB4w8iyAIMXuttRyUOFsm74BimNqo3sJX+TN8LX24lI1+2edfbZ24fcYfJ5f
    9nvwAAEYqaUjr0+YfS3mcP7ijEFSOyLIy1w1ptvWsJrrQyqxi8n7+oAKgwMBEuMZ7IzXsVGQ
    mAQubuhnJpKO+wKgsrmdaArzEIKCCYJYHE4NGkalAGIscq9mLU6jQg==
  </SignatureValue><KeyInfo>
      <KeyValue>
        <RSAKeyValue>
          <Modulus>
            zYGWOK5covLB397Qq5WN1jydH4vDXYYuXfCxcvWrrIhqtdqxInsLyMilS5FeIhPp+fUjnbX0
            bnau7+6kPMfEwFlcP6uzczMmpmKBYXmhYvRuiJXQbt3Hn9KkURF2YbpwimWhlhaJp12B0ERm
            5dtWnkDK/Nx2JC5EMADl1n17lRHVWB2j6E8LyYjcotZTmWzKY8qZapqSXkxNEegv01tbXl9S
            o3MtpbuERQ2MGRV2ywjamqZwFehN7Gn9XbJrj+0pUTc4i8ZGSRWUUJiw9Gik194JcWd0nneM
            HYVrl+rnX0XM4OZxDdFjAJN7MZiOC7QTvbPQ7vHfIe6pYGHuN0M9ww==
          </Modulus>
          <Exponent>AQAB</Exponent>
        </RSAKeyValue>
      </KeyValue>
      <X509Data>
        <X509Certificate>
          MIIFMzCCBBugAwIBAgIKYUaeywAEAAAAZTANBgkqhkiG9w0BAQUFADCBpjELMAkGA1UEBhMC
          VVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAcBgNVBAoTFU1p
          Y3Jvc29mdCBDb3Jwb3JhdGlvbjErMCkGA1UECxMiQ29weXJpZ2h0IChjKSAyMDAwIE1pY3Jv
          c29mdCBDb3JwLjEjMCEGA1UEAxMaTWljcm9zb2Z0IENvZGUgU2lnbmluZyBQQ0EwHhcNMDYw
          NDA0MTk0MzQ2WhcNMDcxMDA0MTk1MzQ2WjB0MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2Fz
          aGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0
          aW9uMR4wHAYDVQQDExVNaWNyb3NvZnQgQ29ycG9yYXRpb24wggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQDNgZY4rlyi8sHf3tCrlY3WPJ0fi8Ndhi5d8LFy9ausiGq12rEiewvI
          yKVLkV4iE+n59SOdtfRudq7v7qQ8x8TAWVw/q7NzMyamYoFheaFi9G6IldBu3cef0qRREXZh
          unCKZaGWFomnXYHQRGbl21aeQMr83HYkLkQwAOXWfXuVEdVYHaPoTwvJiNyi1lOZbMpjyplq
          mpJeTE0R6C/TW1teX1Kjcy2lu4RFDYwZFXbLCNqapnAV6E3saf1dsmuP7SlRNziLxkZJFZRQ
          mLD0aKTX3glxZ3Sed4wdhWuX6udfRczg5nEN0WMAk3sxmI4LtBO9s9Du8d8h7qlgYe43Qz3D
          AgMBAAGjggGSMIIBjjAOBgNVHQ8BAf8EBAMCBsAwHQYDVR0OBBYEFO7Za6l1U81P7htOGQYe
          o5yrz5T9MBMGA1UdJQQMMAoGCCsGAQUFBwMDMIGpBgNVHSMEgaEwgZ6AFCX4K0tdyHJUreX2
          oCoXFvvB+VOBoXSkcjBwMSswKQYDVQQLEyJDb3B5cmlnaHQgKGMpIDE5OTcgTWljcm9zb2Z0
          IENvcnAuMR4wHAYDVQQLExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jv
          c29mdCBSb290IEF1dGhvcml0eYIQaguZT8AAHasR2sQCoWYnujBLBgNVHR8ERDBCMECgPqA8
          hjpodHRwOi8vY3JsLm1pY3Jvc29mdC5jb20vcGtpL2NybC9wcm9kdWN0cy9Db2RlU2lnblBD
          QTIuY3JsME8GCCsGAQUFBwEBBEMwQTA/BggrBgEFBQcwAoYzaHR0cDovL3d3dy5taWNyb3Nv
          ZnQuY29tL3BraS9jZXJ0cy9Db2RlU2lnblBDQTIuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQA4
          2e+VOJtcmBRdVG5p3wLI57P708JNrS+rf1QN2jK2+GrmDfshGnc+pWh6tJV+ilzyQ8SDm2V9
          iFBRfIIU9YNz16K+XMoCcM4mbBe8UhSlicC35KHMoXWdkXE9G8BWAFa1+IQm2l4z+9Ylel6a
          2qb79PJBGqxVRq1I3JE4E1gJSfHzMYcfvASOWxJlA+kLUdChDIqZvdnBqNAIFSUhtbZXiRzR
          W4Y1pcr9qofsqTc/t0Nr4yDxRbx+runxVbKhSLxlvlM02cnoBmMEBnhuUP9Iu5vqQ1qH260K
          gPVZxSzk5X9bSuUyee4ihZIMLbNQW8bCQFhYq9LN4y/Bzextnzd5
        </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>
          MIIEwzCCA6+gAwIBAgIQaguZT8AAHasR2sQCoWYnujAJBgUrDgMCHQUAMHAxKzApBgNVBAsT
          IkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jvc29m
          dCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4XDTA2
          MDQwNDE3NDQxNFoXDTEyMDQyNjA3MDAwMFowgaYxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpX
          YXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9y
          YXRpb24xKzApBgNVBAsTIkNvcHlyaWdodCAoYykgMjAwMCBNaWNyb3NvZnQgQ29ycC4xIzAh
          BgNVBAMTGk1pY3Jvc29mdCBDb2RlIFNpZ25pbmcgUENBMIIBIDANBgkqhkiG9w0BAQEFAAOC
          AQ0AMIIBCAKCAQEAw8wgjbzf/z5Q7nrC1CQl9nbOIf/NKlZOypy3grI1eS0AxKgI1WPJt6X2
          6cHB1rGMlqIH+g+2glKa64LGvRDFqMDua4SOUxu7UPpkAYnBFtSCaABAeET1EjhO+2NR4Po9
          ueU3sd9jByM7cUA0R/Rrrkb1J3MeIstCGR5RtlKa06PQE8YZP3EGbfKVIURfQu3AyZlkILjB
          NPyiROZ7sh0vuKbe9KHfmyEP/lgxQVU4fq9Y5+TsWXklq/cqLxE/OHg+Qn+naOR+ImgX5kqS
          xHhEUkehT4SJk5vAZ3vqCfuGA332mXE8K6dmmMzfLeIrAhoPNEhl9TwSr/GHHB0mUm/MAwIB
          A6OCASowggEmMBMGA1UdJQQMMAoGCCsGAQUFBwMDMIGiBgNVHQEEgZowgZeAEFvQcO9pcp4j
          UX4Usk2O/8uhcjBwMSswKQYDVQQLEyJDb3B5cmlnaHQgKGMpIDE5OTcgTWljcm9zb2Z0IENv
          cnAuMR4wHAYDVQQLExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jvc29m
          dCBSb290IEF1dGhvcml0eYIPAMEAizw8iBHRPvZj7N9AMBIGCSsGAQQBgjcVAQQFAgMDAAQw
          HQYDVR0OBBYEFCX4K0tdyHJUreX2oCoXFvvB+VOBMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIA
          QwBBMAsGA1UdDwQEAwIBRjAPBgNVHRMBAf8EBTADAQH/MAkGBSsOAwIdBQADggEBAGPj4PMF
          uLDqCws00YIxPoliRdUIp/lhZcguA/o4SEHPtfIng9PjxVZTqLUZzszm8aD5VrZIlEck5akf
          3HrU9hZ6EtvzkBvsCF2zhZC5jFi7HMyV05WUM/SR3v+Im15LSVA5JjogG1Q3/H1cFZPD3ByO
          8GFSPOUH7WbveeyPzldjZZUYSaB632W33yau/sgStsaizMZfi3Dzyturgm4H3GUZuaj2hsIJ
          QpjxJqxperHBK6ewZh+lr4cIa5cTuLA2mR4FoxM4o8CsMD66IdcwpspiEhyvV43l8XoRul48
          DDfxk8GSiE4EWgVcx8/WqdnhfZF4J/u0bqWPBjNYsV4qEQ8=
        </X509Certificate>
      </X509Data>
    </KeyInfo><Object id="ts-countersig"><X509Data><X509Certificate>MIID/zCCAuegAwIBAgIQDekr8NTYKYgYMgUJXpp2iDANBgkqhkiG9w0BAQUFADBTMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xKzApBgNVBAMTIlZlcmlTaWduIFRpbWUgU3Rh
bXBpbmcgU2VydmljZXMgQ0EwHhcNMDMxMjA0MDAwMDAwWhcNMDgxMjAzMjM1OTU5WjBXMQswCQYD
VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xLzAtBgNVBAMTJlZlcmlTaWduIFRpbWUg
U3RhbXBpbmcgU2VydmljZXMgU2lnbmVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
slAoSN3TaHqEGERmdV1+xLifYyb/PUOcfBE4ECVVc9l1J2n9TrkgXNMK+aAbKu1VViFh2B7b5Lwz
a8fv3aM3ZY4bkwy2Ux5cfGY1XwWKRf52Tt9TgKKBIJ2uiFyiCPflMPnuIjdMQgrO38YfxNZV6YE/
tVKjLKoBevKiqo01/p/mXWoFnz1r47+WwP7MYPlA5wegROuBUW6lKvK2ihAo7Y/cBqCGUJp7SggN
MB3KEJ5r9+lYrgSpQJmyKOiPFqw841NvS9M1nbVvZB2zliy7Ped56216+RbmJq2v75lTt0Aslbh5
qv7UUqspdH5C7DkeomoW5lm7JGjYAIBDEIeAawIDAQABo4HKMIHHMDQGCCsGAQUFBwEBBCgwJjAk
BggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29tMAwGA1UdEwEB/wQCMAAwMwYDVR0f
BCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vdHNzLWNhLmNybDAWBgNVHSUBAf8E
DDAKBggrBgEFBQcDCDAOBgNVHQ8BAf8EBAMCBsAwJAYDVR0RBB0wG6QZMBcxFTATBgNVBAMTDFRT
QTIwNDgtMS01NDANBgkqhkiG9w0BAQUFAAOCAQEAh3hw2k5SASBb4HnJgjDE/bkZlr2RAMO9zc3G
9A7Y//lNwDNiMBHF9XQb1JLeX5wgE7F8Rb5QzYPngBeDpyeTZxNG+8q4mEEDzJtRWwWLf6hv8xtQ
GyQu8mmNbCL3u8oWle0MdMBod9nrmWKHwXOQ+Il0eiOro5h7l7H3jylxTS51G0hB2vC1DSBU1neg
l4Jjaf0Jz4rwdbsJm9n5EVUmmmEyvnoCsHuGvqLDiyIseNE1drySc1z5ueZMFQojzOTS1DQuSUAV
PA9geiTGpWbvls9w6z7n9A1+3NF8o3ZxacGcT0cwNSGxoq8aYjwr2Y6qKgd72BizXHvinaVv/jyJ
rQ==</X509Certificate></X509Data><X509Data><X509Certificate>MIIDxDCCAy2gAwIBAgIQR78Zld+NUkZD99ttSA0xpDANBgkqhkiG9w0BAQUFADCBizELMAkGA1UE
BhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNV
BAoTBlRoYXd0ZTEdMBsGA1UECxMUVGhhd3RlIENlcnRpZmljYXRpb24xHzAdBgNVBAMTFlRoYXd0
ZSBUaW1lc3RhbXBpbmcgQ0EwHhcNMDMxMjA0MDAwMDAwWhcNMTMxMjAzMjM1OTU5WjBTMQswCQYD
VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xKzApBgNVBAMTIlZlcmlTaWduIFRpbWUg
U3RhbXBpbmcgU2VydmljZXMgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCpyrKk
zM0grwp9iayHdfC0TvHfwQ+/Z2G9o2Qc2rv5yjOrhDCJWH6M22vdNp4Pv9HsePJ3pn5vPL+Trw26
aPRslMq9Ui2rSD31ttVdXxsCn/ovax6k96OaphrIAuF/TFLjDmDsQBx+uQ3eP8e034e9X3pqMS4D
mYETqEcgzjFzDVctzXg0M5USmRK53mgvqubjwoqMKsOLIYdmvYNYV291vzyqJoddyhAVPJ+E6lTB
Cm7E/sVK3bkHEZcifNs+J9EeeOyfMcnx5iIZ28SzR0OaGl+gHpDkXvXufPF9q2IBj/VNC97QIlao
lc2uiHau7roN8+RN2aD7aKCuFDuzh8G7AgMBAAGjgdswgdgwNAYIKwYBBQUHAQEEKDAmMCQGCCsG
AQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0TAQH/BAgwBgEB/wIBADBBBgNV
HR8EOjA4MDagNKAyhjBodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9UaGF3dGVUaW1lc3RhbXBpbmdD
QS5jcmwwEwYDVR0lBAwwCgYIKwYBBQUHAwgwDgYDVR0PAQH/BAQDAgEGMCQGA1UdEQQdMBukGTAX
MRUwEwYDVQQDEwxUU0EyMDQ4LTEtNTMwDQYJKoZIhvcNAQEFBQADgYEASmv56ljCRBwxiXmZK5a/
gqwB1hxMzbCKWG7fCCmjXsjKkxPnBFIN70cnLwA4sOTJk06a1CJiFfc/NyFPcDGA8Ys4h7Po6JcA
/s9Vlk4k0qknTnqut2FB8yrO58nZXt27K4U+tZ212eFX/760xX71zwye8Jf+K9M7UhsbOCf3P0o=</X509Certificate></X509Data><CounterSignature xmlns="http://schemas.microsoft.com/xmldsig/timestamp/2003" ts-format="cms-timestamp-message">MIIDLQYJKoZIhvcNAQcCoIIDHjCCAxoCAQExDjAMBggqhkiG9w0CBQUAMIIBEwYJKoZIhvcNAQcB
oIIBBASCAQAhkt7ag3hck8htRk2gbhnxevycqm3NsE1prEMixX4g9vT4BygnzWtQ61dpPBWA/AY9
ejxBr3nHI5LRUN/4SEBXVL9hEBEhWV3wzDHOlg5OC8DHtOMoESkIV60Dyfai+nIAuNM3AuvrYtft
Y/WB8z3Qp1XXdYR4HjDyLIAgxe621HJQ4WybvgGKY2qjewlf5M3wtfbiUjX7Z519tnbh9xh8nl/2
e/AAARippSOvT5h9LeZw/uKMQVI7IsjLXDWm29awmutDKrGLyfv6gAqDAwES4xnsjNexUZCYBC5u
6Gcmko77AqCyuZ1oCvMQgoIJglgcTg0aRqUAYixyr2YtTqNCMYIB7DCCAegCAQEwZzBTMQswCQYD
VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xKzApBgNVBAMTIlZlcmlTaWduIFRpbWUg
U3RhbXBpbmcgU2VydmljZXMgQ0ECEA3pK/DU2CmIGDIFCV6adogwDAYIKoZIhvcNAgUFAKBZMBgG
CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MTIwMzA5MDkyMlowHwYJ
KoZIhvcNAQkEMRIEELEs4teU0DJeIi3p3pDre9AwDQYJKoZIhvcNAQEBBQAEggEAfJ7U2+3vUosN
uEkFRvjoolpXGKQJ2JipGQVbUyRZZOIbt0ka0UD4vvGvbAYLQ/RmsEUtToEBaBZBwsLg4BZ9/Hz6
TIHvP5c0CNLKOGdF0V5oEDgfy7YrCwIm55iXliCJDyfeyQY8/cVUDDvqGxevRUDIaVEAprJSqVi4
rhoEuCppwKorIf4hHuIClbVELA9YGYLVqEX3wzArWfJ88WFix3tnWWG2VwXu/rcgwB8yUjRTR6qG
Kdt4dV6to2OD7TkZsdZLEl6g81vlTS/f4/O5uQqtDfSphO4LDMFKygljOKCPvT+8pOMrbX249F+L
AowYWTU+14cjSRyJu99oggaGHw==</CounterSignature></Object></Signature></startpage>