In our previous post we successfully completed our first Exchange 2010 Install, and after looking back the most difficult part was ensuring all the prerequisites were met for a new Exchange environment . In today’s post we will continue with our installation with a focus on basic configuration to get mail flowing for internal and external clients, configuring our Anti-Spam agents on the Hub Transport Server (remember we are not utilising the Edge Role in our dev environment) and testing all of this using the brand spanking new Outlook Web Access (OWA). Just a reminder, the next and last article in this series will scrutinise some of the new features of Exchange 2010 with OWA being one of them, so stay tuned!
You will notice when you launch Exchange Management Console that Exchange 2010 has an organizational summary screen which will need to get refreshed when changes are made. To do so, Right Click on Microsoft Exchange On-Premises and select “Gather Organizational Information”, this will go ahead and run a couple of scripts and then provide you with an updated summary screen.
The quickest method in verifying a successful install (apart from checking the installation logs) is to navigate to the various nodes and ensure that your Mailbox Database is mounted, your OWA site is setup (navigate to the site via /OWA”>https://<servername>/OWA) and finally check your Hub Transport Server configuration. You should notice that the Client and Default Receive connectors have been setup by default.
(Default Mailbox Database in a “Mounted” Status)
(Default OWA Web Site)
(Hub Transport Server Configuration with client and default receive connectors)
Let’s now proceed by creating a second Active Directory Account so we can test mail flow between two user accounts (note that the Administrator user has already been created). To do so, you can create the Active Directory account first in Active Directory Users and Computers and then run the “New Mailbox” wizard or you could create the Active Directory User and Mailbox in the one step using the same “New Mailbox” Wizard. The “New Mailbox” Wizard is located under Recipient Configuration / Mailbox.
Upon completing the wizard you will be presented with 2 users listed under Recipient Configuration / Mailbox.
Login using your newly created User Account and Mailbox through OWA and send a test message to the administrator account and CC yourself (this will test the Hub Transport internal routing)
Okay! We have now confirmed that internal traffic is being routed successfully, now for external. We need to ensure that we have setup our External Domain as an Accepted Domain. To do so, navigate to the “Organization Configuration / Hub Transport node and click on the Accepted Domains Tab. Run the New Accepted Domain Wizard under Actions.
Your Exchange Server is now authoritative for that domain and you should now be able to receive external emails to that domain.
Let’s now setup an Email Address Policy for our external domain. Note that a Default Policy is already setup for your internal domain.
Under Organization Configuration / Hub Transport / Email Address Policies Tab, click on New E-Mail Address Policy under Actions.
Click Next and specify any conditions, in my case I left the default for all recipient types, click Next, then select Add SMTP, and fill out your Email address naming convention and the specified accepted domain we just created earlier.
Click Next to apply the policy immediately, and then click New.
Our newly created Email Address Policy is now listed with a higher priority.
We are now making some good progress and should soon be able to send email to the outside world. Because we have not setup an Edge Server to handle smtp routing externally, we will need to manually setup a send connector to send directly to the Internet. Obviously this isn’t best practice and one should always setup a separate Edge Server with its notable advantages such as dedicated messaging hygiene especially when run in conjunction with a compatible Virus Scanning API (VSAPI) such as Forefront for Exchange, but for our dev environment this will suffice. In order to setup a send connector, navigate to, Organization configuration / Hub Transport / Send Connectors and click on New Send Connector under Actions. Type in a Name and select Internet as the intended use for this send connector and then click Next.
Specify your address space, Select Add SMTP Address Space and type * to be able to send to all external domains.
Select your preferred Network Settings, Click Next.
Your source server should then automatically populate, click Next.
That’s it, you should now be able to send to external remote domains. Now I mentioned earlier that we were not going to setup an Edge Role in our dev environment but having said that we can still utilise the Anti-Spam functionality on our multi-role virtual machine, specifically on the Hub Transport Server Role. TechNet has a great article on enabling this functionality and can be found here. In summary, the process is as follows;
Launch the Exchange Management Shell and browse to where the Install-AntispamAgents.ps1 is located which by default is under
%system drive%/Program Files\Microsoft\Exchange Server\v14\Scripts folder
Type the following command ./install-AntispamAgents.ps1
After the command has successfully run you will need to restart the Microsoft Exchange Transport Service by running the following command;
You will now notice that there is an Anti-spam tab located under Organization Configuration / Hub Transport with the Anti-spam features listed and enabled.
Well, that’s all that is to it. Basic configuration for an Exchange 2010 server is pretty much identical to Exchange 2007 which is great for Messaging Administrators who have already adopted Exchange 2007. The last article in this series will outline some of the new Exchange 2010 features with nice pretty pictures outlining these, so stay tuned.