Exchange 2007 SP1 Single Server Install


source: http://www.commodore.ca/windows/exchange/how_to_setup_exchange_2007_in_2hours.htm
A Newbies Guide to Getting Exchange Configured
By Ian Matthews, Up & Running Technologies Inc, April 19, 2008 Last Updated October 1, 2009

I could not have done a better job explaining the process than Ian Mattews of Comodore.ca did, so I just pasted the first part of his instructions here. Thank you Ian for the great instructions!

A – PREWORK:

1.

Install Windows 2008 64 Bit on a new box and run Microsoft Update to patch it to whatever is current.
2.

Make sure IPv6 is DISABLED PRIOR to the install of Exchange. NOTE: Unchecking the IPv6 checkbox on the network card, will not cut it. See THIS and THIS and THIS for details..
3.

If the server is not already a Domain Controller, you need to run DCPROMO to make it so. Exchange 2007 must be on a network with Active Directory. DCPROMO will install required DNS for most config’s.
4.

There are 4 DNS changes you should make:
*

Create your EXTERNAL DNS’ MX records for the email domains in question to point to this new Exchange Server’s IP Address
*

Create an A Record in DNS for AUTODISCOVER.YOURMAILDOMAIN.COM for your servers IP
*

Create a REVERSE LOOKUP (RDNS) entry for your Exchange servers IP
*

Create a Sender Policy Framework (SPF) entry for your Exchange servers IP

Note that only the MX record is required to get Exchange to function. The last three are NOT required but you will likley want them so why not do it now? Also you will have to wait for those settings to replicate throughout the internet (usually 12 hours).
*

For example, if your internal domain is CORPDOMAIN.LOCAL and your email domain is ABCDEDOMAIN.COM, you need to make sure that whoever is hosting the “authoritative DNS” for ABCDEDOMAIN.COM has an MX (i.e Mail Exchanger) record as well as an “A” record for AUTODISCOVER.ABCDEDOMAIN.COM, pointed to your new Exchange servers IP address.
5.

I ran my Server 08 live on the internet, relying solely on its integrated firewall. This is great for testing because when you install Exchange, it will automatically open required the holes in the firewall. If you have an external/hardware/real firewall you will need to poke your own holes in it!

B – EXCHANGE INSTALL:

1.

Install “Exchange Service Pack 1”
*

This is largely a “click next” affair but but it will perform a pile of “preinstallation checks” to make you have the prerequisites; you won’t. So just do exactly what it tells you. For example it will tell you to install IIS and IIS 6 MANAGEMENT CONSOLE, so do that. Below are screen shots of my test servers ROLES and also a shot of IIS7 FEATURES.
o

The one additional FEATURE to what is Exchange tells you to do is RPC OVER HTTP. I will mention it later, so if you don’t install it now, don’t worry about it

#

*

Ignore the following error: (as per Microsoft article 556055)
Warning: Setup cannot detect an SMTP or Send connector with an address space of ‘*’.
Mail flow to the Internet may not work properly.”.
*

Service Pack 1 for Exchange is the FULL version of Exchange, not a bunch of new hot fix binary bits and so you can install it directly. You do not need to install Exchange 07 and then patch it. If that isn’t clear enough know that Windows Server 08 will not let you install the original RTM version of Exchange 2007.
*

This process will require at least one reboot after installing pre-req’s.

#

Run Microsoft Update and make sure it includes Roll Up 1 for SP1 and then reboot.
#

Users created in ACTIVE DIRECTORY USERS AND COMPUTERS do not have email accounts automatically created for them. As such you may want to create new users via RECEPIENT CONFIGURATION, NEW MAILBOX.
#

From the server surf to https://127.0.0.1/owa/ (this is the Outlook Web Access page) and sign in as ADMINISTRATOR (or the account you created in step 3) to make sure the core is functional then log out. From a different PC surf to https://mail.yourdomain.com/owa .

*

At this point you won’t be able to do much other than see that your Exchange is installed properly.

#

Go to ORGANIZATION CONFIGURATION, HUB TRANSPORT, ACCEPTED DOMAINS, and set the default.
#

Go to ORGANIZATION CONFIGURATION, HUB TRANSPORT, EMAIL ADDRESS POLICIES and create a entry for your primary domain.
#

Create a wild card (*) SEND CONNECTOR (As per Microsoft article 556055)
#

Exchange Server 2007 Hub Transport, by default, allow only secure authenticated connections. If you don’t have an Edge server in front of the Hub Transport server (i.e. you are setting up Exchange to function completely from a single server, like we are in this article) , you will need tell Exchange to accept anonymous connections from other mail servers and clients on the web.

You cannot set this change through GUI (only when creating new connectors), so you’ll need to open the Exchange Management Shell and enter (just copy and paste this text then go back and edit the :

set-ReceiveConnector “Default ” -permissiongroups:”ExchangeUsers,ExchangeServers,ExchangeLegacyServers,AnonymousUsers”

*

Be sure sure to get rid of the brackets:

*

http://forums.msexchange.org/m_1800412705/mpage_1/key_/tm.htm http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=703467&SiteID=17

#

Surf to the OWA site (i.e. https://127.0.0.1/owa) and send an email to a remote address then reply to that message and make sure you receive it back

followed by:
Outlook anywhere install
Exchange Anti-spam
Pop3
Verification

Click on the link above for details on these last 4 steps
OUt 8, 2010

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: