Installing and configuring Exchange server 2007

in Windows server 2008

Prerequisites:

 Active Directory Domain Services

 Domain Name System
 Web Server (IIS)

Other major prerequisites for Exchange Server 2007 are .Net Framework, MMC 3.0 and
PowerShell installed before we deploy Exchange Server 2007.

.Net Framework and Microsoft Management Console (MMC) 3.0 features have already installed
in the Windows 2008 by default, so we have to install PowerShell and to accomplish this task we
have to follow these steps:

1. Open Server Manager  (Start/ Administrative Tools/ Server Manager)

2. Click on Features, then click on Add Features
3. Choose PowerShell on that list, and then click Next

Final screen of the Windows PowerShell installation

Now, we have to wait the Exchange Server 2007 SP1 to deploy Exchange Server 2007 on
Windows Server 2008, but all Exchange Server 2007 prerequisites are done.

Steps for Installing exchange server 2007

Step 4: Install Microsoft Exchange

And in the Introduction window click on Next

4. Click on the I accept the terms in the license agreement option and click Next
5. Select Yes or No for the Error Reporting option. In my example I’m going to enable this
feature. When ready, click on Next

6. Select one of the installation types listed. We are going to select the Custom Installation
Setup. In this window you may also specify the path for the installation and we are specifying
default when ready, click next
7. Select the roles to be installed. We are going to select Hub transport role and client access
server role to install.

If the installation path needs to be changed we can change it here.

7. In the next window you can specify client settings. Click on the Yes option if you think that
one of your clients might have Outlook 2003 on his or her system.

If you are positive that all client computers have Outlook 2007 installed, you may click on No.
When ready, click on Next to continue
8. Once the Readiness Checks are done running, click on the Install button to start the
installation

9. The entire installation takes approximately 30 minutes. When it is successful you will see this
window, on which you can go ahead and click Finish
10. You should update your Exchange server right after the installation. To do so, go back to the
main install screen and click on Step 5: Critical Updates for Microsoft Exchange
 Creating failover clustering and MultiPathing in windows 2008 server

Steps for Multipathing I/O

To add MPIO on a server running Windows Server 2008 R2

1. Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then
click Server Manager.

2. In the Server Manager tree, click Features.

3. In the Features area, click Add Features.

4. In the Add Features Wizard, on the Select Features page, select the Multipath I/O check box, and then
click Next.

5. On the Confirm Installation Selections page, click Install.

6. When the installation has completed, on the Installation Results page, click Close. When prompted to
restart the computer, click Yes.

7. After restarting the computer, the computer finalizes the MPIO installation.

8. Click Close.

Steps for configuring Failover Clustering

To connect the cluster servers to the networks and storage

1. Connect and configure the networks that the servers in the cluster will use.

2. If your test configuration includes clients or a non-clustered domain controller, make sure that these
computers can connect to the clustered servers through at least one network.

3. Follow the manufacturer's instructions for physically connecting the servers to the storage.

4. Ensure that the disks (LUNs) that you want to use in the cluster are exposed to the servers that you will
cluster (and only those servers). You can use any of the following interfaces to expose disks or LUNs:

 The interface provided by the manufacturer of the storage.

 If you are using iSCSI, an appropriate iSCSI interface.

 Microsoft Storage Manager for SANs (part of the operating system in Windows Server 2008). To
use this interface, you need to contact the manufacturer of your storage for a Virtual Disk Service
(VDS) provider package that is designed for your storage.

5. If you have purchased software that controls the format or function of the disk, follow instructions from
the vendor about how to use that software with Windows Server 2008.
 6. On one of the servers that you want to cluster, click Start, click Administrative Tools, click Computer
Management, and then click Disk Management. (If the User Account Control dialog box appears,
confirm that the action it displays is what you want, and then click Continue.) In Disk Management,
confirm that the cluster disks are visible.

7. If you want to have a storage volume larger than 2 terabytes, and you are using the Windows interface to
control the format of the disk, convert that disk to the partition style called GUID partition table (GPT). To
do this, back up any data on the disk, delete all volumes on the disk and then, in Disk Management, right-
click the disk (not a partition) and click Convert to GPT Disk.

For volumes smaller than 2 terabytes, instead of using GPT, you can use the partition style called master boot
record (MBR).

Step 2: Install the failover cluster feature

In this step, you install the failover cluster feature. The servers must be running Windows Server 2008.

To install the failover cluster feature on the servers

1. If you recently installed Windows Server 2008, the Initial Configuration Tasks interface is displayed, as
shown in the following illustration.

If this interface is displayed, under Customize This Server, click Add features. Then skip to step 3.

2. If the Initial Configuration Tasks interface is not displayed and Server Manager is not running, click
Start, click Administrative Tools, and then click Server Manager. (If the User Account Control
dialog box appears, confirm that the action it displays is what you want, and then click Continue.)
 In Server Manager, under Features Summary, click Add Features.

3. In the Add Features Wizard, click Failover Clustering, and then click Install.

4. Follow the instructions in the wizard to complete the installation of the feature. When the wizard finishes,
close it.

5. Repeat the process for each server that you want to include in the cluster.

Step 3: Validate the cluster configuration

Before creating a cluster, we strongly recommend that you validate your configuration. Validation helps you
confirm that the configuration of your servers, network, and storage meets a set of specific requirements for
failover clusters.

To validate the failover cluster configuration

1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover
Cluster Management. (If the User Account Control dialog box appears, confirm that the action it
displays is what you want, and then click Continue.)
2. Confirm that Failover Cluster Management is selected and then, in the center pane under
Management, click Validate a Configuration.
 3. Follow the instructions in the wizard to specify the two servers and the tests, and then run the tests. To
fully validate your configuration, run all tests before creating a cluster.

4. The Summary page appears after the tests run. To view Help topics that will help you interpret the
results, click More about cluster validation tests.

5. While still on the Summary page, click View Report and read the test results.

To view the results of the tests after you close the wizard, see

SystemRoot\Cluster\Reports\Validation Report date and time.html

where SystemRoot is the folder in which the operating system is installed (for example, C:\Windows).

6. As necessary, make changes in the configuration and rerun the tests.

Step 4: Create the cluster

To create a cluster, you run the Create Cluster wizard.

To run the Create Cluster wizard

1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover
Cluster Management. (If the User Account Control dialog box appears, confirm that the action it
displays is what you want, and then click Continue.)

2. Confirm that Failover Cluster Management is selected and then, in the center pane under
Management, click Create a cluster.

Follow the instructions in the wizard to specify:

 The servers to include in the cluster.

 The name of the cluster.

 Any IP address information that is not automatically supplied by your DHCP settings.

3. After the wizard runs and the Summary page appears, to view a report of the tasks the wizard
performed, click View Report.

Steps for configuring a two-node file server cluster

To configure a two-node file server failover cluster, follow these steps:

To configure a two-node file server failover cluster

1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover
Cluster Management. (If the User Account Control dialog box appears, confirm that the action it
displays is what you want, and then click Continue.)

2. In the console tree, if the cluster that you created is not displayed, right-click Failover Cluster
Management, click Manage a Cluster, and then select the cluster you want to configure.

3. In the console tree, click the plus sign next to the cluster that you created to expand the items
underneath it.
4. If the clustered servers are connected to a network that is not to be used for network communication in
the cluster (for example, a network intended only for iSCSI), then under Networks, right-click that
network, click Properties, and then click Do not allow the cluster to use this network. Click OK.

5. Click Services and Applications. Under Actions (on the right), click Configure a Service or
Application.

6. Review the text on the first page of the wizard, and then click next.

7. Click File Server, and then click Next.

8. Follow the instructions in the wizard to specify the following details:

 A name for the clustered file server

 Any IP address information that is not automatically supplied by your DHCP settings—for
example, a static IPv4 address for this clustered file server

 The storage volume or volumes that the clustered file server should use

9. After the wizard runs and the Summary page appears, to view a report of the tasks the wizard
performed, click View Report.

10. To close the wizard, click Finish.

11. In the console tree, make sure Services and Applications is expanded, and then select the clustered file
server that you just created.

12. Under Actions, click Add a shared folder.

 The Provision a Shared Folder Wizard appears. This is the same wizard that you would use to
provision a share on a nonclustered file server.

13. Follow the instructions in the wizard to specify the following settings for the shared folder:

 Path and name.

 NTFS permissions (optional).

 Advanced settings for the SMB protocol (optional). SMB is used by Windows-based clients. The
settings include:

- User limits.

- Offline settings (caching).

- Access-based enumeration, described in Shared folders in a failover cluster

 Whether the NFS protocol will be used, for support of UNIX-based clients (optional).

14. After completing the wizard, confirm that the clustered file server comes online. If it does not, review the
state of the networks and storage and correct any issues. Then right-click the new clustered file server
and click Bring this service or application online.

15. To perform a basic test of failover, right-click the clustered file server, click Move this service or
application to another node, and click the available choice of node. When prompted, confirm your
choice.

Steps to create a cluster

Go to Start>Failover cluster management

The new MMC Snap-In for “Failover Clustering Management” appears:

Select create a cluster
Creating a Cluster
So, hit the link Create a Cluster…, and the Create Cluster Wizard appears, with some useful
information regarding clustering. After reading, hit Next and the fun begins. This is where
you will enter the servers that will participate in your “soon-to-be-formed” cluster. Just
put the name and hit add for each one of them.
Once you are done listing your hit Next, and the new validation screen appears, asking if
you want to validate your configuration
Select yes to validate the configuration
Hit Next and it starts the validate configuration

 
  
 
A copy of this report is stored in your %windir%\cluster\reports directory if you need to
access it later.
So here it is finally, your cluster name. This is how everybody will acces this cluster and hit
Next.

So we get to a review page, with our cluster name, the nodes

that will participate on it, even the IP addresses! Hit Next.
Some time passes by, some messages, some blue bar filling up and click on finish

We created a new cluster! You can even check a detailed report with the View Report
button. When you press Finish, you go back to our Cluster Control Panel, with our two-
node cluster created and ready to configure a highly-available service or application.

After the cluster installation has finished the Failover cluster management will be as shown in
below
 After finished creating the cluster successfully we shall proceed with installing the Active
and passive mailbox role. Since cluster in the primary requirement for Active and passive
mailbox installation.
Steps for installing Active and Passive Mailbox

Requirements:

 A public network interface for normal network operations

 A private network interface for the cluster “heartbeat”
 Shared disk storage for the database, log files, and cluster quorum disk

Once the failover cluster has been configured we can install Exchange Server 2007 on the first
node.  Run setup as normal, and when selecting the roles to install choose “Active Clustered
Mailbox Role” as the server role.  You will notice that a clustered mailbox server cannot co-exist
with any other server role.
Choose “Single Copy Cluster” as the cluster type, give the cluster a name, and specify a path for
the database files.  The database path must be on a shared cluster disk.

Finally, give the cluster an IP address.

Exchange setup will configure all of the required cluster groups and resources for the underlying
failover cluster automatically.  Once the active node is installed repeat the setup process on the
passive cluster node, this time choosing “Passive Clustered Mailbox Role”.
Managing a Single Copy Cluster

For most Exchange administrative tasks the clustered mailbox server will appear like any other
mailbox server.  For example, the storage group will show up as with any other mailbox server.

[PS] C:>Get-StorageGroup

Name                      Server            Replicated

----                      ------            ----------

First Storage Group       EXCHMAILBOX       None

Second Storage Group      EXCHMAILBOX       None
First Storage Group       EXCHCMS           None

You can view the status of the CMS using the Exchange Management Shell.

[PS] C:>Get-ClusteredMailboxServerStatus

Identity                        : EXCHCMS
ClusteredMailboxServerName      : EXCHCMS.contoso.com
State                           : Online
OperationalMachines             : {EXCHMAILBOX1 <Active,...
FailedResources                 : {}
OperationalReplicationHostNames : {exchmailbox1, exchmail...
FailedReplicationHostNames      : {}
InUseReplicationHostNames       : {exchmailbox1, exchmail...
IsValid                         : True
ObjectState                     : Unchanged

Although the CMS is configured as part of the Microsoft Cluster Service it should not be
administered using Cluster Admin (cluadmin.exe).  Instead, Exchange cluster operations such as
moving the cluster group to another node should be performed in the Exchange Management
Shell.

[PS] C:>Move-ClusteredMailboxServer
cmdlet Move-ClusteredMailboxServer at command pipeline
position 1

Supply values for the following parameters:

Identity: exchcms
TargetMachine: exchmailbox2
MoveComment: Testing

Confirm
Are you sure you want to perform this action?
Moving clustered mailbox server "exchcms" to target
node "exchmailbox2" with move comment "Testing".

[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend
[?] Help (default is "Y"):y