Part 7 – Install and Configure Exchange Server 2019
In part 6 of this blog post series, we have successfully activated Exchange Server 2019 product key and reviewed the methods available to activate Exchange 2019 server. After you have activated the product key for exchange server 2019, next step is to setup mail flow for your organization. Without configuring mail flow, you will not be able to send mail to the internet and external clients like Microsoft Outlook and Exchange ActiveSync devices won’t be able to connect to your Exchange.
You will receive certificate warnings when you connect to the Exchange admin center (EAC) website until you configure a secure socket layer (SSL) certificate on the Mailbox server. We will go through SSL configuration later on in this blog post series.
Exchange Server 2019 Send Connector
When you install your first Exchange 2019 server, the server can not send email outside of your Exchange organization. To send email outside of your Exchange organization, you need to create a Send connector.
By default, a Receive connector named “Default Frontend <ServerName>” is created when Exchange is installed. This Receive connector accepts anonymous SMTP connections from external servers. If you want to restrict inbound connections from external servers, modify the Default Frontend <Mailbox server> Receive connector on the Mailbox server.
Without a Send Connector, mail cannot flow from your Exchange to the internet. The exception is if you install an Edge Transport in your perimeter network and subscribe the Edge Transport to your Exchange organization.
Option 1 – Use the EAC to create an internet Send connector
- In the EAC, navigate to Mail flow > Send connectors, and then click Add . This starts the New Send connector
- On the first page, enter the following information:
- Name: Enter a descriptive name for the Send connector, for example, Outbound to internet.
- Type: Select Internet.
- When you’re finished, click Next.
- On the next page, verify that MX record associated with recipient domain is selected. This means the connector uses DNS on the internet to route mail, as opposed to routing all outbound mail to a smart host. When you’re finished, click Next.
- On the next page, enter the following information:
- In the Address space section, click Add . In the Add domain dialog box that appears, in Fully Qualified Domain Name (FQDN), enter an asterisk (*), and then click Save. This value indicates that the Send connector applies to messages addressed to all external domains.
- 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 2013 or later Mailbox servers and Exchange 2010 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.
- When you’re finished, click Next.
- 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’ve selected at least one Mailbox server, click Add, click OK, and then click Finish.
Option 2 – Use the Exchange Management Shell to create an internet Send connector
- Open the Exchange Management Shell. Run the following Exchange Management cmdlet:
New-SendConnector -Name <Connector Name> -AddressSpaces * -Internet [-SourceTransportServer <SERVER NAME>]
This example creates the internet Send connector with the following properties:
- The usage type is Internet.
- The Send connector uses DNS routing. We aren’t using the DNSRoutingEnabled parameter, and the default value is $true.
- The Send connector is for all external domains (*).
- 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. We aren’t using the IsScopedConnector parameter, and the default value is $false.
In this blog post, we have successfully created our first “Send Connector” in Exchange Server 2019. With Send connector, we can send emails to internal domains like gmail.com, yahoo.com, microsoft.com and other domains. In next blog post series, we will go through the configuration of virtual directories and related services.
- Part 1 – Exchange Server 2019 Installation and configuration
- Part 2 – Exchange Server 2019 Installation and configuration
- Part 3 – Exchange Server 2019 Installation and Configuration
- Part 4 – Exchange Server 2019 Installation and configuration
- Part 5 – Exchange Server 2019 Installation and configuration
- Part 6 – Exchange Server 2019 Installation and configuration
- Part 8 – Exchange Server 2019 Installation and configuration
- Part 9 – Exchange Server 2019 Installation and configuration
- Part 10 – Exchange Server 2019 Installation and Configuration