<?xml version="1.0"?><?xml-stylesheet type='text/xsl' href='StartPage.xsl'?><!--
//  Copyright (C) 2006 Microsoft Corporation.  All rights reserved.
//  The xml file that describes the content of 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 Sever 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</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 Product Key for 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">Go to Server Configuration</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ServersNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G6_L1_S2_SS2_TEXT">Select the sever that requires the product key.</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L1_S2_SS3_TEXT">In the action pane, click the "Enter Product Key" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L1_S2_SS4_TEXT">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 install.  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 Exchange Best Practices Analyzer</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G6_L2_S1_TEXT">Step 1: Run the Exchange Best Practices Analyzer tool</text>
                <description _locID="G6_L2_S1_DESCRIPTION">The Exchange Best Practices Analyzer programmatically collects settings and values from data repositories such as Active Directory, registry, metabase and performance monitor. Once collected, a set of comprehensive ‘best practice’ rules are applied to the topology.  Administrators running this tool will get a detailed report listing the recommendations that can be made to the environment to achieve greater performance, scalability and uptime.</description>
                <substeps>
                  <substep>
                    <text _locID="G6_L2_S1_SS1_TEXT">Go to the Toolbox</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ToolboxNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G6_L2_S1_SS2_TEXT">Click on the Best Practices Analyzer tool.</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L2_S1_SS3_TEXT">In the action pane, click the "Open Tool" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G6_L2_S1_SS4_TEXT">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 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>
      </links>
    </group>
    <group applyOn="Edge">
      <icon>ServerConfiguration</icon>
      <text _locID="G7_TEXT">All Exchange Servers</text>
      <links>
        <!--This link is for the Sever 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 information on how to purchase Exchange Server:</description>
                <substeps>
                  <substep>
                    <text _locID="G7_L1_S1_SS1_TEXT">How to buy Exchange</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 Product Key for 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">Go to Edge Transport</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>EdgeServerConfigurationNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G7_L1_S2_SS2_TEXT">Select the sever that requires the product key.</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L1_S2_SS3_TEXT">In the action pane, click the "Enter Product Key" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L1_S2_SS4_TEXT">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 install.  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 Active Directory, registry, metabase and performance monitor. Once collected, a set of comprehensive ‘best practice’ rules are applied to the topology.  Administrators running this tool will get a detailed report listing the recommendations that can be made to the environment to achieve greater performance, scalability and uptime.</description>
                <substeps>
                  <substep>
                    <text _locID="G7_L2_S1_SS1_TEXT">Go to the Toolbox</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ToolboxNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G7_L2_S1_SS2_TEXT">Click on the Best Practices Analyzer tool.</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L2_S1_SS3_TEXT">In the action pane, click the "Open Tool" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G7_L2_S1_SS4_TEXT">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>
      </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 setting 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:  Enable Web Distribution on the Default Address Book</text>
                <description _locID="G3_L1_S2_DESCRIPTION">After you install a Client Access server, you should add an OAB virtual directory for the default OAB</description>
                <substeps>
                  <description _locID="G3_L1_S2_SS_DESCRIPTION">To associate an OAB virtual directory with an OAB:</description>
                  <substep>
                    <text _locID="G3_L1_S2_SS1_TEXT">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">Select "Default Offline Address Book" </text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS3_TEXT">Select the "Properties" link in the Action Pane</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS4_TEXT">Select the "Distribution" tab</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS5_TEXT">Select the "Enable Web-based Distribution" checkbox</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS6_TEXT">Click the "Add" button and then select an OAB virtual directory</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S2_SS_TEXT">Click "OK" to add the OAB virtual directory as a web distribution point.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G3_L1_S3_TEXT">Step 3: Set the External URL for the Offline Address Book Virtual Directory (Optional)</text>
                <description _locID="G3_L1_S3_DESCRIPTION">You must configure an external URL to allow Outlook 2007 to download an OAB from a remote network.</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">Go to OAB Virtual Directory Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>ClientAccessNode\OabDistributionResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS2_TEXT">Select the server that hosts the OAB virtual directory that you want to configure.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS3_TEXT">Select the OAB virtual directory to configure.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS4_TEXT">In the Action Pane, click the "Properties" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS5_TEXT">Click the "URLs" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L1_S3_SS6_TEXT">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">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.  Offline Address Books must be configured to take advantage of the new distribution mechanism.</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) 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 Offline Address Book (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">Go to Database Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>MailboxNode\StorageGroupsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S1_SS2_TEXT">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">In the Action Pane, select the "New Public Folder Database" link</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S1_SS4_TEXT">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">The default offline address book (OAB) must be configured for public folder distribution and for version 3 and version 4 of OAB generation (you can choose only version 4 if all of your client computers are running Outlook 2003 SP2 or later).</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">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">Select "Default Offline Address Book".</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS3_TEXT">In the Action Pane, click the "Properties" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS4_TEXT">Click the "Distribution" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS5_TEXT">Select the "Enable Public Folder Distribution" check box.</text>
                  </substep>
                  <substep>
                    <text _locID="G3_L2_S2_SS6_TEXT">Select the boxes under "Client Support" that correspond to the Outlook versions in your organization.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G3_L2_DESCRIPTION">Offline Address Books may need to be configured for coexistence with Outlook 2003 and earlier.</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 options for obtaining an 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.  This is not supported by Outlook Anywhere or the Offline Address Book.  Exchange ActiveSync will require the device to have the corresponding Trusted Root Certificate installed.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS2_TEXT">Option 2:  Purchase an SSL Certificate from a well known Certificate Authority</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS3_TEXT">Option 3:  Obtain an SSL Certificate from a Windows PKI Certificate Authority</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS4_TEXT">If you choose Option 1 please skip Steps 2 and 3 go straight to Step 4.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S1_SS5_TEXT">If you choose Option 2 or Option 3 please proceed 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 the corresponding Trusted Root Certificate installed.</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">Open the Exchange Management Shell.</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS2_TEXT">Run the following command replacing domainname and friendlyname with the appropriate values:  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 (FQDN) 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 friendly name for the resulting certificate. The friendly name must be less than 64 characters.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S2_SS5_TEXT">Submit the request to the Certificate 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 Website</text>
                  <description _locID="G2_L2_S3_DESCRIPTION">Once you have the newly generated certificate you must import it and then enable that certificate on the Default Web Site.</description>
                  <substeps>
                    <substep>
                      <text _locID="G2_L2_S3_SS1_TEXT">From the machine 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">Open the Exchange Management Shell.</text>
                      <action>
                        <name>LaunchMsh</name>
                        <argument></argument>
                      </action>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS3_TEXT">Run the following command where "c:\newcert.cer" is the location and name of your certificate:  Import-ExchangeCertificate -path c:\newcert.cer</text>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS4_TEXT">Copy the thumbprint, which is the digest of the certificate data, of the certificate to the clipboard by doing the following:</text>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS5_TEXT">Open the Exchange Management Shell.</text>
                      <action>
                        <name>LaunchMsh</name>
                        <argument></argument>
                      </action>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS6_TEXT">Run the following command:  dir cert:\LocalMachine\My | fl</text>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS7_TEXT">Locate the certificate you just imported by finding the one that matches the FriendlyName from Step 2 and copy the Thumbprint property to the Windows Clipboard.</text>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS8_TEXT">Enable the certificate on the Default Web Site by doing the following:</text>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS9_TEXT">Open the Exchange Management Shell.</text>
                      <action>
                        <name>LaunchMsh</name>
                        <argument></argument>
                      </action>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS10_TEXT">Run the following command:  enable-ExchangeCertificate -thumbprint [value you got from above] -services "IIS,IMAP,POP"</text>
                    </substep>
                    <substep>
                      <text _locID="G2_L2_S3_SS11_TEXT">Using the "enable-ExchangeCertificate" cmdlet will update the certificate mapping thus replacing the self-signed certificate installed by default with Exchange 2007 and configured in IIS, IMAP4 and POP3 configuration.</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">The IIS Default Web Site is, by default, configured to require SSL for all virtual directories except for Offline Address Book.  Since it is possible to configure additional virtual directories, for each client access feature that you plan to use you must ensure that the virtual directory uses SSL.  For each of the virtual directories listed below repeat the steps described also below in the Internet Information Services Manager to require SSL</description>
                <substeps>
                  <description _locID="G2_L2_S4_SS_DESCRIPTION">For each of the virtual directories listed below repeat the steps described also below in the Internet Information Services Manager to require SSL.</description>
                  <substep>
                    <text _locID="G2_L2_S4_SS1_TEXT">Outlook Web Access 2007 virtual directory is “owa”</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS2_TEXT">Outlook Web Access 2003 and WebDAV the virtual directories are “exchange” and “public”</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS3_TEXT">Exchange ActiveSync virtual directory is “Microsoft-Server-ActiveSync"</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS4_TEXT">Outlook Anywhere virtual directory is “Rpc”</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS5_TEXT">Autodiscover virtual directory is "Autodiscover"</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS6_TEXT">Exchange Web Services virtual directory is “EWS”</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS7_TEXT">Unified Messaging virtual directory is “Unified Messaging”</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS8_TEXT">Offline Address Book virtual directory is “OAB”</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS9_TEXT">For each of the virtual directories above that you are going to use, open up the Internet Information Services (IIS) Manager and perform the steps below.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS10_TEXT">Select the desired virtual directory under Default Web Site, "owa" for example.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS11_TEXT">Right-click and choose “Properties”.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS12_TEXT">Select the “Directory Security” tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS13_TEXT">Under the “Secure Communications” section choose the “Edit…” button.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS14_TEXT">In the “Secure Communications” dialog ensure that the “Require secure channel (SSL)” checkbox is checked, and the “Require 128-bit encryption” checkbox.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS15_TEXT">Click the “OK” button to save changes.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L2_S4_SS16_TEXT">Restart POP3 and IMAP4 services by opening the Component Services Windows administrative tool, selecting "Microsoft Exchange POP3" or "Microsoft Exchange IMAP4", right-clicking, and choosing "Restart".  IIS does not need to be restarted.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G2_L2_S5_TEXT">Additional information on configuring SSL on the Client Access Server</text>
                <description _locID="G2_L2_S5_DESCRIPTION">Read the following topic to find out more about SSL on the Client Access Server.</description>
                <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 in order to secure the channel between your clients and your Exchange Server.  If your network offloads SSL with an SSL accelerator or 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 firewall settings for Direct Push Mobile Devices running Windows Mobile 5.0 and the Messaging Security and Feature Pack and later can utilize Exchange ActiveSync’s Direct Push technology to remain always up to date.  Direct Push performance and device battery life can be enhanced by modifying your firewall settings to ensure the timeout value is between 15 and 30 minutes. </description>
                <substeps>
                  <substep>
                    <text _locID="G2_L1_S1_SS1_TEXT">Read more about adjusting 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.  For Windows Mobile 5.0 with the Messaging and Security Feature Pack or later, the remote wipe functionality requires that a policy is applied to that 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">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">In the action pane, click New Exchange ActiveSync Mailbox Policy.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S2_SS3_TEXT">Fill in the details to create an Exchange ActiveSync mailbox policy that matches your organization’s security requirements, and then click the “New” button 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 as part of the New Mailbox Wizard.</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">Go to Recipient Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS2_TEXT">In the action pane, click "New Mailbox"</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS3_TEXT">Fill in the mailbox details for the new user account.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS4_TEXT">In the Mailbox Settings section, select the "Exchange ActiveSync mailbox policy:" check box, and then click the "Browse" button.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S3_SS5_TEXT">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">In Exchange Server 2007, you can assign Exchange ActiveSync mailbox policies at the user level for greater control. 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">Go to Recipient Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS2_TEXT">Select the user that you want to add to an Exchange ActiveSync mailbox policy.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS3_TEXT">In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS4_TEXT">Click the "Mailbox Features" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS5_TEXT">Click the Exchange ActiveSync feature in the list, and then click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS6_TEXT">Select the "Apply an Exchange ActiveSync mailbox policy:" check box, and then click "Browse".</text>
                  </substep>
                  <substep>
                    <text _locID="G2_L1_S4_SS7_TEXT">Select the appropriate policy for this user, and then click "OK".</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">Go to Accepted Domain Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationBridgeheadNode\AcceptedDomainsResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS2_TEXT">In the action pane, select "New Accepted Domain"</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L1_S1_SS3_TEXT">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">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: Export the Edge Subscription file</text>
                <description _locID="G1_L2_S1_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="G1_L2_S1_SS_DESCRIPTION">On the Edge Transport server to be subscribed:</description>
                  <substep>
                    <text _locID="G1_L2_S1_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S1_SS2_TEXT">Run the following command: New-EdgeSubscription -file "C:\EdgeSubscriptionExport.xml"</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S2_TEXT">Step 2: Transfer the exported file to a Hub Transport server</text>
                <description _locID="G1_L2_S2_DESCRIPTION">You must transfer the exported file to a Hub Transport Server in your Exchange organization.</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L2_S2_SS1_TEXT">Move 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="G1_L2_S3_TEXT">Step 3: Import the Edge Transport server subscription file</text>
                <description _locID="G1_L2_S3_DESCRIPTION">On a Hub Transport server, import the Edge Subscription file by using the Exchange Management Console.</description>
                <substeps>
                  <description _locID="G1_L2_S3_SS_DESCRIPTION">On a Hub Transport server:</description>
                  <substep>
                    <text _locID="G1_L2_S3_SS1_TEXT">Go to Edge Subscription Management</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>OrganizationConfigurationBridgeheadNode\edgeSubscriptionResultPane</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S3_SS2_TEXT">In the action pane, click "New Edge Subscription". The New Edge Subscription wizard starts.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S3_SS3_TEXT">On the New Edge Subscription page, in the Active Directory Site: drop-down list, select an Active Directory site.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S3_SS4_TEXT">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_S3_SS5_TEXT">On the New Edge Subscription page, click New.</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S3_SS6_TEXT">On the Completion page, click Finish.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S4_TEXT">Step 4: Manually start Edge synchronization</text>
                <description _locID="G1_L2_S4_DESCRIPTION">On a Hub Transport server, the Microsoft Exchange EdgeSync service synchronizes configuration data hourly and recipient data every four hours out to the Edge Transport server.</description>
                <substeps>
                  <description _locID="G1_L2_S4_SS_DESCRIPTION">To manually start EdgeSync synchronization immediately:</description>
                  <substep>
                    <text _locID="G1_L2_S4_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S4_SS2_TEXT">Run the following command: Start-EdgeSynchronization</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S5_TEXT">Step 5: Verify the Edge Subscription</text>
                <description _locID="G1_L2_S5_DESCRIPTION">To verify that the Microsoft Exchange EdgeSync service successfully propagated the configuration data, log on to the Edge Transport server and verify the following conditions are true: a Send connector is configured to send Internet mail and accepted domains exist.</description>
                <substeps>
                  <description _locID="G1_L2_S5_SS_DESCRIPTION">On the Edge Transport server:</description>
                  <substep>
                    <text _locID="G1_L2_S5_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S5_SS2_TEXT">Run the following command: Get-AcceptedDomain</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_S5_SS3_TEXT">Verify that at least one item is returned by the command.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S6_TEXT">Read more about how to manually configure mail flow</text>
                <description _locID="G1_L2_S6_DESCRIPTION">If you are deploying an Edge Transport server but not by using the Microsoft Exchange EdgeSync service, you must manually configure mail flow on the Edge Transport server.</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L2_S6_SS1_TEXT">Read about how to manually configure connectors on an Edge Transport server</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/980a2461-ca82-45ed-b885-d53032e3b8ba.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L2_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>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L2_S7_TEXT">Read more about the Microsoft Exchange EdgeSync service.</text>
                <description _locID="G1_L2_S7_DESCRIPTION">For more information about how to use the Microsoft Exchange EdgeSync service:</description>
                <substeps>
                  <substep>
                    <text _locID="G1_L2_S7_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 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 a Postmaster Mailbox (3) -->
        <link>
          <text _locID="G1_L3_TEXT">Create a postmaster mailbox</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G1_L3_S1_TEXT">Step 1: View the postmaster address</text>
                <description _locID="G1_L3_S1_DESCRIPTION">View the settings for the postmaster address and determine whether a mailbox is defined to receive mail for that address.</description>
                <substeps>
                  <description _locID="G1_L3_S1_SS_DESCRIPTION">To view the settings for the postmaster address:</description>
                  <substep>
                    <text _locID="G1_L3_S1_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS2_TEXT">Run the following command: Get-TransportServer</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S1_SS3_TEXT">In the "ExternalPostmasterAddress" column of the command output, verify that a mailbox for the postmaster address already exists. If no mailbox for the postmaster address exists, complete step 2. </text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G1_L3_S2_TEXT">Step 2: Set the postmaster address</text>
                <description _locID="G1_L3_S2_DESCRIPTION">A postmaster address must be configured for the postmaster to receive mail. You can configure a mailbox specifically for the postmaster address, or you can configure the postmaster address as a secondary e-mail address for an existing user. </description>
                <substeps>
                  <description _locID="G1_L3_S2_SS_DESCRIPTION">To set the postmaster address:</description>
                  <substep>
                    <text _locID="G1_L3_S2_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S2_SS2_TEXT">Run the following command: Set-TransportServer [servername] -ExternalPostmasterAddress [postmaster e-mail address]</text>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S2_SS3_TEXT">Create a new mailbox for the user specified in the postmaster address (Optional).</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/556e2935-2b03-44c9-baa8-e7568a0b1e03.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G1_L3_S2_SS4_TEXT">Add the postmaster address as a secondary e-mail address to an existing mailbox user (Optional).</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/93e2d9a4-7558-4509-8641-8381a7eb674f.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G1_L3_DESCRIPTION">Your Transport server configuration includes a setting for the postmaster address. You must have a mailbox in your organization to receive any e-mail 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">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">In the action pane, click the "New UM Dial Plan" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S1_SS3_TEXT">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/VoIP 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">Read more information about what models of  IP/VoIP 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">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">In the action pane, click the "New UM IP Gateway" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S2_SS4_TEXT">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">Go to Unified Messaging Server Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>UnifiedMessagingNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS2_TEXT">Select the Unified Messaging server to associate with a dial plan.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS3_TEXT">In the action pane, click "Properties".</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS4_TEXT">Click the "UM Settings" tab.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS5_TEXT">In the "Associated Dial Plans" section, click the "Add" button.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS6_TEXT">Select the dial plan to associate with this server.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S3_SS7_TEXT">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 user 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">Go to Recipient Management.</text>
                    <action>
                      <name>SelectNodeByName</name>
                      <argument>RecipientsNode</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S4_SS2_TEXT">Select the mailbox to enable for Unified Messaging.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S4_SS3_TEXT">In the action pane, click the "Enable Unified Messaging" link.</text>
                  </substep>
                  <substep>
                    <text _locID="G4_L1_S4_SS4_TEXT">Complete the Enable Unified Messaging Wizard.</text>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G4_L1_DESCRIPTION">Unified Messaging combines voice messaging, 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>
      </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: Export the Edge Subscription file</text>
                <description _locID="G5_L1_S1_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_S1_SS_DESCRIPTION">On the Edge Transport server to be subscribed:</description>
                  <substep>
                    <text _locID="G5_L1_S1_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S1_SS2_TEXT">Run the following command: New-EdgeSubscription -file "C:\EdgeSubscriptionExport.xml"</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S2_TEXT">Step 2: Transfer the exported file to a Hub Transport server</text>
                <description _locID="G5_L1_S2_DESCRIPTION">You must transfer the exported file to a Hub Transport Server in your Exchange organization.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S2_SS1_TEXT">Move 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_S3_TEXT">Step 3: Import the Edge Transport server subscription file</text>
                <description _locID="G5_L1_S3_DESCRIPTION">On a Hub Transport server, import the Edge Subscription file by using the Exchange Management Console. </description>
                <substeps>
                  <description _locID="G5_L1_S3_SS_DESCRIPTION">On a Hub Transport server:</description>
                  <substep>
                    <text _locID="G5_L1_S3_SS1_TEXT">Go to Edge Subscription Management</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S3_SS2_TEXT">In the action pane, click "New Edge Subscription". The New Edge Subscription wizard starts.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S3_SS3_TEXT">On the New Edge Subscription page, in the Active Directory Site: drop-down list, select an Active Directory site.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S3_SS4_TEXT">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="G5_L1_S3_SS5_TEXT">On the New Edge Subscription page, click New.</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S3_SS6_TEXT">On the Completion page, click Finish.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S4_TEXT">Step 4: Manually start Edge synchronization</text>
                <description _locID="G5_L1_S4_DESCRIPTION">On a Hub Transport server, the Microsoft Exchange EdgeSync service synchronizes configuration data hourly and recipient data every four hours out to the Edge Transport server.</description>
                <substeps>
                  <description _locID="G5_L1_S4_SS_DESCRIPTION">To manually start EdgeSync synchronization immediately:</description>
                  <substep>
                    <text _locID="G5_L1_S4_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S4_SS2_TEXT">Run the following command: Start-EdgeSynchronization</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S5_TEXT">Step 5: 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 Edge Transport server and verify the following conditions are true: a Send connector is configured to send Internet mail and accepted domains exist.</description>
                <substeps>
                  <description _locID="G5_L1_S5_SS_DESCRIPTION">On the Edge Transport server:</description>
                  <substep>
                    <text _locID="G5_L1_S5_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S5_SS2_TEXT">Run the following command: Get-AcceptedDomain</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L1_S5_SS3_TEXT">Verify that at least one item is returned by the command.</text>
                  </substep>
                </substeps>
              </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 are deploying an Edge Transport server but not by using the Microsoft Exchange EdgeSync service , you must manually configure mail flow on the Edge Transport server.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S6_SS1_TEXT">Read about how to manually configure connectors on an Edge Transport server</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/980a2461-ca82-45ed-b885-d53032e3b8ba.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>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L1_S7_TEXT">Read more about the Microsoft Exchange EdgeSync service.</text>
                <description _locID="G5_L1_S7_DESCRIPTION">For more information about how to use the Microsoft Exchange EdgeSync service:</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L1_S7_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="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">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">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">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">How to Apply an Existing SCW Policy to an Exchange Server Role (Optional)</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">Create a postmaster mailbox</text>
          <postIt>
            <steps>
              <step>
                <text _locID="G5_L3_S1_TEXT">Step 1: View the postmaster address</text>
                <description _locID="G5_L3_S1_DESCRIPTION">View the settings for the postmaster address and determine whether a mailbox is defined to receive mail for that address.</description>
                <substeps>
                  <description _locID="G5_L3_S1_SS_DESCRIPTION">To view the setting for the postmaster address:</description>
                  <substep>
                    <text _locID="G5_L3_S1_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S1_SS2_TEXT">Run the following command: Get-TransportServer</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S1_SS3_TEXT">In the "ExternalPostmasterAddress" column of the command output, verify that a mailbox for the postmaster address already exists. If no mailbox for the postmaster address exists, complete step 2.</text>
                  </substep>
                </substeps>
              </step>
              <step>
                <text _locID="G5_L3_S2_TEXT">Step 2: Set the postmaster address</text>
                <description _locID="G5_L3_S2_DESCRIPTION">A postmaster address must be configured for the postmaster to receive mail. You can configure a mailbox specifically for the postmaster address, or you can configure the postmaster address as a secondary e-mail address for an existing user.</description>
                <substeps>
                  <description _locID="G5_L3_S2_SS_DESCRIPTION">To set the postmaster address:</description>
                  <substep>
                    <text _locID="G5_L3_S2_SS1_TEXT">Open the Exchange Management Shell</text>
                    <action>
                      <name>LaunchMsh</name>
                      <argument></argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S2_SS2_TEXT">Run the following command: Set-TransportServer [servername] -ExternalPostmasterAddress [postmaster e-mail address]</text>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S2_SS3_TEXT">Create a new mailbox for the user specified in the postmaster address (Optional).</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/556e2935-2b03-44c9-baa8-e7568a0b1e03.htm</argument>
                    </action>
                  </substep>
                  <substep>
                    <text _locID="G5_L3_S2_SS4_TEXT">Add the postmaster address as a secondary e-mail address to an existing mailbox user (Optional).</text>
                    <action>
                      <name>ShowHelpTopic</name>
                      <argument>exchhelp.chm::/html/93e2d9a4-7558-4509-8641-8381a7eb674f.htm</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L3_DESCRIPTION">Your Transport server configuration includes a setting for the postmaster address. You must have a mailbox in your organization to receive any e-mail sent to the postmaster address.</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">Configure DNS</text>
                <description _locID="G5_L4_S1_DESCRIPTION">Verify that an MX record is registered in a public DNS server for each domain for which you accept e-mail. The MX record must resolve to a Host record with an IP address that can be resolved by external mail senders. Additionally, if you are using the Sender ID anti-spam feature, you must also configure your DNS records to include your Sender ID information.</description>
                <substeps>
                  <substep>
                    <text _locID="G5_L4_S1_SS1_TEXT">Learn more about SenderID</text>
                    <action>
                      <name>ShowUrl</name>
                      <argument>http://go.microsoft.com/fwlink/?LinkID=50977</argument>
                    </action>
                  </substep>
                </substeps>
              </step>
            </steps>
          </postIt>
          <description _locID="G5_L4_DESCRIPTION">DNS Mail Exchange (MX) Records must be configured for this server to receive mail.</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>LDcemnWHia/uD0yTk5cpigWbWGs=</DigestValue></Reference></SignedInfo><SignatureValue>
    UFKW2nKRwovH+q96kwzPupxAnmlsAn0Yp36qKeBo+ILzGAZjillrGzVVZkkNwtgq2J3xJMiY
    AglyLohvLt1CDwrs38fql1JMvQZ7OUvhLG/M2aH7372A/OhleWvGr9Kl/3EOkR9hgdZ1UOY6
    e3Xcf4nzq8+eomv6Ij0FOgYxgCGy+8oLszRp98hKEWuERr3bXGk5IIPwSHQcTde4diLSMhCo
    Kw9Q1yKdr1hi0wV4JL6Qq28igGjY9QshrlGYge5LHA0ocWrPzf5PwRhAalOGWYZxwYwDCPLD
    cZSQoTJR0RWouOJ4KkDfXl0oYNAmB0xpcV7NgF3PCy2Q0mCjuyorVg==
  </SignatureValue><KeyInfo>
      <KeyValue>
        <RSAKeyValue>
          <Modulus>
            zYGWOK5covLB397Qq5WN1jydH4vDXYYuXfCxcvWrrIhqtdqxInsLyMilS5FeIhPp+fUjnbX0
            bnau7+6kPMfEwFlcP6uzczMmpmKBYXmhYvRuiJXQbt3Hn9KkURF2YbpwimWhlhaJp12B0ERm
            5dtWnkDK/Nx2JC5EMADl1n17lRHVWB2j6E8LyYjcotZTmWzKY8qZapqSXkxNEegv01tbXl9S
            o3MtpbuERQ2MGRV2ywjamqZwFehN7Gn9XbJrj+0pUTc4i8ZGSRWUUJiw9Gik194JcWd0nneM
            HYVrl+rnX0XM4OZxDdFjAJN7MZiOC7QTvbPQ7vHfIe6pYGHuN0M9ww==
          </Modulus>
          <Exponent>AQAB</Exponent>
        </RSAKeyValue>
      </KeyValue>
      <X509Data>
        <X509Certificate>
          MIIFMzCCBBugAwIBAgIKYUaeywAEAAAAZTANBgkqhkiG9w0BAQUFADCBpjELMAkGA1UEBhMC
          VVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAcBgNVBAoTFU1p
          Y3Jvc29mdCBDb3Jwb3JhdGlvbjErMCkGA1UECxMiQ29weXJpZ2h0IChjKSAyMDAwIE1pY3Jv
          c29mdCBDb3JwLjEjMCEGA1UEAxMaTWljcm9zb2Z0IENvZGUgU2lnbmluZyBQQ0EwHhcNMDYw
          NDA0MTk0MzQ2WhcNMDcxMDA0MTk1MzQ2WjB0MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2Fz
          aGluZ3RvbjEQMA4GA1UEBxMHUmVkbW9uZDEeMBwGA1UEChMVTWljcm9zb2Z0IENvcnBvcmF0
          aW9uMR4wHAYDVQQDExVNaWNyb3NvZnQgQ29ycG9yYXRpb24wggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQDNgZY4rlyi8sHf3tCrlY3WPJ0fi8Ndhi5d8LFy9ausiGq12rEiewvI
          yKVLkV4iE+n59SOdtfRudq7v7qQ8x8TAWVw/q7NzMyamYoFheaFi9G6IldBu3cef0qRREXZh
          unCKZaGWFomnXYHQRGbl21aeQMr83HYkLkQwAOXWfXuVEdVYHaPoTwvJiNyi1lOZbMpjyplq
          mpJeTE0R6C/TW1teX1Kjcy2lu4RFDYwZFXbLCNqapnAV6E3saf1dsmuP7SlRNziLxkZJFZRQ
          mLD0aKTX3glxZ3Sed4wdhWuX6udfRczg5nEN0WMAk3sxmI4LtBO9s9Du8d8h7qlgYe43Qz3D
          AgMBAAGjggGSMIIBjjAOBgNVHQ8BAf8EBAMCBsAwHQYDVR0OBBYEFO7Za6l1U81P7htOGQYe
          o5yrz5T9MBMGA1UdJQQMMAoGCCsGAQUFBwMDMIGpBgNVHSMEgaEwgZ6AFCX4K0tdyHJUreX2
          oCoXFvvB+VOBoXSkcjBwMSswKQYDVQQLEyJDb3B5cmlnaHQgKGMpIDE5OTcgTWljcm9zb2Z0
          IENvcnAuMR4wHAYDVQQLExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jv
          c29mdCBSb290IEF1dGhvcml0eYIQaguZT8AAHasR2sQCoWYnujBLBgNVHR8ERDBCMECgPqA8
          hjpodHRwOi8vY3JsLm1pY3Jvc29mdC5jb20vcGtpL2NybC9wcm9kdWN0cy9Db2RlU2lnblBD
          QTIuY3JsME8GCCsGAQUFBwEBBEMwQTA/BggrBgEFBQcwAoYzaHR0cDovL3d3dy5taWNyb3Nv
          ZnQuY29tL3BraS9jZXJ0cy9Db2RlU2lnblBDQTIuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQA4
          2e+VOJtcmBRdVG5p3wLI57P708JNrS+rf1QN2jK2+GrmDfshGnc+pWh6tJV+ilzyQ8SDm2V9
          iFBRfIIU9YNz16K+XMoCcM4mbBe8UhSlicC35KHMoXWdkXE9G8BWAFa1+IQm2l4z+9Ylel6a
          2qb79PJBGqxVRq1I3JE4E1gJSfHzMYcfvASOWxJlA+kLUdChDIqZvdnBqNAIFSUhtbZXiRzR
          W4Y1pcr9qofsqTc/t0Nr4yDxRbx+runxVbKhSLxlvlM02cnoBmMEBnhuUP9Iu5vqQ1qH260K
          gPVZxSzk5X9bSuUyee4ihZIMLbNQW8bCQFhYq9LN4y/Bzextnzd5
        </X509Certificate>
      </X509Data>
      <X509Data>
        <X509Certificate>
          MIIEEjCCAvqgAwIBAgIPAMEAizw8iBHRPvZj7N9AMA0GCSqGSIb3DQEBBAUAMHAxKzApBgNV
          BAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jv
          c29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4X
          DTk3MDExMDA3MDAwMFoXDTIwMTIzMTA3MDAwMFowcDErMCkGA1UECxMiQ29weXJpZ2h0IChj
          KSAxOTk3IE1pY3Jvc29mdCBDb3JwLjEeMBwGA1UECxMVTWljcm9zb2Z0IENvcnBvcmF0aW9u
          MSEwHwYDVQQDExhNaWNyb3NvZnQgUm9vdCBBdXRob3JpdHkwggEiMA0GCSqGSIb3DQEBAQUA
          A4IBDwAwggEKAoIBAQCpAr3BcOY78k4bKJ+XeF4w6qKpjSVf+P6VTKO3/p2iID58UaKboo9g
          MmvRQmR57qx2yVTa8uuchhyPn4Rms8VremIj1h083g8BkuiWxL8tZpqaaCaZ0Dosvwy1WCbB
          RucKPjiWLKkoOajsSYNC44QPu5psVWGsgnyhYC13TOmZtGQ7mlAcMQgkFJ+p55ErGOY9mGMU
          YFgFZZ8dN1KH96fvlALGG9O/VUWziYC/OuxUlE6u/ad6bXROrxjMlgkoIQBXkGBpN7tLEgc8
          Vv9b+6RmCgim0oFWV++2O14WgXcE2va+roCV/rDNf9anGnJcPMq88AijIjCzBoXJsyB3E4Xf
          AgMBAAGjgagwgaUwgaIGA1UdAQSBmjCBl4AQW9Bw72lyniNRfhSyTY7/y6FyMHAxKzApBgNV
          BAsTIkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jv
          c29mdCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5gg8A
          wQCLPDyIEdE+9mPs30AwDQYJKoZIhvcNAQEEBQADggEBAJXoC8CN85cYNe24ASTYdxHzXGAy
          n54Lyz4FkYiPyTrmIfLwV5MstaBHyGLv/NfMOztaqTZUaf4kbT/JzKreBXzdMY09nxBwarv+
          Ek8YacD80EPjEVogT+pie6+qGcgrNyUtvmWhEoolD2Oj91Qc+SHJ1hXzUqxuQzIH/YIX+OVn
          bA1R9r3xUse958Qw/CAxCYgdlSkaTdUdAqXxgOADtFv0sd3IV+5lScdSVLa0AygS/5DW8AiP
          friXxas3LOR65Kh343agANBqP8HSNorgQRKoNWobats14dQcBOSoRQTIWjM4bk0cDWK3CqKM
          09VUP0bNHFWmcNsSOoeTdZ+n0qA=
        </X509Certificate>
      </X509Data>
      <X509Data>
        <X509Certificate>
          MIIEwzCCA6+gAwIBAgIQaguZT8AAHasR2sQCoWYnujAJBgUrDgMCHQUAMHAxKzApBgNVBAsT
          IkNvcHlyaWdodCAoYykgMTk5NyBNaWNyb3NvZnQgQ29ycC4xHjAcBgNVBAsTFU1pY3Jvc29m
          dCBDb3Jwb3JhdGlvbjEhMB8GA1UEAxMYTWljcm9zb2Z0IFJvb3QgQXV0aG9yaXR5MB4XDTA2
          MDQwNDE3NDQxNFoXDTEyMDQyNjA3MDAwMFowgaYxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpX
          YXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9y
          YXRpb24xKzApBgNVBAsTIkNvcHlyaWdodCAoYykgMjAwMCBNaWNyb3NvZnQgQ29ycC4xIzAh
          BgNVBAMTGk1pY3Jvc29mdCBDb2RlIFNpZ25pbmcgUENBMIIBIDANBgkqhkiG9w0BAQEFAAOC
          AQ0AMIIBCAKCAQEAw8wgjbzf/z5Q7nrC1CQl9nbOIf/NKlZOypy3grI1eS0AxKgI1WPJt6X2
          6cHB1rGMlqIH+g+2glKa64LGvRDFqMDua4SOUxu7UPpkAYnBFtSCaABAeET1EjhO+2NR4Po9
          ueU3sd9jByM7cUA0R/Rrrkb1J3MeIstCGR5RtlKa06PQE8YZP3EGbfKVIURfQu3AyZlkILjB
          NPyiROZ7sh0vuKbe9KHfmyEP/lgxQVU4fq9Y5+TsWXklq/cqLxE/OHg+Qn+naOR+ImgX5kqS
          xHhEUkehT4SJk5vAZ3vqCfuGA332mXE8K6dmmMzfLeIrAhoPNEhl9TwSr/GHHB0mUm/MAwIB
          A6OCASowggEmMBMGA1UdJQQMMAoGCCsGAQUFBwMDMIGiBgNVHQEEgZowgZeAEFvQcO9pcp4j
          UX4Usk2O/8uhcjBwMSswKQYDVQQLEyJDb3B5cmlnaHQgKGMpIDE5OTcgTWljcm9zb2Z0IENv
          cnAuMR4wHAYDVQQLExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xITAfBgNVBAMTGE1pY3Jvc29m
          dCBSb290IEF1dGhvcml0eYIPAMEAizw8iBHRPvZj7N9AMBIGCSsGAQQBgjcVAQQFAgMDAAQw
          HQYDVR0OBBYEFCX4K0tdyHJUreX2oCoXFvvB+VOBMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIA
          QwBBMAsGA1UdDwQEAwIBRjAPBgNVHRMBAf8EBTADAQH/MAkGBSsOAwIdBQADggEBAGPj4PMF
          uLDqCws00YIxPoliRdUIp/lhZcguA/o4SEHPtfIng9PjxVZTqLUZzszm8aD5VrZIlEck5akf
          3HrU9hZ6EtvzkBvsCF2zhZC5jFi7HMyV05WUM/SR3v+Im15LSVA5JjogG1Q3/H1cFZPD3ByO
          8GFSPOUH7WbveeyPzldjZZUYSaB632W33yau/sgStsaizMZfi3Dzyturgm4H3GUZuaj2hsIJ
          QpjxJqxperHBK6ewZh+lr4cIa5cTuLA2mR4FoxM4o8CsMD66IdcwpspiEhyvV43l8XoRul48
          DDfxk8GSiE4EWgVcx8/WqdnhfZF4J/u0bqWPBjNYsV4qEQ8=
        </X509Certificate>
      </X509Data>
    </KeyInfo><Object id="ts-countersig"><X509Data><X509Certificate>MIID/zCCAuegAwIBAgIQDekr8NTYKYgYMgUJXpp2iDANBgkqhkiG9w0BAQUFADBTMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xKzApBgNVBAMTIlZlcmlTaWduIFRpbWUgU3Rh
bXBpbmcgU2VydmljZXMgQ0EwHhcNMDMxMjA0MDAwMDAwWhcNMDgxMjAzMjM1OTU5WjBXMQswCQYD
VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xLzAtBgNVBAMTJlZlcmlTaWduIFRpbWUg
U3RhbXBpbmcgU2VydmljZXMgU2lnbmVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
slAoSN3TaHqEGERmdV1+xLifYyb/PUOcfBE4ECVVc9l1J2n9TrkgXNMK+aAbKu1VViFh2B7b5Lwz
a8fv3aM3ZY4bkwy2Ux5cfGY1XwWKRf52Tt9TgKKBIJ2uiFyiCPflMPnuIjdMQgrO38YfxNZV6YE/
tVKjLKoBevKiqo01/p/mXWoFnz1r47+WwP7MYPlA5wegROuBUW6lKvK2ihAo7Y/cBqCGUJp7SggN
MB3KEJ5r9+lYrgSpQJmyKOiPFqw841NvS9M1nbVvZB2zliy7Ped56216+RbmJq2v75lTt0Aslbh5
qv7UUqspdH5C7DkeomoW5lm7JGjYAIBDEIeAawIDAQABo4HKMIHHMDQGCCsGAQUFBwEBBCgwJjAk
BggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29tMAwGA1UdEwEB/wQCMAAwMwYDVR0f
BCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vdHNzLWNhLmNybDAWBgNVHSUBAf8E
DDAKBggrBgEFBQcDCDAOBgNVHQ8BAf8EBAMCBsAwJAYDVR0RBB0wG6QZMBcxFTATBgNVBAMTDFRT
QTIwNDgtMS01NDANBgkqhkiG9w0BAQUFAAOCAQEAh3hw2k5SASBb4HnJgjDE/bkZlr2RAMO9zc3G
9A7Y//lNwDNiMBHF9XQb1JLeX5wgE7F8Rb5QzYPngBeDpyeTZxNG+8q4mEEDzJtRWwWLf6hv8xtQ
GyQu8mmNbCL3u8oWle0MdMBod9nrmWKHwXOQ+Il0eiOro5h7l7H3jylxTS51G0hB2vC1DSBU1neg
l4Jjaf0Jz4rwdbsJm9n5EVUmmmEyvnoCsHuGvqLDiyIseNE1drySc1z5ueZMFQojzOTS1DQuSUAV
PA9geiTGpWbvls9w6z7n9A1+3NF8o3ZxacGcT0cwNSGxoq8aYjwr2Y6qKgd72BizXHvinaVv/jyJ
rQ==</X509Certificate></X509Data><X509Data><X509Certificate>MIIDxDCCAy2gAwIBAgIQR78Zld+NUkZD99ttSA0xpDANBgkqhkiG9w0BAQUFADCBizELMAkGA1UE
BhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNV
BAoTBlRoYXd0ZTEdMBsGA1UECxMUVGhhd3RlIENlcnRpZmljYXRpb24xHzAdBgNVBAMTFlRoYXd0
ZSBUaW1lc3RhbXBpbmcgQ0EwHhcNMDMxMjA0MDAwMDAwWhcNMTMxMjAzMjM1OTU5WjBTMQswCQYD
VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xKzApBgNVBAMTIlZlcmlTaWduIFRpbWUg
U3RhbXBpbmcgU2VydmljZXMgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCpyrKk
zM0grwp9iayHdfC0TvHfwQ+/Z2G9o2Qc2rv5yjOrhDCJWH6M22vdNp4Pv9HsePJ3pn5vPL+Trw26
aPRslMq9Ui2rSD31ttVdXxsCn/ovax6k96OaphrIAuF/TFLjDmDsQBx+uQ3eP8e034e9X3pqMS4D
mYETqEcgzjFzDVctzXg0M5USmRK53mgvqubjwoqMKsOLIYdmvYNYV291vzyqJoddyhAVPJ+E6lTB
Cm7E/sVK3bkHEZcifNs+J9EeeOyfMcnx5iIZ28SzR0OaGl+gHpDkXvXufPF9q2IBj/VNC97QIlao
lc2uiHau7roN8+RN2aD7aKCuFDuzh8G7AgMBAAGjgdswgdgwNAYIKwYBBQUHAQEEKDAmMCQGCCsG
AQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0TAQH/BAgwBgEB/wIBADBBBgNV
HR8EOjA4MDagNKAyhjBodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9UaGF3dGVUaW1lc3RhbXBpbmdD
QS5jcmwwEwYDVR0lBAwwCgYIKwYBBQUHAwgwDgYDVR0PAQH/BAQDAgEGMCQGA1UdEQQdMBukGTAX
MRUwEwYDVQQDEwxUU0EyMDQ4LTEtNTMwDQYJKoZIhvcNAQEFBQADgYEASmv56ljCRBwxiXmZK5a/
gqwB1hxMzbCKWG7fCCmjXsjKkxPnBFIN70cnLwA4sOTJk06a1CJiFfc/NyFPcDGA8Ys4h7Po6JcA
/s9Vlk4k0qknTnqut2FB8yrO58nZXt27K4U+tZ212eFX/760xX71zwye8Jf+K9M7UhsbOCf3P0o=</X509Certificate></X509Data><CounterSignature xmlns="http://schemas.microsoft.com/xmldsig/timestamp/2003" ts-format="cms-timestamp-message">MIIDLQYJKoZIhvcNAQcCoIIDHjCCAxoCAQExDjAMBggqhkiG9w0CBQUAMIIBEwYJKoZIhvcNAQcB
oIIBBASCAQBQUpbacpHCi8f6r3qTDM+6nECeaWwCfRinfqop4Gj4gvMYBmOKWWsbNVVmSQ3C2CrY
nfEkyJgCCXIuiG8u3UIPCuzfx+qXUky9Bns5S+Esb8zZofvfvYD86GV5a8av0qX/cQ6RH2GB1nVQ
5jp7ddx/ifOrz56ia/oiPQU6BjGAIbL7yguzNGn3yEoRa4RGvdtcaTkgg/BIdBxN17h2ItIyEKgr
D1DXIp2vWGLTBXgkvpCrbyKAaNj1CyGuUZiB7kscDShxas/N/k/BGEBqU4ZZhnHBjAMI8sNxlJCh
MlHRFai44ngqQN9eXShg0CYHTGlxXs2AXc8LLZDSYKO7KitWMYIB7DCCAegCAQEwZzBTMQswCQYD
VQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xKzApBgNVBAMTIlZlcmlTaWduIFRpbWUg
U3RhbXBpbmcgU2VydmljZXMgQ0ECEA3pK/DU2CmIGDIFCV6adogwDAYIKoZIhvcNAgUFAKBZMBgG
CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA2MTIwMzA5MDg0MFowHwYJ
KoZIhvcNAQkEMRIEECKFRBSX3myJSrZ1AY3T+RMwDQYJKoZIhvcNAQEBBQAEggEAnes3NzxcIxue
+m6URD7ZqkLc1y5cRCBFTwp4Vb6xuBTIwR1OXzQ0n3hWPFTXJnmeiZqSqM6chXpGbYK6R2GVU1zJ
SSeOJbJUUZT7n2rStg/ADL8v4c88/tFpTle9dm0RZqIfAGzIdKmGgYHlmVyP5hPOPkF4L9wbombZ
ihAiQllxCH4FhItHdeWs4/oJZTVdjrXzNWSE6KCZs/K0zbpFnZ6su4OhRb329fiAJs8EfhQ3J213
p3IcC7akA0NdKnqOaU+L634Hrvs55/UrmT6ztYNQbyIE0csj+XHx2gc9U3Q9UV1vfQy5tN97g7yv
K9Spe7GwMblRWMQLKLFy5yLv6w==</CounterSignature></Object></Signature></startpage>