<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='StartPage.xsl'?><!--
//  Copyright (C) 2007 Microsoft Corporation. All rights reserved.
//  The xml file that describes the content of Finalize Deployment 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 Finalize Deployment</title>
  <groups>
    <!--This is the group for "All Exchange Servers", had to remove action link because this is different on an Edge server-->
    <group applyOn="Mailbox,ClientAccess,HubTransport,UnifiedMessaging">
      <icon>ServerConfiguration</icon>
      <text _locID="G6_TEXT">All Exchange Servers</text>
      <links>
        <!--This link is for the Server Product Key-->
        <link>
          <text _locID="G6_L1_TEXT">Enter the Exchange Server Product Key</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G6_L1_S1_TEXT">Step 1: Obtain Product Key</text>
                <description _locID="G6_L1_S1_DESCRIPTION">If you have purchased Exchange Server through Volume Licensing or Retail, please use the product key that came with your media. If you are evaluating Exchange Server and would like information on how to purchase Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G6_L1_S1_SS1_TEXT">- How to buy Exchange Server 2007.</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?LinkId=63906</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G6_L1_S2_TEXT">Step 2: Enter the product key for the server </text>
                <description _locID="G6_L1_S2_DESCRIPTION">The product key is entered using a wizard that runs against the desired server object.</description>
                <substeps>
                  <description _locID="G6_L1_S2_SS1_DESCRIPTION">To enter a product key for a server:</description>
                  <substep>
                    <text _locID="G6_L1_S2_SS1_TEXT">1. Go to Server Configuration.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ServersNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G6_L1_S2_SS2_TEXT">2. Select the server that requires the product key.</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L1_S2_SS3_TEXT">3. In the action pane, click "Enter Product Key".</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L1_S2_SS4_TEXT">4. Complete the Product Key wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G6_L1_DESCRIPTION">The product key is no longer entered during setup and is instead configured in the Exchange Management Console after installation. Until the product key is entered, the server will run in trial mode.</description>
        </link>
        <!--This link is for running ExBPA-->
        <link>
          <text _locID="G6_L2_TEXT">Run the Microsoft Exchange Best Practices Analyzer</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G6_L2_S1_TEXT">Step 1: Run the Exchange Best Practices Analyzer</text>
                <description _locID="G6_L2_S1_DESCRIPTION">The Exchange Best Practices Analyzer programmatically collects settings and values from data repositories such as the Active Directory directory service, registry, Internet Information Services (IIS) metabase, and Performance Monitor. After collection of this information, a set of comprehensive "best practice" rules is applied to the topology. Administrators running this tool receive a detailed report with recommendations for changes that can be made to the environment to achieve greater performance, scalability, and availability.</description>
                <substeps>
                  <substep>
                    <text _locID="G6_L2_S1_SS1_TEXT">1. Go to the Toolbox.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ToolboxNode</argument></action>
                  </substep>
                  <substep>
                    <text _locID="G6_L2_S1_SS2_TEXT">2. Click "Best Practices Analyzer".</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L2_S1_SS3_TEXT">3. In the action pane, select "Open Tool".</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L2_S1_SS4_TEXT">4. Complete the Best Practices Analyzer wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G6_L2_DESCRIPTION">The Microsoft Exchange Best Practices Analyzer should be run proactively on production Exchange servers after installation and on a scheduled basis to determine the overall health of those servers and topology. The tool will identify any items that do not adhere to Microsoft best practices and make recommendations about changes that should be applied.</description>
        </link>
        <!--This link is for Forefront AntiVirus-->
        <link>
          <text _locID="G6_L3_TEXT">Protect your Exchange Servers from Viruses, Worms, and Other Malware</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G6_L3_S1_TEXT">Step 1: Learn about Forefront Security for Exchange Server</text>
                <description _locID="G6_L3_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="G6_L3_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="G6_L3_S2_TEXT">Step 2: Install Forefront Security for Exchange Server</text>
                <description _locID="G6_L3_S2_DESCRIPTION">To install Forefront Security for Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G6_L3_S2_SS1_TEXT">- Insert the Exchange Server DVD in your DVD drive and select "Install Microsoft Forefront Security for Exchange Server" from the first screen,</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L3_S2_SS2_TEXT">OR</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L3_S2_SS3_TEXT">- Download Forefront Security for Exchange Server.</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?LinkId=98787</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G6_L3_DESCRIPTION">Microsoft Forefront Security for Exchange Server helps protect your Exchange servers from viruses, worms, and other malware.</description>
        </link>
      </links>
    </group>
    <group applyOn="Edge">
      <icon>ServerConfiguration</icon>
      <text _locID="G7_TEXT">All Exchange Servers</text>
      <links>
        <!--This link is for the Server Product Key-->
        <link>
          <text _locID="G7_L1_TEXT">Enter the Exchange Server Product Key</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G7_L1_S1_TEXT">Step 1: Obtain Product Key</text>
                <description _locID="G7_L1_S1_DESCRIPTION">If you have purchased Exchange Server through Volume Licensing or Retail, please use the product key that came with your media. If you are evaluating Exchange Server and would like more information about how to purchase Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G7_L1_S1_SS1_TEXT">- How to buy Exchange Server 2007.</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?LinkId=63906</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G7_L1_S2_TEXT">Step 2: Enter the product key for the server </text>
                <description _locID="G7_L1_S2_DESCRIPTION">The product key is entered using a wizard that runs against the desired server object.</description>
                <substeps>
                  <description _locID="G7_L1_S2_SS1_DESCRIPTION">To enter a product key for a server:</description>
                  <substep>
                    <text _locID="G7_L1_S2_SS1_TEXT">1. Go to Edge Transport.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G7_L1_S2_SS2_TEXT">2. Select the server that requires the product key.</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L1_S2_SS3_TEXT">3. In the action pane, click "Enter Product Key".</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L1_S2_SS4_TEXT">4. Complete the Product Key wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G7_L1_DESCRIPTION">The product key is no longer entered during setup and is instead configured in the Exchange Management Console after installation. Until the product key is entered, the server will run in trial mode.</description>
        </link>
        <!--This link is for running ExBPA-->
        <link>
          <text _locID="G7_L2_TEXT">Run the Exchange Best Practices Analyzer</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G7_L2_S1_TEXT">Step 1: Run the Exchange Best Practices Analyzer tool</text>
                <description _locID="G7_L2_S1_DESCRIPTION">The Exchange Best Practices Analyzer programmatically collects settings and values from data repositories such as the Active Directory directory service, registry, Internet Information Services (IIS) metabase, and Performance Monitor. After collection of this information, a set of comprehensive "best practice" rules is applied to the topology. Administrators running this tool receive a detailed report with recommendations for changes that can be made to the environment to achieve greater performance, scalability, and availability.</description>
                <substeps>
                  <substep>
                    <text _locID="G7_L2_S1_SS1_TEXT">1. Go to the Toolbox.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ToolboxNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G7_L2_S1_SS2_TEXT">2. Click "Best Practices Analyzer."</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L2_S1_SS3_TEXT">3. In the action pane, click "Open Tool".</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L2_S1_SS4_TEXT">4. Complete the Best Practices Analyzer wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G7_L2_DESCRIPTION">The Microsoft Exchange Best Practices Analyzer should be run proactively on production Exchange servers after install and on a scheduled basis to determine the overall health of those servers and topology. The tool will identify any items that do not adhere to Microsoft best practices and will make recommendations on changes that should be applied.</description>
        </link>
        <!--This link is for Forefront AntiVirus-->
        <link>
          <text _locID="G7_L3_TEXT">Protect your Exchange Servers from Viruses, Worms and other Malware</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G7_L3_S1_TEXT">Step 1: Learn about Forefront Security for Exchange Server</text>
                <description _locID="G7_L3_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="G7_L3_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="G7_L3_S2_TEXT">Step 2: Install Forefront Security for Exchange Server</text>
                <description _locID="G7_L3_S2_DESCRIPTION">To install Forefront Security for Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G7_L3_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="G7_L3_S2_SS2_TEXT">OR</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L3_S2_SS3_TEXT">- Download Forefront Security for Exchange Server.</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?LinkId=98787</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G7_L3_DESCRIPTION">Microsoft Forefront Security for Exchange Server helps protect your Exchange servers from viruses, worms and other malware.</description>
        </link>
      </links>
    </group>
    <group applyOn="Mailbox">
      <icon>MailboxServer</icon>
      <text _locID="G3_TEXT">Mailbox</text>
      <links>
        <!--This link is for Configuring OABs for Distribtion to OL 12 (1)-->
        <link>
          <text _locID="G3_L1_TEXT">Configure offline address book (OAB) distribution for Outlook 2007 Clients</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G3_L1_S1_TEXT">Step 1: Install at least one Client Access server in the Exchange organization</text>
                <description _locID="G3_L1_S1_DESCRIPTION">A Client Access server will have an offline address book (OAB) virtual directory automatically created on it to be used for Web distribution.</description>
                <substeps>
                  <substep>
                    <text _locID="G3_L1_S1_SS1_TEXT">- Read about how to set up a Client Access server.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/406a2d1a-ddc6-4d43-a162-c7179d31a973.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G3_L1_S2_TEXT">Step 2: Modify Web-Based Distribution on the Default Offline Address Book</text>
                <description _locID="G3_L1_S2_DESCRIPTION">After you install a Client Access server, Web-based distribution is enabled by default. However, you can change the virtual directory for the Default Offline Address Book.</description>
                <substeps>
                  <description _locID="G3_L1_S2_SS_DESCRIPTION">To change the OAB virtual directory associated with the Default Offline Address Book:</description>
                  <substep>
                    <text _locID="G3_L1_S2_SS1_TEXT">1. Go to Offline Address Book management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\OfflineAddressBookResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS2_TEXT">2. In the result pane, select "Default Offline Address Book".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS4_TEXT">4. Click the "Distribution" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS5_TEXT">5. Select the "Enable Web-based distribution" check box.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS6_TEXT">6. Click "Add", and then select an OAB virtual directory.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS_TEXT">7. Click "OK" to add the OAB virtual directory as a Web-based distribution point.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G3_L1_S3_TEXT">Step 3: (Optional) Set the external URL for the OAB virtual directory</text>
                <description _locID="G3_L1_S3_DESCRIPTION">To allow Outlook 2007 to download an OAB from a remote network, you must configure an external URL.</description>
                <substeps>
                  <description _locID="G3_L1_S3_SS_DESCRIPTION">To set an external URL on an OAB virtual directory:</description>
                  <substep>
                    <text _locID="G3_L1_S3_SS1_TEXT">1. Go to Offline Address Book Distribution management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ClientAccessNode\OabDistributionResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS2_TEXT">2. In the result pane, select the server that hosts the OAB virtual directory that you want to configure.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS3_TEXT">3. In the work pane, select the OAB virtual directory that you want to configure.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS4_TEXT">4. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS5_TEXT">5. Click the "URLs" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS6_TEXT">6. In the "External URL" box, type the fully qualified domain name (FDQN) where Outlook clients from outside the corporate network can access this virtual directory.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS7_TEXT">7. Click "OK".</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G3_L1_DESCRIPTION">Outlook 2007 can take advantage of a new Web-based distribution method for offline address books (OABs). To take advantage of the Web-based distribution method, you must enable OAB distribution.</description>
        </link>
        <!--This link is for Configuring OABs for Distribtion to OL 11 (2) -->
        <link>
          <text _locID="G3_L2_TEXT">Configure offline address book (OAB) public folder distribution for Outlook 2003 and earlier clients</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G3_L2_S1_TEXT">Step 1: Create a public folder database</text>
                <description _locID="G3_L2_S1_DESCRIPTION">For Outlook 2003 and earlier, a public folder database is required for OAB distribution.</description>
                <substeps>
                  <description _locID="G3_L2_S1_SS_DESCRIPTION">To create a public folder database:</description>
                  <substep>
                    <text _locID="G3_L2_S1_SS1_TEXT">1. Go to Database Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode\StorageGroupsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S1_SS2_TEXT">2. If there is no public folder database, select a storage group where you want to create the public folder database.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S1_SS3_TEXT">3. In the action pane, click "New Public Folder Database".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S1_SS4_TEXT">4. Complete the New Public Folder Database wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G3_L2_S2_TEXT">Step 2: Configure the Default Offline Address Book</text>
                <description _locID="G3_L2_S2_DESCRIPTION">You must configure the Default OAB for public folder distribution and for version 3 and version 4 of OAB generation (if all your client computers are running Outlook 2003 SP2 or later, you can select only version 4).</description>
                <substeps>
                  <description _locID="G3_L2_S2_SS_DESCRIPTION">To configure the Default Offline Address Book:</description>
                  <substep>
                    <text _locID="G3_L2_S2_SS1_TEXT">1. Go to Offline Address Book Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationMailboxNode\OfflineAddressBookResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS2_TEXT">2. In the result pane, select "Default Offline Address Book".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS4_TEXT">4. Click the "Distribution" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS5_TEXT">5. Select the check boxes under "Client Support" that correspond to the Outlook versions in your organization.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS6_TEXT">6. Select the "Enable public folder distribution" check box.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G3_L2_DESCRIPTION">OABs may need to be configured for coexistence with Outlook 2003 and earlier clients.</description>
        </link>
      </links>
    </group>
    <group applyOn="ClientAccess">
      <icon>ClientAccessServer</icon>
      <text _locID="G2_TEXT">Client Access</text>
      <links>
        <!-- This link is for configuring SSL for Client Access Server-->
        <link>
          <text _locID="G2_L2_TEXT">Configure SSL for your Client Access Server</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G2_L2_S1_TEXT">Step 1: Obtain an SSL certificate</text>
                <description _locID="G2_L2_S1_DESCRIPTION">There are three ways to obtain a Secure Sockets Layer (SSL) certificate:</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S1_SS1_TEXT">- Option 1: Use the self-signed SSL certificate that Exchange 2007 installs by default. Use of the self-signed certificate is not supported by Outlook Anywhere or the offline address book.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS2_TEXT">- Option 2: Purchase an SSL certificate from a well-known certification authority (CA).</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS3_TEXT">- Option 3: Obtain an SSL certificate from a Windows PKI certification authority.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS4_TEXT">If you choose Option 1, skip steps 2 and 3 and go straight to step 4.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS5_TEXT">If you choose Option 2 or Option 3, go straight to step 2.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS6_TEXT">Note: For all three options, Exchange ActiveSync will require the device to have a copy of the SSL certificate installed in the Trusted Root Certificate Store.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L2_S2_TEXT">Step 2: Generate and submit the certificate request</text>
                <description _locID="G2_L2_S2_DESCRIPTION">Create a new certificate request for Secure Sockets Layer (SSL) services.</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S2_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS2_TEXT">2. Run the following command, replacing domainname and friendlyname with your domain name and display name: New-ExchangeCertificate -GenerateRequest -domainname mail.contoso.msft,autodiscover.contoso.msft,myserver,myserver.internal.contoso.msft -FriendlyName mail.contoso.msft -privatekeyexportable:$true -path c:\cert_myserver.txt</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS3_TEXT">Note: "DomainName" is used to populate one or more domain names (FQDNs) or server names in the resulting certificate request.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS4_TEXT">Note: "FriendlyName" is used to specify a display name for the resulting certificate. The display name must be fewer than 64 characters.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS5_TEXT">3. Submit the request to the certification authority and have the CA generate the certificate.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L2_S3_TEXT">Step 3: Enable the certificate on the Default Web site</text>
                <description _locID="G2_L2_S3_DESCRIPTION">After your certificate has been generated, you must import it and then enable the certificate on the Default Web site.</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S3_SS1_TEXT">From the computer where step 2 was run, import the certificate. To import the certificate, do the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS2_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS3_TEXT">2. Run the following command. Import-ExchangeCertificate -path c:\newcert.cer</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS4_TEXT">Note: "c:\newcert.cer" is the location and name of your certificate.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS5_TEXT">Copy the thumbprint of the certificate, which is the digest of the certificate data, to the clipboard by doing the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS6_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS7_TEXT">2. Run the following command: dir cert:\LocalMachine\My | fl</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS8_TEXT">3. Locate the certificate that you just imported by finding the one that matches FriendlyName from step 2. Then copy the Thumbprint property of that certificate to the Windows Clipboard.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS9_TEXT">Enable the certificate on the Default Web site by doing the following:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS10_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS11_TEXT">2. Run the following command: enable-ExchangeCertificate -thumbprint &lt;value copied to the Clipboard&gt; -services "IIS,IMAP,POP"</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S3_SS12_TEXT">3. Using the "enable-ExchangeCertificate" cmdlet will update the certificate mapping, replacing the self-signed certificate that is installed by default with Exchange 2007 and configured in IIS, IMAP4, POP3.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L2_S4_TEXT">Step 4: Require the Client Access server virtual directories to use SSL</text>
                <description _locID="G2_L2_S4_DESCRIPTION">By default, the Default Web site in IIS is configured to require SSL for all virtual directories except the offline address book virtual directory. However, you can configure additional virtual directories for each Client Access feature. You must confirm that each virtual directory is configured to require SSL. The Client Access virtual directories are as follows:</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S4_SS1_TEXT">- Outlook Web Access 2007 virtual directory:  owa</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS2_TEXT">- Outlook Web Access 2003 and WebDAV virtual directories: exchange and public</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS3_TEXT">- Exchange ActiveSync virtual directory: Microsoft-Server-ActiveSync</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS4_TEXT">- Outlook Anywhere virtual directory: Rpc</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS5_TEXT">- Autodiscover virtual directory: Autodiscover</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS6_TEXT">- Exchange Web Services virtual directory: EWS</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS7_TEXT">- Unified Messaging virtual directory: Unified Messaging</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS8_TEXT">- Offline Address Book virtual directory: OAB</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS9_TEXT">For each of the Client Access virtual directories that you will use, open Internet Information Services (IIS) Manager, and follow these steps:</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS10_TEXT">1. Under Default Web site, select the virtual directory that you want, for example, "owa".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS11_TEXT">2. Right-click the virtual directory, and then click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS12_TEXT">3. Click the "Directory Security" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS13_TEXT">4. In the "Secure Communications" section, click "Edit".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS14_TEXT">5. In the "Secure Communications" dialog box, make sure that both the "Require secure channel (SSL)" check box and the "Require 128-bit encryption" check box are selected.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS15_TEXT">6. Click "OK" to save your changes.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS16_TEXT">7. Restart the POP3 and IMAP4 services by opening the Services Windows administrative tool, selecting "Microsoft Exchange POP3" or "Microsoft Exchange IMAP4", right-clicking the name of the service, and then clicking "Restart". IIS does not have to be restarted.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L2_S5_TEXT">Read more about SSL on the Client Access server</text>
                <substeps>
                  <substep>
                    <text _locID="G2_L2_S5_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>
            </steps>
          </postIt>
          <description _locID="G2_L2_DESCRIPTION">An SSL certificate is required on your Client Access server to help secure the channel between your clients and your Exchange server. If your network offloads SSL with an SSL accelerator or a similar device, you can skip this step.</description>
        </link>
        <!--This link is for configuring ActiveSync-->
        <link>
          <text _locID="G2_L1_TEXT">Configure Exchange ActiveSync</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G2_L1_S1_TEXT">Step 1: Verify firewall settings for Direct Push mobile devices</text>
                <description _locID="G2_L1_S1_DESCRIPTION">Verify the firewall settings for mobile devices that are Direct Push-compatible and are running Windows Mobile 5.0 and the Messaging Security and Feature Pack (MSFP) and later versions of Windows Mobile software. Direct Push is designed to keep a mobile device up-to-date over a cellular network connection. Direct Push performance and device battery life can be enhanced by modifying your firewall settings to ensure the time-out value is between 15 and 30 minutes.</description>
                <substeps>
                  <substep>
                    <text _locID="G2_L1_S1_SS1_TEXT">Read more about how to adjust firewall settings for Direct Push.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/373c1629-3d4b-4828-b014-9e103de4ef25.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S2_TEXT">Step 2: Create an Exchange ActiveSync mailbox policy</text>
                <description _locID="G2_L1_S2_DESCRIPTION">You can create an Exchange ActiveSync mailbox policy to apply security and password settings to a mailbox. To use remote device wipe functionality on a mobile device that has Windows Mobile 5.0 or later versions and the MSFP installed, a mailbox policy must be applied to the device.</description>
                <substeps>
                  <description _locID="G2_L1_S2_SS_DESCRIPTION">To create an Exchange ActiveSync Mailbox policy:</description>
                  <substep>
                    <text _locID="G2_L1_S2_SS1_TEXT">1. Go to Exchange ActiveSync Policy Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationClientAccessNode\ActiveSyncResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S2_SS2_TEXT">2. In the action pane, click "New Exchange ActiveSync Mailbox Policy".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S2_SS3_TEXT">3. Add the information that is required to create an Exchange ActiveSync mailbox policy that matches your organization’s security requirements, and then click "New" to continue.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S3_TEXT">Step 3: Assign new users to the Exchange ActiveSync mailbox policy</text>
                <description _locID="G2_L1_S3_DESCRIPTION">In Exchange Server 2007, you can assign Exchange ActiveSync mailbox policies at the user level for greater control. New users can be assigned an Exchange ActiveSync mailbox policy by using the New Mailbox wizard. In Exchange Server 2007 Service Pack 1 (SP1), you can designate one Exchange ActiveSync mailbox policy to be the default policy for all new users.</description>
                <substeps>
                  <description _locID="G2_L1_S3_SS_DESCRIPTION">To assign an Exchange ActiveSync mailbox policy to a new user:</description>
                  <substep>
                    <text _locID="G2_L1_S3_SS1_TEXT">1. Go to Recipient Configuration.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS2_TEXT">2. In the action pane, click "New Mailbox".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS3_TEXT">3. Fill in the mailbox details for the new user account.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS4_TEXT">4. In the Mailbox Settings section, select the "Exchange ActiveSync mailbox policy" check box, and then click "Browse".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS5_TEXT">5. Select the appropriate mailbox policy for this user, and then click "OK".</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S4_TEXT">Step 4: Assign existing users to the Exchange ActiveSync mailbox policy</text>
                <description _locID="G2_L1_S4_DESCRIPTION">Existing users are assigned an Exchange ActiveSync mailbox policy as part of their mailbox properties.</description>
                <substeps>
                  <description _locID="G2_L1_S4_SS_DESCRIPTION">To assign an Exchange ActiveSync mailbox policy to an existing user:</description>
                  <substep>
                    <text _locID="G2_L1_S4_SS1_TEXT">1. Go to Recipient Configuration.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS2_TEXT">2. Select the user that you want to add to an Exchange ActiveSync mailbox policy.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS4_TEXT">4. Click the "Mailbox Features" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS5_TEXT">5. Click the Exchange ActiveSync feature in the list, and then click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS6_TEXT">6. Select the "Apply an Exchange ActiveSync mailbox policy" check box, and then click "Browse".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS7_TEXT">7. Select the appropriate policy for this user, and then click "OK".</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L1_S5_TEXT">You can also assign an Exchange ActiveSync mailbox policy to a user by using the Set-CASMailbox command.</text>
                <substeps>
                  <substep>
                    <text _locID="G2_L1_S5_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S5_SS2_TEXT">2. Run the following command: Set-CASMailbox –Identity adam@contoso.com –ActiveSyncMailboxPolicy SalesPolicy</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G2_L1_DESCRIPTION">Exchange 2007 ActiveSync provides secure, always-up-to-date access to messaging from mobile devices. ActiveSync must be configured for optimal performance.</description>
        </link>
      </links>
    </group>
    <group applyOn="HubTransport">
      <icon>BridgeheadServer</icon>
      <text _locID="G1_TEXT">Hub Transport</text>
      <links>
        <!--This Link is Used to Configure Accepted Domains (1) -->
        <link>
          <text _locID="G1_L1_TEXT">Configure Domains for which You Will Accept E-Mail</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G1_L1_S1_TEXT">Step 1: Create an accepted domain entry.</text>
                <description _locID="G1_L1_S1_DESCRIPTION">As part of the Hub Transport server installation, a default accepted domain is created as an authoritative domain for the Exchange organization. The default accepted domain is the fully qualified domain name (FQDN) for your forest root domain. You may want to add authoritative domains for your organization, such as external SMTP domains that differ from your internal SMTP domains. Accepted domains include both authoritative domains and relay domains.</description>
                <substeps>
                  <description _locID="G1_L1_S1_SS_DESCRIPTION">To create an accepted domain entry:</description>
                  <substep>
                    <text _locID="G1_L1_S1_SS1_TEXT">1. Go to Accepted Domain Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationBridgeheadNode\AcceptedDomainsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS2_TEXT">2. In the action pane, click "New Accepted Domain".</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS3_TEXT">3. Complete the New Accepted Domain wizard to add an authoritative domain or relay domain. (Note: You must configure an accepted domain before that SMTP namespace can be used in an e-mail address policy.)</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS4_TEXT">4. Read more about how to manage accepted domains.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/c1839a5b-49f9-4c53-b247-f4e5d78efc45.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L1_DESCRIPTION">You must create an accepted domain entry for each SMTP domain for which you will accept e-mail.</description>
        </link>
        <!--This Link is Used to Configure Edge Transport Subscriptions (2) -->
        <link>
          <text _locID="G1_L2_TEXT">Subscribe the Edge Transport Server</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G1_L2_S1_TEXT">Step 1: Prepare to run the Microsoft Exchange EdgeSync service</text>
                <substeps>
                  <substep>
                    <text _locID="G1_L2_S1_SS1_TEXT">1. Verify that the perimeter network firewall that separates the Edge Transport server from the Exchange organization is configured to enable communications through the correct ports. By default, TCP port 50636 is used for directory synchronization from Hub Transport servers to the Edge Transport server. This port must be open for successful EdgeSync synchronization.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S1_SS2_TEXT">Read more about how to prepare to run the Microsoft Exchange EdgeSync service.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/edcc6d86-f45b-4449-85fc-7e39e1221d93.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S1_SS3_TEXT">2. Verify that Domain Name System (DNS) host name resolution is successful from the Edge Transport server to the Hub Transport server and from the Hub Transport server to the Edge Transport server. </text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S1_SS4_TEXT">Read more about how to configure DNS settings for Exchange 2007 servers.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/de468880-4a6b-42dd-837c-64b974d7da59.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S1_SS5_TEXT">3. License the Edge Transport server. If the product key is applied on the Edge Transport server after you perform the Edge Subscription process, the licensing information is not updated in the Exchange organization, and you must resubscribe the Edge Transport server.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S1_SS6_TEXT">Read more about how to enter the product key.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/40d9e583-69cd-4363-807f-43e02e03ca78.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S2_TEXT">Step 2: Export the Edge Subscription file</text>
                <description _locID="G1_L2_S2_SS_DESCRIPTION">On the Edge Transport server, create an Edge Subscription file.</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L2_S2_SS1_TEXT">- Read more about how to export an Edge Subscription file.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/3ecff856-48d8-4a7e-908f-eb83b9d448b6.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S3_TEXT">Step 3: Copy the Edge Subscription file to a Hub Transport server</text>
                <description _locID="G1_L2_S3_DESCRIPTION">Copy the Edge Subscription file to a directory location on a Hub Transport server in your Exchange organization. Exchange Organization Administrators must have read access to the file.</description>
              </step>
              <step>
                <text _locID="G1_L2_S4_TEXT">Step 4: Import the Edge Subscription file</text>
                <description _locID="G1_L2_S4_DESCRIPTION">On a Hub Transport server, import the Edge Subscription file by using the following procedure in the Exchange Management Console. You must have the Exchange Organization Administrator role to perform this procedure.</description>
                <substeps>
                  <description _locID="G1_L2_S4_SS_DESCRIPTION">On a Hub Transport server:</description>
                  <substep>
                    <text _locID="G1_L2_S4_SS1_TEXT">1. Go to Edge Subscription Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationBridgeheadNode\edgeSubscriptionResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S4_SS2_TEXT">2. In the action pane, click "New Edge Subscription". The New Edge Subscription wizard starts.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S4_SS3_TEXT">3. On the New Edge Subscription page, in the Active Directory Site: drop-down list, select the Active Directory site that contains the Hub Transport servers that you want to replicate to the Edge Transport server.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S4_SS4_TEXT">4. On the New Edge Subscription page, click Browse. Locate the Edge Subscription file to import. Select the file, and then click “Open”.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S4_SS5_TEXT">5. On the New Edge Subscription page, click “New”.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S4_SS6_TEXT">6. On the Completion page, click “Finish”.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S5_TEXT">Step 5: (Optional) Verify the Edge Subscription</text>
                <substeps>
                  <description _locID="G1_L2_S5_SS_DESCRIPTION">On the Hub Transport server:</description>
                  <substep>
                    <text _locID="G1_L2_S5_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S5_SS2_TEXT">2. Run the following command: Test-EdgeSynchronization</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S6_TEXT">Read more about the Microsoft Exchange EdgeSync service.</text>
                <description _locID="G1_L2_S6_DESCRIPTION">For more information about how to use the Microsoft Exchange EdgeSync service:</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L2_S6_SS1_TEXT">- Read more about the Microsoft Exchange EdgeSync service.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/fbf3f7c0-de5d-4a2a-b219-5c412a628c29.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L2_DESCRIPTION">The Microsoft Exchange EdgeSync service establishes one-way replication of recipient and configuration information from the Active Directory directory service to the Edge Transport server. The Microsoft Exchange EdgeSync service lets you quickly and easily configure your Edge Transport server to take advantage of its full feature set.</description>
        </link>
        <!--This Link is Used to Configure Internet Mail Flow (3) -->
        <link>
          <text _locID="G1_L3_TEXT">Configure Internet Mail Flow</text>
          <postIt>
            <description _locID="G1_L3_S_DESCRIPTION">Use one of the following procedures to establish Internet mail flow to and from your Exchange organization:</description>
            <steps>
              <step>
                <text _locID="G1_L3_S1_TEXT">Deploy an Edge Transport server and manually configure the Send connectors and Receive connectors that are required for Internet mail flow</text>
                <substeps>
                  <description _locID="G1_L3_S1_SS_DESCRIPTION">If you are deploying an Edge Transport server but not by using the Microsoft Exchange EdgeSync service, you must manually configure mail flow and accepted domains on the Edge Transport server. This method does not establish any replication of recipient and configuration information from the Active Directory directory service to the Edge Transport server.</description>
                  <substep>
                    <text _locID="G1_L3_S1_SS1_TEXT">The following connectors are required on the Edge Transport server:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS2_TEXT">- A Send connector that is configured to send messages to the Internet.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS3_TEXT">- A Send connector that is configured to send messages to the Hub Transport servers in the Exchange organization.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS4_TEXT">- A Receive connector that is configured to receive messages only from Hub Transport servers in the Exchange organization.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS5_TEXT">- A Receive connector that is configured to accept messages only from the Internet.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS6_TEXT">The following connector is required on the Hub Transport server:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS7_TEXT">- A Send connector that is configured to send messages to the Edge Transport server in the perimeter network for relay to the Internet.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS8_TEXT">For more details about how to configure mail flow between an Edge Transport server and an Exchange organization without using EdgeSync, read the following topics:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS9_TEXT">- Read more about how to configure mail flow between an Edge Transport Server and Hub Transport servers without using EdgeSync.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/6bb98d10-6f12-4b08-a58e-36375f605d65.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS10_TEXT">- Read more about how to manually configure accepted domains on an Edge Transport server.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/2b9e4e3b-109d-45fc-b300-2fe2f073d50c.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS11_TEXT">- Read more about the Microsoft Exchange EdgeSync service.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/fbf3f7c0-de5d-4a2a-b219-5c412a628c29.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L3_S2_TEXT">Manually configure Internet mail flow between your Exchange 2007 organization and Microsoft Exchange Hosted Services or other external SMTP gateway servers</text>
                <substeps>
                  <description _locID="G1_L3_S2_SS_DESCRIPTION">This method requires you to create the Send connectors and Receive connectors on one or more Hub Transport servers in your organization that are assigned to communicate with Exchange Hosted Services or the external SMTP gateway servers.</description>
                  <substep>
                    <text _locID="G1_L3_S2_SS1_TEXT">The following connectors are required on the Hub Transport server:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S2_SS2_TEXT">- A Send connector to send e-mail to Exchange Hosted Services or the external SMTP gateway.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S2_SS3_TEXT">- A Receive connector to receive e-mail from Exchange Hosted Services or the external SMTP gateway. An additional Receive connector is only required if you are using external authentication or anonymous relay. If Basic authentication is used, the default Receive connector will accept e-mail submissions from the authenticated SMTP gateway.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S2_SS4_TEXT">Read more about how to configure Internet mail flow through Exchange Hosted Services or an external SMTP gateway.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/e94e8ff4-4e21-4bec-94e9-4c49446de3d8.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L3_S3_TEXT">Manually configure the Hub Transport server for direct mail flow with the Internet</text>
                <substeps>
                  <description _locID="G1_L3_S3_SS_TEXT">This method requires you to create the Send connectors and Receive connectors on one or more Hub Transport servers in your organization that are assigned to connect to the Internet. To establish mail flow to and from the Internet through a Hub Transport server, follow these steps:</description>
                  <substep>
                    <text _locID="G1_L3_S3_SS1_TEXT">1. Create a Send connector to send e-mail to the Internet.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S3_SS2_TEXT">2. Modify the default Receive connector to allow anonymous connections.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S3_SS3_TEXT">3. Read more about how to manually configure Internet mail flow directly through a Hub Transport server.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/5cf52f4f-e65b-4c56-9ea1-a43a1d3765b7.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L3_DESCRIPTION">By default, a Hub Transport server isn't configured for Internet mail flow. If you do not subscribe an Edge Transport server to your Exchange organization, you must manually configure Internet mail flow.</description>
        </link>
        <!--This Link is Used to Configure a Postmaster Mailbox (4) -->
        <link>
          <text _locID="G1_L4_TEXT">Configure an External Postmaster Recipient to Receive Mail</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G1_L4_S1_TEXT">Step 1: View the current value of the external postmaster address</text>
                <description _locID="G1_L4_S1_DESCRIPTION">Configuration of the external postmaster address is controlled by the ExternalPostmasterAddress parameter in the Set-TransportServer cmdlet. Parameters that are configured by using the Set-TransportServer cmdlet only apply to the Hub Transport server on which the cmdlet is run. By default, the value of the ExternalPostmasterAddress parameter is $null. The value $null causes the default value of the external postmaster address to be “postmaster@&lt;Default accepted domain&gt;” on the Hub Transport server.</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L4_S1_SS1_TEXT">To view the value of the external postmaster address on a specific Hub Transport server:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS2_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS3_TEXT">2. Run the following command: Get-TransportServer [server name]</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS4_TEXT">To view the value of the external postmaster address on all Hub Transport servers in the organization:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS5_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS6_TEXT">2. Run the following command: Get-TransportServer | FormatList Name,ExternalPostmasterAddress</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS7_TEXT">3. Examine the value of the “ExternalPostmasterAddress” field or fields in the command output. The default value is blank.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS8_TEXT">4. If the value is blank, proceed to step 2.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS9_TEXT">5. If a value has been specified for the external postmaster address, use that value in step 2 to add the external postmaster address to an existing mailbox user.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S1_SS10_TEXT">6. If the external postmaster address values are unintentionally inconsistent across different Hub Transport servers, proceed to step 2, but then complete the optional procedure in step 3 to simultaneously standardize the external postmaster address values on all Hub Transport servers.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L4_S2_TEXT">Step 2: Configure an external postmaster mailbox</text>
                <description _locID="G1_L4_S2_DESCRIPTION">To create a recipient for messages that are sent to the postmaster address, perform either of the following actions on a Mailbox server in the Exchange organization:</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L4_S2_SS1_TEXT">- Create a new mailbox that is named "Postmaster". The default e-mail address policy of the Exchange organization should automatically add an SMTP address of postmaster@&lt;Authoritative domain&gt; to the mailbox.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S2_SS2_TEXT">- Add the postmaster address as a secondary e-mail address to an existing mailbox user.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L4_S3_TEXT">Step 3: (Optional) Modify the external postmaster address</text>
                <substeps>
                  <substep>
                    <text _locID="G1_L4_S3_SS1_TEXT">To modify the external postmaster address on a specific Hub Transport server:</text>
                  </substep>          
                  <substep>
                    <text _locID="G1_L4_S3_SS2_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S3_SS3_TEXT">2. Run the following command: Set-TransportServer [servername] -ExternalPostmasterAddress [postmaster e-mail address]</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S3_SS4_TEXT">To modify the external postmaster address on all Hub Transport servers in the organization:</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S3_SS5_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S3_SS6_TEXT">2. Run the following command: Get-TransportServer | Set-TransportServer –ExternalPostmasterAddress [external postmaster e-mail address]</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L4_S3_SS7_TEXT">Note: To return the ExternalPostmasterAddress parameter to the default value, specify the value $null. If you specify any value for the external postmaster address other than $null, you must also configure the external postmaster address on any Edge Transport servers.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L3_S3_SS8_TEXT">Read more about configuring the external postmaster address.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/6b0c8675-3238-462d-8973-b52305fb90d2.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L4_DESCRIPTION">The external postmaster address is used as the sender for system-generated messages and notifications that are sent to message senders that exist outside the Exchange 2007 organization. By default, no mailbox or other recipient object is configured to receive messages that are sent to the postmaster address for any accepted domains that are defined in the Exchange organization. According to RFC 2821, every domain must be able to receive mail that is sent to the postmaster address.</description>
        </link>
      </links>
    </group>
    <group applyOn="UnifiedMessaging">
      <icon>UnifiedMessagingServer</icon>
      <text _locID="G4_TEXT">Unified Messaging</text>
      <links>
        <!--This is the Start Page item for configuring Unified Messaging-->
        <link>
          <text _locID="G4_L1_TEXT">Configure Unified Messaging</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L1_S1_TEXT">Step 1: Create a UM dial plan</text>
                <description _locID="G4_L1_S1_DESCRIPTION">A dial plan establishes a link between an Exchange Server 2007 recipient's telephone extension to a UM-enabled mailbox.</description>
                <substeps>
                  <description _locID="G4_L1_S1_SS_DESCRIPTION">To create a UM dial plan:</description>
                  <substep>
                    <text _locID="G4_L1_S1_SS1_TEXT">1. Go to UM Dial Plan Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\DialPlansResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS2_TEXT">2. In the action pane, click "New UM Dial Plan".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS3_TEXT">3. Complete the New UM Dial Plan Wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L1_S2_TEXT">Step 2: Create a UM IP gateway</text>
                <description _locID="G4_L1_S2_DESCRIPTION">A UM IP gateway establishes a logical link between your IP gateway or IP PBX and the UM dial plan.</description>
                <substeps>
                  <description _locID="G4_L1_S2_SS_DESCRIPTION">To create a UM IP gateway:</description>
                  <substep>
                    <text _locID="G4_L1_S2_SS1_TEXT">1. Read more about what models of IP gateways are supported.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/9ed9dc7a-82e4-47da-b341-a64a1c0da8fd.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS2_TEXT">2. Go to UM IP Gateway Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\umIpGatewaysResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS3_TEXT">3. In the action pane, click "New UM IP Gateway".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS4_TEXT">4. Complete the New UM IP Gateway Wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L1_S3_TEXT">Step 3: Associate the Unified Messaging server with a dial plan</text>
                <description _locID="G4_L1_S3_DESCRIPTION">Although the operational status of the Unified Messaging server is set to enabled after the Unified Messaging server role is installed, the Unified Messaging server will not be able to process incoming calls to UM-enabled users without being associated with at least one UM dial plan.</description>
                <substeps>
                  <description _locID="G4_L1_S3_SS_DESCRIPTION">To associate a Unified Messaging server with a dial plan:</description>
                  <substep>
                    <text _locID="G4_L1_S3_SS1_TEXT">1. Go to Unified Messaging Server Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>UnifiedMessagingNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS2_TEXT">2. Select the Unified Messaging server to associate with a dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS4_TEXT">4. Click the "UM Settings" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS5_TEXT">5. In the "Associated Dial Plans" section, click "Add".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS6_TEXT">6. Select the dial plan to associate with this server.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS7_TEXT">7. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L1_S4_TEXT">Step 4: Enable mailboxes for Unified Messaging</text>
                <description _locID="G4_L1_S4_DESCRIPTION">By default, an Exchange Server 2007 mailbox is not enabled for Unified Messaging when it is created. After the user is enabled for Unified Messaging, you can manage, modify, and configure the UM-related properties for the user.</description>
                <substeps>
                  <description _locID="G4_L1_S4_SS_DESCRIPTION">To enable mailboxes for Unified Messaging:</description>
                  <substep>
                    <text _locID="G4_L1_S4_SS1_TEXT">1. Go to Recipient Configuration.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S4_SS2_TEXT">2. Select the mailbox to enable for Unified Messaging.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S4_SS3_TEXT">3. In the action pane, click "Enable Unified Messaging".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S4_SS4_TEXT">4. Complete the Enable Unified Messaging wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L1_DESCRIPTION">Unified Messaging combines voice, fax, and e-mail messaging into one store, accessible from both a telephone and the desktop. For more information about Unified Messaging components, see Overview of Unified Messaging Components in help.</description>
        </link>
        <link>
          <text _locID="G4_L2_TEXT">Configure Unified Messaging and Office Communications Server 2007 Integration</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G4_L2_S1_TEXT">Step 1: Install Office Communications Server 2007 in your organization</text>
                <description _locID="G4_L2_S1_DESCRIPTION">Follow the setup instructions that are provided in the documentation for Communications Server 2007 to:</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S1_SS1_TEXT">1. Install Communications Server 2007 in the same Active Directory forest as Exchange Unified Messaging.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S1_SS2_TEXT">2. Install a certificate that is valid and signed by a certification authority (CA) on the Communications Server 2007 computers in your organization.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S1_SS3_TEXT">3. Make sure that the certificate is trusted by the Unified Messaging servers in your organization. </text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S1_SS4_TEXT">4. Confirm that at least one Communications Server 2007 pool object is created during installation.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S2_TEXT">Step 2: Install a certificate that is valid and signed by a CA on the Exchange Unified Messaging servers</text>
                <description _locID="G4_L2_S2_DESCRIPTION">Communication between the Unified Messaging servers and Communications Server 2007 servers requires the use of mutual TLS.</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S2_SS1_TEXT">1. Install a certificate that is valid and signed by a CA on the Unified Messaging servers that are used by Communications Server 2007 users.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS2_TEXT">2. Make sure that the certificate is trusted by the Communications Server 2007 servers in your organization.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS3_TEXT">3. Restart the Microsoft Exchange Unified Messaging service on the Unified Messaging servers.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S2_SS4_TEXT">4. Confirm that each Unified Messaging server has loaded the trusted certificate by viewing the System log and searching for event 1112.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S3_TEXT">Step 3: Create a SIP URI Unified Messaging dial plan</text>
                <description _locID="G4_L2_S3_SS_DESCRIPTION">For Communications Server 2007 users to access their voice mail, they must be associated with a SIP URI dial plan. To create a SIP URI Unified Messaging dial plan, follow these steps:</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S3_SS1_TEXT">1. Go to UM Dial Plan Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\DialPlansResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS2_TEXT">2. In the action pane, click the "New UM Dial Plan" link.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationUnifiedMessagingNode\DialPlansResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS3_TEXT">3. Select “SIP URI” as the URI type.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS4_TEXT">4. Select “SIP Secured” or “Secured” as the security setting for the UM dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S3_SS5_TEXT">5. Complete the New UM Dial Plan wizard.</text>
                  </substep>
                </substeps>
              </step>              
              <step>
                <text _locID="G4_L2_S4_TEXT">Step 4: Associate the Unified Messaging server with the SIP URI dial plan that was created</text>
                <description _locID="G4_L2_S4_SS_DESCRIPTION">Although the operational status of the Unified Messaging server is set to enabled after the Unified Messaging server role is installed, the Unified Messaging server will not be able to process incoming calls for UM-enabled users without being associated with at least one UM dial plan. Associate the Unified Messaging server with the SIP URI dial plan by doing the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S4_SS1_TEXT">1. Go to Unified Messaging Server Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>UnifiedMessagingNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS2_TEXT">2. Select the Unified Messaging server to associate with a dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS3_TEXT">3. In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS4_TEXT">4. Click the "UM Settings" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS5_TEXT">5. In the "Associated Dial Plans" section, click "Add".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS6_TEXT">6. Select the dial plan to associate with this server.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S4_SS7_TEXT">7. Click "OK" to save your changes.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S5_TEXT">Step 5: Run the ExchUCUtil.ps1 script</text>
                <description _locID="G4_L2_S5_SS_DESCRIPTION">The ExchUCUtil.ps1 script will grant the Communications Server 2007 administrative groups read permission to the Exchange Unified Messaging Active Directory objects. In addition, it will create a corresponding UM IP gateway for each Communications Server 2007 pool object that is located in the Active Directory forest and will then associate the pool object with the SIP URI dial plan that was created. To run the ExchUCUtil.ps1 script, do the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S5_SS1_TEXT">• In the Exchange Management Shell, run the &lt;%Exchangedir%&gt;\Scripts\ExchUCUtil.ps1 script.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S6_TEXT">Step 6: Enable a user for Unified Messaging</text>
                <description _locID="G4_L2_S6_DESCRIPTION">By default, an Exchange Server 2007 user is not enabled for Unified Messaging when the user’s mailbox is created. To enable the user for Unified Messaging:</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S6_SS1_TEXT">1. Go to Mailbox Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxesNode\MailboxesResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S6_SS2_TEXT">2. Select the mailbox to enable for Unified Messaging.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S6_SS3_TEXT">3. In the action pane, click the "Enable Unified Messaging" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S6_SS4_TEXT">4. Select the UM mailbox policy that is associated with the SIP URI dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S6_SS5_TEXT">5. Specify the SIP address for the user in the SIP resource identifier field.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S6_SS6_TEXT">6. Complete the Enable Unified Messaging wizard.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S7_TEXT">Step 7: Enable the user to use Office Communications Server 2007</text>
                <description _locID="G4_L2_S7_DESCRIPTION">Complete the configuration on the Communications Server 2007 servers by doing the following:</description>
                <substeps>
                  <description _locID="G4_L2_S7_SS_DESCRIPTION">Use the Communication Server 2007 administration tools and follow the instructions that are provided by the Communications Server 2007 documentation  to:</description>
                  <substep>
                    <text _locID="G4_L2_S7_SS1_TEXT">1. Enable the user for Communications Server 2007.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S7_SS2_TEXT">2. Verify that the SIP address that is specified corresponds to the SIP resource identifier property on the user’s UM mailbox that was specified in step 6.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S7_SS3_TEXT">3. Enable voice routing for the user.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S8_TEXT">Step 8: Install Office Communicator 2007</text>
                <description _locID="G4_L2_S8_DESCRIPTION">Install Office Communicator 2007 and then confirm that you can access the user’s mailbox by doing the following:</description>
                <substeps>
                  <substep>
                    <text _locID="G4_L2_S8_SS1_TEXT">1. Install Office Communicator 2007 on the user’s client computer.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S8_SS2_TEXT">2. Log on to Office Communicator 2007 by using the credentials for the user.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L2_S8_SS3_TEXT">3. Confirm that you can directly access the user’s mailbox by selecting the "Call Voice Mail" option in Office Communicator 2007.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G4_L2_S9_TEXT">Note: You may have to repeat steps 6 through 8 for each user who wants to access their voice mail directly from Office Communicator 2007.</text>
              </step>
              <step>
                <text _locID="G4_L2_S10_TEXT">You can use Office Communicator 2007 to directly access Exchange Unified Messaging voice mail. However, to do this, you must perform several installation and configuration steps on both the Unified Messaging and Communications Server 2007 servers in your organization.</text>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L2_DESCRIPTION">Unified Messaging can use the Communications Server 2007 platform to combine voice messaging, Instant Messaging (IM), enhanced presence, audio-video conferencing, and e-mail into a familiar, integrated communications experience.</description>
        </link>
      </links>
    </group>
    <group applyOn="Edge">
      <icon>EdgeServerConfiguration</icon>
      <text _locID="G5_TEXT">Edge Transport</text>
      <links>
        <!--This Link is Used to Configure Edge Transport Subscriptions (1) -->
        <link>
          <text _locID="G5_L1_TEXT">Subscribe the Edge Transport Server</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L1_S1_TEXT">Step 1: Prepare to run the Microsoft Exchange EdgeSync service</text>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S1_SS1_TEXT">1. Verify that the perimeter network firewall that separates the Edge Transport server from the Exchange organization is configured to enable communications through the correct ports. By default, TCP port 50636 is used for directory synchronization from Hub Transport servers to the Edge Transport server. This port must be open for successful EdgeSync synchronization.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S1_SS2_TEXT">2. Read more about how to prepare to run the Microsoft Exchange EdgeSync service.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/edcc6d86-f45b-4449-85fc-7e39e1221d93.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S2_TEXT">Step 2: Export the Edge Subscription file</text>
                <description _locID="G5_L1_S2_DESCRIPTION">A subscribed Edge Transport server receives the following data from the Microsoft Exchange EdgeSync service: Send connector configuration, accepted domain configuration, remote domain configuration, Safe Senders Lists, and Recipients.</description>
                <substeps>
                  <description _locID="G5_L1_S2_SS_DESCRIPTION">On the Edge Transport server to be subscribed:</description>
                  <substep>
                    <text _locID="G5_L1_S2_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S2_SS2_TEXT">2. Run the following command: New-EdgeSubscription -file "C:\EdgeSubscriptionExport.xml"</text>                    
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S3_TEXT">Step 3: Copy the Edge Subscription file to a Hub Transport server</text>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S3_SS1_TEXT">- Copy the Edge Subscription file to a directory location on a Hub Transport server in your Exchange organization. Exchange Organization Administrators must have read access to the file.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S4_TEXT">Step 4: Import the Edge Subscription file</text>
                <description _locID="G5_L1_S4_DESCRIPTION">On a Hub Transport server, import the Edge Subscription file by using the Exchange Management Console. You must have the Exchange Organization Administrator role to perform this procedure.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S4_SS1_TEXT">- Read more about how to import the Edge Subscription file on a Hub Transport server.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/838b9bbc-aff2-4213-a292-a5fdcd8e2202.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S5_TEXT">Step 5: (Optional) Verify the Edge Subscription</text>
                <description _locID="G5_L1_S5_DESCRIPTION">To verify that the Microsoft Exchange EdgeSync service successfully propagated the configuration data, log on to the Hub Transport server and run the Test-EdgeSynchronization cmdlet in the Exchange Management Shell.</description>
              </step>
              <step>
                <text _locID="G5_L1_S6_TEXT">Read more about how to manually configure mail flow</text>
                <description _locID="G5_L1_S6_DESCRIPTION">If you do not create an Edge Subscription, you manually configure mail flow.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S6_SS1_TEXT">- Read about how to configure mail flow between an Edge Transport server and Hub Transport servers without using EdgeSync.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/6bb98d10-6f12-4b08-a58e-36375f605d65.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S6_SS2_Text">- Read about how to manually configure accepted domains on an Edge Transport server.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/2b9e4e3b-109d-45fc-b300-2fe2f073d50c.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S6_SS3_Text">- Read more about the Microsoft Exchange EdgeSync service.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/fbf3f7c0-de5d-4a2a-b219-5c412a628c29.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L1_DESCRIPTION">The Microsoft Exchange EdgeSync service establishes one-way replication of recipient and configuration information from the Active Directory directory service to Active Directory Application Mode (ADAM).  The Microsoft Exchange EdgeSync service lets you quickly and easily configure your Edge Transport server to take advantage of its full feature set.</description>
        </link>
        <!-- This Link is Used to Configure Secure Transport (2)-->
        <link>
          <text _locID="G5_L2_TEXT">Protect the Edge Transport Server by Using the Security Configuration Wizard (SCW)</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L2_S1_TEXT">Step 1: Protect the Edge Transport server by using the SCW</text>
                <description _locID="G5_L2_S1_DESCRIPTION">To install and use the Security Configuration Wizard (SCW), follow these steps:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L2_S1_SS1_TEXT">1. Install the SCW through the Add/Remove Programs control panel.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/4644a2fe-f0a3-4e00-8d1c-cb8a300a1761.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L2_S1_SS2_TEXT">2. Register the SCW extension, using the "scwcmd" command.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/e51d49a0-808b-4731-b7d8-f35536a90853.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L2_S1_SS3_TEXT">3. Run the SCW, create a custom security policy and apply the policy to the local server.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/743a0819-cd87-4b9a-ab33-16424bb1861e.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L2_S2_TEXT">Step 2:  Read more about the Security Configuration Wizard</text>
                <description _locID="G5_L2_S2_DESCRIPTION">For more information about the SCW:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L2_S2_SS1_TEXT">- Using the Security Configuration Wizard to Secure Windows for Exchange Server Roles.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/56211f98-950f-4df3-9db3-1742e065eed9.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L2_S2_SS2_TEXT">- (Optional) How to Apply an Existing SCW Policy to an Exchange Server Role.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/718129f3-786e-4a1b-b15d-fb3e11aa922d.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L2_DESCRIPTION">Use the SCW to minimize security vulnerabilities by disabling functionality on your server that is not required for the Edge Transport server role. The SCW automates security best practices to reduce the attack surface for a server.</description>
        </link>
        <!--This Link is Used to Configure a Postmaster Mailbox (3) -->
        <link>
          <text _locID="G5_L3_TEXT">Configure an External Postmaster Recipient to Receive Mail</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L3_S1_TEXT">Step 1: View the postmaster address on all Hub Transport servers in your Exchange organization</text>
                <substeps>
                  <description _locID="G5_L3_S1_SS_DESCRIPTION">To view the setting for the external postmaster address on all Hub Transport servers in your Exchange organization:</description>
                  <substep>
                    <text _locID="G5_L3_S1_SS1_TEXT">1. On a Hub Transport server, run the following command: Get-TransportServer | FormatList Name,ExternalPostmasterAaddress</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S1_SS2_TEXT">2. Examine the value of the “ExternalPostmasterAddress” field or fields in the command output. The default value is blank.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S1_SS3_TEXT">3. If the value is blank, and you are going to subscribe the Edge Transport server to the Exchange organization, you don’t have to do anything.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S1_SS4_TEXT">4. If the value is blank, and you are not going to subscribe the Edge Transport server to the Exchange organization, proceed to step 2.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S1_SS5_TEXT">5. If a value has been specified for the external postmaster address on the Hub Transport servers, use that value in step 2.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L3_S2_TEXT">Step 2: Configure an external postmaster mailbox</text>
                <description _locID="G5_L3_S2_DESCRIPTION">To create a recipient for messages that are sent to the postmaster address, perform either of the following actions on a Mailbox server in the Exchange organization:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L3_S2_SS1_TEXT">1. Create a new mailbox that is named "Postmaster". The default e-mail address policy of the Exchange organization should automatically add an SMTP address of postmaster@&lt;Authoritative domain&gt; to the mailbox.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S2_SS2_TEXT">2. Add the postmaster address as a secondary e-mail address to an existing mailbox user.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L3_S3_TEXT">Step 3: (Optional) Configure the external postmaster address on the Edge Transport server</text>
                <description _locID="G5_L3_S3_DESCRIPTION">You must configure an external postmaster address on an Edge Transport server if you deploy an Edge Transport server that won’t be subscribed to the Exchange organization, or if you specify a custom value for the external postmaster address on the Hub Transport servers in your Exchange organization.</description>
                <substeps>
                  <description _locID="G5_L3_S3_SS_DESCRIPTION">To configure the external postmaster address on an Edge Transport server:</description>
                  <substep>
                    <text _locID="G5_L3_S3_SS1_TEXT">1. Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S3_SS2_TEXT">2. Run the following command: Set-TransportServer [servername] -ExternalPostmasterAddress [postmaster e-mail address]</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S3_SS3_TEXT">3. Read more about configuring the external postmaster address.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/6b0c8675-3238-462d-8973-b52305fb90d2.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L3_DESCRIPTION">If you have not subscribed this Edge Transport server to your Exchange organization, the value of the external postmaster address is postmaster@[Edge Transport server FQDN]. After you subscribe the Edge Transport server to the Exchange organization, the value of the external postmaster address is postmaster@[default accepted domain]. If you specify a custom value for the external postmaster address on the Hub Transport servers in your Exchange organization, you must manually configure the external postmaster address on the Edge Transport server.</description>
        </link>
        <!-- This Link is Used for Configure DNS (4)-->
        <link>
          <text _locID="G5_L4_TEXT">Configure DNS</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L4_S1_TEXT">Step 1: Configure internal DNS lookup settings and external DNS lookup settings</text>
                <description _locID="G5_L4_S1_DESCRIPTION">Internal DNS lookups are used to locate servers inside the Exchange organization. External DNS lookups are used to locate servers outside the Exchange organization.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S1_SS1_TEXT">- Read about internal address resolution and external address resolution.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/31398fb0-9b71-4ed9-9f69-00e647cdc5a7.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L4_S2_TEXT">Step 2: Configure Public DNS Records</text>
                <description _locID="G5_L4_S2_DESCRIPTION">For this Edge Transport server to successfully send and receive messages from the Internet, the following DNS records are required in a public DNS server:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S2_SS1_TEXT">1. At least one MX record for each domain for which you accept e-mail. The MX records contain the FQDN of a publicly available SMTP messaging sever, such as this Edge Transport server, and a preference value. A lower preference value indicates a more preferred messaging server. Multiple MX records pointing to different SMTP messaging servers that have different preference values are common for fault tolerance.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS2_TEXT">2. The FQDN of an SMTP messaging server that is listed in an MX record must resolve to an Address (A) record that contains the public IP address of the SMTP messaging server.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS3_TEXT">3. The A records of any SMTP messaging servers that are responsible for sending mail to Internet recipients, such as this Edge Transport server, should have a pointer (PTR) record that is used for reverse lookup. This reverse lookup functionality is used by many organizations to test the validity of a message source.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L4_S2_SS4_TEXT">4. Read more about configuring DNS settings for Exchange 2007 servers.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/de468880-4a6b-42dd-837c-64b974d7da59.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L4_S3_TEXT">Additionally, if you are using the Sender ID anti-spam feature, you must also configure your DNS records to include your Sender ID information.</text>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S3_SS1_TEXT">- Learn more about Sender ID.</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/0f628f83-df8c-43fb-bf49-7aaa9ec69ab1.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L4_DESCRIPTION">The Edge Transport server must be configured for internal DNS lookups within the Exchange organization and external DNS lookups for external recipients. Public DNS records must also be configured for this server to send mail or receive mail from the Internet.</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>4ASw82gTBbRIn9/fcrzjaumxMV4=</DigestValue></Reference></SignedInfo><SignatureValue>
    T9scN5peFD/L8LQ911xWtFqgSwqEbfmXzfsO1QiQJR1jEn2TfPrWzATZemaPTjtVRc0W4XbD
    DtKr35PcQVwoC82QZrVOSxuE0KF1hhBYkQuTq6T2Rd30JHkS12OvENaCau/AAGozISvct/02
    Iv6AXkwCWeTtkr9PbC0nup6D48OyxBUyDU3HZGkDv6PdNDx8rzGW9WYpiJ4AfPhBVI/+PFug
    uKcRq9eaHiyA4Hrlupn0nO7qc44iHVsrxMicnyQfQTTBaBQzijjigXuIfXpazNIbN8mFueTh
    Qq0vAwuVI58LB7yNA7oVE/dTg7IXIr9hQvU/f/EXel2Zml/zetUdsg==
  </SignatureValue><KeyInfo>
      <KeyValue>
        <RSAKeyValue>
          <Modulus>
            vTCJ+0VyqFNrnolPACPAvtQdPbFZQDjzc5GCJuaWEgBT2RyCDjzOHbu990KNl9T8OBrkufnj
            7NNhA7+g09Z1TVxGqe1e8NLiaVsac+qzHI0EzSlEoGRZLx6YXW7Hqxg5gmXEp7yrdYgZ6oeX
            FCazfyZ2pNQ4OYTjsybVGPkr6dLJFlpUIfKXjYeGKf70SSzmi/gEP33NzZaShg1xA+LQ/gxC
            Nf/XuD/djkUKffbXS61b8HZyHXcjfYk1xBxdslADS0dtB6dViJgGgKaBrVRO2IHW+r9CwDG+
            VQ2Z1VNJEjDr5aWIfF7EeloUhwi0N2mg6zIkjAjr+dQUuuD8zeqkFQ==
          </Modulus>
          <Exponent>AQAB</Exponent>
        </RSAKeyValue>
      </KeyValue>
      <X509Data>
        <X509Certificate>
          MIIEejCCA2KgAwIBAgIKYQHPPgAAAAAADzANBgkqhkiG9w0BAQUFADB5MQswCQYDVQQGEwJV
          UzETMBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWlj
          cm9zb2Z0IENvcnBvcmF0aW9uMSMwIQYDVQQDExpNaWNyb3NvZnQgQ29kZSBTaWduaW5nIFBD
          QTAeFw0wOTEyMDcyMjQwMjlaFw0xMTAzMDcyMjQwMjlaMIGDMQswCQYDVQQGEwJVUzETMBEG
          A1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0
          IENvcnBvcmF0aW9uMQ0wCwYDVQQLEwRNT1BSMR4wHAYDVQQDExVNaWNyb3NvZnQgQ29ycG9y
          YXRpb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC9MIn7RXKoU2ueiU8AI8C+
          1B09sVlAOPNzkYIm5pYSAFPZHIIOPM4du733Qo2X1Pw4GuS5+ePs02EDv6DT1nVNXEap7V7w
          0uJpWxpz6rMcjQTNKUSgZFkvHphdbserGDmCZcSnvKt1iBnqh5cUJrN/Jnak1Dg5hOOzJtUY
          +Svp0skWWlQh8peNh4Yp/vRJLOaL+AQ/fc3NlpKGDXED4tD+DEI1/9e4P92ORQp99tdLrVvw
          dnIddyN9iTXEHF2yUANLR20Hp1WImAaApoGtVE7Ygdb6v0LAMb5VDZnVU0kSMOvlpYh8XsR6
          WhSHCLQ3aaDrMiSMCOv51BS64PzN6qQVAgMBAAGjgfgwgfUwEwYDVR0lBAwwCgYIKwYBBQUH
          AwMwHQYDVR0OBBYEFDh4BXPIGzKbX5KGVa+JusaZsXSOMA4GA1UdDwEB/wQEAwIHgDAfBgNV
          HSMEGDAWgBTMHc52AHBbr/HaxE6aUUQuo0Rj8DBEBgNVHR8EPTA7MDmgN6A1hjNodHRwOi8v
          Y3JsLm1pY3Jvc29mdC5jb20vcGtpL2NybC9wcm9kdWN0cy9DU1BDQS5jcmwwSAYIKwYBBQUH
          AQEEPDA6MDgGCCsGAQUFBzAChixodHRwOi8vd3d3Lm1pY3Jvc29mdC5jb20vcGtpL2NlcnRz
          L0NTUENBLmNydDANBgkqhkiG9w0BAQUFAAOCAQEAKAODqxMN8f4Rb0J22EOruMZC+iRlNK51
          sHEwjpa2g/py5P7NN+c6cJhRIA66cbTJ9NXkiugocHPV7eHCe+7xVjRagILrENdyA+oSTuzd
          DYx7RE8MYXX9bpwH3c4rWhgNObBg/dr/BKoCo9j6jqO7vcFqVDsxX+QsbsvxTSoc8h52e4av
          xofWsSrtrMwOwOSff+jP6IRyVIIYbirInpW0Gh7Bb5PbYqbBS2utye09kuOyL6t6dzlnagB7
          gp0DEN5jlUkmQt6VIsGHC9AUo1/cczJyNh7/yCnFJFJPZkjJHR2pxSY5aVBOp+zCBmwuchvx
          IdptJEiAgRVAfJ/MdDhKTw==
        </X509Certificate>
      </X509Data>
      <X509Data>
        <X509Certificate>
          MIIEEjCCAvqgAwIBAgIPAMEAizw8iBHRPvZj7N9AMA0GCSqGSIb3DQEBBAUAMHAxKzApBgNV
          BAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jv
          c29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4X
          DTk3MDExMDA3MDAwMFoXDTIwMTIzMTA3MDAwMFowcDErMCkGA1UECxMiQ29weXJpZ2h0IChj
          KSAxOTk3IE1pY3Jvc29mdCBDb3JwLjEeMBwGA1UECxMVTWljcm9zb2Z0IENvcnBvcmF0aW9u
          MSEwHwYDVQQDExhNaWNyb3NvZnQgUm9vdCBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQCpAr3BcOY78k4bKJ+XeF4w6qKpjSVf+P6VTKO3/p2iID58UaKboo9g
          MmvRQmR57qx2yVTa8uuchhyPn4Rms8VremIj1h083g8BkuiWxL8tZpqaaCaZ0Dosvwy1WCbB
          RucKPjiWLKkoOajsSYNC44QPu5psVWGsgnyhYC13TOmZtGQ7mlAcMQgkFJ+p55ErGOY9mGMU
          YFgFZZ8dN1KH96fvlALGG9O/VUWziYC/OuxUlE6u/ad6bXROrxjMlgkoIQBXkGBpN7tLEgc8
          Vv9b+6RmCgim0oFWV++2O14WgXcE2va+roCV/rDNf9anGnJcPMq88AijIjCzBoXJsyB3E4Xf
          AgMBAAGjgagwgaUwgaIGA1UdAQSBmjCBl4AQW9Bw72lyniNRfhSyTY7/y6FyMHAxKzApBgNV
          BAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jv
          c29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5gg8A
          wQCLPDyIEdE+9mPs30AwDQYJKoZIhvcNAQEEBQADggEBAJXoC8CN85cYNe24ASTYdxHzXGAy
          n54Lyz4FkYiPyTrmIfLwV5MstaBHyGLv/NfMOztaqTZUaf4kbT/JzKreBXzdMY09nxBwarv+
          Ek8YacD80EPjEVogT+pie6+qGcgrNyUtvmWhEoolD2Oj91Qc+SHJ1hXzUqxuQzIH/YIX+OVn
          bA1R9r3xUse958Qw/CAxCYgdlSkaTdUdAqXxgOADtFv0sd3IV+5lScdSVLa0AygS/5DW8AiP
          friXxas3LOR65Kh343agANBqP8HSNorgQRKoNWobats14dQcBOSoRQTIWjM4bk0cDWK3CqKM
          09VUP0bNHFWmcNsSOoeTdZ+n0qA=
        </X509Certificate>
      </X509Data>
      <X509Data>
        <X509Certificate>
          MIIEYDCCA0ygAwIBAgIKLqsR3FD/XJ3LwDAJBgUrDgMCHQUAMHAxKzApBgNVBAsTIkNvcHly
          aWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jvc29mdCBDb3Jw
          b3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4XDTA3MDgyMjIy
          MzEwMloXDTEyMDgyNTA3MDAwMFoweTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0
          b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEj
          MCEGA1UEAxMaTWljcm9zb2Z0IENvZGUgU2lnbmluZyBQQ0EwggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQC3eX3WXbNFOag0rDHa+SU1SXfA+x+ex0Vx79FG6NSMw2tMUmL0mQLD
          TdhJbC8kPmW/ziO3C0i3f3XdRb2qjw5QxSUr8qDnDSMf0UEk+mKZzxlFpZNKH5nNsy8iw0ot
          fG/ZFR47jDkQOd29KfRmOy0BMv/+J0imtWwBh5z7urJjf4L5XKCBhIWOsPK4lKPPOKZQhRcn
          h07dMPYAPfTG+T2BvobtbDmnLjT2tC6vCn1ikXhmnJhzDYav8sTzILlPEo1jyyzZMkUZ7rtK
          ljtQUxjOZlF5qq2HyFY+n4JQiG4FsTXBeyS9UmY9mU7MK34zboRHBtGe0EqGAm6GAKTAh99T
          AgMBAAGjgfowgfcwEwYDVR0lBAwwCgYIKwYBBQUHAwMwgaIGA1UdAQSBmjCBl4AQW9Bw72ly
          niNRfhSyTY7/y6FyMHAxKzApBgNVBAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQg
          Q29ycC4xHjAcBgNVBAsTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9z
          b2Z0IFJvb3QgQXV0aG9yaXR5gg8AwQCLPDyIEdE+9mPs30AwDwYDVR0TAQH/BAUwAwEB/zAd
          BgNVHQ4EFgQUzB3OdgBwW6/x2sROmlFELqNEY/AwCwYDVR0PBAQDAgGGMAkGBSsOAwIdBQAD
          ggEBAHurrn5KJvLOvE50olgndCp1s4b9q0yUeABN6crrGNxpxQ6ifPMCQ8bKh8z4U8zCn71W
          b/BjRKlEAO6WyJrVHLgLnxkNlNfaHq0pfe/tpnOsj945jj2Yarw4bdKIryP93+nWaQmRiL3+
          4QC7NPP3fPkQEi4F6ymWk0JrKHG3OI/gBw3JXWjNvYBBa2aou7e7jjTK8gMQfHr10uBC33v+
          4eGs/vbf1Q2zcNaS40+2OKJ8LdQ92zQLYjcCn4FqI4n2XGOPsFq7OddgjFWEGjP1O5igggyi
          X4uzLLehpcur2iC2vzAZhSAUDSq8UvRB4F4w45IoaYfBcOLzp6vOgEJydg4=
        </X509Certificate>
      </X509Data>
    </KeyInfo><Object id="ts-countersig"><X509Data><X509Certificate>MIIEqjCCA5KgAwIBAgIKYQWiMAAAAAAACDANBgkqhkiG9w0BAQUFADB5MQswCQYDVQQGEwJVUzET
MBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0
IENvcnBvcmF0aW9uMSMwIQYDVQQDExpNaWNyb3NvZnQgVGltZXN0YW1waW5nIFBDQTAeFw0wODA3
MjUxOTAxMTVaFw0xMzA3MjUxOTExMTVaMIGzMQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGlu
Z3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0aW9uMQ0w
CwYDVQQLEwRNT1BSMScwJQYDVQQLEx5uQ2lwaGVyIERTRSBFU046ODVEMy0zMDVDLTVCQ0YxJTAj
BgNVBAMTHE1pY3Jvc29mdCBUaW1lLVN0YW1wIFNlcnZpY2UwggEiMA0GCSqGSIb3DQEBAQUAA4IB
DwAwggEKAoIBAQDwBC2ylsAagWclsSZisxNLzjC6wBI4/IFlNAfENrIkaPYHBMAHl/S38XseYixG
2UukUTS302ztWju0g6FHPREILjVrRebCPIwCZgKpGGnrSu0nLO48d1uk1HCZS1eEENCvLfiJHebq
KbTnz54GYqdyVMI7xs8/uOGwWBBs5aXXw8J1N730heGB6CjYG/HyrvGCo9bXA6KfFYT7Pfqr4bYy
yKACZPPm/xomcQhTihUC8oMndkmCcafvrTJ4xtdsFk8iZZdiTUYv/yOvheymcL0Dy9rYMgXFK5BA
tp7VLIZst8sTMn2Nxn6uFy8y/Ga7HbBFVfit+i1ng2cpk4TSWqEjAgMBAAGjgfgwgfUwHQYDVR0O
BBYEFOiX9vfvjPHmaeNZaE73mIp63ZsuMB8GA1UdIwQYMBaAFG/oTj+XuTSrS4aPvJzqrDtBQ8bQ
MEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6Ly9jcmwubWljcm9zb2Z0LmNvbS9wa2kvY3JsL3Byb2R1
Y3RzL3RzcGNhLmNybDBIBggrBgEFBQcBAQQ8MDowOAYIKwYBBQUHMAKGLGh0dHA6Ly93d3cubWlj
cm9zb2Z0LmNvbS9wa2kvY2VydHMvdHNwY2EuY3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMIMA4GA1Ud
DwEB/wQEAwIGwDANBgkqhkiG9w0BAQUFAAOCAQEADT93X5E8vqU1pNsFBYQfVvLvmabHCI0vs80/
cdWGfHcf3esXsr184/mZ8gpFSK0Uu2ks8j5nYlTy7n8nEZI57M7Zh06I92BHI3snFUAIn78NMQSC
2DW2DJwA04uqeGHFtYhBnT423FikJ5s62r0GXRSmsg9MwY48i/Jimfhm7dXzHCiwMtvKMQm8+yJo
Rkz603Mi5ymOIgD7Vr8GroGgFbo0+SiOH0piBaGJ9YFH6Q2RCNdYO48eawlpqcBIfFWCP18AOEOc
Bsw/2C+/T3MJPf26XvTH7DfCZGGgTdQ9cMxbsBOBwdSjMRq9ZNaW0no/KltGUwk8zQP5P1kAzIlT
YQ==</X509Certificate></X509Data><X509Data><X509Certificate>MIIEnTCCA4WgAwIBAgIQaguZT8AAJasR20UfWHpnojANBgkqhkiG9w0BAQUFADBwMSswKQYDVQQL
EyJDb3B5cmlnaHQgKGMpIDE5OTcgTWljcm9zb2Z0IENvcnAuMR4wHAYDVQQLExVNaWNyb3NvZnQg
Q29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jvc29mdCBSb290IEF1dGhvcml0eTAeFw0wNjA5MTYw
MTA0NDdaFw0xOTA5MTUwNzAwMDBaMHkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpXYXNoaW5ndG9u
MRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xIzAhBgNV
BAMTGk1pY3Jvc29mdCBUaW1lc3RhbXBpbmcgUENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA3Ddu+6/IQkpxGMjOSD5TwPqrFLosMrsST1LIg+0+M9lJMZIotpFk4B9QhLrCS9F/Bfjv
db6Lx6jVrmlwZngnZui2t++Fuc3uqv0SpAtZIikvz0DZVgQbdrVtZG1KVNvd8d6/n4PHgN9/TAI3
lPXAnghWHmhHzdnAdlwvfbYlBLRWW2ocY/+AfDzu1QQlTTl3dAddwlzYhjcsdckO6h45CXx2/p1s
bnrg7D6Pl55xDl8qTxhiYDKe0oNOKyJcaEWL3i+EEFCy+bUajWzuJZsT+MsQ14UO9IJ2czbGlXqi
zGAG7AWwhjO3+JRbhEGEWIWUbrAfLEjMb5xD4GrofyaOawIDAQABo4IBKDCCASQwEwYDVR0lBAww
CgYIKwYBBQUHAwgwgaIGA1UdAQSBmjCBl4AQW9Bw72lyniNRfhSyTY7/y6FyMHAxKzApBgNVBAsT
IkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jvc29mdCBD
b3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5gg8AwQCLPDyIEdE+
9mPs30AwEAYJKwYBBAGCNxUBBAMCAQAwHQYDVR0OBBYEFG/oTj+XuTSrS4aPvJzqrDtBQ8bQMBkG
CSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MA0G
CSqGSIb3DQEBBQUAA4IBAQCUTRExwnxQuxGOoWEHAQ6McEWN73NUvT8JBS3/uFFThRztOZG3o1YL
3oy2OxvR+6ynybexUSEbbwhpfmsDoiJG7Wy0bXwiuEbThPOND74HijbB637pcF1Fn5LSzM7djsDh
vyrNfOzJrjLVh7nLY8Q20Rghv3beO5qzG3OeIYjYtLQSVIz0nMJlSpooJpxgig87xxNleEi7z62D
Ok+wYljeMOnpOR3jifLaOYH5EyGMZIBjBgSW8poCQy97Roi6/wLZZflK3toDdJOzBW4MzJ3cKGF8
SPEXnBEhOAIch6wGxZYyuOVAxlM9vamJ3uhmN430IpaczLB3VFE61nJEsiP2</X509Certificate></X509Data><CounterSignature xmlns="http://schemas.microsoft.com/xmldsig/timestamp/2003" ts-format="cms-timestamp-message">MIIGyQYJKoZIhvcNAQcCoIIGujCCBrYCAQMxCTAHBgUrDgMCGjCCARMGCSqGSIb3DQEHAaCCAQQE
ggEAT9scN5peFD/L8LQ911xWtFqgSwqEbfmXzfsO1QiQJR1jEn2TfPrWzATZemaPTjtVRc0W4XbD
DtKr35PcQVwoC82QZrVOSxuE0KF1hhBYkQuTq6T2Rd30JHkS12OvENaCau/AAGozISvct/02Iv6A
XkwCWeTtkr9PbC0nup6D48OyxBUyDU3HZGkDv6PdNDx8rzGW9WYpiJ4AfPhBVI/+PFuguKcRq9ea
HiyA4Hrlupn0nO7qc44iHVsrxMicnyQfQTTBaBQzijjigXuIfXpazNIbN8mFueThQq0vAwuVI58L
B7yNA7oVE/dTg7IXIr9hQvU/f/EXel2Zml/zetUdsqCCA32hggN5MIICYQIBATCB46GBuaSBtjCB
szELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAc
BgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjENMAsGA1UECxMETU9QUjEnMCUGA1UECxMebkNp
cGhlciBEU0UgRVNOOjg1RDMtMzA1Qy01QkNGMSUwIwYDVQQDExxNaWNyb3NvZnQgVGltZS1TdGFt
cCBTZXJ2aWNloiUKAQEwCQYFKw4DAhoFAAMVAE1vNX8OZDTal7GvxUD7b90OhaifoIHBMIG+pIG7
MIG4MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEe
MBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0aW9uMQwwCgYDVQQLEwNBT0MxJzAlBgNVBAsTHm5D
aXBoZXIgTlRTIEVTTjoyMkExLTIwOEUtODdCMDErMCkGA1UEAxMiTWljcm9zb2Z0IFRpbWUgU291
cmNlIE1hc3RlciBDbG9jazANBgkqhkiG9w0BAQUFAAIFAM+MSogwIhgPMjAxMDA1MDUxOTUwMzJa
GA8yMDEwMDUwNjE5NTAzMloweDA+BgorBgEEAYRZCgQBMTAwLjAKAgUAz4xKiAIBADAKAgEAAgIA
jQIB/zAIAgEAAgMDHMkwCgIFAM+NnAgCAQAwNgYKKwYBBAGEWQoEAjEoMCYwDAYKKwYBBAGEWQoD
AaAKMAgCAQACAw9CQKEKMAgCAQACAwehIDANBgkqhkiG9w0BAQUFAAOCAQEAGknjsWMLm7VOVfLX
6WvrEFmxcWTdJKSDe+/Td4EPf9DuJAO5R+MhYS1ABKQahTnqFW4pQgxc6b64OCGaYbJem1qxGavu
1dzrgaJrgXUkThNWUf201K+UIp5SB/VjahhgoI+aAMZt1yV7G91fkDZ+oN/AnD1v2ucPPd7f3e7j
yFcIBeRPgVtG3xkygpZzCNQZyvmM/Y8JomHawfjnKd5KshSrZgZgnGk8a2F+ZjUtd/3wzWNnZ42t
1njsfbu5FyKqWIRJmeZ2COcLOt935DoF4tmJMinN16ddLWzfqBEBOHarobtLGpW33wep8hJW5Ux+
6lrS9rGHkLE7J3W6Q6BazTGCAgwwggIIAgEBMIGHMHkxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpX
YXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRp
b24xIzAhBgNVBAMTGk1pY3Jvc29mdCBUaW1lc3RhbXBpbmcgUENBAgphBaIwAAAAAAAIMAcGBSsO
AwIaoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTAwNTA1MjM1
ODMxWjAjBgkqhkiG9w0BCQQxFgQUcCCsr+/1lc3sGaMkDWO+bRyEGoEwDQYJKoZIhvcNAQEFBQAE
ggEAxl+9CQrZvPcMMeWBK6ZiNpqSpbXZ9xs4RISIQHMcR+ja+NjYGhj5W3uZVPB9ce54nt0LbRlE
6uVKJT9nYaRVpeSLdtrSQx0v4AXeVG9ImBEHUznzOQY37uyTKD+3eo2lKzV0CH8RNAc8p82rvklp
GwppTtXAFZACsVANZ/TMvhcZYg50VoFNnalmJw6c2pEzYWP16Xnk6lxhDbI7zLMlWDt5fNixJyJs
uQgCtLfhdIu+y7uA2EASamjA0bGj8KgbrVbeedBu/H3vcoq4bN0ynN+OKG3ManyvJFQR5HIer1fS
FfAAbA4wbwHvyc8rH6JXlO2DAF2SQttlhTrbb+LA5A==</CounterSignature></Object></Signature></startpage>