Exchange Server 2010 Setup is the program you use to perform installation tasks for Exchange Server 2010. You use Exchange Server 2010 Setup to install Exchange Server roles and the Exchange management tools. When you want to manage the Exchange server configuration, you use Programs And Features in Control Panel. Tasks you can perform with these utilities include:
Installing Exchange Server roles and management tools Adding server roles or management tools Maintaining existing components Uninstalling Exchange Server
1. Installing New Exchange Servers
You can install multiple
Exchange Server roles on a single computer. For servers deployed within
the organization, you can deploy any combination of the Mailbox, Client
Access, Hub Transport, and Unified Messaging roles on a single computer.
You cannot combine the Edge Transport role with other roles, however,
because this role is for the organization's perimeter network and you
must install it separately from other roles.
Often, small and
medium-size organizations can deploy Exchange servers that host multiple
roles in each Active Directory site and might not need to have an Edge
Transport server in a perimeter zone. As the size and needs of the
organization increase, however, it becomes more and more beneficial to
host some roles on separate servers. Keep the following in mind:
You may be able to achieve increased efficiency for message routing
and delivery by combining the Mailbox and Hub Transport roles on a
single server. However, keep in mind that routing rules change when you
combine Hub and Mailbox roles in a database availability group. You can achieve increased security by isolating the Internet-facing Client Access role and deploying it on a server other than one that also hosts the Mailbox and Hub Transport roles. You can improve responsiveness for dial-in and voice access by isolating the Unified Messaging role and deploying it on a server other than one that also hosts the Mailbox and Hub Transport roles. You can achieve high
availability for the Mailbox role, simply by installing two or more
Mailbox servers, creating a database availability group, adding mailbox
databases to this group, and then adding database copies. You
can achieve high availability for the Hub Transport role simply by
installing the role on multiple servers. Thanks to the new shadow
redundancy feature, a message that is submitted to a Hub Transport
server is stored in the transport database until the transport server
verifies that all of the next hops for that message have completed
delivery. If the next hop doesn't report successful delivery, the
message is resubmitted for delivery. In addition, when messages are in
the transport dumpster, they aren't removed until they are replicated to
all the appropriate mailbox databases. You can achieve high availability for the Client Access role by installing the role on multiple servers, configuring network or hardware load
balancing, and creating a load-balanced array called the Client Access
Server (CAS) array. Creating a CAS array requires planning. If you are
going to create and use an array, you should specify the URL of the
array as the external domain name for the Client Access server during
setup. This will ensure that clients connect to the array.
When you use multiple Exchange servers, you should deploy the roles in the following order:
For client access to work
correctly, install at least one Client Access server in each Active
Directory site that has a Mailbox server. For Hub Transport, Mailbox,
and Unified Messaging servers, install at least one of each server role
for each group of Active Directory sites that are well connected on a
common LAN. For example, if the organization consists of Sites A and B,
which are well connected on a common LAN, and Sites C and D, which are
well connected on a common LAN, with wide area network (WAN) links
connecting Sites A and B to Sites C and D, a minimal implementation
would be to have Hub Transport, Mailbox, and Unified Messaging servers
only in Site A and Site C. However, Microsoft recommends that you have
the Client Access, Hub Transport, Mailbox, and Unified Messaging serve roles in each Active Directory site.
Because you install Edge
Transport servers outside the Active Directory forest, you can deploy
them at any time. By configuring multiple Edge Transport servers, you
can ensure that if one server fails, Edge Transport services continue.
If you also configure your Edge Transport servers with round-robin DNS, you can load-balance between them.
Note:
REAL WORLD
If you are installing Exchange Server on a new network, such as one for
a new company or a development environment, be sure that you've
properly configured Active Directory and DNS before installing Exchange
Server. You need to create a domain. Typically, you do this by
installing a server and establishing the server as a domain controller
in a new forest. Ideally, the operating system on the domain controller
should be Windows Server 2008 Service Pack 2 or later or Windows Server
2008 Release 2. Active Directory must operate in Windows Server 2003 or
higher forest functional mode.
When you set up DNS, be sure you configure the appropriate reverse
lookup zones. You should have one reverse lookup zone for each subnet.
If you forget to set up the reverse zones and do this after installing your servers, be sure that the appropriate PTR records have been created for your domain controllers and Exchange
servers. In Active Directory Sites And Services, check that the sites
and subnets are configured appropriately. You need to create a subnet in
Active Directory to represent each of the subnets on your network. If
DNS reverse zones and Active Directory subnets are not configured
properly, you will likely experience long startup times on your servers,
and Exchange services will likely not start properly.
2. Installing Exchange Server
The Exchange Server 2010 installation process uses Windows Installer and requires the .NET Framework version 3.5.1, Windows PowerShell 2.0, and WinRM 2.0. Some Exchange server roles also require additional components, as discussed previously.
Using Windows Installer helps
to streamline and stabilize the installation process, and it makes
modification of installation components fairly easy. Thanks to Windows
Installer, you can do the following:
Install additional roles or components by rerunning the Installation Wizard. With Windows Server 2008, use the Programs And Features page under Control Panel, Programs. Maintain installed components. With Windows Server 2008, use the Programs And Features page under Control Panel, Programs. Resume a failed installation or modification. Do this by rerunning Exchange Setup.
For administration purposes, you can install the Exchange management tools on a workstation computer running Windows
Vista with Service Pack 2 or later, or Windows 7. This workstation must
also have the .NET Framework version 3.5.1, Windows PowerShell 2.0,
WinRM 2.0, IIS 6 Metabase Compatibility, and the IIS 6 Management
Console. For Windows Vista SP2 or later, Windows Management Framework
has most of what you need. After you install PowerShell, you can add the
IIS components by entering the following commands at an elevated
administrator PowerShell prompt:
Add-WindowsFeature -name Web-Server
Add-WindowsFeature -name Web-Metabase
To install Exchange Server roles on a server, complete the following steps:
Log
on to the server using an administrator account. When you install the
Mailbox, Hub Transport, Client Access, and Unified Messaging roles, you
must use a domain account that is a member of the Enterprise
Administrators group. If you've already prepared Active Directory, this
account must also be a member of the Exchange Organization Administrators group. If
you are using an installation disc, insert the Exchange Server 2010 DVD
into the DVD-ROM drive. If Autorun is enabled, Exchange Server 2010
Setup should start automatically. Otherwise, double-click Setup.exe on
the root folder of the DVD. On
the Start page, you need to install required components if they are not
already installed by clicking the links for steps 1, 2, and 3, each in
turn. For Windows Server 2008, this helps you download and install the
.NET Framework version 3.5.1 and Windows PowerShell version 2.0. Note
that you also need WinRM 2.0 (which you get from Windows Management
Framework) and the .NET update. For R2, these should all be available,
except for .NET Framework version 3.5.1, which you can install using the
Add Feature wizard in Server Manager. And for a CAS, you need to set
Net.TCP Port Sharing service to Automatic startup. This service does not
even appear in Windows 2008 R2 until other prerequisites are installed,
so you cannot configure the service ahead of time. On the Start page, click Step 3: Choose Exchange
Language Option, and then choose a language installation option. You
can install only languages from the DVD or all languages from the
language bundle. If your e-mails messages are sent and received
primarily in your native language, you probably need only the languages
from the DVD. However, if you operate in a multilingual environment, you
might need to install all languages from the language bundle. On
the Start page, click Step 4: Install Microsoft Exchange. In the
Exchange Server 2010 Installation Wizard, read the introductory text and
then click Next. On
the License Agreement page, read the license agreement. Select I Accept
The Terms In The License Agreement, and then click Next. On
the Error Reporting page, choose Yes if you'd like to send error
reports automatically to Microsoft or No if you would like to turn off
automatic error reporting. Click Next. On the Installation Type page, click Custom Exchange Server Installation and then click Next. On the Server Role Selection Page, select the server roles that you want to install on the computer. When you select one or more roles, the wizard selects the Management
Tools option automatically to install the Exchange management tools.
The default installation location for Exchange Server and all its
components is %SystemDrive%\Program Files\Microsoft\Exchange Server\V14.
If you want to change the path for the Exchange Server 2010
installation, click Browse, locate the relevant folder in the folder
tree, and then click OK. Click Next.
Note:
When you are installing
production versions of Exchange Server 2010, the Management Tools
option installs the 64-bit management tools. You can install the
management tools on your 64-bit workstation running Windows Vista SP 2
or later or Windows 7. You can't install the management tools on 32-bit
computers. To manage Exchange Server 2010 remotely from a 32-bit Windows
installation, you can install the Windows Management Framework and then use remote Windows PowerShell for management.
If you selected Mailbox
Role, Client Access Role, Hub Transport Role, or Unified Messaging
Role, and if this is the first Exchange 2010 server in your
organization, on the Exchange Organization page, type a name for your
Exchange organization or accept the default value of First Organization.
Click Next. If
you selected Mailbox Role, and if this is the first Exchange 2010
server in your organization, you'll next see the Client Settings page.
If you have client computers that are running Outlook 2003 and earlier
or Entourage,
select the Yes option so that Exchange creates a public folder database
on the mailbox server. If all of your client computers are running Outlook 2007 or later or are all non-MAPI clients, public
folders are optional because the OAB and free/busy information are
maintained separately. If you select the No option, Exchange does not
create a public folder database on the mailbox server. You can add a
public folder database later if desired. Click Next. If
you selected Client Access Role, you'll see the Configure Client Access
Server External Domain page. This page allows you to specify whether
the Client Access server will be Internet facing. An internet-facing
server is one that clients outside the domain can connect to using
Exchange ActiveSync, Outlook Web App, or Outlook Anywhere. If your
Client Access server is Internet facing, select the check box provided,
and then enter the external domain name for the Client Access server,
such as mail.cpandl.com. Click Next. Specify whether you want to join the Exchange Customer Experience Improvement Program, and then click Next. On the Readiness Checks page, Setup then checks to see whether Exchange is ready to be installed with the roles
you selected. Review the status to determine whether the organization
and server role prerequisite checks completed successfully. You must
complete any required prerequisites before continuing. After the checks
are completed successfully, click Install to install Exchange Server
2010. If
an error occurs, note the error and take the appropriate corrective
action. Otherwise, on the Completion page, click Finish. Optionally, you
can verify the installation by doing the following on the server: Start the Exchange Management Shell, and type get-ExchangeServer to display a list of all Exchange roles installed on that server. Review
the application logs for events from Exchange Setup. These events have
event IDs 1003 and 1004, with the source as MSExchangeSetup. Review
the Exchange Setup logs in the %SystemRoot%\ExchangeSetupLogs folder.
Because these logs contain standard text, you can perform a search using
the keyword error to find any setup errors that occurred.
Note:
REAL WORLD
With a new Exchange Server 2010 implementation, each new recipient
object (such as a mailbox, contact, distribution list, mailbox agent, or
mail-enabled public folder) will have a special attribute called legacyDN
that corresponds to the appropriate administrative group for the
Exchange Server 2010 server. Because of this legacyDN, Microsoft Outlook
will request a full OAB download from the Exchange Server 2010 server
for each user in this organization that logs on. In a large
organization, this could mean multiple simultaneous OAB downloads,
which, in turn, could cause high network utilization.
To complete the installation for
an initial deployment of Exchange into an organization, you need to
perform the following tasks:
For Client Access servers: If you plan to use ActiveSync for mobile messaging clients, configure direct push, authentication, and mobile devices. Configure internal and external URLs for the Outlook Web applications, Exchange ActiveSync, Exchange Control Panel, and Offline Address Book. Configure authentication and display options, as appropriate. Enable the server for POP3 and IMAP4, as appropriate.
For Edge Transport servers: Export the Edge Transport server subscription file, and import it on Hub Transport servers. If you are using Edge Transport servers with Exchange Server 2003 organizations, you must manually configure the necessary connectors, as discussed previously. Configure DNS MX resource records for each accepted domain. Configure antispam, junk e-mail, and safe sender features, as appropriate.
For Hub Transport servers: Configure
domains for which you will accept e-mail. You need an accepted domain
entry for each SMTP domain for which you will accept e-mail. Configure
Send connectors as appropriate. If you are unsure about the Send
connectors that are needed, create an Internet Send connector at a
minimum. Use the address space of "*" to route all outbound mail to the
Internet. If
you also deployed the Edge Transport server role, you need to subscribe
to the Edge Transport server so that the EdgeSync service can establish
one-way replication of recipient and configuration information from
Active Directory to the AD LDS store on the Edge Transport server. Configure DNS MX resource records for each accepted domain.
For Mailbox servers: Configure OAB distribution for Outlook 2007 and later clients. Configure OAB distribution for Outlook 2003 or earlier clients. Configure database availability groups and mailbox database copies.
For Unified Messaging servers: Configure a unified messaging dial plan, and add the server to it. Configure Unified Messaging hunt groups. Enable users for unified messaging, as appropriate. Configure your IP/VoIP gateways or IP-PBXs to work with Exchange server. Configure a Unified Messaging IP gateway in Exchange server. As desired, create auto-attendant and mailbox policies and configure additional dial plans, gateways, and hunt groups.
3. Adding, Modifying, or Uninstalling Server Roles
After you install an Exchange
server with its initial role or roles, you can add new roles or remove
existing roles. With Windows Server 2008, use Programs And Features and
follow these steps:
In
Control Panel, click the Uninstall A Program link under Programs. In
Programs And Features, select the Microsoft Exchange Server 2010 entry
to display the Change and Uninstall buttons. If
you want to add roles, click Change. Select the check boxes for the
roles you want to add. Click Next, and then follow the prompts. If
you want to remove roles, click Uninstall. Clear the check boxes for
roles you want to remove. Click Next, and then follow the prompts.
Before you can remove the
Mailbox role from a server, you must move or delete all mailboxes hosted
in mailbox databases on the server and all offline address books hosted
in public folder databases on the server. If the public folder database
is the last one in the Exchange organization—which might be the case if
you are uninstalling Exchange on a test or development server—you need
to delete the public folder database after you've emptied it.
To remove the last public
folder database in the Exchange organization, type the following command
at the Exchange Management Shell prompt:
remove-publicfolderdatabase "CORPSVR127\Public Folder Database"
-removelastallowed -confirm:$false
|
