Exchange Server 2007 - Install
How to Install Exchange 2007 SP1 Server
This page explains how to install an Exchange 2007 server. My first impression was that the whole look and feel was very different from previous Exchange installs. I have to say the 2007 installation process felt easier; whereas Exchange 2003 left me with a feeling of bemusement at its clunky controls, Exchange 2007 combined power with simplicity. What particularly impressed me was the new Exchange Roles menu.
Topics for - How to Install Exchange 2007 Server
Introduction to Installing Exchange Server 2007
All installations reward planning; in the case of Exchange 2007, decide on the underlying operating system and then decide which Exchange roles to install. What makes setting up Exchange 2007 such a joy is the way the wizard helps you check the pre-requisites. For example, it prompts you to raise the domain level, and shows you the way to install .Net Framework 2.0
The trickiest feature of Exchange 2007 is not the installation, but the new method of creating Mailboxes from the Exchange manager. In Exchange 2007, creating mailboxes (mailbox enabled users) with Active Directory Users and Computers is fool's gold. Any objects you manage to create have no SMTP address and don't work. You simply must use the Exchange Management Console to create mailboxes.
Before you install Exchange Server 2007, you need a 64-bit operating system; I choose the Windows Server 2003 R2 rather than the minimum requirement of Windows Server 2003 with SP1.
An even better option would be to install Exchange Server 2007 SP1 on Windows Server 2008, but note those three letters: SP1. Just to emphasise that for Server 2008 you need the later, slipstreamed SP1 DVD (or image), and not the original RTM disk. Furthermore, you need a clean install of Windows Server 2008 on 64-bit hardware, and not an upgrade from W2K3.
It terms of tactics, Microsoft recommend that you install Exchange 2007 on member server. Exchange on a Domain Controller is not supported, and should only be used for testing where you only have one machine. If you have already prepared your domain, then jump to Key preparation steps
Here is a free tool to monitor your Exchange Server. Download and install the utility, then inspect your mail queues, monitor the Exchange server's memory, confirm there is enough disk space and check the CPU utilization.
This is the real deal - there is no catch. SolarWinds provides this fully-functioning freebie, as part of their commitment to supporting the network management community.
Creating the Active Directory domain is not strictly a part of installing Exchange, I added here below a brief description of the most important features for the sake of completeness.
Domain Functional Level
You also need to check the Forest Functional Level, particularly where you want the advanced features of Exchange 2007. Incidentally, Functional Level is my one of my 'Litmus tests' for seeing if people have sufficient Active Directory knowledge to install Exchange 2007. If someone does not know how to find and configure Function Levels, then they are likely to need help installing Exchange 2007.
System Icon - DNS Domain Configuration
As with Exchange 200x, the mail server relies on Active Directory. Therefore, I installed a Windows Server 2003 (RC2) member server then ran DCPROMO, from there I followed the wizard's prompting to create a new domain in a new forest.
DNS - Automatic addition of _SRV
I was taken aback to get an error message, however, I allowed the DCPROMO to finish, then I went to the Services and Stopped then restarted the Netlogon Service. What followed was a magic moment, restarting the Netlogon Service triggered the creation of all the DNS records under _msdcs.
The bottom line is check that DNS has the 'A' Host record for each Exchange 2007 server.
SolarWinds' Network Performance Monitor will help you discover what's happening on your network. This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.
What I like best is the way NPM suggests solutions to network problems. Its also has the ability to monitor the health of individual VMware virtual machines. If you are interested in troubleshooting, and creating network maps, then I recommend that you try NPM now.
At every stage of installing Exchange 2007, kind friendly wizards guide you through the minefield. Here is a screen shot of the wizard checking then explaining a problem with mixed mode.
Raise Domain Level
.Net Framework 2.0
MMC v 3.0
Other than this processor requirement, just use common sense and provide plenty of RAM. It's also worth spending a few minutes thought and planning on the disks sizes and partitions, particularly servers hosting the Mailbox Role. For larger organization, this would be a good time to review your SAN (Storage Area Network) needs.
Exchange 2007 has its very own SMTP server which transports messages using MAPI. Thus you no longer need to install the IIS SMTP and NNTP services. Indeed, you must not install these Windows services on servers which run Exchange 2007.
Prerequisites, you need the Exchange Server 2007 disk or image. (SP1 would be even better) Each command is prefaced by setup. You could also try setup /? to see the full list of options, for example: /mode or /role.
Setup /PrepareAD Creates the necessary global Exchange objects and universal security groups in Active Directory. Must be run by a member of the Enterprise Admins group, run this command in both the root and current domain. You may find that if you run this command as a Schema Admin (and Enterprise Admin), there is no need to run the other commands.
/PrepareLegacyExchangePermissions This command is needed if your organization contains Exchange Server 2003 or 2000 computers. It modifies the permissions assigned to the Enterprise Exchange Servers group so that the Recipient Update Service can run. Remember to logon as a member of the Enterprise Admins group.
/PrepareSchema This prepares the Active Directory schema so that it allows Exchange Server 2007 to install. You must be a member of both the Schema Admins and Enterprise Admins. You need to run this command in the root domain, or the domain which holds the Schema Master role.
/PrepareDomain /PrepareDomain domainname This creates a new global group in the Microsoft Exchange System Objects container called Exchange. You must be a member of both the Enterprise Admins and the Domain Admins group.
One more point, if you are using a Windows Server 2008 computer, first install the AD DS management tools.
Import users from a spreadsheet, complete with their mailbox. Just provide a list of the users with the fields in the top row, and save as .csv file. Then launch this FREE utility, match your Exchange fields with AD's attributes, click and import the users. Optionally, you can provide the name of the OU where the new mailboxes will be born.
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.
Once I completed all the preparatory steps, I was ready for the main Exchange 2007 installation. All that remained was to decide upon the role or roles for your exchange server. As expected, you can always return to this menu to add more roles.
Additional Requirements for the Various Roles
Client Access Server (CAS)
Unified Messaging Server
Edge Transport Server
The role of Edge Transport server is to accept messages from the internet that come 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.
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 -Server <YourExchangeServer> | fl
Get-PublicFolder -Server <server containing the public folder database> "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server <server containing the public folder database> -Recurse -ErrorAction:SilentlyContinue
Get-PublicFolder -Server <server containing the public folder database> "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server <server containing the public folder database> -Recurse -ErrorAction:SilentlyContinue
Problem: Email Address Policy
Solution: Check the Exchangesetup.log for this message:
[ERROR]The Exchange server Address list failed to respond- error 0x8004010f
Next launch the Event Viewer and check the Application log (not the system log) for Event ID: 8325. If you examine the details it will tell you precise Filter Rule that is preventing installation.
This problem occurs when you add the Mailbox role to Exchange 2007. The root cause was an incorrect filter was created in Exchange 2003.
Problem: Existing object in Active Directory
[ERROR] Active Directory operation failed on DC.YourDom.com 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: Windows 2000 Domain Controllers
Solution: Upgrade to Windows Server 2003. Or install a Windows Server 2003 in that child domain or site.
Problem: ADC (Active Directory Connectors)
Remove (uninstall) the ADC on the Windows 2003 servers before continuing with Exchange 2007 server install.
Problem: CAS server setup fails with a Watson MultiValuedProperty error
Solution: Launch ADSI Edit check Default Offline Address List. In particular, set the value of the MsExchVersion attribute to 4535486012416
Problem: Disabled IPv6
Windows Server 2008. Problem installation failed. Reason, I had foolishly disabled IPv6. Solution, give the NIC and IPv6 address. Extra information, I had checked the install Hub Transport role, whether this was relevant, I have not had time to research.
Guy Recommends SolarWinds' Free Network Monitor
Thus utility makes it easy to check the health of a router or firewall. Check the real-time performance, and availability statistics, for any device on your network. Get started with an extensive collection of "out-of-the-box" monitors for popular network devices. Give Network Monitor a whirl - it's free. Download your free Network Device Monitor
If you need more comprehensive
network analysis software:
Whenever I produce my recommendations for Exchange, clients accuse me of not belonging to the real-world. Nevertheless, I will persist in pushing my simple strategy.
What you need for Exchange Server 2007 SP1 is:
I realize that it could be an immense capital cost to replace Outlook 2003, Windows Server 2003 and probably XP. While all manner of other combinations are supported by Microsoft, in the sense that they SHOULD work, in practice they never actually deliver what you hoped. Thus you are condemned to years of frustrating cycles of playing 'fix it'.
Suppose you start with Exchange Server 2007 housed on Windows Server 2003, on the client side you have Outlook 2003 and XP. My estimate is that you will have 4 months of chasing compatibility problems and trying various Microsoft Kb work-arounds. Then you get the money to upgrade XP to Vista, this will spark another round of stuff which needs fixing. Then a year later you belated try to upgrade to Windows Server 2008 only to run into more problems. To cap it all, by this time the original team have left your company and there will be incomplete documentation of what they did.
It all depends how you cost time and frustration, but after 9 months of fire-fighting, most managers and many of the techies would pay a small fortune to have implemented my suggestion of a matched system, Exchange 2007, Outlook 2007, with Vista and Windows Server 2008.
There is an insidious side to running older computing system which managers wont talk about. The best 'teams' of employees are drawn to companies with the best kit. Thus your organization will attract good people if you follow my 'expensive' solution. Even worse, if your network is plagued by computer problems then it is always the most talented people who jump ship first.
The secret of avoiding a lot of re-work is planning. Begin by deciding the domain that your Exchange 2007 organization will join. Once you have installed the operating system, check the specific Exchange prerequisites, finally choose the role or roles for each Exchange 2007 server. Bear in mind that the wizards are helpful and friendly, when you are new to Exchange 2007 use them at every opportunity. Once you become experienced then you can automate many of the tasks with PowerShell cmdlet scripts.
If you like this page then please share it with your friends
See more Microsoft Exchange Server 2007 topics: