I have been blogging a lot about SharePoint lately and thought I’d post a 3 part series about my other favourite topic of interest, Exchange. Exchange is one of those technologies that once you spend the time designing, beta testing, dev testing and finally implementing in your production environment, there’s not too much development later in its lifecycle, so when Exchange 2010 was released as a public beta I couldn’t wait to get my hands on it and set it up in my dev environment. I implemented my first Exchange server back in the days of 5.5 and progressively kept up to date through the versions, 2000, 2003 and 2007. I must admit the learning curve between 5.5 and 2000 was steep and again between 2003 and 2007, but it’s still one of those technologies that continues to excite me!
So here it is, I have documented below a step by step installation guide with links to TechNet articles for reference. This will be a 3 part series with part 1 focusing on meeting the prerequisites for an Exchange 2010 Beta installation and going through the process in its entirety step by step. Part 2 will focus on some basic Exchange configuration to get your environment up and running and we’ll finish off with investigating and discussing some of the latest features on offer.
My dev environment for simplicity consists of a single Virtual Machine running Windows 2008 Enterprise Server with Active Directory and DNS configured in a single forest/domain setup. This will also be the same server that we will install Exchange 2010 Beta on, definitely not best practice but sufficient for the purpose of this article.
History tells us that since the introduction of Active Directory we have always been required to prepare Active Directory and update the necessary schema. Exchange 2010 Beta is no different and TechNet has a great article on that which you can access here explaining the process. http://technet.microsoft.com/en-us/library/bb125224(EXCHG.140).aspx
Word of warning, Microsoft highly advises against installing Exchange 2010 in an existing production domain being still in Beta and is not supported with this build, purely due to the fact that schema changes will be made to Active Directory and may be destructive and irreversible.
The first command you need to run is setup /p or setup /PrepareAD
Second command is setup /pad or setup /PrepareAllDomains (I only had one domain in this forest)
Now that we have Active Directory at the right schema level, we can now begin with the Exchange 2010 installation. Run the downloaded executable and extract the installation files and then run setup.exe to launch the wizard.
Run Step 1. Install .NET Framework 3.5. This will open a link in Internet Explorer (or your preferred default browser) to the Microsoft Download Center.
Run Step 2. Install Windows Remote Management 2.0. Again, this will open a link in Internet Explorer, this time directing you to the Microsoft Connect Site. This is still in Community Technology Preview 3 (CTP3) and uses the Microsoft File Transfer Manager to download the file so please ensure you have Active X enabled. This installation may request a reboot once complete.
Run Step 3. Install Windows PowerShell v2. Again, this link will direct you to the Microsoft Download Center.
We are now ready to install Exchange and you will notice the first 3 steps are now dimmed, i.e. they have successfully been installed.
You will then receive the Language Pack confirmation screen advising that all subsequent screens will be in English. Click Next.
Accept the License Agreement screen, click Next
The Error Reporting Screen then appears. Let’s help the guys at Microsoft and click yes.
The installation type screen appears and because I want to install the Unified Messaging Role as well I will select the custom Exchange Server Installation, remember you cannot install the Edge Transport Role on the same box as the other Exchange Roles, this restriction has not changed since Exchange 2007.
Select your roles. You will notice as soon as you select one of the top roles that the Edge Transport Server role becomes dimmed and vice versa.
Specify the Exchange Organization name.
Select your client settings option. In my case I don’t use Public Folders (that’s why we have SharePoint right?) and don’t run earlier Outlook or MAC OS X Entourage clients.
The next screen is a first for me, I have not seen this before with any Microsoft installation wizard specifically the part where you can choose the industry that best represents your organization. Select your industry and again, let’s help the guys at Microsoft and click Join the Exchange Customer Experience Improvement Program.
Like Exchange 2007, the wizard then performs a readiness check for the different roles that you have selected.
In my instance, I failed miserably, so I followed the instructions outlined in order to get myself up to scratch and downloaded the necessary missing components and hot fixes!
They were notably;
- IIS via Server Manager (always seem to miss that one)
- 2007 Office System Converter Microsoft Filter Pack (This download will install and register iFilters with the Windows Indexing Service)
- Windows Media Encoder Desktop Experience Component (Unified Messaging Role)
Later I found the complete pre-requisites from the Microsoft TechNet Site READ THIS FIRST!http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx
Once you have ensured all prerequisites are met, restart your server and re-run the installation. Hopefully this time round your readiness checks succeeds for all items. Click Next.
The Installation will now continue, so take a seat back, make a coffee as this may take a while, in my case approximately 20 minutes.
The new Exchange Management Console launches upon completion and you will notice that there are similarities with Exchange 2007, notably the Nodes on the left hand side haven’t changed that much with configuration options segregated between Organization, Server and Recipient just as it was laid out in Exchange 2007 however you will notice some new tabs within these nodes. Note that Exchange 2010 is the first version of Exchange that provides both an in house “On Premises” solution and a hosted cloud “On-Line” solution for customers who don’t want to manage and maintain an in house messaging system.
Let’s now just verify that our installation has completed successfully. If you did receive an error during installation you can locate the Exchange Setup Logs via this TechNet article.
I would quickly skim through the various nodes and ensure your Mailbox Database is mounted. This usually indicates that most things are in order.
Well, that’s it for now but stay tuned for Part II where we will dive into some of the configuration options in getting a basic Exchange environment up and running with mail flow.