Figure 1 : Request before installation
When the Install Wizard program starts, you can read through the introduction, then read and accept the terms in the EULA. Next you have the option to allow using Error Reporting function, select and click Next . You are provided with two installation methods: Typical (typical) and Custom (optional) (see Figure 2). The typical type will install all roles (roles), except the Edge Transport . If you want to customize the installation components, you should choose Custom . You can also change the installation location if you want here.
Figure 2: Installation Options (Install Options)
When choosing the Custom type and clicking Next , you are provided with a number of options and can choose one or more of the roles you want to install. You can choose to install Active, Passive Mailbox server clusters or Management Console (see Figure 3).
Figure 3 : Server Roles
Before continuing, you must provide the name of the Exchange Oranization organization and be asked if any computer is using Outlook 2003 or earlier Outlook versions (see Figure 4). If you select Yes , the public Folders public folder will be created. If you select No , nothing happens.
Figure 4 : Outlook versions
You need to be cautious when choosing roles to install. If you are running in a multi-site AD environment, you need to install a Hub Transport and Mailbox server in each AD Site. Client Access Server is also needed in each site with a Mailbox server. Finally, all roles can be installed in the same server (except the Edge Transport) or on each individual server.
Now the installer will run a set of test requests to determine if the domain and server are ready to receive Exchange 2007. Figure 5 illustrates an example of some common errors you will encounter if IIS is omitted or the domain is not at the required functional level. (Note the Install button is dimmed).
Figure 5 : Error checking availability level
When no errors appear, the Install button appears. You can click on it to start the installation program (see Figure 6).
Figure 6 : Check the readiness level successfully
You can see the installation process, how long the installation takes depends on the role installed. Once finished, click the Finish button. The next job is to build the configuration for the Exchange 2007 server (See Figure 7).
Figure 7 : Installation process
CLI and installation program are not monitored
Exchange 2007 also supports the Command Line Interface (CLI) installation, which can be used to perform unattended installations. There are some required changes depending on the type of Exchange 2007 installation you are working on.
/ roles - describes the server role to be installed. Can be replaced with / r
The basic syntax of CLI or unattended installation program is as follows:
Setup.exe / console / roles: / mode: [/ targetdir:] [/ prepareAD] [/ RecoverServer] [/?]
To install Exchange 2007 with Bridgehead, Client Access and Mailbox server roles, use the following command:
Setup.exe / roles: ET, MB, CA or
Setup.exe / r: E, M, C
When you want to install the Gateway server, put the " Program files " program files into a folder in drive D named E2007 and read, write it from DC1, you need to use the following transformation command in Setup.exe:
Setup.exe / r: E / targetdir: D: E2007 /dc:dc1.thelazyadmin.lab
This final example explains which command you will use to install the new Exchange 2007 server during the "disaster" recovery process.
Setup.exe / mode: recoverserver
When this command is executed, the installation program determines whether .NET 2.0 Framework, MMC 3.0 and Microsoft Shell are installed. If any other checked software fails, the installation program will stop and give an error message.
Check the settings
After the installation process is complete, you should check that everything has been successfully completed. There are several ways you can do it. First open MSH and run the following command, which will give a list of installed roles (see Figure 8).
Get-ExchangeServer
Figure 8: MSH Get-ExchangeServer
Next, consider the Application Log application log information in Event Viewer with events with ID numbers of 1003 and 1004. These two events provide information to see if the installation was successful. Finally interested in some log files created.
• % SystemDrive% ExchangeExchangeSetupLogsSetup.log : This file tells you whether the pre-installation request checks are okay and which roles are installed.
• % SystemDrive% ExchangeSetupLogsExchangeServerMSI.log : This file tells you whether the file decompression process is responsible for any errors.
• % SystemDrive% ExchangeSetupLogsExchange Server Setup Progress.log : This file tells you which system changes were made during the installation process.
• % SystemDrive% Program FilesMicrosoftExchange Server LoggingSetupLogssetup.log : This file keeps track of the activities during installation. You should see this file if the installation program fails.
Conclude
There are many configuration options and settings in Exchange 2007 for you to choose from. The command line interface provides powerful and scriptable options for deploying Exchange 2007 servers with the smallest administrative interaction. Both installation types perform some pre-installation system requirements checks to ensure that Exchange 2007 installation is started correctly from the original.