Installation of Exchange 2007 SP1 on Windows Server 2008 Part 2 of 2

Category: Software

Installation of Exchange 2007 SP1 on Windows Server 2008 [Part 2 of 2]

Read Part One of this article.

Having successfully completed the installation of prerequisites, it is time to install Exchange. Start setup and click “Install Microsoft Exchange Server 2007 SP1”.

Need help with Windows Dedicated Hosting? Try Server Intellect. I'm a happy customer!

[Click to enlarge]
Figure 1: Starting Setup of Exchange Server 2007 SP1

Now follow the wizard down the install steps as show below

[Click to enlarge]
Figure 2: The SP1 Setup introduction screen

I just signed up at Server Intellect and couldn't be more pleased with my Windows Server! Check it out and see for yourself.

Figure 3: Accept the license agreement


Figure 4: Opting into the Microsoft Error Reporting scheme

Exchange 2007 Roles

Once all the preparatory steps are completed, we are now ready for the main Exchange 2007 installation.  At this point, the server roles should be chosen, and move on to the next steps in the installation. There are several different roles available, but for this installation, we will be using Hub Transport, client access, and mailbox server roles. I will briefly go over the different roles.

Server Intellect offers Windows Hosting Dedicated Servers at affordable prices. I'm very pleased!

Additional Requirements for the Various Roles

Figure 5

Mailbox Server
This back-end server needs IIS and WWW.

Client Access Server (CAS)
The CAS server also requires ASP.Net and the WWW service.  Remember that this should be the first role to implement for Exchange Server 2007.

Unified Messaging Server
Needs speechify, setup will automatically install as needed.  This Unified Messaging role provides integration for email, calendars, voicemail and if you still use it, fax.

Bridgehead Server
No special requirements

Edge Transport Server
The Edge Transport Server (Formerly Gateway Server) must be in it's own workgroup will not operate in a Domain for the obvious reason of security. 
The role of Edge Transport server is to accept messages from the internet that are addressed to your Exchange 2007 organization.  After these emails are processed, the Edge server routes them to the Hub Transport servers inside your organization.

Try Server Intellect for Windows Server Hosting. Quality and Quantity!

Client Requirements
Mapi clients need Outlook 2002 or later.  Outlook 2007 is by far the best client.  Outlook 2007 and Exchange 2007 are made for one another.  OWA (Outlook Web Access) is a great alternative all clients need is a browser.
At this point we are ready to start the install. Remember, if you need to install other features, you need to select custom install. While you will be able to go back and re-run setup to install other features, it will be more time consuming to do it that way.


[Click to enlarge]
Figure 6: Selecting Typical installation


[Click to enlarge]
Figure 7: Setting the new Exchange Organisation name


[Click to enlarge]
Figure 8: Opting not to create public folders

Server Intellect assists companies of all sizes with their hosting needs by offering fully configured server solutions coupled with proactive server management services. Server Intellect specializes in providing complete internet-ready server solutions backed by their expert 24/365 proactive support team.

[Click to enlarge]
Figure 9: Exchange Readiness checks in progress

Finalize Deployment Tab

Once the Exchange setup wizard finishes its tasks, there is yet more work for you.  Seek out the Finalize Deployment tab, and also the End-to-End Scenarios tab.
Launch the Exchange Management Console, select Microsoft Exchange in the left tree, and now you should see the 'Finalize Deployment tab'.   Most of these configuration tasks are optional, and will vary depending on which Server Role(s) you added.  However, I bet that there will be at least two items that you had forgotten or not previously considered changing.
While you have the Management Console open, take the chance to investigate the End-to-End Scenarios tab.  As with the previous tab, these tasks are optional and vary depending on which Exchange 2007 features you added.

Verification Check List

  • Check the installation log at: C: \ExchangeSetupLogs.  Also check the system and application event logs.
  • Launch the Exchange Management Console and check your newly installed Exchange server.  If this is a brand new installation check that the Organization Name is the same as you planned.
  • Create a mail-enabled user and then connect to that mailbox using Outlook Web Access, or an Outlook client if you prefer.
  • Once you create a Hub Server see if you can receive email from another mail-enabled account.
  • For CAS servers make sure you check with OWA.
  • In the case of the Edge Server send email to an external internet account.
  • Check that services to see that the dozen or so Microsoft Exchange Services are running.  Note they begin with Microsoft and not Exchange. 
  • If anything seems wrong check the Exchange files underneath: C: \Program Files\Microsoft\Exchange Server. 
  • When there is no quick resolution to the problem, seek the ExBPA (Exchange Server Best Practices Analyzer), then run the Exchange 2007 Readiness check.  The best way is to launch the Exchange Management Console and open the Toolbox and there you will find the Exchange Server Best Practices Analyser.

Troubleshooting Exchange 2007 SP1 Installation Problems

If you're looking for a really good web host, try Server Intellect - we found the setup procedure and control panel, very easy to adapt to and their IT team is awesome!

Problem: Public Folder Replicas
Solution: Temporarily disable the OAB, then delete the replicas or move them to another Exchange server. This task is ideal for PowerShell:
The cmdlets are

get-PublicFolderStatistics   Check the situation
remove-PublicFolder  Dangerous if you don't know what you are doing, effective if you do.
Get-PublicFolderStatistics -Server | fl
Get-PublicFolder -Server "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server -Recurse -ErrorAction:SilentlyContinue
Get-PublicFolder -Server "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server -Recurse -ErrorAction:SilentlyContinue

Problem: Existing object in Active Directory
[ERROR] Active Directory operation failed on The object 'CN=Default Global Address List,CN=All Global Address List
Solution: Launch ADSI Edit and investigate the  Address Lists Container, in particular, edit the purportedSeach attribute.

Example: Unable to connect to 'YourDC' DC No Exchange Server with identity 'YourServer' was found
Solution: Check with Netdiag and Dcdiag.  With luck it could just be a latency, or initial connection problem, which mysteriously disappears when you try to repeat the Exchange 2007 server install.

Problem: Disabled IPv6
Problem installation failed.  Reason, IPv6 is disabled.  Solution, give the NIC IPv6 address. 

 What we have learned?
We have now prepared our environment for Exchange and completed the installation process. We have described some of the problems that you may encounter along the way and hopefully given you a solution to solve that problem. This completes our article on Installing Exchange, I hope you enjoyed it.

We used over 10 web hosting companies before we found Server Intellect. Their dedicated servers and add-ons were setup swiftly, in less than 24 hours. We were able to confirm our order over the phone. They respond to our inquiries within an hour. Server Intellect's customer support and assistance are the best we've ever experienced.

There are no attachments associated with this article.