Exchange 2003 Setup Guide

[LEFT][CODE]http://www.mmmug.co.uk/articles/exchange-2003-setup-guide[/CODE]

First install two servers running Windows 2003 (R2 if you have it)
Next patch fully using Windows update
Create a domain controller (any therefore a domain)
Join the second machine to the domain
On the second machine which will become your Exchange server install the prereqs for Exchange
Open Add/Remove Programs control panel
[IMG]http://www.mmmug.co.uk/images/stories/image002.jpg[/IMG]

Click Add/Remove Windows Components
[IMG]http://www.mmmug.co.uk/images/stories/Add-Remove-Components.jpg[/IMG]

Select Application Server and click Details
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image006.jpg[/IMG]

Click ASP.NET
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image008.jpg[/IMG]

Double Click Internet Information Services (IIS)
Scroll down and check the box next to NNTP and SMTP
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image010.jpg[/IMG]

Click OK twice and then click Next
When prompted insert the CDs as requested
Once the install is complete click Finish and close the Add/Remove programs control panel
[B][IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image012.jpg[/IMG]

Exchange install - Forest and Domain Prep
[/B]

Next insert the Exchange 2003 CD
Click Exit on the first page
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image014.jpg[/IMG]
Now download the latest Exchange deployment tools which can be found at the link below (as of 30/12/2006)
[URL]http://www.microsoft.com/downloads/details.aspx?familyid=271e51fd-fe7d-42ad-b621-45f974ed34c0&displaylang=en[/URL]
Once you have the latest Exdelpoy.exe double click it.
Enter the location to save the files and click "OK"
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image016.jpg[/IMG]
Click OK
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image018.jpg[/IMG]

Next locate and double click the exdeploy.hta file
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image020.jpg[/IMG]
You are now at the first page of the Exchange deployment tools
Click "Deploy the first Exchange server"
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image022.jpg[/IMG]

Click "New Exchange 2003 Installation"
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image024.jpg[/IMG]
The first three steps are all about ensuring the prerequisites are met. Select the checkboxes by steps 1 and 2 as these have already been covered.
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image026.jpg[/IMG]

Select the checkboxes by steps 1 and 2 as these have already been covered.
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image028.jpg[/IMG]

For step three ensure the support tools are installed. If they are not, download them from the link below and install them:
[url=http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en]Download details: Windows Server 2003 Service Pack 1 32-bit Support Tools[/url]
Click the box by step three
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image030.jpg[/IMG]
To perform step four open a CMD prompt (Start, Run, type "CMD", Press "Enter")
In the CMD prompt window type the command below and press enter:
[I]dcdiag /f:c:\dcdiaglog.txt /s:domaincontrollername.domain.com[/I]
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image032.jpg[/IMG]
This will output the results to a text file in the C: called dcdiaglog.txt. Open the file and ensure there are no errors. You should see output like the following:
[I]Domain Controller Diagnosis[/I]
[I]Performing initial setup:[/I]
[I] Done gathering initial info.[/I]

[I]Doing initial required tests[/I]

[I] Testing server: Default-First-Site-Name\E2K7DC1[/I]
[I] Starting test: Connectivity[/I]
[I] ......................... E2K7DC1 passed test Connectivity[/I]

[I]Doing primary tests[/I]

[I] Testing server: Default-First-Site-Name\E2K7DC1[/I]
[I] Starting test: Replications[/I]
[I] ......................... E2K7DC1 passed test Replications[/I]
[I] Starting test: NCSecDesc[/I]
[I] ......................... E2K7DC1 passed test NCSecDesc[/I]
[I] Starting test: NetLogons[/I]
[I] ......................... E2K7DC1 passed test NetLogons[/I]
[I] Starting test: Advertising[/I]
[I] ......................... E2K7DC1 passed test Advertising[/I]
[I] Starting test: KnowsOfRoleHolders[/I]
[I] ......................... E2K7DC1 passed test KnowsOfRoleHolders[/I]
[I] Starting test: RidManager[/I]
[I] ......................... E2K7DC1 passed test RidManager[/I]
[I] Starting test: MachineAccount[/I]
[I] ......................... E2K7DC1 passed test MachineAccount[/I]
[I] Starting test: Services[/I]
[I] ......................... E2K7DC1 passed test Services[/I]
[I] Starting test: ObjectsReplicated[/I]
[I] ......................... E2K7DC1 passed test ObjectsReplicated[/I]
[I] Starting test: frssysvol[/I]
[I] ......................... E2K7DC1 passed test frssysvol[/I]
[I] Starting test: frsevent[/I]
[I] ......................... E2K7DC1 passed test frsevent[/I]
[I] Starting test: kccevent[/I]
[I] ......................... E2K7DC1 passed test kccevent[/I]
[I] Starting test: systemlog[/I]
[I] ......................... E2K7DC1 passed test systemlog[/I]
[I] Starting test: VerifyReferences[/I]
[I] ......................... E2K7DC1 passed test VerifyReferences[/I]

[I] Running partition tests on : ForestDnsZones[/I]
[I] Starting test: CrossRefValidation[/I]
[I] ......................... ForestDnsZones passed test CrossRefValidation[/I]
[I] Starting test: CheckSDRefDom[/I]
[I] ......................... ForestDnsZones passed test CheckSDRefDom[/I]

[I] Running partition tests on : DomainDnsZones[/I]
[I] Starting test: CrossRefValidation[/I]
[I] ......................... DomainDnsZones passed test CrossRefValidation[/I]
[I] Starting test: CheckSDRefDom[/I]
[I] ......................... DomainDnsZones passed test CheckSDRefDom[/I]

[I] Running partition tests on : Schema[/I]
[I] Starting test: CrossRefValidation[/I]
[I] ......................... Schema passed test CrossRefValidation[/I]
[I] Starting test: CheckSDRefDom[/I]
[I] ......................... Schema passed test CheckSDRefDom[/I]

[I] Running partition tests on : Configuration[/I]
[I] Starting test: CrossRefValidation[/I]
[I] ......................... Configuration passed test CrossRefValidation[/I]
[I] Starting test: CheckSDRefDom[/I]
[I] ......................... Configuration passed test CheckSDRefDom[/I]

[I] Running partition tests on : exchange[/I]
[I] Starting test: CrossRefValidation[/I]
[I] ......................... exchange passed test CrossRefValidation[/I]
[I] Starting test: CheckSDRefDom[/I]
[I] ......................... exchange passed test CheckSDRefDom[/I]

[I] Running enterprise tests on : exchange.local[/I]
[I] Starting test: Intersite[/I]
[I] ......................... exchange.local passed test Intersite[/I]
[I] Starting test: FsmoCheck[/I]
[I] ......................... exchange.local passed test FsmoCheck[/I]

If you get any errors then investigate them. You could post a question to the forums at [url=http://www.mmmug.co.uk/forum]Microsoft Messaging and Mobility User Group UK - Categories - Microsoft Messaging & Mobility User Group Forum[/url]
So long as you have no errors move back to the deployment tools and check the 4th box.

[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image034.jpg[/IMG]
Next move back to the command prompt and enter the command below and press enter:
Netdiag >c:\netdiaglog.txt
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image036.jpg[/IMG]

The command will take a short while to execute. Once complete view the log file in the C:
[I] ...................................[/I]
[I] Computer Name: E2K7MB1[/I]
[I] DNS Host Name: E2K7MB1.exchange.local[/I]
[I] System info : Microsoft Windows Server 2003 R2 (Build 3790)[/I]
[I] Processor : x86 Family 6 Model 13 Stepping 8, GenuineIntel[/I]
[I] List of installed hotfixes :[/I]
[I] KB890046[/I]
[I] KB893756[/I]
[I] KB896358[/I]
[I] KB896422[/I]
[I] KB896424[/I]
[I] KB896428[/I]
[I] KB898715[/I]
[I] KB899587[/I]
[I] KB899588[/I]
[I] KB899589[/I]
[I] KB899591[/I]
[I] KB900725[/I]
[I] KB901017[/I]
[I] KB901214[/I]
[I] KB902400[/I]
[I] KB904706[/I]
[I] KB904942[/I]
[I] KB905414[/I]
[I] KB908519[/I]
[I] KB908531[/I]
[I] KB909520[/I]
[I] KB910437[/I]
[I] KB911164[/I]
[I] KB911280[/I]
[I] KB911562[/I]
[I] KB911567[/I]
[I] KB911927[/I]
[I] KB912919[/I]
[I] KB914389[/I]
[I] KB916281[/I]
[I] KB917344[/I]
[I] KB917734[/I]
[I] KB917953[/I]
[I] KB918439[/I]
[I] Q147222[/I]
[I]Netcard queries test . . . . . . . : Passed[/I]
[I]Per interface results:[/I]
[I] Adapter : Local Area Connection[/I]
[I] Netcard queries test . . . : Passed[/I]
[I] Host Name. . . . . . . . . : E2K7MB1[/I]
[I] IP Address . . . . . . . . : 192.168.23.20[/I]
[I] Subnet Mask. . . . . . . . : 255.255.255.0[/I]
[I] Default Gateway. . . . . . : 192.168.23.1[/I]
[I] Dns Servers. . . . . . . . : 192.168.23.10[/I]
[I] AutoConfiguration results. . . . . . : Passed[/I]
[I] Default gateway test . . . : Failed[/I]
[I] No gateway reachable for this adapter.[/I]
[I] NetBT name test. . . . . . : Passed[/I]
[I] [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.[/I]
[I] WINS service test. . . . . : Skipped[/I]
[I] There are no WINS servers configured for this interface.[/I]
[I]Global results:[/I]
[I]Domain membership test . . . . . . : Passed[/I]
[I]NetBT transports test. . . . . . . : Passed[/I]
[I] List of NetBt transports currently configured:[/I]
[I] NetBT_Tcpip_{BA408A51-ABAA-4413-8D49-BA81B877126B}[/I]
[I] 1 NetBt transport currently configured.[/I]
[I]Autonet address test . . . . . . . : Passed [/I]
[I]IP loopback ping test. . . . . . . : Passed [/I]
[I]Default gateway test . . . . . . . : Failed[/I]
[I] [FATAL] NO GATEWAYS ARE REACHABLE.[/I]
[I] You have no connectivity to other network segments.[/I]
[I] If you configured the IP protocol manually then[/I]
[I] you need to add at least one valid gateway.[/I]
[I]NetBT name test. . . . . . . . . . : Passed[/I]
[I] [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.[/I]
[I]Winsock test . . . . . . . . . . . : Passed[/I]
[I]DNS test . . . . . . . . . . . . . : Passed[/I]
[I]Redir and Browser test . . . . . . : Passed[/I]
[I] List of NetBt transports currently bound to the Redir[/I]
[I] NetBT_Tcpip_{BA408A51-ABAA-4413-8D49-BA81B877126B}[/I]
[I] The redir is bound to 1 NetBt transport.[/I]
[I] List of NetBt transports currently bound to the browser[/I]
[I] NetBT_Tcpip_{BA408A51-ABAA-4413-8D49-BA81B877126B}[/I]
[I] The browser is bound to 1 NetBt transport.[/I]
[I]DC discovery test. . . . . . . . . : Passed[/I]
[I]DC list test . . . . . . . . . . . : Passed[/I]
[I]Trust relationship test. . . . . . : Passed[/I]
[I] Secure channel for domain 'EXCHANGE' is to '\\E2K7DC1.exchange.local'.[/I]
[I]Kerberos test. . . . . . . . . . . : Passed[/I]
[I]LDAP test. . . . . . . . . . . . . : Passed[/I]
[I]Bindings test. . . . . . . . . . . : Passed[/I]
[I]WAN configuration test . . . . . . : Skipped[/I]
[I] No active remote access connections.[/I]
[I]Modem diagnostics test . . . . . . : Passed[/I]
[I]IP Security test . . . . . . . . . : Skipped[/I]
[I] Note: run "netsh ipsec dynamic show /?" for more detailed information[/I]
[I]The command completed successfully[/I]

The text file should like the above output. You should get no errors. (I have errors for Default gateway because this is an isolated test system)
If you get any errors then investigate them. You could post a question to the forums at [url=http://www.mmmug.co.uk/forum]Microsoft Messaging and Mobility User Group UK - Categories - Microsoft Messaging & Mobility User Group Forum[/url]
So long as you have no errors move back to the deployment tools and check the 5th box.
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image038.jpg[/IMG]
The next step is to run Forest prep. This must be run by a user with Schema administrator permissions. Forest Prep will extend the AD Schema with the new classes and attributes that Exchange 2003 requires to operate.
To proceed enter the path to the install CD in the box provided and click "Run ForestPrep now"
[B]WARNING: This operation is not undoable. Only do this if you are certain you want to proceed. I suggest testing in a lab environment before going into production. If you are unsure post a question in the Forums. [/B][URL="http://www.mmmug.co.uk/forum"][B]http://www.mmmug.co.uk/forum[/B][/URL]
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image040.jpg[/IMG]

If prompted about an incompatibility then select the checkbox to ignore the warning in the future and click “Continue”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image042.jpg[/IMG]
The Warning occurs because Exchange 2003 RTM needs upgrading to SP2 which we will install later.
Once the install opens click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image044.jpg[/IMG]
Agree to the license and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image046.jpg[/IMG]

Note that only ForestPrep will be performed and that files will go in the default location C:\Program Files\Exchsrvr (this can be changed if required to place files on an Application drive)
Click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image048.jpg[/IMG]
Select the account to be the first Exchange Full Administrator. The default is the account you are logged in as. If you are only logging in as a special schema admin account then you should select an account that will be used to admin Exchange. I will leave the default in place of Administrator.
Click “Next”
[B]SCREENSHOT of ACCOUNT DETAILS MISSING[/B]
ForestPrep is a fairly slow process that could take around 30mins on a slow network. You will see several screens like the one below
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image050.jpg[/IMG]
Once the process is complete click Finish
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image052.jpg[/IMG]

Next move back to the deployment tools and check the box on the 6th step

[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image054.jpg[/IMG]
Now move onto the Domain Prep. This will need to be performed in the root domain and any others which will hold Exchange mailboxes. Personally it is simplest to run it in all domains in the forest.
In a simple single domain forest proceed as follows:
Enter the path to the Install files where requested and click “Run DomainPrep now”.
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image056.jpg[/IMG]
On the welcome page click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image057.jpg[/IMG]

Accept the licence and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image059.jpg[/IMG]
Again note that only DomainPrep will be carried out and that you can change the file location if you want (Only change it if you changed the location for ForestPrep too)
Click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image061.jpg[/IMG]
Early in the process you will likely be warned that your domain is insecure for mail-enabled groups with hidden DL membership. Anyone in the Pre-Windows 2000 Compatible Access group can view this membership. So long as you are not using the group for a valid reason remove the default membership of Authenticated users to remove the problem.
Click "OK"
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image063.jpg[/IMG]
The DomainPrep is quick and shows the screen below whilst running

[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image065.jpg[/IMG]
Once complete click Finish
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image066.jpg[/IMG]
Move back to the deployment tools and check the box of the 7th step.
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image068.jpg[/IMG]

You are now ready to install Exchange.
Move onto step 8. Again enter the path to the install files and click “Run Setup Now”
On the welcome page click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image069.jpg[/IMG]
Accept the licence and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image070.jpg[/IMG]

This time check the install options carefully. You can choose which components to install. Generally the defaults are fine and that is what we shall stick with. Note also, that you can change the file location. Again you should do this if you changed the location for forest and domain prep.
Once you are happy with your selections, click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image072.jpg[/IMG]
As there is no Exchange org setup currently select to create one and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image074.jpg[/IMG]
Name the org and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image076.jpg[/IMG]

Agree to the licence and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image078.jpg[/IMG]
Verify your choices and click “Next”
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image080.jpg[/IMG]
The installation will progress
[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image082.jpg[/IMG]
When complete click Finish

[IMG]http://www.mmmug.co.uk/images/stories/Exchange-2003-Setup-Guide/image083.jpg[/IMG]
Now return to the deployment tools and check the box next to step 8.
Click “Next” on the deployment tools bottom right hand corner
The next page runs through the steps again for other Exchange servers.
For now we will not install another server so again click “Next” on the deployment tools bottom right hand corner.
Read through the post installation steps. We will cover the important items from here, like SMTP Filtering, Memory optimisation and Connecting to the Internet later on.
Congratulations you have just installed Exchange
[/LEFT]

[LEFT][CODE]http://www.mmmug.co.uk/articles/installing-exchange-2003-sp2-and-current-patches[/CODE]


After installing Exchange 2003, the next step is to patch it to the latest version. The biggest patch is SP2. Download this from the MS Downloads site and install as follows.

Double click E3SP2ENG.EXE

Choose a location to Extract the files and click OK

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image002.jpg[/IMG]

The files will begin extracting

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image004.jpg[/IMG]

Once complete click OK

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image006.jpg[/IMG]

Next locate the extracted files and run \E3SP2ENG\setup\i386\update.exe

On the first setup page click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image008.jpg[/IMG]

Accept the license and click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image010.jpg[/IMG]

See how update is selected for all the installed components. Note you can change the install location if required (for example if you changed it during the Exchange install).

Once you are happy with the selections click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image012.jpg[/IMG]

Verify the setting and click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image014.jpg[/IMG]

Installation will begin and will likely take several minutes (approx 20)

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image016.jpg[/IMG]

When complete click Finish

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image018.jpg[/IMG]


You have now completed SP2 install and notice, that a reboot is not required!

The next step is to install any post SP2 patches. At time of writing (30/12/2006) this means the following:

[url=http://www.microsoft.com/downloads/details.aspx?FamilyID=41275dec-4c01-4c41-aa64-c9dbe5ea3f7e&DisplayLang=en]Download details: Update for Exchange Server 2003 SP2 (KB 924334)[/url]

[url=http://www.microsoft.com/downloads/details.aspx?FamilyID=82ae4397-0982-4585-84c1-dc1af6944a0f&DisplayLang=en]Download details: Security Update for Exchange Server 2003 SP2 (KB916803)[/url]

[url=http://www.microsoft.com/downloads/details.aspx?FamilyID=c777bc9f-52b7-4f17-96c7-daf3b9987d70&DisplayLang=en]Download details: Security Update for Exchange Server 2003 SP2 (KB912442)[/url]

[url=http://www.microsoft.com/downloads/details.aspx?FamilyID=c16aea4a-ed33-4cd9-a7c3-8b5df5471b7a&DisplayLang=en]Download details: Update for daylight saving time changes in 2007 for Exchange 2003 Service Pack 2 (KB 926666)[/url]

The first one is an update to ensure OWA works with IE7. The second and third are security patches and the fourth sets up daylight saving time changes for 2007.

Download the patches from the above locations and then install as follows:

Double click the exe file to launch the patch installer

Click “Next” at the first screen

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image020.jpg[/IMG]

Agree to the license and click “Next”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image022.jpg[/IMG]

The patch will install

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image024.jpg[/IMG]

If any services need stopping you will be prompted, click “Continue”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image026.jpg[/IMG]

The services will be stopped and the install will continue

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image028.jpg[/IMG]

Once the install is complete click “Finish”

[IMG]http://www.mmmug.co.uk/images/stories/Installing-Exchange-2003-SP2-Current-Patches/image030.jpg[/IMG]

Repeat the process for the other patches
[/LEFT]

[LEFT][CODE]http://www.servolutions.com/support/config_exchange_2003.htm[/CODE]
Configuring your new Exchange 2003 server for internet email with POPcon for downloading the email from POP3 mailboxes isn't hard if you just do it step by step as shown in this configuration sample. In this guide we will step through a sample installation of Exchange 2003 for a company we will call "Mycompany". Mycompany consequently owns the internet domain name "mycompany.com".
Actually it only takes these five steps:

[LIST=1][*]Adding your internet domain name to the recipient policies[*]Configuring the SMTP server for inbound email[*]Adding a SMTP Connector for outbound emails[*]Configuring the email addresses of your users[*]Installing and configuring POPcon or POPcon PRO[/LIST]
And this is how to configure the Exchange Server to accept email for mycompany.com and work with POPcon:

First install the software from CD. You may have to go back to the "Add/remove Software" utility in the control panel to add NNTP support if you did not do so during initial setup of your windows installation. Then open the Exchange System Manager and configure the new Exchange installation.

[B]1. Adding your internet domain name to the recipient policies[/B]

Open the Exchange System-Manager. It should look like this:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-1.png[/IMG][/CENTER]

One of the problems most often encountered when configuring an Exchange 2003 Server system is the fact that often the internet domain nane you want to receive email for ("mycompany.com") does not match your standard active directory domain name (i.e. "servername.mycompany.com"). The Exchange 2003 Server component handling incomming emails - the SMTP server - does not accept emails for other domains than the ones entered in the "recipient policies", even if you entered the correct email addresses ("user@mycompany.com") in the active directory.
To make Exchange accept email for additional domains like your internet domain you need to add the domain names to the default recipient policy like this:

On the main tree panel of the exchange system manager expand the tree "Recipients" and then click on "Recipient Policies". The policies will be shown on the right panel. Normally only the "Default Policy" will be there:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-2.png[/IMG][/CENTER]



Open the properties of the "Default Policy" by double-clicking it:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-3.png[/IMG][/CENTER]



In the Default Policy Properties please choose the tab "E-Mail Addresses". There you will find a list of domains supported by your exchange server. Usually only your internal active directory server domain will be listed here:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-4.png[/IMG][/CENTER]


Like you can see, after installing our Exchange Server from scratch only our AD domain "Christensen.local" was listed as accepted SMTP address. But emails from the internet will be comming in addressed to "@mycompany.com" and not Christensen.local!

Choose "New..." here to add another accepted inbound domain. Since emails on the internet are sent via the SMTP protocol we want to add an "SMTP Address":
[CENTER][IMG]http://www.servolutions.com/images/e2k3-5.png[/IMG][/CENTER]


Now enter the domain name you want to receive email for. Please add a leading "@" to the domain name. This is what we entered to support emails addressed to @mycompany.com:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-6.png[/IMG][/CENTER]



This is how the Default Policy Properties look like after entering the additional SMTP domain:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-7.png[/IMG][/CENTER]



Enable the newly created entry with a check mark next to it:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-9.png[/IMG][/CENTER]


When you OK the above dialog, Exchange will ask you with the next dialog box if you want to add the new address to all new users. Usually you do want exactly that to save some typing later.
[CENTER][IMG]http://www.servolutions.com/images/e2k3-10.png[/IMG][/CENTER]


Please note: You may need to restart your server to activate the new domain!

[B]2. Configuring the SMTP server for inbound email[/B]

Next we will configure the SMTP-Server. This is the part of Exchange that accepts incomming emails from POPcon. No special settings are needed to work with POPcon but these are the standard settings in any case:

You will find the settings for the SMTP server under Servers/Protocols/SMTP/Default SMTP Virtual Server. Open the properties by right-clicking on the Default SMTP Virtual Server and choosing "Properties":
[CENTER][IMG]http://www.servolutions.com/images/e2k3-11.png[/IMG][/CENTER]

The settings on tab "General" can normally be left to the defaults.
[CENTER][IMG]http://www.servolutions.com/images/e2k3-12.png[/IMG][/CENTER]


On the tab "Access" you can find some configuration settings that might interfere with POPcon.
[CENTER][IMG]http://www.servolutions.com/images/e2k3-13.png[/IMG][/CENTER]




POPcon only works with a standard SMTP connection WITHOUT authentication, so allow "Anonymous access" in the "Authentication" dialog:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-14.png[/IMG][/CENTER]



Choose "Connection" to grant or refuse the right to connect to the SMTP server to individual or multiple IP Address Ranges. Please ensure the system POPcon runs on does have the right to connect granted. With this setting ALL systems will have access to your SMTP server:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-15.png[/IMG][/CENTER]



Under "Relay..." you can assign the right to relay through your SMTP-Server to some systems. This might be needed in some configuration and to be sure you should grant the system POPcon runs on relay rights. All other systems will need to authenticate before accessing the SMTP server to prevent unauthorized users using your system to relay spam:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-16.png[/IMG][/CENTER]






Under the "Messages" tab you can restrict message size and number of messages accepted for each connection. Please make sure these settings are liberal enough to allow POPcon to transmit large messages to your server.

Also, on this tab you can choose an internal additional recipient for copies of the non-delivery reports. These NDRs will be sent back to senders of mails addressed to recipients unknown in your Exchange Server and they include a copy of the original message sent. You can use these postmaster copies of the NDRs to manually forward emails sent to mistyped recipients to the correct users.
[CENTER][IMG]http://www.servolutions.com/images/e2k3-17.png[/IMG][/CENTER]






Under tab "Delivery" some more configuration settings for outgoing emails can be found:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-18.png[/IMG][/CENTER]





[B]3. Adding the SMTP Connector for outbound emails[/B]

Now we need to add an SMTP-Connector (vs. SMTP Server) to handle outgoing email to the Internet.

Right-click "Connectors" in the Exchange System Manager and choose "New", "SMTP-Connector" to start adding the new connector and name it appropriately (like "SMTP-Out" in our case):
[CENTER][IMG]http://www.servolutions.com/images/e2k3-20.png[/IMG][/CENTER]



On the "General" tab you can now choose wether Exchange will send outgoing emails directly to the recipients system ("Use DNS...") or if all emails should be relayes through a SMTP relay server ("smart host").
The first option, DNS, is more direct but can sometimes cause problems when you use a dialup internet connection because some recipient systems will not accept emails that are coming from you ISP's dialup IP range while pretending to come from your real internet domain. Sending via your ISP's smart host / smtp relay server is the better option in this case. We chose our ISPs smtp relay server here.
[CENTER][IMG]http://www.servolutions.com/images/e2k3-21.png[/IMG][/CENTER]



Also, on this tab you need to add the "local bridgehead" server (as shown above)
On the tab "Address Space" we need to add a wildcard address space for SMTP. We want to allow emails to any domain, so we use the wildcard "*" here:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-22.png[/IMG][/CENTER]

Side note about the "Cost" entry: If you want to send emails to some domains via a different route you can create multiple SMTP connectors and set the "Cost" entry of this wildcard connector to a higher value while setting the cost entry of the special domain route to a lower cost but with only the special domain allowed on this page. This is especially useful if you generally want to send via DNS and only route to some systems that won't accept your email via some relay server.

If your ISP's SMTP server requires authentication (and almost all of them do today) you can set the username and password on the "Advanced" tab of the SMTP connector. Select "Outbound Security":
[CENTER][IMG]http://www.servolutions.com/images/e2k3-23.png[/IMG][/CENTER]



Select "Basic authentication" and chose "Modify" to enter the username and password:
[CENTER][IMG]http://www.servolutions.com/images/e2k3-24.png[/IMG][/CENTER]

[CENTER][IMG]http://www.servolutions.com/images/e2k3-25.png[/IMG][/CENTER]





And that's alreay it - Your Exchange is now configured to send email to the internet and receive an SMTP email feed like it will come from POPcon or a direct internet connection. All you should do now is configure your users' email addresses in the Active directory.




[B]4. Configuring your user's email addresses in the Active Directory[/B]

You can set one or multiple email addresses for each user to receive email at. We will step through the neccessary actions when creating a new user called John Galt.
First open the active directory and right-click the "Users" item to select "New", "User":
[IMG]http://www.servolutions.com/images/nu001.gif[/IMG]
The resulting dialog will allow you to create a new AD user to log into your server and creates an Exchange mailbox all in one wizard pass:

[IMG]http://www.servolutions.com/images/nu002.gif[/IMG]
Next... [IMG]http://www.servolutions.com/images/nu003.gif[/IMG]
Next... [IMG]http://www.servolutions.com/images/nu004.gif[/IMG]
Now the wizard continues into the Exchange Server realm and lets us create a new exchange mailbox
We just accepted the default alias here. Next...
[IMG]http://www.servolutions.com/images/nu005.gif[/IMG]
Ok, fine - but wait: What about our desired email address? [EMAIL="john@servolutions.com"]john@servolutions.com[/EMAIL]? We need to add this mail address manually. We are back at the AD configuration console and select the properties of our new user "John Galt" by right-clicking on the name:
[IMG]http://www.servolutions.com/images/nu006.gif[/IMG]

Lot's of tabs on this resulting dialog:
[IMG]http://www.servolutions.com/images/nu007.gif[/IMG]
We go to the "E-mail Addresses" tab:
[IMG]http://www.servolutions.com/images/nu008.gif[/IMG] And surprise: [EMAIL="john@servolutions.com"]john@servolutions.com[/EMAIL] is already there, but in suspiciously non-bold print. Actually, Exchange automatically entered this additional email address because we choose so during the editing of the default recipient policies. But we want this address to be the primary address meaning all email sent by John will get this address as the "senders" and "reply" addresses in the mail headers. So we click on "Set As Primary" and are done:
[IMG]http://www.servolutions.com/images/nu009.gif[/IMG]
We could also add more email addresses like [EMAIL="info@servolutions.com"]info@servolutions.com[/EMAIL] or [EMAIL="sales@servolutions.com"]sales@servolutions.com[/EMAIL] but only one of these addresses can be the primary address that will be the default senders' address in all emails sent out by john.
And that's really it - just step through you other user's AD entries and set the appropriate primary and additional email addresses.




[B]5. Installing and configuring POPcon or POPcon PRO[/B]

After going through the above 4 steps your Exchange is configured to send out email but it still can't pull down email from POP3 or IMAP mailboxes on your provider server. For this you need to install and configure POPcon.
Configuring POPcon is quite straightforward. You need to follow these steps:[INDENT] a) Configure a Postmaster email address on the GENERAL configuration tab.
b) Add one or more POP3 mailboxes on the POP3/IMAP tab.
c) Configure the Exchange server name on the EXCHANGE configuration tab.[/INDENT]Download and run the self-extracting installer of [URL="http://www.servolutions.com/popcon/download.htm"]POPcon[/URL] or [URL="http://www.servolutions.com/popconpro/download.htm"]POPcon PRO[/URL] and follow the instructions during the installation. It will install the POPcon Administrator program and the POPcon service that runs in the background on your system.
Run POPcon Adminstrator from Start > Programs > POPcon
[URL="http://www.servolutions.com/images/popcon1.gif"][IMG]http://www.servolutions.com/images/popcon1small.gif[/IMG][/URL]
[CENTER]POPcon Screenshot[/CENTER]

Click on "Configure" to open up the POPcon configuration screen.

[B]a) Configure a Postmaster email address on the GENERAL configuration tab.[/B]
[INDENT] [IMG]http://www.servolutions.com/images/popcongeneral.gif[/IMG] On this first configuration page you only need to enter the email address of your Postmaster or Administrator user. The Postmaster will receive all emails without a valid recipient as well as general POPcon status notifications. It is very important to define a real email address from inside your exchange server here because mails can be lost irretrievably if POPcon forwards some mail with no recipient information to the postmaster and that account does not exist in your exchange server.
You can leave the log file options to their default settings for now.
[/INDENT]Next go to the POP3/IMAP tab to configure the POP3 or IMAP mailbox accoutns you want POPcon to download email from.
[B]b) Add one or more POP3 mailboxes on the POP3/IMAP tab.[/B]
[INDENT] [IMG]http://www.servolutions.com/images/popconpop3.gif[/IMG] POPcon PRO collects mail from as many POP3 accounts you like. Just click on Add to add another POP3 host or account to the list of Polled POP3 Hosts. For each server or account you need to fill in the POP3 server settings as shown below.
If you are using catch-all style mailboxes (mailboxes that receive email for a whole domain, regardless of the recipient part before the "@") POPcon needs to filter recipients from incoming mail so only the recipients at your own internet domain are accepted. Please add the domain you consider your own in the "Accepted Recipient Domains" box. This is the same domain you configured earlier in the Exchange Default Policy.

[B]Individual account settings[/B]

[CENTER][IMG]http://www.servolutions.com/images/popconpop3s.gif[/IMG][/CENTER]
This dialog lets you input the specifics about a POP3 or an IMAP server you want to have polled by POPcon PRO.
This is the information POPcon PRO needs to know about each server:
[INDENT] [B]Server type:[/B]

Here you can select on the four supported server types:
[INDENT] [B]POP3:[/B] Default. POP3 servers are by far the most common mail server types on the internet.
[B]POP3-SSL:[/B] Some POP3 Servers need SSL encryption enabled for the connection in order to protect passwords and sensitive information. Choose this type to have a SSL-encrypted connection to a POP3 server.
[B]IMAP:[/B] IMAP Servers are also quite common and theoretically allow the client to manipulate email folders and move email between folders online. In our case the protocol is used to download email from the INBOX of the IMAP server to your exchange server.
[B]IMAP-SSL:[/B] Supports SSL connections to IMAP servers for added protection.[/INDENT]
[B]Access:[/B]

Configure the server name, account name and password to connect to the mail server here.
[INDENT] [B]Servername:[/B] The name the server you want to have polled. You can also enter the IP address directly.
[B]Username:[/B] The username needed to log into your POP3 or IMAP mail server.
[B]Password:[/B] The password needed to log into your mail server.
[B]IP portnumber:[/B] Almost always the TCP/IP port for POP3 mail is 110. Under some circumstances, internet routers or firewalls change the port number. Please ask your network administrator or internet provider. The standard port for POP3-SSL is 995, for IMAP it is 143 and for IMAP-SSL this should be set to 993.
[B]Timeout:[/B] Leave this to the default value.[/INDENT]Please ask your POP3 mailbox hosting provider if you do not have the above information.

[B]Type of mailbox / distribution:[/B]

POPcon PRO supports both catch-all and single user mailboxes
[INDENT] [B]Catch-all mailbox ("*@domainname.com"):[/B] For this type of mailbox, POPcon PRO will distribute the email retrieved from this server according to what it finds in the TO:, CC:, BCC: and other header-fields of the mail. If you choose this option, don’t forget to add your internet domain name(s) to the "Accepted Recipient Domains" box. on the POP3/IMAP configuration dialog
[B]Single user mailbox ("user@domainname.com"):[/B] This type of mailbox receives email for only one specific Exchange mailbox. You need to specify the receiver of the email here. POPcon PRO will then direct all mail retrieved from this server to the recipient email address given here.[/INDENT]
[B]Delete / keep email on the server:[/B]

This block allows you to configure POPcon PRO to either delete email after downloading or keep it on your POP3 or IMAP server for a specified amount of time or indefinitely.
[INDENT] [B]Delete downloaded email:[/B] This is the default setting – POPcon PRO will delete the Email on your POP3 or IMAP server after successfully downloading it.
[B]Leave a copy of downloaded email (indefinitely):[/B] This option will cause POPcon PRO to leave a copy of the email on the server. Only use this option during testing or when you are sure the mail will be deleted eventually, i.e. by another system periodically downloading an deleting email.
[B]Leave a copy of downloaded email for n number of days:[/B] Causes POPcon PRO to leave a copy of the email on the POP3/IMAP server for the specified number of days before deleting it. You can use this option to allow access to a single POP3 or IMAP mailbox by two different systems.[/INDENT][/INDENT][/INDENT][B]c) Configure the Exchange server name on the EXCHANGE configuration tab.[/B]
[INDENT] [IMG]http://www.servolutions.com/images/popconsmtp.gif[/IMG]
On this configuration screen you can specify the Exchange™-(SMTP) Server you want the mail to be directed to. Normally this will be the computer name of your Exchange™ server (like "MYSERVER").
You can leave all other settings default[/INDENT]These three steps to configure POPcon will provide you with a working set-up. Test it out by confirming the new configuration with OK and then use the "Trigger mail retrieval" button on the POPcon Administrator main screen to start the first mail download. You can follow what is happening in the scrolling log display on that screen. Watch out for any error messages there. There is also a POPcon log file (c:\program files\POPcon\POPconSrv.log – open with notepad) that you can view at your leisure
[/LEFT]