Click here to load reader

Exchange Server 2013

  • View
    120

  • Download
    3

Embed Size (px)

Text of Exchange Server 2013

Server 2013

1

1. Installation guide

Here we go, this is the first part of Exchange 2013 Preview/beta. It's will walk you through the installation procedure using Windows 2008 R2 SP1. Since Exchange Server 2013 beta was released a couple of days ago Im glad to announce that my first installation is done and heres a complete walk through. My setup is basic, using one server as domain controller, Windows 2008 R2. Initially for Exchange Im using 3 servers, 1 server for the CAS role and 2 servers for the Mailbox role. There are some prerequisites that need to be installed/removed before the installation of Exchange can take place. Note: Its now recommended to install the Mailbox server first. So Im starting with that server. Step 1. Install the administration pack using the commands below, make sure to restart the server before proceeding to step 2. Import-Module ServerManager Add-WindowsFeature RSAT-ADDS

Step 2. Install the Windows features that Exchange uses, for Mailbox and CAS server use the command below: Import-Module ServerManager Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-overHTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, WebBasic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-MgmtService, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-StaticContent, Web-Windows-Auth, Web-WMI

2

Step 3. When the feature is completed. Continue with the installation of the required components, use the links below to download the components. .NET Framework 4.5 RC Windows Management Framework 4.0 Unified Communications Managed API 4.0, Core Runtime 64-bit Office 2010 Filterpack x64 Office 2010 Filterpack SP1 x64 KB 974405 (Windows Identity Foundation) KB 2619234 (RPC over HTTP) KB 2533623 (Remote code execution) Note: Make sure to uninstall the Visual C++ 11 Beta Redistributable (x64) before starting the Exchange 2013 installation. You can have a look at the setup.exe parameters using setup.exe /? setup.exe /help:install

Step 4. Start the installation using unattended installation for the Mailbox server role setup.exe /mode:install /roles:Mailbox, ManagementTools /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /OrganizationName:Testlabs /TargetDir:"D:\Program Files\Microsoft\Exchange Server\V15" The installation process starts up and prepare the organization for Exchange 2013, install the necessary Windows components. The schema prep can also be done manually using setup.exe /preparead, Ive chosen to go with the default behavior. When for the Mailbox server role installation is successfully finished it will tell you to restart the server.

3

Step 5. Start the installation of the Windows features for the CAS server role Import-Module ServerManager Add-WindowsFeature RSAT-ADDS Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-overHTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, WebBasic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-MgmtService, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-StaticContent, Web-Windows-Auth, Web-WMI Make sure to restart the server after the Windows features got installed. Step 6. Start the installation of the CAS server role setup.exe /mode:install /roles:ClientAccess, ManagementTools /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /OrganizationName:Testlabs /TargetDir:"D:\Program Files\Microsoft\Exchange Server\V15" Since this is the second server, the schema prep is already done so the installation will skip that step. When its finished it will look like the picture below, a restart of the server is required.

The installation of both servers are now completed. Next blog post will be around how to configure Exchange 2013. Thanks for reading, looking forward to your comments about the post and also about Exchange 2013 in general.

4

2. Basic configuration, Configure Mail Flow and CertificatesIf you havent read it already, I did post a complete guide for installing Exchange 2013, it can be found here. That was part 1, now its time for part 2. Which of course is the configuration of the server setup. We have lots of changes between how you configured Exchange 2007/2010 and 2013. First thing is that Exchange Management Console is gone and replaced by a refreshed ECP called Exchange Admin Center (EAC), built on Silverlight (I suppose). The old Exchange Management Shell (EMS) is still there, so I suppose lots of us geeks will use more PowerShell in the near future. The fact that EMC is replaced will make the administration easier and more portable, but I still like the EMC better. I will like the EAC better after used it for a while. This portable administration together with Remote PowerShell will be awesome. I will use both methods for the configuration steps, both EAC and PowerShell. The easiest way to find the URL path to the EAC is to start the Exchange Management Shell and run the command below: Get-EcpVirtualDirectory | fl *url* The picture below is my output from my lab environment

So lets get things started.. Start up an Internet browser and go to the URL output from the command above

Mail Flow Lets get the mail flow configured first so we can receive mails from external senders. In EAC: on the left side (menu) press Mail Flow.

5

Accepted Domains Ensure sure that your domains that should be used for SMTP is listed in here for making Exchange able to receive mails for these domains. More info about Accepted Domains can be found here. In EAC: After selecting Mail Flow to the left, press Accepted Domains at the top menu in the middle.

If your domain is not listed and you need to add it, press the plus mark and fill in the information, like my example below.

Using PowerShell: Since Im a geek I like to use PowerShell because it gives you the advantage of see what happens, have the full control and easily build scripts. For listing and adding a domain like above in PowerShell you should write: Get-AcceptedDomain New-AcceptedDomain Name testlabs.com DomainName testlabs.com DomainType Authoritative

6

Email Address Policies These policies are used to stamp each user mailbox object with an email address/SMTP address. These policies does not remove any addresses used previously, it just adds new addresses to mail objects. In EAC: By default after the installation we only have one policy, called Default Policy. I want to edit this one, by selecting the Default Policy and pressing the pen icon.

The Default Policy is showing up, in the left menu, press Email Address Format.

Since I live in Sweden and we have some special characters that I want to get rid of, Im using the custom policy, Address type: SMTP and the Email address parameters: %ra%ra%ro%g.%ra%ra%ro%[email protected] %r means it replaces the character after, in this case . Which it replaces with aao. When you have done the change press the Save button at the bottom of the page.

Check so that the change is correct, then press the Save button.

7

After the changes have been saved, it needs to be applied. This is done by pressing the Apply text/button down in the right menu.

Using PowerShell: Lets start with listing the Policy and the settings in it. As a final step lets do the same configuration to the Default Policy that we did using EAC. If you want to create more than just [email protected] to your policies, then this is done by comma separation. For setting the PrimarySMTP address, use capital letters for SMTP, and for additional addresses use small letters for smtp. See the example below: Get-EmailAddressPolicy Get-EmailAddressPolicy | fl Get-EmailAddressPolicy | Set-EmailAddressPolicy EnabledEmailAddressTemplates SMTP: %ra%ra%ro%g.%ra%ra%ro%[email protected],smtp: %[email protected] Set-EmailAddressPolicy identity Default Policy EnabledEmailAddressTemplates SMTP: %ra%ra%ro%g.%ra%ra%ro%[email protected],smtp: %[email protected] Get-EmailAddressPolicy | Update-EmailAddressPolicy It can easily be checked if the policy has been applied, it will show a True or False value. For checking the value run the command below: Get-EmailAddressPolicy | fl *appl*

8

Note: Dont forget to update the Policy, or else the new addresses wont be pushed out to the recipients.

Receive Connectors Since the HUB Transport server role now is gone and the HUB role is placed together with the CAS role, this is the server you should be looking at. After the SMTP domains have been added into the Accepted Domain tab, some settings could be of value to have a look at before starting to use the servers. A change has been made to the new version, the default connector now named Default Frontend servername. It now allows traffic from Anonymous users by default. I suppose this is due to that the Edge Transport Role also is removed. In EAC: Go to the Receive Connectors, found under Mail Flow. Make sure to select your CAS server(s) and the Default Frontend servername. Then press the pen icon for Edit the selected connector.

The only thing I did change was the Maximum receive message size to 30 MB. When you have done your changes for the connector, press the Save button.

Using PowerShell: Start the Exchange Management Shell, lets view the receive connectors and then make the changes like above. Get-ReceiveConnector

9

Get-ReceiveConnector | fl Set-ReceiveConnector Id