0% found this document useful (0 votes)
41 views45 pages

Win 2012 and Exchange Server 2013

This document provides instructions for configuring a basic Exchange Server setup that includes creating a send connector, adding additional accepted domains, configuring the default email address policy, and configuring external URLs. The summary is: 1. Create a send connector to allow mail to be sent to the internet. 2. Add additional accepted domains so recipients can receive mail for other domains. 3. Configure the default email address policy to apply the new accepted domain to all recipients. 4. Configure external URLs on the Client Access server's virtual directories so clients can connect from the internet.

Uploaded by

aung aung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
41 views45 pages

Win 2012 and Exchange Server 2013

This document provides instructions for configuring a basic Exchange Server setup that includes creating a send connector, adding additional accepted domains, configuring the default email address policy, and configuring external URLs. The summary is: 1. Create a send connector to allow mail to be sent to the internet. 2. Add additional accepted domains so recipients can receive mail for other domains. 3. Configure the default email address policy to apply the new accepted domain to all recipients. 4. Configure external URLs on the Client Access server's virtual directories so clients can connect from the internet.

Uploaded by

aung aung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 45

Win 2012 install Exchange

Server setup
run seup

၁ Office 2010 FilterPack64bit

၂ Office 2010 FilterPack64bit sp1 or sp2

၃ Unified Communications Managed API 4.0 Runtime

d ’ check f r upd e r gh w
Next
Next
Use recommended settings next
Server Role ၂ mail box role and client access role

client access role ၂ server ၁


p h Next
exchange server Next

Malware Protection setting No


Install err r ( IIS etc.)

၃ err r
Configuration

Windows Server Exchange Server

၁ Configure Mail Flow and Client Access


Step 1: Create a Send connector

You need to be assigned permissions before you can perform this procedure or procedures. To
see what permissions you need, see the "Send connectors" entry in the Mail Flow Permissions
topic.

Before you can send mail to the Internet, you need to create a Send connector on the Mailbox
server. Do the following.

1. Open the EAC by browsing to the URL of your Client Access server. For example,
https://localhost/ECP
2. Enter your user name and password in Domain\user name and Password and then click
Sign in.

domain\Administrator dp w rd Sign in

3. Go to Mail flow > Send connectors. On the Send connectors page, click New .
4. In the New send connector wizard, specify a name for the Send connector and then
select Internet. Click Next.
ue hr ugh r h
rec rd

5. Under Address space, click Add . In the Add domain window, make sure SMTP is
selected in the Type field.
6. Make sure Scoped send connector isn't selected and then click Next.
7. In the Fully Qualified Domain Name (FQDN) field, enter *.

Click Save.
8. Under Source server, click Add . In the Select a Server window, select a Mailbox
server. After you've selected the server, click Add and then click OK.
9. Click Finish.

How do you know this step worked?

To verify that you have successfully created an outbound Send connector, do the following:

1. In the EAC, verify the new Send connector appears in Mail flow > Send connectors.
2. Open Outlook Web App and send an email message to an external recipient. If the
recipient receives the message, you've successfully configured the Send connector.

Note:
A default inbound Receive connector is created when Exchange 2013 is installed. This Receive
connector accepts anonymous SMTP connections from external servers. You don't need to do
any additional configuration if this is the functionality you want. If you want to restrict inbound
connections from external servers, modify the Default Frontend <Client Access server>
Receive connector on the Client Access server.

Step 2: Add additional accepted domains

You need to be assigned permissions before you can perform this procedure or procedures. To
see what permissions you need, see the "Accepted domains" entry in the Mail Flow Permissions
topic.

By default, when you deploy a new Exchange 2013 organization in an Active Directory forest,
Exchange uses the domain name of the Active Directory domain where Setup /PrepareAD was
run. If you want recipients to receive and send messages to and from another domain, you must
add the domain as an accepted domain. This domain is also added as the primary SMTP address
on the default email address policy in the next step.

Important:
A public Domain Name System (DNS) MX resource record is required for each SMTP domain
for which you accept email from the Internet. Each MX record should resolve to the Internet-
facing server that receives email for your organization.

1. Open the EAC by browsing to the URL of your Client Access server. For example,
https://localhost/ECP.

2. Enter your user name and password in Domain\user name and Password and then click
Sign in.
3. Go to Mail flow > Accepted domains. On the Accepted domains page, click New .
4. In the New accepted domain wizard, specify a name for the accepted domain.

5. In the Accepted domain field, specify the SMTP recipient domain you want to add. For
example, contoso.com.
6. Select Authoritative domain and then click Save.

How do you know this step worked?

To verify that you have successfully created an accepted domain, do the following:

 In the EAC, verify the new accepted domain appears in Mail flow > Accepted domains.

Step 3: Configure the default email address policy

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.

1. Open the EAC by browsing to the URL of your Client Access server. For example,
https://localhost/ECP.

2. Enter your user name and password in Domain\user name and Password and then click
Sign in.

3. Go to Mail flow > Email address policies. On the Email address policies page, select
Default Policy and then click Edit .
4. On the Default Policy Email Address Policy page, click Email Address Format.
5. Under Email address format, click the SMTP address you want to change and then click
Edit .

e ddre
ch ge ddre
: yangon.com.mm; mymail.com.mm; yahoo.com.mm; google.com.mm
rc d e
6. On the Email address format page in the Email address parameters field, specify the
SMTP recipient domain you want to apply to all recipients in the Exchange organization.
This domain must match the accepted domain you added in the previous step. For
example, @contoso.com. Click Save.
7. Click Save
8. In the Default Policy details pane, click Apply.

ch ge e ddre p c
r duc

Note:
We recommend that you configure a user principal name (UPN) that matches the primary email
address of each user. If you don't provide a UPN that matches the email address of a user, the
user will be required to manually provide their domain\user name or UPN in addition to their
email address. If their UPN matches their email address, Outlook Web App, ActiveSync, and
Outlook will automatically match their email address to their UPN.

How do you know this step worked?

To verify that you have successfully configured the default email address policy, do the
following:

1. In the EAC, go to Recipients > Mailboxes.


2. Select a mailbox and then, in the recipient details pane, verify that the User mailbox field
has been set to <alias>@<new accepted domain>. For example, [email protected].
3. Optionally, create a new mailbox and verify the mailbox is given an email address with
the new accepted domain by doing the following:
1. Go to Recipients > Mailboxes, click New and then select User mailbox.
2. On the new user mailbox page, provide the information required to create a new
mailbox. Click Save.
3. Select the new mailbox and then, in the recipient details pane, verify that the User
mailbox field has been set to <alias>@<new accepted domain>. For example,
[email protected].

Step 4: Configure external URLs

You need to be assigned permissions before you can perform this procedure or procedures. To
see what permissions you need, see the "<Service> virtual directory settings" entry in the Clients
and Mobile Devices Permissions topic.

er e e ch ge er er we cce
g h

Before clients can connect to your new server from the Internet, you need to configure the
external domains, or URLs, on the Client Access server's virtual directories and then configure
your public domain name service (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 Virtual Directory Management.

1. Open the EAC by browsing to the URL of your Client Access server. For example,
https://Ex2013CAS/ECP.
2. Enter your user name and password in Domain\user name and Password and then click
Sign in.

g
3. Go to Servers > Servers, select the name of the Internet-facing Client Access server and

4. then click Edit .


5. Click Outlook Anywhere.

6. In the Specify the external hostname field, specify the externally accessible FQDN of
the Client Access server. For example, mail.contoso.com.

internal hostname

e er er
7. While you’re here, let’s also set the internally accessible FQDN of the Client Access
server. In the Specify the internal hostname field, insert the FQDN you used in the
previous step. For example, mail.contoso.com.
8. Click Save.

9. Go to Servers > Virtual directories and then click Configure external access domain
.

10. Under Select the Client Access servers to use with the external URL, click Add

Virtual directories c f gur u er

ecur e
11. Select the Client Access servers you want to configure and then click Add. After you’ve
added all of the Client Access servers you want to configure, click OK.

12. In Enter the domain name you will use with your external Client Access servers,
type the external domain you want to apply. For example, mail.contoso.com. Click Save.

Note:
Some organizations make the Outlook Web App FQDN unique to protect users against
changes to underlying server FQDN changes. Many organizations use owa.contoso.com
for their Outlook Web App FQDN instead of mail.contoso.com. If you want to configure
a unique Outlook Web App FQDN, do the following after you completed the previous
step. This checklist assumes you have configured a unique Outlook Web App FQDN.
1. Select owa (Default Web Site) and click Edit .
2. In External URL, type https://, then the unique Outlook Web App FQDN you
want to use, and then append /owa. For example, https://owa.contoso.com/owa.

3. Click Save.
4. Select ecp (Default Web Site) and click Edit .
5. In External URL, type https://, then the same Outlook Web App FQDN that you
specified in the previous step, and then append /ecp. For example,
https://owa.contoso.com/ecp.
6. Click Save.
After you've configured the external URL on the Client Access server virtual directories, you
need to configure your public DNS records for Autodiscover, Outlook Web App, and mail flow.
The public DNS records should point to the external IP address or FQDN of your Internet-facing
Client Access server and use the externally accessible FQDNs that you've configured on your
Client Access server. The following are examples of recommended DNS records that you should
create to enable mail flow and external client connectivity.

FQDN DNS record type Value


Contoso.com MX Mail.contoso.com
Mail.contoso.com A 172.16.10.11
Owa.contoso.com CNAME Mail.contoso.com
Autodiscover.contoso.com CNAME Mail.contoso.com
How do you know this step worked?

To verify that you have successfully configured the external URL on the Client Access server
virtual directories, do the following:

1. In the EAC, go to Servers > Virtual directories.


2. In the Select server field, select the Internet-facing Client Access server.
3. 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 below:

Virtual directory External URL value


Autodiscover No external URL displayed
ECP https://owa.contoso.com/ecp
EWS https://mail.contoso.com/EWS/Exchange.asmx
Microsoft-Server-ActiveSync https://mail.contoso.com/Microsoft-Server-ActiveSync
OAB https://mail.contoso.com/OAB
OWA https://owa.contoso.com/owa
PowerShell http://mail.contoso.com/PowerShell

To verify that you have successfully configured your public DNS records, do the following:

1. Open a command prompt and run nslookup.exe.


2. Change to a DNS server that can query your public DNS zone.
3. In nslookup, look up the record of each FQDN you created. Verify that the value that's
returned for each FQDN is correct.
4. In nslookup, type set type=mx and then look up the accepted domain you added in Step
1. Verify that the value returned matches the FQDN of the Client Access server.
Step 5: Configure internal URLs

You need to be assigned permissions before you can perform this procedure or procedures. To
see what permissions you need, see the "<Service> virtual directory settings" entry in the Clients
and Mobile Devices Permissions topic.

Before clients can connect to your new server from yourintranet, you need to configure the
internal domains, or URLs, on the Client Access server’s virtual directories and then configure
your private domain name service (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 the choice you make, you need to make sure you configure a private DNS zone for
the address space you configure. For more information about administering DNS zones, see
Administering DNS Server.

For more information about internal and external URLs on virtual directories, see Virtual
Directory Management.

Configure internal and external URLs to be the same

1. Open the Exchange Management Shell on your Client Access server.


2. Store the host name of your Client Access server in a variable that will be used in the
next step. For example, Ex2013CAS.
3. $HostName = "Ex2013CAS"
4. Run each of the following commands in the Shell to configure each internal URL to
match the virtual directory’s external URL.
5.
6. Set-EcpVirtualDirectory "$HostName\ECP (Default Web Site)" -InternalUrl
((Get-EcpVirtualDirectory "$HostName\ECP (Default Web
Site)").ExternalUrl)
7.
8. Set-WebServicesVirtualDirectory "$HostName\EWS (Default Web Site)" -
InternalUrl ((get-WebServicesVirtualDirectory "$HostName\EWS (Default
Web Site)").ExternalUrl)
9.
10. Set-ActiveSyncVirtualDirectory "$HostName\Microsoft-Server-ActiveSync
(Default Web Site)" -InternalUrl ((Get-ActiveSyncVirtualDirectory
"$HostName\Microsoft-Server-ActiveSync (Default Web
Site)").ExternalUrl)
11.
12. Set-OabVirtualDirectory "$HostName\OAB (Default Web Site)" -
InternalUrl ((Get-OabVirtualDirectory "$HostName\OAB (Default Web
Site)").ExternalUrl)
13.
14. Set-OwaVirtualDirectory "$HostName\OWA (Default Web Site)" -
InternalUrl ((Get-OwaVirtualDirectory "$HostName\OWA (Default Web
Site)").ExternalUrl)
15.
16. Set-PowerShellVirtualDirectory "$HostName\PowerShell (Default Web
Site)" -InternalUrl ((Get-PowerShellVirtualDirectory
"$HostName\PowerShell (Default Web Site)").ExternalUrl)

After you've configured the internal URL on the Client Access server virtual directories, you
need to configure your private DNS records for Outlook Web App, and other connectivity.
Depending on your configuration, you’ll need to configure your private DNS records to point to
the internal or external IP address or fully qualified domain name (FQDN) of your Client Access
server. The following are examples of recommended DNS records that you should create to
enable internal client connectivity.

FQDN DNS record type Value


Mail.contoso.com CNAME Ex2013CAS.corp.contoso.com
Owa.contoso.com CNAME Ex2013CAS.corp.contoso.com
How do you know this step worked?

To verify that you have successfully configured the internal URL on the Client Access server
virtual directories, do the following:

1. In the EAC, go to Servers > Virtual directories.


2. In the Select server field, select the Internet-facing Client Access server.
3. Select a virtual directory and then click Edit .
4. Verify that the Internal URL field is populated with the correct FQDN and service as
shown below:

Virtual directory Internal URL value


Autodiscover No internal URL displayed
ECP https://owa.contoso.com/ecp
EWS https://mail.contoso.com/EWS/Exchange.asmx
Microsoft-Server-ActiveSync https://mail.contoso.com/Microsoft-Server-ActiveSync
OAB https://mail.contoso.com/OAB
OWA https://owa.contoso.com/owa
PowerShell http://mail.contoso.com/PowerShell
To verify that you have successfully configured your private DNS records, do the following:

1. Open a command prompt and run nslookup.exe.


2. Change to a DNS server that can query your private DNS zone.
3. In nslookup, look up the record of each FQDN you created. Verify that the value that's
returned for each FQDN is correct.

Configure different internal and external URLs

1. Open the EAC by browsing to the URL of your Client Access server. For example,
https://Ex2013CAS/ECP.
2. Go to Servers > Virtual directories.
3. In the Select server field, select the Internet-facing Client Access server.
4. Select the virtual directory you want to change and click Edit .
5. In Internal URL, replace the host name between https:// and the first forward slash (/ )
with the new FQDN you want to use. For example, if you want to change the EWS
virtual directory FQDN from Ex2013CAS.corp.contoso.com to internal.contoso.com,
change the internal URL from https://Ex2013CAS.corp.contoso.com/ews/exchange.asmx
to https://internal.contoso.com/ews/exchange.asmx.
6. Click Save.
7. Repeat steps 5 and 6 for each virtual directory you want to change.

Note:
The ECP and OWA virtual directory internal URLs must be the same.
You can’t set an internal URL on the Autodiscover virtual directory.

After you've configured the internal URL on the Client Access server virtual directories, you
need to configure your private DNS records for Outlook Web App, and other connectivity.
Depending on your configuration, you’ll need to configure your private DNS records to point to
the internal or external IP address or FQDN of your Client Access server. The following is an
example of recommended DNS record that you should create to enable internal client
connectivity if you’ve configured your virtual directory internal URLs to use
internal.contoso.com.

FQDN DNS record type Value


internal.contoso.com CNAME Ex2013CAS.corp.contoso.com
How do you know this step worked?

To verify that you have successfully configured the internal URL on the Client Access server
virtual directories, do the following:
1. In the EAC, go to Servers > Virtual directories.
2. In the Select server field, select the Internet-facing Client Access server.
3. Select a virtual directory and then click Edit .
4. Verify that the Internal URL field is populated with the correct FQDN. For example,
you may have set the internal URLs to use internal.contoso.com.

Virtual directory Internal URL value


Autodiscover No internal URL displayed
ECP https://internal.contoso.com/ecp
EWS https://internal.contoso.com/EWS/Exchange.asmx
Microsoft-Server- https://internal.contoso.com/Microsoft-Server-
ActiveSync ActiveSync
OAB https://internal.contoso.com/OAB
OWA https://internal.contoso.com/owa
PowerShell http://internal.contoso.com/PowerShell

To verify that you have successfully configured your private DNS records, do the following:

1. Open a command prompt and run nslookup.exe.


2. Change to a DNS server that can query your private DNS zone.
3. In nslookup, look up the record of each FQDN you created. Verify that the value that's
returned for each FQDN is correct.

Step 6: Configure an SSL certificate

SSL certificate configure

You need to be assigned permissions before you can perform this procedure or procedures. To
see what permissions you need, see the "Certificate management" entry in the Mail Flow
Permissions topic.

Some services, such as Outlook Anywhere and Exchange ActiveSync, require certificates to be
configured on your Exchange 2013 server. The following steps show you how to configure an
SSL certificate from a third-party certificate authority (CA):

1. Open the EAC by browsing to the URL of your Client Access server. For example,
https://Ex2013CAS/ECP.
2. Enter your user name and password in Domain\user name and Password and then click
Sign in.
3. Go to Servers > Certificates. On the Certificates page, make sure your Client Access
server is selected in the Select server field, and then click New .

4. In the New Exchange certificate wizard, select Create a request for a certificate from
a certification authority and then click Next.
5. Specify a name for this certificate and then click Next.

6. If you want to request a wildcard certificate, select Request a wild-card certificate and
then specify the root domain of all subdomains in the Root domain field. If you don't
want to request a wildcard certificate and instead want to specify each domain you want
to add to the certificate, leave this page blank. Click Next.
7. Click Browse and specify an Exchange server to store the certificate on. The server you
select should be the Internet-facing Client Access server. Click Next.
8. For each service in the list shown, verify that the external or internal server names that
users will use to connect to the Exchange server are correct. For example:
o If you configured your internal and external URLs to be the same, Outlook Web
App (when accessed from the Internet) and Outlook Web App (when
accessed from the Intranet) should show owa.contoso.com. OAB (when
accessed from the Internet) and OAB (when accessed from the Intranet)
should show mail.contoso.com.
o If you configured the internal URLs to be internal.contoso.com, Outlook Web
App (when accessed from the Internet) should show owa.contoso.com and
Outlook Web App (when accessed from the Intranet) should show
internal.contoso.com.
These domains will be used to create the SSL certificate request. Click Next.

9. Add any additional domains you want included on the SSL certificate.
10. Select the domain that you want to be the common name for the certificate, and then click
Set as common name. For example, contoso.com. Click Next.

11. Provide information about your organization. This information will be included with the
SSL certificate. Click Next.
\mycertrequest.REQ

12. Specify the network location where you want this certificate request to be saved. Click
Finish.

After you've saved the certificate request, submit the request to your certificate authority (CA).
This can be an internal CA or a third-party CA, depending on your organization. Clients that
connect to the Client Access server must trust the CA that you use. After you receive the
certificate from the CA, complete the following steps:

1. On the Server > Certificates page in the EAC, select the certificate request you created
in the previous steps.
2. In the certificate request details pane, click Complete under Status.
3. On the complete pending request page, specify the path to the SSL certificate file and
then click OK.
4. Select the new certificate you just added, and then click Edit .
5. On the certificate page, click Services.
6. Select the services you want to assign to this certificate. At minimum, you should select
SMTP and IIS. Click Save.
7. If you receive the warning Overwrite the existing default SMTP certificate?, click
Yes.

How do you know this step worked?


To verify that you have successfully added a new certificate, do the following:

1. In the EAC, go to Servers > Certificates.


2. Select the new certificate and then, in the certificate details pane, verify that the following
are true:
o Status shows Valid
o Assigned to services shows, at minimum, IIS and SMTP.

How do you know this task worked?

To verify that you have configured mail flow and external client access, do the following:

1. In Outlook, on an Exchange ActiveSync device, or on both, create a new profile. Verify


that Outlook or the mobile device successfully creates the new profile.
2. In Outlook, or on the mobile device, send a new message to an external recipient. Verify
the external recipient receives the message.
3. In the external recipient's mailbox, reply to the message you just sent from the Exchange
mailbox. Verify the Exchange mailbox receives the message.
4. Go to https://owa.contoso.com/owa and verify that there are no certificate warnings.

er

Exchange er er

d w ch ge p

([email protected]) ၀၉ ၄၅၀၀ ၃၆၃၅၄

You might also like