ENTERPRISE

Installing Exchange Server 2010 : Post-setup configuration (part 1)

1/18/2011 2:53:05 PM
When the installations of both the internal Exchange organization and the Edge Transport Server are finished, the "post setup" configuration can be started. As in Exchange Server 2007, there are a couple of additions and changes in the configuration that have to be made to the Exchange Server 2010 instance before mail can be sent or received from the Internet:
  • Enter an Exchange Server 2010 license key.

  • Enter accepted domains and setup email address policies.

  • Configure a Send Connector to send email to the Internet.

  • Configure the Hub Transport Server to accept anonymous SMTP if an Edge Transport Server is not used.

  • Add a Certificate to the Client Access Server role.

  • Configure the Client Access Server role.

1 Exchange Server 2010 license key

The public Exchange Server 2010 Release Candidate does not need a license key, but the version that's available from the Microsoft download site at the time of writing has a lifetime of 120 days. Entering a license key is not possible in this Release Candidate version, but this will obviously change when Exchange Server 2010 gets to the Release To Manufacturing (RTM) stage.

2 Accepted domains

The first thing for Exchange Server 2010 to configure is the accepted domains. In order to receive SMTP messages from the Internet, an Exchange server has to know what domains it will be receiving email for, as well as which domains it is responsible for. These are called "accepted domains," and there are three types:

  • Authoritative Domain – For this type of domain, the Exchange organization is fully responsible and there will be no other messaging environment responsible. This Exchange organization will also generate NDR (Non Delivery Report) messages when mailboxes are not available.

  • Internal Relay Domain – The Exchange organization will receive mail for this type of domain, but it will relay all messages to an Exchange organization within the company.

  • External Relay Domain – For this type of domain, the Exchange organization will receive mail, but it will relay all messages to a messaging platform outside the company.

For all three scenarios the MX records for the domain will be pointing to your Exchange organization, and mail will be initially delivered to your Exchange servers.

Accepted domains are configured on the organization level and, as such, are known by all Hub Transport Servers. If you are using an Edge Transport Server as well, the accepted domain information will also be synchronized to the Edge Transport Servers.

To configure accepted domains follow these steps:

  1. Log on to an Exchange Server 2010 server with domain administrator credentials and open the Exchange Management Console.

  2. Expand the "Microsoft Exchange On-Premises."

  3. Expand the Organization Configuration.

  4. Click on Hub Transport in the left pane.

  5. In the middle pane there are eight tabs; click on the Accepted Domains one.

  6. One entry will appear, and the name will be the local domain (FQDN) that's used when installing the Active Directory. In the Actions pane click on New Accepted Domain.

  7. In the New Accepted Domain Wizard enter a (friendly) name and the Accepted Domain itself, for example yourdomain.com. When entered, select the type of Accepted Domain in your Exchange Organization. In this example select the "Authoritative Domain." Click New to continue.

  8. The Accepted Domain will now be created, and you can now click Finish on the Completion window.

You have just created an accepted domain in your Exchange organization; the Exchange server will accept messages for this domain and, if no recipients are found, a NDR (Non Delivery Report) will be generated.

3 Email Address Policies

Exchange recipients clearly need an email address for receiving email. For receiving email from the Internet, recipients need an email address that corresponds to an accepted domain. Recipients are either assigned an email address using an Email Address Policy, or it is also possible to manually assign email addresses to recipients.

To configure Email Address Policies follow these steps:

  1. Log on to an Exchange Server 2010 server with domain administrator credentials and open the Exchange Management Console.

  2. Expand the "Microsoft Exchange On-Premises."

  3. Expand the Organization Configuration.

  4. Click on Hub Transport in the left pane.

  5. In the middle pane there are eight tabs; click on the one labeled "Email Address Policies."

  6. There will be one default policy that will be applied to all recipients in your organization. For now the default policy will be changed so that recipients will have the email address corresponding to your Accepted Domain. Click on "New Email Address Policy" to create a new policy.

  7. On the Introduction page enter a new friendly name. Click the Browse button to select a container or Organizational Unit in Active Directory where you want to apply the filter. Select the Users container. Click Next to continue.

  8. On the Conditions page you can select conditions on how the recipients in the container will be queried, for example on State, Province, Department, Company, etc. Do not select anything for this demonstration, and click Next to continue.

  9. On the Email Addresses tab click the Add button, the SMTP Email Address pop-up will be shown. Leave the local part default (Use Alias) and select the "Select the accepted domain for the email address" option and click Browse.

  10. Select the Accepted Domain you entered earlier (in Section 2.7.2), click OK twice and click Next to continue.

  11. On the Schedule page you have the option to apply the policy immediately or schedule a deploy during, for example, non-office hours. This is useful when you have to change thousands of recipients. For now leave it on Immediately and click Next to continue.

  12. Review the settings and, if everything is OK, then click New to create the policy and apply it immediately.

  13. When finished successfully, click the Finish button.

You can check the email address on a recipient through the EMC to confirm your policy has been correctly applied. Expand the Recipient Configuration in the left pane of the Exchange Management Console and click on "Mailbox." In the middle pane a list of recipients should show up, although right after installation only an administrator mailbox should be visible. Double-click on the mailbox and select the Email Addresses tab. The Administrator@ yourdomain.com should be the primary SMTP address.

4 Configure a Send Connector to the Internet

Exchange Server 2010 cannot send out SMTP messages to the Internet by default. To achieve this you'll need to create an SMTP connector, which is a connector between one or more Hub Transport Servers and the Internet. Since this information is stored in Active Directory, all Hub Transport Servers in the organization know of its existence and know how to route messages via the SMTP connector to the Internet.

To create an SMTP connector to the Internet, follow these steps:

  1. Log on to the Exchange Server 2010 server using a domain administrator account, and open the Exchange Management Console.

  2. Expand "Microsoft Exchange On-Premises" and then expand the Organization Configuration.

  3. Click on the Hub Transport, and then click on the "Send Connectors" tab in the middle pane.

  4. In the Actions Pane click on "New Send Connector."

  5. On the Introduction page enter a friendly name, "Internet Connector" for example, and in the "Select the intended use for this Send connector" drop-down box select the Internet option. Click Next to continue.

  6. On the Address Space page, click on the Add button to add an address space for the Internet Connector. In the address field enter an asterisk *, leave the cost on default and click OK. Click Next to continue.

  7. On the Network settings page you can select if the Send Connector will use its own network DNS settings to route email to other organizations, or to use a smart host. Change this according to your own environment and click Next to continue.

  8. On the source server page you can choose multiple source servers for the Send Connector. You can compare this to Bridgehead Servers in Exchange Server 2003. When you enter multiple Hub Transport Servers, the Exchange organization will automatically load balance the SMTP traffic between the Hub Transport Servers. Since we have only one Hub Transport Server installed we can leave this as default. Click Next to continue.

  9. Check the Configuration Summary, and if everything is OK click on New to create the Send Connector.

  10. On the Completion page click Finish.

You have now created a Send Connector that routes messages from the internal Exchange Server 2010 organization to the Internet.

Other  
  •  Exchange Server 2007: Design and Deploy Disaster Recovery Settings - Use Dial-Tone Restores
  •  Exchange Server 2007: Design and Deploy Disaster Recovery Settings - Work with Recovery Storage Groups
  •  Exchange Server 2007: Design and Deploy Disaster Recovery Settings - Implement Database Portability
  •  Sharepoint 2007: Specify Your Colleagues
  •  Sharepoint 2007: Modify the Links in the SharePoint Sites Web Part
  •  Sharepoint 2007: Get Started with Your Personal Site
  •  Sharepoint 2007: Create a Personal Site
  •  Exchange Server 2007 : Backup and Recover Data (part 2) - Backup and Recovery with Server 2008
  •  Exchange Server 2007 : Backup and Recover Data (part 1) - Backup and Recovery with Server 2003
  •  Exchange Server 2007 : Design and Deploy Disaster Recovery Settings - Recover Deleted Items and Mailboxes
  •  Exchange Server 2007 : Design and Deploy Disaster Recovery Settings - Design for Disaster
  •  Architecting a SharePoint 2010 Deployment : Choosing the Right Hardware for SharePoint
  •  Architecting a SharePoint 2010 Deployment : Understanding the Reasons for Deploying Multiple Farms
  •  Understanding the SharePoint Server Roles
  •  Installing Exchange Server 2010 : Installing the Edge Transport Server
  •  Installing Exchange Server 2010 : Installing dedicated server roles
  •  Installing Exchange Server 2010 : Check the Exchange installation
  •  Introducing SharePoint 2010 (part 2)
  •  Introducing SharePoint 2010 (part 1)
  •  Installing Exchange Server 2010 : Unattended setup
  •  
    Most View
    Retro Thorens TD 150 - Start It Up (Part 2)
    OpenGL on Windows : Full-Screen Rendering, Double Buffering
    Creative Sound BlasterAxx SBX 20
    Quiet PC Serenity Gamer - Take On All Challengers
    Group Test: Eight Panels Beyond HD (Part 5) : DIGIMATE IPS-2701WPH
    How Much Watts Do You Need (Part 4) : LEPA G850, Astro PT 700W, Desert Fox Commander III 800w
    Mesh Elite 3570K-W8CS - A Good Buy For Gamers
    Programming with DirectX : The 2D Resurgence - Handling Multiple Sprites
    Pentax K-30 With WR 18-55mm Lens
    WD My Passport Edge 500GB – The Smallest One Yet
    Top 20
    The Wet Servers
    Thin Berry Client (Part 2)
    Thin Berry Client (Part 1)
    Oppo Find Way - The First Smartphone With 5-Megapixel Front Camera (Part 2)
    Oppo Find Way - The First Smartphone With 5-Megapixel Front Camera (Part 1)
    Humax DTR-T1010 - Digital TV Recorders
    Take It To The Limit (Part 4)
    Take It To The Limit (Part 3)
    Take It To The Limit (Part 2)
    Take It To The Limit (Part 1)
    Orgfinances V2.3: Managing Finances On Your PC
    Sapphire Radeon HD 7790 1GB Dual-X - An Effective And Quiet Cooler
    How To Get The Most Of Your Windows 8 Experience
    StarTech SV231UAF 2 Port USB VGA KVM Switch
    Lenovo IdeaTab Lynx - A Pretty Nice Windows 8 Tablet (Part 3)
    Lenovo IdeaTab Lynx - A Pretty Nice Windows 8 Tablet (Part 2)
    Lenovo IdeaTab Lynx - A Pretty Nice Windows 8 Tablet (Part 1)
    Manage Your Google Account
    Sonos Playbar - Excellent And Expensive Home Theater Addition (Part 2)
    Sonos Playbar - Excellent And Expensive Home Theater Addition (Part 1)