How to setup front end exchange server

You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Email address policies" entry in the Email address and address book permissions topic. If you added an accepted domain in the previous step and you want that domain to be added to every recipient in the organization, you need to update the default email address policy.

For instructions, see Modify email address policies and Apply email address policies to recipients. We recommend that you configure a user principal name UPN that matches the primary email address of each user. Before clients can connect to your new server from the internet, you need to configure the external domains or URLs on the virtual directories in the Client Access frontend services on the Mailbox server and then in your public DNS records.

The steps below configure the same external domain on the external URL of each virtual directory. If you want to configure different external domains on one or more virtual directory external URLs, you need to configure the external URLs manually. For more information, see Default settings for Exchange virtual directories.

In the Exchange server properties window that opens, select the Outlook Anywhere tab, configure the following settings:. Specify the external host name Specify the internal host name In the Configure external access domain window opens, configure the following settings:. In the Select a server dialog that opens, select the Mailbox server you want to configure and then click Add. After you've added all of the Mailbox servers that you want to configure, click OK.

Enter the domain name you will use with your external Mailbox servers : Enter the external domain that you want to apply for example, mail. When you're finished, click Save. Many organizations use owa. The owa Default web site window opens. After you've configured the external URL in the Client Access services virtual directories on the Mailbox server, you need to configure your public DNS records for Autodiscover, Outlook on the web, and mail flow.

The recommended DNS records that you should create to enable mail flow and external client connectivity are described in the following table:. To verify that you've successfully configured the external URLs in the Client Access services virtual directories on the Mailbox server, do the following steps:.

Select a virtual directory and then, in the virtual directory details pane, verify that the External URL field is populated with the correct FQDN and service as shown in the following table:.

In nslookup , look up the record of each FQDN you created. Verify that the value that's returned for each FQDN is correct. Before clients can connect to your new server from your internal network, you need to configure the internal domains or URLs on the virtual directories in the Client Access frontend services on the Mailbox server and then in your internal DNS records.

The procedure below lets you choose whether you want users to use the same URL on your intranet and on the internet to access your Exchange server or whether they should use a different URL. What you choose depends on the addressing scheme you have in place already or that you want to implement. If you're implementing a new addressing scheme, we recommend that you use the same URL for both internal and external URLs. Using the same URL makes it easier for users to access your Exchange server because they only have to remember one address.

Regardless of your decision, you need to configure a private DNS zone for the address space you choose. Click Sign In to add the tip, solution, correction or comment that will help other users. Report inappropriate content using these instructions. You might be wondering how mail flows within Exchange Let's take a look: The Mailbox server role has three transport services called the transport pipeline , take a look below at how mail flows: Front End Transport service: Front End Transport service acts as a proxy for all incoming and outgoing emails.

It does not perform any email queuing or an email inspection and does not communicate with mailbox transport service directly. It receives all external Mail traffic and then sends it to transport service. The Scoped send connector setting is important if your organization has Exchange servers installed in multiple Active Directory sites:.

If you don't select Scoped send connector , the connector is usable by all transport servers Exchange or later Mailbox servers and Exchange Hub Transport servers in the entire Active Directory forest. This is the default value.

If you select Scoped send connector , the connector is only usable by other transport servers in the same Active Directory site. On the next page, in the Source server section, click Add. In the Select a Server dialog box that appears, select one or more Mailbox servers that you want to use to send mail to the internet.

If you have multiple Mailbox servers in your environment, select the ones that can route mail to the internet. If you have only one Mailbox server, select that one. After you create the Send connector, it appears in the Send connector list. To configure the Send connector to proxy outbound mail through the Front End Transport service, see Configure Send connectors to proxy outbound mail.

Open the Exchange Management Shell. For more information, see Open the Exchange Management Shell. This example creates the internet Send connector named "To internet" with the following properties:.

The Send connector uses DNS routing. The local Exchange server is the source server. We aren't using the SourceTransportServer parameter, and the default value is the local Exchange server. The Send connector isn't scoped to the local Active Directory site. For information about other options, see New-SendConnector.