Saturday, 6 August 2011

Installing a New Exchange 2010 with CA, Hub, and Mailbox Roles, and Additional Steps to Achieve an Operational Exchange

Requirements:

AD forest functional level Windows Server 2003 or higher
AD Schema Master running Windows Server 2003 SP1 or later
Full installation of Windows Server 2008 SP2 or later, or Windows 2008 R2 for Exchange server
Exchange server joined to the domain


Prerequisites to installing Exchange:

1) Apply updates to Windows 2008 R2
2) Download and install Microsoft Office 2010 Filter Packs
3) To install required Windows components/features
i: Open PowerShell
ii: Run the following command: Import-Module ServerManager
iii: For the typical install with CA, Hub, and Mailbox roles run the following command:
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
(Note: if a brand new Exchange 2010 install is experiencing issues like a blank screen when try to access OWA via an internet browser, it is likely that not all the required components have been installed, can reapply the above to fix.)
4) For a CAS set the Net.Tcp Port Sharing Service to start automatically
i: Open PowerShell
ii: Run the following command: Set-Service NetTcpPortSharing -StartupType Automatic


Exchange 2010 Installation

Not really much to it – run setup from the Exchange 2010 media, stick with the default 'Typical Exchange Server Installation' which will install the CA, Hub, and Mailbox roles, and answer prompts as desired. When the install has finished, install Microsoft Update (if necessary) and apply all the latest updates


Additional steps to achieve a fully operational Exchange

1) Enter Product Key
i: In the console tree, navigate to Server Configuration.
ii: In the action pane, click Enter Product Key Group.
iii: On the Enter Product Key page, enter the product key, and then click Enter.
iv: On the Completion page, review the following, and then click Finish to close the wizard:

2) Configure domains for which the Exchange server will accept e-mail messages
EMC → Organization Configuration → Hub Transport → Accepted Domains → New Accepted Domain

3) Configure e-mail address policies
EMC → Organization Configuration → Hub Transport → E-mail Address Policies → New E-mail Address Policy (or modify Default Policy)

4) Manually configure send connector
EMC → Organization Configuration → Hub Transport → Send Connectors → New Send Connector (or modify default Internet send connector)

5) Manually configure receive connector
EMC → Server Configuration → Hub Transport → Receive Connectors → New Receive Connector (or modify Default receive connector)
(Note: to allow emails to be received from outside the Exchange Organization, on the 'Permission Groups' tab must tick 'Anonymous users' for 'Specify who is allowed to connect to this Receive connector')

6) Configure and external postmaster recipient to receive e-mail addresses (according to RFC 2821, every domain must be able to receive mail that is sent to the postmaster address.)

This is all the configuration that is required on an Exchange server to complete a basic setup. Additional work needs to be carried out on the internal and external interfaces of the network firewall to allow SMTP and HTTPS traffic in and out (may also desire to allow HTTP.) An MX record needs to be set up for the external domain and either point to a 3rd party mail filtering company who then forward the e-mails to the Exchange server, or point directly to a public IP address NAT-ed on the firewall to point to the internal IP address of the Exchange. A DNS A record will need to be created also for the external IP address of the Exchange server.


Credits:


No comments:

Post a Comment