HP E5000 Messaging System for Microsoft
Exchange Administrator Guide
Abstract
This document explains how to install, configure, and maintain all models of the HP E5000 Series Messaging System for
Microsoft Exchange. The intended audience is decision makers, IT support staff, and project managers involved in planning
and deploying Microsoft Exchange Server 2010 solutions. For more information on Exchange 2010 terminology and best
practices, go to http://www.hp.com/solutions/activeanswers/exchange. For the latest version of this guide, go to www.hp.com/
support/manuals. Select Solution appliances in the solutions group, and then select an E5000 product.
HP Part Number: 5697-1789
Published: June 2012
Edition: 3
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Microsoft®, Windows®, and Windows Server® are registered trademarks of Microsoft Corporation in the United States and other countries.
Revision History
DateEdition
DescriptionSoftware
Version
First release1.0February 2011First
2.01September 2011Second
Documented E5000 Configuration Wizard, Exchange Deployment Tool, E5000
System Manager, and System Management Homepage improvements. Added
appendices for E5000 error codes and troubleshooting. Updated details for
using the EMU CLI and physical interface. Updated information about network
connections.
2.03August 2012Third
Documented new Recovery LUN Manager and Storage Viewer features.
Documented E5000 Configuration Wizard, Exchange Deployment Tool, and
Alerts and Email improvements. Added requirement for installing Exchange
2010 SP2. Updated information about network connections. Updated details
for using the EMU CLI and physical interface.
Contents
1 HP E5000 Messaging Systems for Microsoft Exchange....................................7
1 HP E5000 Messaging Systems for Microsoft Exchange
The HP E5000 Messaging System for Microsoft Exchange (“messaging system”) is an integrated
hardware-software solution that simplifies the initial deployment of Microsoft Exchange Server
2010. Each messaging system features HP server blades and dense disk storage in a single 3U
enclosure (Figure 1 (page 8)). E5000 expansion disk enclosures are optional or standard
depending on the model. The following models are available:
•HP E5300 G2 Messaging System for Microsoft Exchange
•HP E5500 G2 Messaging System for Microsoft Exchange
•HP E5700 G2 Messaging System for Microsoft Exchange
Features
The HP E5000 Messaging System provides the following advantages:
•Each system ships from the factory with preintegrated hardware and preloaded software, to
significantly reduce the time and complexity of deploying Exchange 2010.
•Built on the HP converged application platform, which combines two server blades and dense
storage drawer into a single enclosure
•Simplified deployment with presized, tested, and optimized configurations
•Lower overall TCO with reduced footprint and lower energy consumption
•Presized configurations deliver high availability in hours instead of days
•Specially developed setup tools (setup wizards) provide guided setup assistance, performing
many of the complex and time-consuming tasks needed to configure and deploy a high
availability messaging system. The setup tools make it easy to get both Windows and Exchange
configured and running quickly.
•Automatic database-level recovery from failures
•HP and Microsoft management integration, including Microsoft Server Manager and System
Center and HP Systems Insight Manager and Integrated Lights Out (iLO)
For more information about E5000 Messaging System features, go to:
http://www.hp.com/go/E5000
Hardware components
Figure 1 (page 8) and Figure 2 (page 8) show front and rear views of the messaging system.
Features7
Figure 1 Front view
1. Disk drive drawer
2. Server blade 1, Bay 1
3. Server blade 2, Bay 2
4. Chassis fault LED
Figure 2 Rear view
1. System fan
2. HP 2-port Ethernet I/O module (2) (These modules connect to the NIC located on the server blade motherboard)
3. Drive fan
4. SAS I/O module (2)
5. Power button
6. Power supply (2)
7. HP 2-port Ethernet I/O module. These modules (2) connect to the NIC located on top of the Mezzanine card on the
server blade. Standard on the E5500 and E5700 and can be added as option for the E5300.
8. Management port (for iLO and Enclosure Manager Unit)
Software components
The E5000 Messaging System includes factory integration of the hardware and preloading of the
E5000 software image, including Windows Server 2008 R2, which has been preinstalled and
activated. The E5000 system configuration also includes the HP E5000 Messaging System
8HP E5000 Messaging Systems for Microsoft Exchange
Configuration Wizard and HP E5000 Messaging System Exchange Deployment Tool, which are
used to deploy the Exchange servers and storage in their optimal configurations.
The E5000 Configuration Wizard assists during the initial out of box setup and configuration of
the messaging system. This tool helps to configure each of the customer-specific settings needed
to prepare the server.
Exchange 2010 is then installed and configured using the E5000 Exchange Deployment Tool,
which has been developed to automate many of the deployment tasks.
To provide ongoing monitoring and facilitate management, the messaging system includes the
System Manager, which provides a snapshot view of the health and status of the messaging system
and tools to manage firmware updates.
Software components9
2 Preparing to install the messaging system
Before you install the messaging system, plan how you will integrate the system into your network
and whether you will use Insight Remote Support (see “HP Insight Remote Support software”
(page 58)). See the HP E5000 Messaging System for Microsoft Exchange Installation Checklist for
Exchange Server 2010 includes a high-availability feature called DAG, which requires two networks:
•Client/MAPI network provides the following functions:
Server-to-server connectivity between the CAS, Hub Transport, and Mailbox server roles◦
◦Server-to-server communication with domain controllers, global catalog servers, and name
services like DNS.
◦Management of Exchange client traffic such as Outlook and Outlook Web Access
◦Exchange client access to mail on CASs.
◦Replication, if the replication network is unavailable.
•Replication network provides the cluster heartbeat, Exchange Server 2010 log shipping, and
database seeding or reseeding when available.
IMPORTANT:The Replication and MAPI networks should be isolated from each other, preventing
Client/MAPI and Replication network traffic from being routed between networks.
Network connections
To facilitate manageability and diagnostic services on the messaging system, the server blades
require network connections to the EMU. The EMU provides connections to two types of management
processors:
•EMU processor
•iLO processor for each server blade
The EMU and iLO NIC port should be connected to the Client/MAPI network or to the dedicated
management network if used. For additional information, see Figure 4 (page 12) and Figure 5
(page 13) and “Configure the EMU and iLO management processors” (page 17). Because many
administrators use iLO remote management functions, including virtual console, HP recommends
that you configure the EMU so that administrators have remote network access to the unit. The
EMU and iLO management processors support DHCP and static network addressing. To simplify
initial setup, the processors are configured for static addressing as follows:
•EMU: 10.0.0.10
•Server 1 iLO: 10.0.0.11
•Server 2 iLO: 10.0.0.12
•Subnet: 255.255.255.0
NOTE:The EMU must share a LAN with the server blades.
Figure 3 (page 11) shows the network ports on the rear of the messaging system.
10Preparing to install the messaging system
Figure 3 Network ports
5. E5000 enclosure power button
6. Server 2, Mezzanine NIC, port 21. Server 1, NIC port 1
7. Server 1, Mezzanine NIC, port 22. Server 2, NIC port 1
8. Server 2, Mezzanine NIC, port 13. Server 1, NIC port 2
9. Server 1, Mezzanine NIC, port 14. Server 2, NIC port 2
10. Enclosure Manager NIC (includes iLO connections for both
servers)
NOTE:E5300 Mezzanine NICs (6, 7, 8, and 9) are optional on E5300 servers.
For the initial configuration, the EMU port must be connected directly to the administrator's laptop
or PC, as described in “Configure the EMU and iLO management processors” (page 17).
The E5500 and E5700 enclosures have more NIC ports than the E5300 enclosure, and they
provide more network connection options. Figure 5 (page 13) shows the recommended management
network configuration.
While alternate network ports can be used for network-based backup, they can also be used for
EMU connectivity. As with the E5300, the Client/MAPI or Replication network can also be used
to establish EM network connectivity to the servers.
NOTE:NIC teaming is not recommended or supported with these interfaces.
By default, the E5000 Configuration Wizard sets up the following networks:
•Client/MAPI network
This network is labeled as the MAPI network on each server.◦
◦The default setting is dynamic (DHCP), but you can use the E5000 Configuration Wizard
to configure static addressing.
•Replication network
◦The E5000 Configuration Wizard automatically sets these static addresses by default
(but also allows you to change them):
–Server 1: 10.0.0.1
–Server 2: 10.0.0.2
Use the short Ethernet cable shipped with the messaging system to connect the Replication
network ports, as shown in Figure 4 (page 12) or Figure 5 (page 13).
Network connections11
•Management network
◦The default setting is dynamic (DHCP) addressing, but you can change this setting as
needed.
◦HP recommends that the management network be on the same network as the EMU and
iLO NIC port.
◦This NIC is not standard on the E5300 model.
•Alternate network
◦The default setting is dynamic (DHCP) addressing, but you can change this setting as
needed.
◦This NIC is not standard on the E5300 model.
Figure 4 (page 12) shows the recommended E5300 network configuration expected by the E5000
Configuration Wizard described in “Configuring the messaging system software” (page 23).
Figure 4 Recommended E5300 network configuration
1. Client/MAPI network
2. Replication network cable
3. Domain controller
4. Connection to EMU
Figure 5 (page 13) shows the typical E5500/5700 network configuration expected by the E5000
Configuration Wizard, as described in “Configuring the messaging system software” (page 23).
12Preparing to install the messaging system
Figure 5 Typical E5500/5700 network configuration
4. Domain controller1. Client/MAPI network
5. Connection to EMU2. Replication network cable
6. Management network3. Connections to management network
Network connections13
3 Installing the messaging system
This chapter explains how to install the messaging system hardware.
Verify the kit contents
Remove the contents, ensuring that you have all of the following components. If components are
missing, contact HP technical support.
Hardware
•HP E5000 Messaging System base system configuration
•Expansion disk enclosures if deploying an E5700 configuration or if purchased as an upgrade
option for other configurations
•Rail kit
•Power cords
•Short CAT5 Ethernet cable
•0.5m mini SAS cable and 2m mini SAS cable per external disk enclosure
Locate and record the product number, serial number, and SAID number
Before you begin installation, locate and record the product number of the messaging system,
serial number, and support contract service agreement ID (SAID) number.
The product number of the messaging system and serial number are located in three places:
•Top of the messaging system
•Back of the messaging system on a pull-out tab
•On the messaging system shipping box
The SAID number is listed on your service contract agreement (see “Obtaining the Service Agreement
ID” (page 60)).
Unpack and rack the messaging system hardware
WARNING!The messaging system enclosure is heavy. Always use at least two people to move
the messaging system into the rack.
14Installing the messaging system
1.If your messaging system is delivered in a rack, proceed to Step 2. If you ordered the messaging
system without the rack, install the rail kit and enclosure in the rack using the installation
instructions that are included with the rail kit.
IMPORTANT:Ensure that cabling in the back of the rack system does not interfere with
system operation or maintenance. Bind cables loosely with cable ties and route the excess
out of the way, along the side of the rack, to keep system components and indicators visible
and accessible.
Figure 6 Messaging system installed in a rack
1. Messaging system enclosure
2-5. Expansion disk enclosures (optional)
6-7. Cable connection, with no bend radius smaller than 5 cm
2.If you purchased expansion disk enclosures, rack and cable the expansion disk enclosures
before moving to the next step. For recommended cabling, see “Cable expansion disk
enclosures” (page 16).
3.Cable the messaging system to your network and attach the power cords. See “Rear view”
(page 8) for connecting the power cables. For information on network configurations, see
“Preparing to install the messaging system” (page 10).
Unpack and rack the messaging system hardware15
Cable expansion disk enclosures
The following figures show the correct cabling of expansion disk enclosures to the messaging
system chassis. Numbers represent the order of attachment. Figure 7 (page 16) shows an E5700
base configuration with two expansion disk enclosures.
Figure 7 E5700 base configuration with two expansion disk enclosures
1. E5700
2-3. Expansion disk enclosures
4. SAS cable connecting expansion disk enclosure 1 (green cable)
5. Green color code for upper SAS I/O module
6. Red color code for lower SAS I/O module
7. SAS cable connecting expansion disk enclosure 2 (red cable)
Figure 8 (page 17) shows an E5700 maximum configuration with four expansion disk enclosures.
16Installing the messaging system
Figure 8 E5700 maximum configuration with four expansion disk enclosures
1. E5700
2–5. Expansion disk enclosures
6. SAS cable connecting expansion disk enclosure 1 (green cable)
7. Green color code for upper SAS I/O module
8. Red color code for lower SAS I/O module
9. SAS cable connecting expansion disk enclosure 2 (red cable)
Power on the messaging system
1.Power on any expansion disk enclosures.
2.Power on the messaging system by pushing the power button on the back of the chassis.
Once the messaging system power is on, power on the server blades if they do not
automatically power on.
Configure the EMU and iLO management processors
Before configuring the management processors, verify the following:
•You have determined whether the network ports on the server are to use DHCP or static
addresses. If the network ports are to use static addresses, you must provide the addresses.
•The server NIC ports are cabled to the appropriate switches or VLANs (see“Network
connections” (page 10)).
•For this step, the EMU port should not be connected to a switch. You can connect the EMU
port to a switch after the EMU and iLO NICs are configured.
Configure the EMU and iLO management processors for both servers as follows:
Power on the messaging system17
1.Connect a system (the configuration system) in the environment or a laptop to the EMU port
(Figure 9 (page 18)). You can use either a crossover or a regular Ethernet cable.
Figure 9 EMU NIC port connection
2.Configure the networking properties for the local system:
a.Open Control Panel, select Network Sharing Center or Network Connections, and navigate
to Local Area Connections.
b.Select Properties→Internet Protocol, and then select Properties.
c.If Use the following IP address: is selected, record values for the following items and
restore them after completing the EMU and iLO setup:
•IP address
•Subnet mask
•Default gateway
d.Enter the following values:
•IP address: 10.0.0.20
•Subnet mask: 255.255.255.0
e.Before continuing, ping the following IP addresses to test connectivity to the EMU and
the iLO located in each of the servers: 10.0.0.10, 10.0.0.11, and 10.0.0.12. The EMU
and iLO interfaces have been assigned IP addresses during factory setup. You must either
update the factory values with site-specific static IP addresses or configure the management
processors to use DHCP IP addressing.
3.Configure iLO on the server blades:
a.Open a web browser and log in to iLO using the address: http://10.0.0.11. You
are prompted to enter the user name and password. The password for the Administrator
account is located on a tear-away label on the back of the server blade (Figure 11
(page 19)).
After you have logged into iLO, HP recommends that you change the administrator
password. To do so, select User Administration under Administration in the iLO
management interface.
b.Configure the network as required for your environment. Select Network under
Administration in the iLO management interface. You can either enable DHCP or edit the
IP address details and enter site-specific network settings. Click Apply to save your settings.
c.Repeat the process on the other server blade. Open a web browser and log in to iLO
using the address: http://10.0.0.12.
18Installing the messaging system
4.Configure the EMU:
a.Connect to the Enclosure Manager software using an ssh compatible tool like PuTTY. In
the PuTTY session basic options, enter the EMU IP address (10.0.0.10) and port (22),
and select SSH for the connection type (Figure 10 (page 19)).
NOTE:See “Managing the EMU” (page 134) for information on using CLI commands.
Figure 10 Connecting to the Enclosure Manager software
b.After you have connected to the EMU port, set the following attributes:
•EMU (DNS) name
•Rack name
•EMU password (located on the tear-away label on the back of the server blade; see
Figure 11 (page 19))
•IP addressing method
To change the static IP address, type the command set ipconfig static
◦
at the command line prompt and follow the instructions.
◦To change the EMU addressing to DHCP, type set ipconfig dhcp at the
command line prompt.
Figure 11 Tear-away label location
Example 1 Setting attributes
CustomerEMU-dnsName> set em name CustomerEMU-dnsName
CSP Enclosure Manager name changed to CustomerEMU-dnsName.
CustomerEMU-dnsName> set rack name CustomerRackName
Changed rack name to "CustomerRackName".
Configure the EMU and iLO management processors19
CustomerEMU-dnsName> set password
New Password: ********
Confirm : ********
Changed password for the "Administrator" user account.
CustomerEMU-dnsName>
NOTE:You will not be able to connect to iLO or the EMU from the configuration system until
you change the network settings on the configuration system.
5.Complete the configuration:
a.Connect the EMU port to the appropriate switch/VLAN/subnet.
b.Log in to the EMU using ssh and the newly assigned EMU name and validate connectivity.
It is assumed that the EMU name is in the DNS.
Example 2 Verifying connectivity
CustomerEMU-dnsName> show server list all
Bay iLO Name iLO IP Address Status Power UID
--- ----------------------------- --------------- -------- ------- -- 1 ILOMXQ0110FJ9 16.78.90.51 OK On Off
2 ILOMXQ0110FHU 16.78.90.113 OK On Off
Totals: 2 server blades installed, 2 powered on.
Accessing the messaging system
For initial messaging system configuration you must have console access for each of the server
blades. You can use either a local I/O diagnostic (SUV) cable or an iLO connection. The iLO
connection is the preferred method because it allows for remote access.
For remote access, open a web browser and enter the iLO name or IP address for the server blade
located in Bay 1. For more information about IP addressing and subnets, see “Network connections”
(page 10). Log in using the iLO administrator name and newly created password for that blade.
For instructions on using iLO, see the Integrated Lights Out user guide available from http://
www.hp.com/go/ilo. On the iLO web page, select More iLO Documentation.
If you are using the direct connect method, connect the supplied SUV cable to the front of the
messaging system server blades in the following sequence: keyboard, mouse, monitor cable, and
monitor power cable.
NOTE:The keyboard, mouse, and monitor are not provided with the messaging system.
20Installing the messaging system
Figure 12 Keyboard, mouse, and monitor
1. Messaging system enclosure
2. Monitor
3. Keyboard
4. Mouse
Adding expansion disk enclosures to an installed messaging system
1.Rack the expansion disk enclosures.
2.Use the Exchange Management Console or the Exchange Management Shell to failover the
databases from the Bay 1 server to the Bay 2 server.
3.Power on the expansion disk enclosures.
CAUTION:In some cases, when adding new expansion disk enclosures, disks are seen
through a single path. This condition is reported as an error in the diagnostics initially performed
by the E5000 Configuration Wizard. To fix this problem, power cycle the expansion disk
enclosures by pressing and holding the button on the back of the unit, then pressing and
holding the button once again to power them back on. Then run the E5000 Configuration
Wizard from the All Programs shortcut.
For instructions, see “Configuring server software” (page 23).
The messaging system identifies the new storage and creates new LUNs.
4.Once the E5000 Configuration Wizard has completed, on the Bay 2 server, use the Exchange
Management Console or the Exchange Management Shell to manually failover the databases
from the Bay 2 server to the Bay 1 server.
5.Rebalance the databases using the RedistributeActiveDatabases.ps1 script located
(by default) at \Program Files\Microsoft\Exchange Server\V14\scripts. Run
this script within the Exchange Management Console.
6.Within the Microsoft Exchange Management Console, select New Mailbox Database:
a.Name the new database the next item in the sequence (for example, DB10).
b.Select a server.
c.Set the path based on the newly created LUNs.
7.Use Microsoft Exchange Management Console to add a mailbox copy.
Adding hard drives to an installed E5000 system
If you are running an E5000 system with fewer than the maximum number of hard drives, you can
add drives as follows:
1.Install the new drives as described in “Replacing the drive drawer hard drive” (page 106).
Adding expansion disk enclosures to an installed messaging system21
2.Run the E5000 Configuration Wizard on the first server manually from the All Programs
shortcut. The wizard recognizes the new storage and creates new LUNs. Exit the wizard at
the first opportunity.
3.Run the wizard on the second server.
4.Within the Microsoft Exchange Management Console, select New mailbox database and
name the new database sequentially. For example, if the previous database name is DB9,
name the new database DB10. After naming the new database, complete the following steps:
a.Select a server.
b.Set the path based on the newly created LUNs.
5.Use Microsoft Exchange Management Console to add a mailbox copy on the other server.
22Installing the messaging system
4 Configuring the messaging system software
This chapter explains how to configure system software using the E5000 Configuration Wizard
and how to deploy Microsoft Exchange Server 2010 using the E5000 Exchange Deployment Tool.
IMPORTANT:To configure the messaging system, you must run these tools on each server blade.
HP recommends that you fully complete the E5000 Configuration Wizard and E5000 Exchange
Deployment Tool on the Bay 1 server blade before beginning to configure the Bay 2 server blade.
After you have completed the initial configuration, be sure to install any available software updates
as described in “Upgrading E5000 software” (page 61).
Configuring server software
The E5000 should be powered on and the network ports cabled for your network configuration,
including the EMU port. For configurations that use expansion disk enclosures, such as the E5700,
all expansion disk enclosures should be cabled to the messaging system and powered on. Complete
the following steps, first on server 1, and then on server 2. Do not start on the second server until
you have completed the steps on server 1. When the server is powered on for the first time, it
completes the initial Windows configuration process and then launches the E5000 Configuration
Wizard.
To configure the software:
1.Enter your locale information in the Windows setup dialog box and accept the license terms.
The Windows setup completes in approximately 15 minutes and the server reboots. Upon
reboot, the server automatically logs on with the default password (HPinvent!) and the E5000
Configuration Wizard starts. After reading the welcome screen, click Next.
NOTE:If the automatic logon does not occur and a message displays that the user name
or password is incorrect, re-enter Administrator as the user name and HPinvent! as
the password to complete the logon and start the E5000 Configuration Wizard.
2.Set and confirm the server Administrator password. The Administrator password is required
only the first time you run the wizard. Click Next.
NOTE:The Windows Server 2008 R2 default password policy requires a strong password
as the server password for each server on the E5000 Messaging System. For more information
on strong passwords for Windows Server 2008 R2, see the following Microsoft Technet article:
3.Set the network configuration. Review each network port configuration and either accept the
default values or click Edit to change them. Click Next when finished.
Configuring server software23
IMPORTANT:
•By default, the Replication network is set to a static network (10.0.0.0/30) with IP
10.0.0.1 on the first node and 10.0.0.2 on the second node. A cable directly connects
the two ports. If these addresses conflict with addresses on your network, reconfigure
them to some other unused static network. If the replication ports will be connected to a
switch, you might have to change the network settings. You can either automatically
configure with DHCP or manually enter a specific IP address.
•Be careful not to put the Client/MAPI and Replication networks on the same subnet. If
you attempt to do so, the wizard displays a warning.
Figure 13 (page 24) shows an E5500/5700 configuration that has four networks per server:
Client/MAPI, Replication, Management, and Alternate. The E5300 configuration has two
(standard) networks per server: Client/MAPI and Replication.
Figure 13 Network configuration
4.Enter the EMU Administrator password and then click Next.
The default password is printed on a label attached to the underside on the EMU module. The
default password is also printed on a tear-away label attached to the rear of the enclosure
(Figure 11 (page 19)). Remove the tear-away label and store it in a safe place. After you
enter the password, an animated icon indicates that the wizard is verifying connection to the
enclosure.
24Configuring the messaging system software
5.The wizard displays the status of tasks it must complete before continuing. If the wizard finds
errors, it reports them and stops. You must exit the wizard, fix the errors and restart the wizard
from the All Programs menu on your system.
NOTE:If the wizard reports fan warnings, replace the fan module as soon as possible.
6.Configure Alerts and Email to send email notification of system events (see “Configuring Alerts
and Email” (page 34)).
7.Set the time zone and then click Next. The correct local time zone is set when the server joins
a domain.
8.Configure the Internet Explorer Proxy Server settings (see Figure 14 (page 25)) and then click
Next.
Figure 14 Internet Explorer proxy server
9.Set the computer name and join a domain (see Figure 15 (page 26)). Enter the computer
name and the name of the domain that the computer will join. Enter the name and password
of a user (typically Administrator) who has permission to add the computer to the domain.
The Administrator password is required only the first time you run the wizard. Click Next when
finished.
IMPORTANT:Be sure to record the name of the first server. You will need that name when
you configure the second server.
Configuring server software25
Figure 15 Computer name
10. Review the summary report and complete the configuration. The Summary screen lists the
configuration settings you have made.
11. Click Apply Settings to apply the configuration settings or Back to modify them. When you
are ready to accept the settings, click Finish to reboot the server. If you do not want to reboot
at this time, clear the Reboot after exiting the wizard box. The server must be rebooted to join
the domain and is also a required step prior to deploying Microsoft Exchange Server 2010.
NOTE:The server blades contain redundant storage controllers. When a server reboots,
one of the controllers shuts down. The partner server sees this event as a redundancy loss and
creates a log entry: “drive array controllers are no longer redundant”. You can ignore the
message if it coincides with a reboot you initiated.
Continue with the next procedure, “Deploying Microsoft Exchange Server 2010” (page 26), and
complete the setup on the Bay 1 server before setting up the Bay 2 server.
Deploying Microsoft Exchange Server 2010
Follow this procedure to deploy Microsoft Exchange Server 2010. Complete the deployment of
Microsoft Exchange Server 2010 on the Bay 1 server blade before beginning the configuration
of the Bay 2 server blade.
26Configuring the messaging system software
IMPORTANT:Before proceeding:
•Install any available software updates as described in “Upgrading E5000 software” (page 61).
•Ensure that the Active Directory and domains have been configured. For more information,
see http://technet.microsoft.com/en-us/library/bb125224.aspx. You must also provide a
witness server to be used by the DAG. For details on selecting and configuring a server to be
a witness server, see http://technet.microsoft.com/en-us/library/dd351107.aspx .
1.Log in to the Bay 1 server. If you have completed this procedure for the Bay 1 server, log in
to the Bay 2 server now.
When you log in, the Windows Security screen appears. Log in using the domain administrator
credentials you used to join the server to the domain. The E5000 Exchange Deployment Tool
starts automatically and displays the Introduction window.
NOTE:If you do not log in as the domain administrator, the E5000 Exchange Deployment
Tool will not run. You must log out and log in as the domain administrator.
Figure 16 Deployment introduction
HP recommends that you run the tests in the Prerequisites checklist. For detailed information
on Microsoft prerequisites, visit the links displayed on Figure 16 (page 27).
After you have run the tests, click Next.
NOTE:You need a properly configured Internet Explorer browser, including proxy
configuration (if applicable), to access the links.
Deploying Microsoft Exchange Server 201027
2.The End User License Agreement Confirmation screen appears. After reading and accepting
the agreements, click Next.
The Jetstress screen appears (Figure 17 (page 28)):
Figure 17 Jetstress Tools
3.If you choose to run a Jetstress test, select the type of Jetstress test. The default is set to skip
Jetstress (click Next to skip the test).
•A normal run of the Jetstress test provides a baseline benchmark of the system. HP
recommends that you run the test now, but only if you have sufficient time before deploying
the server into production.
NOTE:
◦A normal run of the Jetstress test can take 24 hours to complete.
◦Until the Exchange Deployment Tool is run on the final node, the system configuration
is listed as unsupported in the system tray. Ignore the system tray status until Exchange
has been deployed on all nodes.
•A quick run of the Jetstress test does not provide detail performance results but can be
used to validate some of the configuration information.
Choose a quick run if you cannot dedicate the time for a normal Jetstress test. For more
information about Jetstress, see “Using Microsoft Exchange Jetstress and Load Generator
(optional)” (page 32).
28Configuring the messaging system software
Once you make a selection or if you choose to skip the Jetstress test, click Next. The
Prerequisite Checks screen appears (Figure 18 (page 29)).
4.The Prerequisite Checks screen displays the status check results for the configuration settings
in your environment.
If a test fails, the Next button is disabled and you are not allowed to proceed. Check the logs
for the configuration setting failure details and correct the failed setting. Click Refresh checks
to verify the settings.
If all tests pass with either a green checkmark or warning, the Next button is enabled. Click
Next to start deployment of the Exchange Administration Tools.
Figure 18 Prerequisite Checks
5.After the installation of the Exchange Administration Tools finishes, complete the fields on the
Custom Input window.
When deploying to the Bay 1 server, select First blade. The E5000 Exchange Deployment
Tool automatically detects whether any servers are found in the existing Exchange organization
(when existing is selected). When deploying to the Bay 2 server, select Second blade. The
name of the second blade of Bay 1 server is autodetected.
Complete each item on this screen as needed for your deployment:
•New or existing Availability Group (DAG) name. The E5000 Exchange Deployment Tool
automatically detects if any DAGs are found in the existing Exchange organization.
Accept the default name or enter a new name of a DAG that already exists.
•Availability Group IP address. Using an IP address of 0.0.0.0 configures the DAG to use
DHCP. You can update the configured IP address later using the Exchange Management
Deploying Microsoft Exchange Server 201029
Shell, or additional addresses can be added later using the Set-AvailabilityGroup
PowerShell command.
•Witness server name. See http://technet.microsoft.com/en-us/library/dd351107.aspx
for information about special considerations if placing the suggested default witness server
on a domain controller.
•Witness directory. Specify the local path on the witness server.
•Name prefix. Use the suggested default name or enter a new name. The E5000 Exchange
Deployment Tool appends numbers to the name and verifies that the name is unique at
the organization level (an Exchange 2010 requirement).
•Client Access Server (CAS) is Internet facing. For more information, see http://
technet.microsoft.com/en-us/library/dd351198.aspx .
•New or Existing CAS array. If a new array, enter a name or select from the dropdown
list for existing arrays (if detected).
•Enter the name of your load-balanced CAS array that is set on the database property. If
no load-balanced CAS array is available, see:
◦http://go.microsoft.com/?linkid=9738617
◦http://go.microsoft.com/?linkid=9738618
•Enable Error Reporting. For more information, see http://go.microsoft.com/?
linkid=9738619.
•Create Public Folder database. To connect to Exchange 2010 Microsoft Entourage or
Outlook 2003, clients require a public folder database. The E5000 Exchange Deployment
Tool runs Exchange setup to create the public folder database for you. This option is
available only on the first Exchange 2010 Mailbox server being deployed. The public
folders on this system are designed primarily for Free-Busy usage and not large-scale
folder replicas or other applications. The database is created in
h:\ExchangeDatabases\PF\Exch2010PublicFolder.edb.
•Exchange 2003 bridgehead server. Use the parameter to specify an Exchange 2003
bridgehead server that is located in the routing group to which you plan to create the
initial routing group connector. A routing group connector is required for mail flow
between Exchange 2010 and Exchange 2003 when these Exchange server versions
coexist in the same organization.
•Customer Experience Improvement Program. See http://go.microsoft.com/?
linkid=9738620.
6.Click Deploy to start the tools deployment process. This process typically requires about 1
hour and 30 minutes.
The E5000 Exchange Deployment Tool displays the Deployment Status window (Figure 19
(page 31)).
30Configuring the messaging system software
Loading...
+ 169 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.