Exchange 2013

Microsoft Exchange 2013

Once you have installed Windows 2012R2

Microsoft Exchange is an email server. It is one of the email systems that Retain can connect to. It is helpful to have an Exchange server handy for testing. Microsoft is pushing people toward Office 365 but it is safe to say people will continue to use Exchange for 5-20 years. For the lab environment we are not going to give Exchange quite as many resources as it might want. 8GB of RAM and 2 cores would be good enough. Giving it less than that and it really starts to drag.

Give it two drives: OS and Data.

• OS: 60-80GB
• Data: 60GB

The OS drive needs a lot of room mainly for logs. Exchange keeps lots of logs now, but doesn't give you much in the way of tools for managing them. [1] The best you can do is provide plenty of room to store them.

You'll need to follow these directions to move the Exchange database if you didn't set it up correctly the first time. [2]

Installing Microsoft Exchange 2013

You need to install Exchange 2013 on a Microsoft Windows Server 2012 R2 system.

Make sure your server has the name that you want, Exchange does not like having it changed once it is set up.

The most important tool to have handy is the Exchange Server Deployment Assistant. This provides a great checklist of things you must do to successfully deploy an Exchange server.

We will want an On-premise, new install, with both Mailbox and CAS roles on board. We will NOT be using disjoint namespaces. We will NOT be using Unified Messaging (but it will install it anyway). We will NOT be using an Edge server.

Save that checklist.

Make sure to do the prerequisites!

Open PowerShell and execute the commands

Install-WindowsFeature RSAT-ADDS

and

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, 
RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, 
RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-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-Mgmt-Service, Web-Net-Ext45, 
Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, 
Web-WMI, Windows-Identity-Foundation

You'll need to restart here.

Prerequisite installs

• Install the features: .NET Framework 4.5 and Windows Management Framework 3.0 in Server Manager.

Note: .NET Framework 4.5 and Windows Management Framework 3.0 are included with Windows Server 2012 and don't need to be downloaded separately. SP1 is before CU6.

Downloads:

• The Unified Communications Managed API 4.9 Runtime [3]

• The Microsoft Office 2010 Filter Packs [4]

• Filter Packs SP1 [5]

• Filter Packs SP2 [6]

Run Windows update and restart.

Snapshot here.

Preparing AD

First you need to extend the schema. Open a command prompt in administrator mode, go to the disk or directory you downloaded exchange into and run

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

Now you have to prepare Active Directory, this can be done right after the previous command.

Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms

<organization name> is something like gwavasupport, gwava, microsoft, or novell without .com or anything like that.

Now you have to prepare your AD domains and in the case of a lab you want to do all of them.

Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms

Install Exchange

Now we can start installing Exchange:

• From File Explorer you can run Setup.exe as administrator (right-click and choose Run as administrator)

• It will ask you about downloading updates which is a good idea.

• There will be more screens but defaults will be sufficient.

• When it comes to Server Role Selection you want to choose Mailbox role and Client Access role (Client Access will appear to be greyed out but you can select it.)

• Take the default location or if you have two disks set it for the Data disk (recommended).

• Turn off Malware detection.

• Then it will check for the prerequisites. Warnings are okay, because this will be the first exchange server and as long as there are no errors you are good to go.

• Then it will take about an hour to install and prepare all the software.

• Finally, you will have to reboot.

Post-install steps

There are a number of post-install tasks that need to be completed before your Exchange Server is fully functional. These will be done from the Exchange Admin Center (EAC).

You can log into the Exchange Admin Center (EAC) by browsing to https://[serverName|IP address]/ecp Remember to log in with your AD forest domain name\user name

You can use the Outlook Web App(OWA) to send and receive mail https://[serverName|IP address]/owa Remember to log in with your AD forest domain name\user name

You will also want to create a workstation and give it Outlook.

Send Connector

You will need to create a Send Connector so the mail can flow.

First you need to create a send connector.

• Go to EAC/Mail Flow/Send Connector.

• Click the plus sign to create a new connector, a dialog box will appear, for the lab an internal connector will be enough. Route it through a smart host
• I name mine intranetMailSendConnector, not terribly original but it is straightforward
• Route mail through smart hosts. Add the host, which is the Active Directory domain you created before e.g. ad.gwavasupport.net
• No need for authentication, at this time
• Address space: Press + and set Type = SMTP, FQDN = your domain, Cost = 1
• Source server: Press + and add your domain server as a transport server
• Click finish

Add Users

An email system isn't much good without users. You can create users in the EAC but that puts all of them in the Users container in AD. You will want to make some Organizational Units to mimic a real system.

Exchange monitors itself and the most visible way it does that is to send itself mail. In Retain you will see at least two mailboxes that begin with the name HealthMailboxNNNN. These will generate about a thousand messages a day. These will also end up in the Administrator mailbox. You'll have to create a mailbox rule that will move them to the trash so they don't fill up the Administrator's inbox.

Now you can install and connect Retain

Other things

Accepted Domain

The Deployment assistant talks about creating a new one but since Exchange already has the current domain, you can skip this step in the assistant. However, many organizations have multiple domains. One place to add them is Active Directory Domains and Trusts[7], and this is another place. Next configure an accepted domain.

• In the EAC goto Mail flow/Accepted domains.
• Click the Plus sign.
• Give it a name.
• Give it a domain
• Choose the checkbox that makes the most sense, usually Internal relay domain. The first domain would be the Authoritative domain.

Change password policy

“On my server, these settings are disabled under the Local Security Policy (WS2012 Essentials.) However, they can be changed under the Group Policies. From the charms, search Apps for “gpmc.msc” and start it. Group Policy Management -> Forest: YourServerName.local -> Domains -> YourServerName.local Select “Default Domain Policy” then right-click and select “Edit…” to open the Group Policy Management Editor. Group Policy Management Editor Computer Configuration / policies -> Windows Settings -> Security Settings -> Account Policies -> Password Policy ”[8]

Mailbox Limits

Mailboxes have certain limitations that you need to be aware of. [9]

There are also some important practical limits that show up. These were discussed in a Microsoft blog: "I usually recommend no more than about 2500 - 5000 messages in any of the critical path folders. The critical path folders are the Calendar, Contacts, Inbox, and Sent Item folder. Ideally, keep the Inbox, Contacts and Calendar to 1000 or less. Other folders, particularly custom folders created by the user, can handle having larger numbers of items without having a broad impact on the user experience (20,000 items in my "Cookie Recipes" folder? No problem - except when I need to find that recipe from last Christmas!)." [10]

GWAVA has learned by experience that large (100GB+) mailboxes are unable to be served by Exchange.

HealthMailBox users

Each database will also have at least a couple of HealthMailbox users that will show up in Retain, in production they can be excluded as all they are doing are sending "Can you still hear me?" messages.

Next Steps

Installing Windows Server 2012 R2

Creating CAS

Retain Exchange Install