| Working with Exchange 2010 (Part 2), Install Exchange 2010 |
|
| Written by Rafat S. El-Masri |
| Monday, 22 February 2010 12:09 |
|
After installing all prerequisites, we can start the installation using the setup wizard. Before we start, we have to make sure that; the account which we need to use while installing Exchange 2010 has all required permissions which they are as the following:
In this Installation, we will use Exchange 2010 installation wizard (GUI). Our LAB required installing two Exchange 2010 Servers to work with High availability options and other features which required two Exchange Servers. For that; we will install Exchange 2010 by two methods (GUI & Command Line). In this lesson, we will install Exchange 2010 by using the GUI, in another lesson which most properly will be (Part 4 or Part 5), we will install Exchange 2010 by using command line (Unattended installation).
Let’s start the installation. I'm assumed that you already download Exchange 2010 media and you copy it in the Exchange Server. If not; go to the following link and download Exchange 2010 media: Note: This time-limited version of Exchange Server 2010 will end 120 days after installation. After you extract the Exchange 2010 downloaded file to a folder, Open Exchange Server 2010 installation source files and double click on Setup.exe:
When you double click on Setup.exe, the Initial page of Exchange Server 2010 installation will appear:
Here we have to choose one of two Exchange 2010 Language options. Let’s talk about this before choose one of the options: Exchange 2010 language pack contains the necessary resources for a supported Exchange language. Language packs can be installed during installation of Exchange 2010 or after Exchange 2010 has been deployed. Client and server language packs come grouped into a single bundle containing both client and server resource and support files. You can automatically download the language packs when you're running Exchange Setup. For organizations that have users in multiple languages, Microsoft recommends to install the language pack bundle to provide localized messages on all server roles. This will provide localized messages for Microsoft Office Outlook Web App and Exchange Control Panel. There are no performance issues with installing all the languages because they're just stored when not in use.
Choosing Exchange Language Support Options Before you begin your Exchange installation, you must select from these two options in the Setup wizard:
As you can see, you can download the language pack bundle direct from Internet or you can download it offline and then take the second option |Specify the path for the language files ... etc". From the following link you can download the latest Exchange 2010 Language Pack bundle:
Note: To read more about Exchange 2010 language pack, check the following link: http://technet.microsoft.com/en-us/library/dd298152.aspx
In our LAB, we will use the second option "Install only languages from the DVD", click on this option, it will appear the Initial page of Exchange Server 2010 installation again, notes that; "Step 3: Choose Exchange Language option" comes hidden now, which mean the Exchange language pack already installed. Now click on "Install Microsoft Exchange":
Now the Introduction page will appear, it's talking about Exchange Server 2010, read it and then click next:
On License Agreement page, in order to install Exchange Server 2010, the License Agreement must be accepted. Click Next:
On Error Reporting page, if you want your Exchange server sending errors automatically to Microsoft Exchange team through HTTPS, click on Yes and then click next:
On Installation Type page, two options there; typical installation which includes CAS/HUB and Mailbox, or Custom Exchange Server Installation where we can select which roles will be installed. We will choose the second option by clicking on Custom Exchange Server Installation and then click next:
Note: As you can see on the Installation Type page, we can define where the Exchange Server installation files will be located, for our LAB, we will keep the default but you might need to change this in your production environment to meet Exchange 2010 best practices.
On Server Role Selection page, we will select all roles (Except Edge) and then click next:
On Exchange Organization page, specify the Exchange organization name and then click next:
Note: Name for Exchange Organization can be anything, but you need to plan it correctly, you can change the name later but it involves changes the registry and partially (some time) it's need to reinstalling Exchange. This name used by the system and users wouldn't need to know it.
On Client Settings page, If Outlook 2003 or earlier versions are still used in your organization or if you have Microsoft Entourage then you need to choose "Yes" as an option which will create a public folder database which needed to those clients to access system data, such as Free/Busy information. In our LAB we will assume that we have Outlook 2003 and we will choose yes and then click on Next:
Note: If you select “yes”, the Public Folder database will be created during the installation. If you select “No” and you want to enable support for Outlook 2003 later, you can easily create a Public Folder and associate it to the mailbox stores.
Note: Microsoft Entourage is an e-mail client and personal information manager developed by Microsoft for Mac OS 8.5 and higher. The current version of this product is Microsoft Entourage: Mac 2008
On Configure Client Access Server External Domain Page, if your Exchange server will be connected to the Internet, then you can type your External (SMTP) domain name, if you do it; Exchange will configure the domain name automatically while doing the installation process in Exchange Internet facing services such as OWA, ActiveSync ... etc. In our LAB, we will choose to configure this later, keep the page as default and then click next:
On Customer Experience Improvement Program page, we can include our Exchange organization in the customer experience improvement program, Microsoft will collect information on how your Exchange Server 2010 servers are being used and it will help improve the product features. You can select an industry that best represents your company. In our LAB, we will not join this program, click next:
Note: You can Enabled/Disabled this option later using Exchange Management Console.
On Readiness Checks page, this page will going to show you what you have to do in order to complete all the prerequisite installation before installing the actual product (in case if something missed):
As you can see in the result, we just have one warning which appear that our Active Directory is not prepare for Exchange 2010. Back to lesson 1 (Part 1), we mentioned that; we are going to choose the option to not prepare the Active Directory manually and we will keep the Exchange 2010 doing that while the installation, here it's warning us about this. As you can see, the "Install" bottom appear which mean we can install Exchange 2010. If any errors appear, Exchange will hide the "Install" bottom until you correct the error. Now click on Install:
On Progress page, it’s appearing that Exchange start installing all files, roles, components ... etc:
On Completion page, we can check all roles that have been installed on this machine, and we can see that the first item was Organization Preparation where the domain/forest was prepared during the setup to support Exchange Server 2010, now click finish:
Now, Exchange 2010 installation page appear again, click on close:
Confirm Exit message appear which show that some update required for Exchange 2010, we will do this step in next lesson, now click on Yes:
The installation of Exchange Server 2010 completed; it's good to restart the server at this point.
Until here, This lesson finished. In our next lesson we will see the steps of Post Exchange 2010 Installation.
Regards, Ra'fat |
| Last Updated on Tuesday, 23 February 2010 09:11 |



















