Deploying Microsoft® Exchange Server 2010

Deploying Microsoft® Exchange Server 2010
Course 10135A Module 1: Deploying Exchange Server 2010 Module 1 Deploying Microsoft® Exchange Server 2010 1

Module Overview Overview of Exchange Server 2010 Requirements
Course 10135A Module Overview Module 1: Deploying Exchange Server 2010 Overview of Exchange Server 2010 Requirements Installing Exchange Server 2010 Server Roles Completing an Exchange Server 2010 Installation 2

Module Overview This module describes how to prepare for, and perform, an installation of Microsoft® Exchange Server The most important task in preparing for an Exchange Server installation is to ensure that the Active Directory® directory services environment is ready. Exchange Server requires an Active Directory deployment because Active Directory stores all configuration and recipient information that Exchange Server uses. This module also provides details on the Exchange Server deployment. To install Exchange Server properly for your environment, you must be aware of the server roles that Exchange Server can install. Additionally, you should be aware of the infrastructure, hardware, and software requirements for introducing Exchange Server into a messaging environment. Finally, you should know how to verify, troubleshoot, and secure the installation.

Lesson 1: Overview of Exchange Server 2010 Requirements
Course 10135A Lesson 1: Overview of Exchange Server 2010 Requirements Module 1: Deploying Exchange Server 2010 Discussion: Reviewing Active Directory Components Reviewing Active Directory Partitions How Exchange Server 2010 Uses Active Directory Reviewing DNS Requirements for Exchange Server 2010 Preparing Active Directory for Exchange Server 2010 Demonstration: Integration of Active Directory and Exchange Server 2010

Overview of Exchange Server 2010 Requirements
In this lesson, you will review the requirements for installing Exchange Server 2010. The most important requirement is the Active Directory deployment, but you also must ensure that you implement the appropriate Domain Name System (DNS) infrastructure. You also should be aware of the Exchange Server infrastructure requirements when you perform an installation, and when you need to troubleshoot deployment issues.

Active Directory Active Directory is the integrated, distributed directory service that is included with the Windows Server® 2012 R2, Windows Server® 2012, Windows Server® 2008 R2, Windows Server 2008, Windows Server 2003, and Windows® Server operating systems. Many applications, such as Exchange Server 2010, integrate with Active Directory. This creates a link between user accounts and applications, which enables single sign-on for applications. Additionally, the Active Directory replication capabilities enable distributed applications to replicate application-configuration data.

Reviewing Active Directory Components
Course 10135A Reviewing Active Directory Components Module 1: Deploying Exchange Server 2010 Active Directory components include: Domains Forests Trusts Domain controller Global catalog Sites Replication

The goal of this discussion is to ensure that you have a good understanding of Active Directory. Because Exchange Server requires Active Directory to function, it is critical that you have at least a basic understanding of the Active Directory components and processes. Definition and explanation of the functionality of the following terms: Domains. An Active Directory domain is a collection of computers that a Microsoft Windows® network administrator defines. These computers share a common directory database, security policies, and security relationships with other domains. An Active Directory domain provides access to the centralized user and group accounts that the domain administrator maintains. You can organize computer and user accounts within an Active Directory into a hierarchy based on organizational units (OUs).

Forests. A forest is a set of one or more domains that share common configuration and schema information. A tree is set of domains that share the same Domain Name System (DNS) namespace. When multiple domains exist in a forest, there is an automatic trust relationship between the domain, which enables users in one domain to access resources in another domain. There can be only one Exchange Server organization per forest. An Active Directory forest is a security boundary. By default, no security accounts outside of a forest have any access in the forest. Trusts. Trusts enable users from at trusted domain to authenticate in another trusting domain. In a forest, all domains have trusts (either direct trusts, or transitive trusts) with all other domains in the forest.

Domain controllers and global catalog servers: A domain controller holds a copy of the local domain database, which includes user accounts and computer accounts. It also is responsible for authenticating users and computers. Additionally, domain controllers respond to queries for information in Active Directory. A domain controller has directory information only for the domain of which it is a member, and does not have information about users in other domains. A global catalog server is a domain controller that also holds a subset of information from other domains in the forest. For example, a global catalog server has limited information about all users in a forest.

Active Directory sites. Active Directory sites are defined as one or more IP subnets. Typically, all of the IP subnets in a given physical location are part of the same site. Sites do not typically encompass more than one physical location. All of the computers within a single site must have a fast network connection, which is usually 10 megabits per second (Mbps) or more, between them. Active Directory replication. Active Directory replicates information between domain controllers. It replicates domain information between domain controllers in the same domain and to global catalog servers in the forest. Active Directory also replicates configuration data and the schema between all domain controllers in the same forest.

Quiz Question: Under what circumstances would an organization deploy multiple domains in the same forest? Answer: Some organizations deploy multiple domains to provide an administrative boundary. They want to be able to have one group of administrators with full control of part of the organization. Other organizations deploy additional domains to isolate replication traffic. In very large organizations, you can minimize the amount of replication traffic that is sent across a slow wide area network (WAN) link by deploying separate domains. Question: Under what circumstances might an organization deploy multiple forests? Answer: The primary reason to deploy multiple forests is to ensure that there is a complete security boundary between different parts of the organization's IT infrastructure. This could happen if an organization has multiple departments or business units that require isolation, or in the event of two organizations merging.

Question: What type of information do domains in a forest share?
Quiz Question: What type of information do domains in a forest share? Answer: All domains in a forest share the same Active Directory configuration information, Active Directory schema information, and a common global catalog. Question: What is the functionality of a domain controller? Answer: A domain controller holds a copy of the local domain database, which includes user and computer accounts, and it is responsible for authenticating users and computers. A domain controller has directory information only for the domain of which it is a member. Additionally, domain controllers respond to queries for information in Active Directory.

Quiz Question: What is a global catalog server? Answer: A global catalog server is a domain controller that also holds a subset of information from other domains in the forest. For example, a global catalog server has limited information about all users in a forest. By default, the first domain controller deployed in a forest is a global catalog server, but you also can configure other domain controller as a global catalog server. You use global catalog servers for authentication, global address list (GAL) lookups, and universal group membership lookups.

Quiz Question: What is the definition of an Active Directory site? Answer: The definition of an Active Directory site is one or more IP subnets. Typically, all of the IP subnets in a given physical location are part of the same site. Active Directory sites typically do not encompass more than one physical location. All of the computers within a single site must have a fast network connection, typically 10 megabytes per second (Mbps) or more between them. The Active Directory site configuration should be a logical representation of the physical network deployment.

Quiz Question: What is Active Directory replication?
Answer: Active Directory replicates information between domain controllers. It replicates domain information between domain controllers in the same domain and to global catalog servers in the forest. It also replicates configuration data and the schema between all domain controllers in the same forest. Question: How do Active Directory sites affect replication? Answer: Within an Active Directory site, replication of changes starts within a few seconds of the change being made on one domain controller. If an Active Directory site contains more than one domain controller, each domain controller also has at least two replication partners. Between Active Directory sites, replication can be scheduled, and happens every three hours by default. Also, all replication traffic between sites is sent through a bridgehead server in each site.

Reviewing Active Directory Partitions
Course 10135A Reviewing Active Directory Partitions Module 1: Deploying Exchange Server 2010 Partition Type Description Domain All of the objects in the directory for a domain Replicated to all domain controllers in a domain Configuration Configuration information for Active Directory and applications Replicated to all domain controllers in the entire forest Schema All object types, and their attributes, that you can create in Active Directory Application All Specific application data that the application requires Replicated to all domain controllers in the entire forest with a replica of the partition 17

Active Directory Partitions
Active Directory information falls into four types of partitions: domain, configuration, schema, and application. These directory partitions are the replication units in Active Directory. Domain Partition A domain partition contains all objects in the domain’s directory. Domain objects replicate to every domain controller in that domain, and include user and computer accounts, and groups. A subset of the domain partition replicates to all domain controllers in the forest that are global catalog servers. If you configure a domain controller as a global catalog server, it holds a complete copy of its own domain’s objects and a subset of attributes for every domain’s objects in the forest.

Configuration Partition The configuration partition contains configuration information for Active Directory and applications, including Active Directory site and site link information. Additionally, some distributed applications and services store information in the configuration partition. This information replicates through the entire forest so each domain controller has a replica of the configuration partition. Schema Partition The schema partition contains definition information for all object types and their attributes that you can create in Active Directory. This data is common to all domains in the forest, and Active Directory replicates it to all domain controllers in the forest. However, only one domain controller maintains a writable copy of the schema. By default, this domain controller, known as the Schema Master, is the first domain controller installed in an Active Directory forest.

Application Partitions An administrator or an application during installation creates application partitions manually. Application partitions hold specific application data that the application requires. The main benefit of application partitions is replication flexibility. You can specify the domain controllers that hold a replica of an application partition, and these domain controllers can include a subset of domain controllers throughout the forest. Exchange Server 2010 does not use application partitions to store information.

How Exchange Server 2010 Uses Active Directory
Course 10135A How Exchange Server 2010 Uses Active Directory Module 1: Deploying Exchange Server 2010 Schema Exchange object classes and attributes Global Catalog Exchange object attributes for mail-enabled and mailbox-enabled objects Exchange recipients Domain Configuration Exchange configuration Forests Exchange organization and Active Directory forest: one-to-one relationship

To ensure proper placement of Active Directory components in relation to computers running Exchange Server, you must understand how Exchange Server 2010 communicates with Active Directory Domain Services (AD DS) and uses Active Directory information to function. Note: The Exchange Server 2010 Edge Transport server role does not use Active Directory to store configuration information. Instead, the Edge Transport server role uses Active Directory Lightweight Directory Services (AD LDS).

Forests An Exchange Server organization and an Active Directory forest have a one-to-one relationship. You cannot have an Exchange Server organization that spans multiple Active Directory forests. You also cannot have multiple Exchange Server organizations within a single Active Directory forest. Schema Partition The Exchange Server 2010 installation process modifies the schema partition to enable the creation of Exchange Server-specific objects. The installation process also adds Exchange Server- specific attributes to existing objects.

Configuration Partition The configuration partition stores configuration information for the Exchange Server organization. Because Active Directory replicates the configuration partition among all domain controllers in the forest, configuration of the Exchange Server 2010 organization replicates throughout the forest. Domain Partition The domain partition holds information about recipient objects. This includes mailbox-enabled users, and mail-enabled users, groups, and contacts. Objects that are mailbox-enabled or mail- enabled have preconfigured attributes, such as e- mail addresses.

Global Catalog When you install Exchange Server 2010, the attributes for mail-enabled and mailbox-enabled objects replicate to the global catalog. The following is true: • The global address list (GAL) is generated from the recipients’ list in an Active Directory forest’s global catalog. • Exchange Hub Transport servers access the global catalog to find the location of a recipient mailbox when delivering messages. • Exchange Client Access servers access the global catalog server to locate the user Mailbox server and to display the global address list to Microsoft Office Outlook®, Microsoft Outlook Web App, or Exchange ActiveSync® clients.

Important: Because of the importance of the global catalog in an Exchange Server organization, you must deploy at least one global catalog in each Active Directory site that contains an Exchange 2010 server. You must deploy enough global catalog servers to ensure adequate performance. Note: Windows Server 2008 provides a new type of domain controller—a read-only domain controller (RODC). Exchange Server 2010 does not use RODCs or RODCs that you configure as global catalog servers (ROGC). This means that you should not deploy an Exchange 2010 server in any site that contains only RODCs or ROGCs.

Reviewing DNS Requirements for Exchange Server 2010
Course 10135A Reviewing DNS Requirements for Exchange Server 2010 Module 1: Deploying Exchange Server 2010 Exchange Server 2010 requires: ü SRV records to locate domain controllers ü Host records to locate other servers MX records to locate mail servers in other organizations ü DNS Record Type Example SRV _ldap._tcp.Contoso.com. IN SRV SEA-DC1.Contoso.com Host SEA-EX1.Contoso.com. IN A MX MX 10 SEA-EX1.Adatum.com

Each computer running Exchange Server must use DNS to locate Active Directory and global catalog servers. As a site-aware application, Exchange Server 2010 prefers to communicate with directory servers that are located in the same site as the computer running Exchange Server. Role of DNS Exchange Server services use DNS to locate a valid domain controller or global catalog. By default, each time a domain controller starts the Netlogon service, it updates DNS with service (SRV) records that describe it as a domain controller and global catalog server, if applicable.

SRV Resource Records SRV resource records are DNS records. These records identify servers that provide specific services on the network. For example, an SRV resource record can contain information to help clients locate a domain controller in a specific domain or site. Host Records Host records provide a host name to IP address mapping. Host records are required for each domain controller and other hosts that need to be accessible to Exchange Servers or client computers. Host records can use IPv4 (A records) or IPv6 (AAAA records).

MX Records A Mail Exchanger (MX) record is a resource record that allows servers to locate other servers to deliver Internet using the Simple Mail Transfer Protocol (SMTP). An MX record identifies the SMTP server that will accept inbound messages for a specific DNS domain. Each MX record contains a host name and a preference value. When you deploy multiple SMTP servers that are accessible from the Internet, you can assign equal preference values to each MX record to enable load balancing between the SMTP servers. You also can specify a lower preference value for one of the MX records. All messages are routed through the SMTP server that has the lower preference-value MX record, unless that server is not available.

Preparing Active Directory for Exchange Server 2010
Course 10135A Preparing Active Directory for Exchange Server 2010 Module 1: Deploying Exchange Server 2010 Setup switch Description /PrepareAD /OrganizationName: ”organizationname” Prepares the global Exchange objects Creates the Exchange universal security groups in the root domain Prepares the current domain /PrepareLegacy ExchangePermissions Required if the organization includes previous versions of Exchange Server /PrepareSchema Prepares the schema for the Exchange Server 2010 installation /PrepareDomain /PrepareDomain domainname /PrepareAllDomains Prepares the domain by creating a new global group called Exchange Install Domain Servers 31

If you do not specifically prepare Active Directory and the domain before installation, it is prepared as part of a standard installation. You might be confused about the process for upgrading Active Directory to the Windows Server® operating system or the Windows Server R2 operating system and the process for preparing the forest for Exchange Server These are two different processes, and can be completed in any order. Also, organizations can upgrade directly from Microsoft Exchange Server 2003 to Exchange Server without first upgrading to Microsoft Exchange Server The Exchange Server 2010 schema changes include the Exchange Server 2007 schema changes.

Also, it is possible to install Exchange Server 2010 in a new organization without preparing Active Directory as a separate step. This is possible when you are deploying Exchange Server in an organization with only a single Active Directory domain. However, when you are performing transition from a previous version of Exchange Server, or when you are deploying Exchange Server 2010 in an organization with multiple domains, you must prepare Active Directory before installing the first Exchange Server. The following permissions are required to run the listed commands: /PrepareSchema requires Schema Administrator and Enterprise Administrator rights. /PrepareAD requires Enterprise Administrator (and Exchange Organization Administrator rights if the Enterprise administrators have been explicitly denied access to the Exchange configuration) /PrepareDomain requires Domain Administrator rights

To install Exchange Server 2010, you need to run the Exchange Server 2010 setup command for preparing the Active Directory forest for the installation. Important: You must prepare the Active Directory forest in the same domain and the same site as the domain controller that hosts the Schema Master role. You can use the setup command with the following switches. /PrepareAD /OrganizationName:"organizationname" • Prepares the global Exchange Server objects in Active Directory, creates the Exchange Universal Security Groups in the root domain, and prepares the current domain • Must be run by a member of the Enterprise Admins group

/PreparelegacyExchangePermissions • Necessary if the organization contains Exchange Server 2003 servers • Modifies the permissions assigned to the Enterprise Exchange Servers group to allow the Recipient Update Service to run • Must be run by a member of the Enterprise Admins group

Course 2786B Preparing Active Directory for Exchange Server 2010 Module 4: Managing Security /PrepareSchema • Prepares the schema for the Exchange Server 2010 installation • Must be run by a member of the Enterprise Admins and Schema Admins groups

/PrepareDomain /PrepareDomain domainname /PrepareAllDomains Prepares the domain for Exchange Server 2010 by creating a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers • Not required in the domain where /PrepareAD is run • Can prepare specific domains by adding the domain's fully qualified domain name (FQDN), or prepare all domains in the forest • Must be run by a member of the Enterprise Admins and Domain Admins groups

Course 10135A Demonstration: Integration of Active Directory and Exchange Server 2010 Module 1: Deploying Exchange Server 2010 In this demonstration, you will review: The Exchange security groups in Active Directory The Exchange information stored in Active Directory The Exchange attributes in the Active Directory schema In this demonstration, you will use Active Directory Users and Computers to show the Exchange security groups in Active Directory. These groups are created when Active Directory is prepared for the Exchange Server installation. Do not spend much time describing the permissions assigned to each group at this point. Mention that Module 9 will provide details for each of the default groups. Also, you will use ADSIEdit.msc to show the Active Directory partitions and the Exchange Server information stored in each partition. You also will add the Schema partition to ADSIEdit.msc, and show some of the Exchange attributes that are added to the Active Directory schema. Preparation Ensure that the 10135A-VAN-DC1 virtual machine is running. Log on to the virtual machine as Administrator with the password of Pa$$w0rd. Demonstration Steps On VAN-DC1, click Start, point to Administrative Tools, and then click Active Directory Users and Computers. If necessary, expand Adatum.com, and then click the Microsoft Exchange Security Groups organizational unit. Double-click Organization Management, and then click the Members tab. The only default member of this group is the user that installed the first computer running Exchange Server. Members of this group have the necessary permissions to manage any aspect of the Exchange Server organization. Click Cancel. Double-click Recipient Management, and then click the Members tab. Verify that there are no group members. Members of this group are assigned full control permissions to manage the Exchange Server properties of user objects in Active Directory. Double-click the View-Only Organization Management group, and then click the Members tab. The members of this group are assigned read permissions to the Exchange Server container in the Active Directory configuration partition, and read permission to all domains that have Exchange Server recipients. Double-click the Discovery Management group, and then click the Members tab. The members of this group have permission to search all mailboxes in the organization for messages or content that meets specific criteria. Click Cancel. Close Active Directory Users and Computers. Click Start, and in the Search box, type adsiedit.msc, and then press ENTER. By default, when you open Active Directory Service Interfaces (ADSI) Edit in Windows Server 2008 R2, it does not display any partitions. Right-click ADSI Edit, and click Connect to. In the Connection Settings dialog box, click OK. This connects ADSI Edit to the domain partition. In the left pane, expand Default naming context [VAN-DC1.Adatum.com], and then click DC=Adatum,DC=com. The domain partition holds user accounts, computer accounts, and other domain specific configuration information. Objects with names that start with an OU are organizational units. Objects with names that start with CN are containers or other objects, such as users. You can verify the object type by looking at the Class column. In the right pane, double-click CN=Users. Notice that in the Users container, there are users and groups. Double-click OU=ITAdmins. Right-click CN=Andreas Herbinger, and then click Properties. This shows the attributes and values that are part of the Andreas Herbinger user object. In the Connection Settings dialog box, in the Connection Point section, in the Select a well known Naming Context list, click Configuration, and then click OK. This connects ADSI Edit to the configuration partition. In the left pane, expand Configuration[VAN-DC1.ADatum.com], and then click CN=Configuration,DC=Adatum,DC=com. This displays the containers in the configuration partition of Active Directory. The containers contain configuration data used by Active Directory, applications, and services. Double-click CN=Partitions. This container holds a list of the Active Directory partitions. In the left pane, click CN=Sites. This container holds sites and their related configuration objects. Expand CN=Services, expand CN=Microsoft Exchange, and then click CN=AdatumOrg. In the right pane, you can see the containers that hold the various configuration information for Exchange Server. Double-click CN=Address Lists Container. This container stores configuration information for all address lists. In the left pane, click CN=Client Access. This container holds configuration information for the Autodiscover process. In the left pane, expand CN=Administrative Groups, expand CN=Exchange Administrative Group (FYDIBOHF23SPDLT), expand CN=Servers. This container holds the Exchange Server objects. In the Connection Settings dialog box, in the Connection Point section, in the Select a well known Naming Context list, click Schema, and then click OK. This connects ADSI Edit to the schema partition. In the left pane, expand Schema [VAN-DC1.ADatum.com], and then click CN=Schema,CN=Configuration,DC=Adatum,DC=com. The schema container holds a list of classes and attributes that define the objects in Active Directory. In the right page, click CN=ms-Exch-2003-Url, and then scroll down. Notice that many Exchange-specific attributes and classes have been added to the Active Directory schema. Close ADSI Edit. Question: How do you assign permissions in your Exchange organization? How will you assign permissions using the Exchange security groups? Answers will vary. Most small organizations will just have one set of administrators who will have full control of the Exchange organization. They can address the permission requirements by just adding the group to the Organization Management group. Organizations with more complex security requirements will need to use the other groups, or use custom role-based access control (RBAC) management roles. Question: Which Active Directory partition would you expect to contain the following information? User's address: Answer – Domain partition or global catalog. Exchange connector for sending to the Internet: Answer – Configuration partition. Exchange Server configuration: Answer – The configuration partition contains the Exchange Server-specific configuration information, but the Exchange Server computer object is also located in the domain partition. 38

Lesson 2: Installing Exchange Server 2010 Server Roles
Course 10135A Lesson 2: Installing Exchange Server 2010 Server Roles Module 1: Deploying Exchange Server 2010 Overview of Server Roles in Exchange Server 2010 Deployment Options for Exchange Server 2010 Hardware Recommendations for Combining Server Roles Infrastructure Requirements for Exchange Server 2010 Server Requirements for Exchange Server 2010 Considerations for Deploying Exchange Server 2010 as a Virtual Machine Process for Installing Exchange Server 2010 Unattended Installation Options 39

Installing Exchange Server 2010 Server Roles
Before you install Exchange Server 2010, you need to understand the concept of Exchange Server server roles. Each server role provides a specific set of functionality that an Exchange Server organization requires. When you install Exchange Server 2010, you can install all server roles on the same computer, except for the Edge Transport server role. Alternately, you can distribute the roles across multiple computers. After you decide which server role to deploy in each Exchange server, you must ensure that the network infrastructure and servers are ready for the Exchange Server 2010 installation.

Overview of Server Roles in Exchange Server 2010
Course 10135A Overview of Server Roles in Exchange Server 2010 Module 1: Deploying Exchange Server 2010 In Exchange Server 2010, servers are installed with specific functional roles: Hub Transport Server role Mailbox Server role Edge Transport Server role Client Access Server role Unified Messaging Server role

Overview of Server Roles in Exchange Server 2010
Exchange Server 2010 provides functionality that falls into five separate server roles. When you install Exchange Server 2010, you can select one or more of these roles for installation on the server. Large organizations might deploy several servers with each role, whereas a small organization might combine all server roles except the Edge Transport server role on one computer. Important: Exchange Server 2010 server roles are a logical grouping of features and components that perform a specific function in the messaging environment. You can install all server roles, except the Edge Transport server role, on the same physical computer.

Exchange Server 2010 Server Roles
The following server roles are included in Exchange Server 2010: • Hub Transport server role. The Hub Transport server role is responsible for message routing. The Hub Transport server performs message categorization and routing, and handles all messages that pass through an organization. You must configure at least one Hub Transport server in each Active Directory site that contains a Mailbox server or a Unified Messaging server, and the server running the Hub Transport server role must be a member of an Active Directory domain.

Mailbox server role. The Mailbox server role is responsible for managing mailbox and public folder databases. Mailboxes and public folders reside on the Mailbox servers. Mailbox servers contain mailbox and public folder databases. You can enable high availability by adding mailbox servers to a Database Availability Group (DAG). Because Mailbox servers require Active Directory access, you must install this role on a member server in an Active Directory domain.

Edge Transport server role. The Edge Transport server role is the Simple Mail Transport Protocol (SMTP) gateway server between your organization and the Internet. To ensure security, you should deploy the computer that runs the Edge Transport server role in a perimeter network, and it should not be a member of your internal Active Directory forest. Because the Edge Transport server is not part of an Active Directory domain, it cannot use Active Directory to store configuration information. Instead, it uses AD LDS on Windows Server computers to access recipient and configuration information.

Client Access server role. The Client Access server role enables connections from all available client protocols to the Exchange Server mailboxes. You must assign at least one Client Access server in each Active Directory site that contains a Mailbox server. Client protocols that connect through a Client Access server include: • Messaging Application Programming Interface (MAPI) clients • Outlook Web App clients (OWA) • Post Office Protocol (POP) and Internet Message Access Protocol (IMAP) clients • Outlook Anywhere, which is known as remote procedure call (RPC) over HTTP in Exchange Server 2003 • Exchange ActiveSync clients

Unified Messaging server role. The Unified Messaging server role provides the foundation of services that integrate voice and fax messages into your organization’s messaging infrastructure. This role requires the presence of three server roles: Hub Transport, Client Access, and Mailbox. The Unified Messaging server provides access to voice messages and faxes.

Deployment Options for Exchange Server 2010
Course 10135A Deployment Options for Exchange Server 2010 Module 1: Deploying Exchange Server 2010 Small Organization Medium-Size Organization Large Organization

Deployment Options for Exchange Server 2010
You can deploy the server roles in Exchange Server in several different scenarios, depending on an organization’s size and requirements. If you are an administrator, it is important to understand the deployment scenarios when you plan an Exchange Server system. The deployment scenarios are organized into small, medium, and large organizations. The suggested configuration is typical, but not sufficient for every scenario. For example, some medium-size organizations may desire multiple servers for redundancy.

Exchange Server 2010 Editions
Exchange Server 2010 is available as Standard Edition and Enterprise Edition. The Standard Edition should meet the messaging needs of small and medium corporations, but also may be suitable for specific server roles or branch offices. The Enterprise Edition is for large enterprise corporations, and enables you to create additional databases apart from including other advanced features.

Exchange Server 2010 Editions
Feature Standard Enterprise Database Support Five databases 100 databases Database Storage Limit No software storage limit; storage limit is hardware dependent DAG (Database Availability Group ) membership Supported

Exchange Server 2010 Client Access Licenses
Exchange Server 2010 has two client-access license (CAL) options: • Exchange Server Standard CAL. Provides access to , shared calendaring, Outlook Web App, and ActiveSync. • Exchange Server Enterprise CAL. Requires a standard CAL, and provides access to additional features such as unified messaging, per-user and per-distribution list journaling, managed custom e- mail folders, and Forefront® Protection for Exchange Server.

Hardware Recommendations for Combining Server Roles
Course 10135A Hardware Recommendations for Combining Server Roles Module 1: Deploying Exchange Server 2010 You can combine all server roles, except the Edge Transport server role, on one server Component Recommendation Processor cores Minimum: 2 Recommended: 8 Maximum: 24 Plan on using half the processor cores for the mailbox server role Memory Recommended: 8 GB plus 2-10 MB per mailbox Maximum: 64 GB When combining server roles, reduce the maximum number of mailboxes by 20% You can combine server roles with Mailbox servers that are DAG members

You can install all roles, except the Edge Transport server role, on a single computer. When you design the hardware configuration for servers on which you install multiple server roles, consider the following recommendations: • You should plan for at least two processor cores, at a minimum, for a server with multiple server roles. The recommended number of processor cores is eight, while 24 is the maximum recommended number. • You should design a server with multiple roles to use half of the available processor cores for the Mailbox role and the other half for the Client Access and Hub Transport roles. • You should plan for the following memory configuration for a server with multiple server roles: 8 gigabytes (GB) and between 2 megabytes (MB) and 10 MB per mailbox. This can vary based on the user profile and the number of storage groups. We recommend 64 GB as the maximum amount of memory you need.

To accommodate the Client Access and Hub Transport server roles on the same server as the Mailbox server role, you should reduce the number of mailboxes per core calculation, based on the average client profile by 20 percent. • You can deploy multiple Exchange server roles on a mailbox server that is a DAG member. This means that you can provide full redundancy for the Mailbox, Hub Transport, and Client Access server roles on just two Exchange servers.

Infrastructure Requirements for Exchange Server 2010
Course 10135A Infrastructure Requirements for Exchange Server 2010 Module 1: Deploying Exchange Server 2010 Infrastructure Component Requirements Active Directory Schema master must be running Windows Server 2003 (SP2), Windows Server 2008, or Windows Server 2008 R2 All global catalog servers must be running Windows Server 2003 (SP2), Windows Server 2008, or Windows Server 2008 R2 Domain and forest functional levels must be at least Windows 2003 DNS Must be configured to enable domain controller and global catalog server name resolution

Before you deploy Exchange Server 2010 in your organization, you need to ensure that your organization meets Active Directory and DNS requirements. Active Directory Requirements You must meet the following Active Directory requirements before you can install Exchange Server 2010: • The domain controller that is the schema master must have Windows Server 2003 Service Pack 1 (SP1) or later, Windows Server 2008, or Windows Server 2008 R2 installed. By default, the schema master runs on the first Windows domain controller installed in a forest. • In each of the sites where you deploy Exchange Server 2010, at least one global catalog server must be installed and run Windows Server 2003 SP1 or later, Windows Server 2008, or Windows Server 2008 R2. • The Active Directory domain and forest functional levels must run Windows Server 2003, at the minimum.

DNS Requirements Before you install Exchange Server 2010, you must ensure that your organization meets the following requirements: • You must configure DNS correctly in your Active Directory forest. All servers that run Exchange Server 2010 must be able to locate Active Directory domain controllers, global catalog servers, and other Exchange servers.

Server Requirements for Exchange Server 2010
Course 10135A Server Requirements for Exchange Server 2010 Module 1: Deploying Exchange Server 2010 Resource Requirements Processor Intel 64-bit architecture AMD64 architecture Memory 2 gigabytes (GB) minimum Additional memory required based on server role and load Disk 1.2 GB free disk space for Exchange Server files 200 megabytes (MB) free on the system drive File System NTFS file system for all drives Software requirements: 64-bit edition of Windows Server 2008, Windows Server 2008 R2 Standard, or Enterprise Edition AD DS management tools Microsoft .NET Framework 3.5 Windows Remote Management 2.0 Windows PowerShell version 2.0 Additional components based on server roles

Exchange Server 2010 requires a minimum level of hardware, and specific software, before you can install it. Hardware Requirements You can deploy Exchange Server 2010 only on 64-bit versions of Windows Server 2008 or Windows Server 2008 R2 running on 64-bit hardware.

Resource Requirement Processor • x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T). • AMD processor that supports the AMD64 platform. • Intel Itanium IA64 processors not supported. Memory A minimum of 2 GB of system memory, plus 2 to 6 MB per mailbox. This recommendation is based on the number of mailbox databases and the user-usage profile.

Disk 1.2 GB disk space for Exchange Server files and 200 MB of free disk space on the system drive. File system Drives formatted with NTFS file system—for all Exchange Server—related volumes. Important: Exchange Server 2010 is available only in 64-bit versions, which means that you can install all components, including the Exchange Management tools, only on 64-bit operating systems.

Exchange Server 2010 Prerequisite Software All Exchange Server 2010 servers must have the following software installed: • Active Directory Domain Services (AD DS) management tools, which is required on all Exchange Server 2010 servers, except for Edge Transport servers • Microsoft .NET Framework 3.5 (SP1) or later • Windows Remote Management (WinRM) • Windows PowerShell™ Version 2

Important: The Net.Tcp Port Sharing Service must be configured to start automatically before starting the Exchange server installation Server Role Installation Requirements Each server role in Exchange Server 2010 has slightly different installation requirements. All server roles, except for the Edge Transport server role, require some Web Server components, such as Internet Information Services (IIS).

Considerations for Deploying Exchange Server 2010 as a Virtual Machine
Course 10135A Considerations for Deploying Exchange Server 2010 as a Virtual Machine Module 1: Deploying Exchange Server 2010 You can deploy all Exchange server roles, except Unified Messaging servers, on virtual machines running on a supported virtualization platform Because Exchange Server 2010 can be scaled to fully utilize the server hardware, large organizations might not consider it is as important to virtualize Exchange Servers. Some virtualization products provide options for enabling high availability at the virtual machine level. Because Exchange Server provides several options for enabling high availability, you can deploy a highly available Exchange organization without using the high-availability options available in the virtualization products. In particular, if you deploy a DAG, and configure multiple copies of the mailbox databases, you should not use virtual machine-level high availability. Question: What are the benefits of virtualizing servers? Answer: Many organizations are using virtualization to significantly increase server utilization while decreasing hardware and power costs. Question: Discuss the benefits and disadvantages of using virtualization with Exchange Server 2010. Answer: Because you can add several thousand mailboxes to an Exchange Server 2010 server, you typically can utilize the hardware fully without virtualization. With the Exchange Server 2010 high availability models, this option becomes even more feasible. Emphasize that organizations should plan the hardware for virtual machines using the same criteria that they use for planning hardware for physical servers. References Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments: Windows Server Virtualization Validation Program Design the Exchange server deployment to fully utilize the server resources Consider the high-availability features in Exchange Server 2010 as an alternative to highly available virtual machines Virtualization high availability options are not recommended for Mailbox servers Design virtual hardware using the same criteria as physical hardware

Considerations for Deploying Exchange Server 2010 as a Virtual Machine
Because Exchange Server 2010 can be scaled to fully utilize the server hardware, large organizations might not consider it is as important to virtualize Exchange Servers. Some virtualization products provide options for enabling high availability at the virtual machine level. Because Exchange Server provides several options for enabling high availability, you can deploy a highly available Exchange organization without using the high-availability options available in the virtualization products. In particular, if you deploy a DAG, and configure multiple copies of the mailbox databases, you should not use virtual machine-level high availability.

Process for Installing Exchange Server 2010
Course 10135A Process for Installing Exchange Server 2010 Module 1: Deploying Exchange Server 2010 To install Exchange Server 2010: 1 Install prerequisite software 2 Run setup.exe from the installation source 3 Choose the option to install Exchange Server 2010 4 Install the Exchange language packs 5 Choose the installation type 6 Provide the Exchange organization name Choose the option to enable Outlook 2003 or earlier clients 7 8 Configure the Client Access server external name

The Exchange Server 2010 graphical setup program guides you through the installation process. The following steps provide a high-level installation overview: 1. Install the prerequisite software. If you install Exchange Server on Windows Server 2008 R2, the correct versions of Windows PowerShell and Windows Remote Management are installed already. 2. To start the installation, run setup.exe from the installation source. The Setup program checks to ensure that the correct software is installed on the computer. 3. After you finish installing all the required software, you can proceed with the installation of Exchange Server 2010.

4. Exchange Server 2010 provides the option to install additional language packs that will enable the management tools to display in languages other than English. You can choose to install the language packs during the installation. 5. The Installation Type page of the wizard presents you with the option to perform a Typical Exchange Server Installation or a Custom Exchange Server Installation. The typical installation option installs the Hub Transport server role, the Client Access server role, the Mailbox server role, and the Exchange Management tools. The custom installation option allows you to choose the roles you want to install.

6. If this is the first Exchange Server 2010 server in the deployment, and you do not run setup /PrepareAD, you are prompted for the Exchange organization name. 7. If you chose the Mailbox server role, the Exchange Setup program prompts you if you have any Office Outlook or Entourage clients in the organization. If you choose Yes, Exchange Setup creates the public folders required by these clients for the offline address book and for sharing calendar information. 8. If you choose to install the Client Access server role, you also can configure the external domain name for the Client Access server. Clients use this external domain name to connect to the server from the Internet.

Unattended Installation Options
Course 10135A Unattended Installation Options Module 1: Deploying Exchange Server 2010 Parameter Options Description /mode Install, Upgrade, Uninstall, Recoverserver Default: Install Specifies the Setup program actions /roles HubTransport, HT, H ClientAccess, CA, C EdgeTransport, ET, E Mailbox, MB, M UnifiedMessaging, UM, U ManagementTools, MT, T Specifies which roles to install /ServerAdmin User or group Specifies an account with Exchange Server permission /NewProvisionedServer Server name /ServerAdmin: User Creates Exchange computer account for delegated installation

You can use the command line to perform an unattended Exchange Server 2010 installation. When you use the command line, you can use parameters to install specified roles or configure other setup options. Note: To run an unattended installation with setup parameters, you must run setup.com or setup rather than setup.exe. To see all the parameters available for use with setup.com, run the command with the /? parameter.

The syntax for this command is: Setup.com [/roles:<roles to install>] [/mode:<setup mode>] [/console] [/?][/targetdir:<destination folder>] [/prepareAD] [/domaincontroller] For example, if you want to install Exchange Server into the default path, and specify the roles of Hub Transport, Client Access, and Mailbox, you would enter the command: Setup.com /r:H,M,C

Lab A: Installing Exchange Server 2010
Course 10135A Lab A: Installing Exchange Server 2010 Module 1: Deploying Exchange Server 2010 Installing Exchange Server 2010

Lesson 3: Completing an Exchange Server 2010 Installation
Course 10135A Lesson 3: Completing an Exchange Server 2010 Installation Module 1: Deploying Exchange Server 2010 Demonstration: Verifying an Exchange Server Installation Troubleshooting an Exchange Server 2010 Installation Finalizing the Exchange Server Installation 75

Completing an Exchange Server 2010 Installation
After you install the necessary server roles in Exchange Server 2010, you should verify the installation and perform post-installation tasks, including securing Exchange Server 2010 and installing additional third-party software, if necessary. This lesson describes the post-installation tasks that you should perform.

Demonstration: Verifying an Exchange Server 2010 Installation
Course 10135A Demonstration: Verifying an Exchange Server 2010 Installation Module 1: Deploying Exchange Server 2010 In this demonstration, you will see how to: Configure post-installation services View the default folder structure View setup logs Test and administrative tools Preparation Ensure that the 10135A-VAN-DC1 and the 10135A-VAN-EX1 virtual machines are running. Log on to the virtual machines as Administrator with the password Pa$$w0rd. Important: When you start the virtual machines, ensure that you start 10135A-VAN-DC1 first, and that it starts fully before you start any other virtual machines. If you receive a notification that one or more services failed to start when starting a virtual machine, open the Services console on the virtual machine, and ensure that all Microsoft Exchange services that are configured to start automatically are started. On VAN-EX1, click Start, point to Administrative Tools, and then click Services. Scroll down to the Microsoft Exchange services, and expand the name column, so that you can read the service names. These are all of the services that Exchange Server installs. The services that Exchange Server installs vary depending on the Exchange Server roles that are installed on the server. Close Services. Click Start, right-click Computer, and then click Open. Browse to C:\ExchangeSetupLogs. Double-click ExchangeSetup.log to open it. This log file contains information about the status of prerequisite and system-readiness checks that Exchange Server performs before the installation begins. This log also contains information about every task that occurs during the Exchange Server setup, and is the most complete log available for troubleshooting installation errors. Close Notepad. Describe some of the other files in this folder: ExchangeSetup.msilog. This file contains information about the extraction of the Exchange Server code from the installer file. Install-AdminToolsRole-[date and time].ps1. Setup generates this file, which contains the steps that Exchange Server uses to install the Exchange administration tools. Install-BridegeheadRole-[date and time].ps1. Setup generates this file, which contains the steps that Exchange Server uses to install the Hub Transport server role. Install-ClientAccessRole-[date and time].ps1. Setup generates this file, which contains the steps that Exchange Server uses to install the Client Access server role. Install-ExchangeOrganization-[date and time].ps1. Setup generates this file, which contains the steps that Exchange Server uses to create the Exchange Server organization. Install-MailboxRole-[date and time].ps1. Setup generates this file, which contains the steps that Exchange Server uses to install the Mailbox server role. InstallSearch.msilog. This file contains information about the extraction of the Search service that Exchange Server uses. Note: Other .msilog or .ps1 files may exist in this folder, depending on which roles you install on this server. Browse to C:\Program Files\Microsoft\Exchange Server\V14. Describe the contents of the folders: Bin. Applications and extensions that you can use to manage Exchange Server. ClientAccess. Configuration files for the Client Access server role. ExchangeOAB. Contains the Exchange Offline Address book files that Exchange Web Services makes available. GroupMetrics. Contains information about distribution groups and distribution-group membership that MailTips uses. Logging. Various log files. Mailbox. Schema files, .dll files, database files, and database log files for the mailbox databases and public folder databases. Public. Several .dll and .xml files. RemoteScripts. Contains a single script used only by the Exchange Management Console. Scripts. Exchange Management Shell scripts that you can use to retrieve anti-spam statistics and perform other tasks. Setup. Extensible Markup Language (XML) configuration files and data. TransportRoles. Folders and files that the Hub Transport Server role uses. Working. Contains an empty folder. Close Windows Explorer. Click Start, point to All Programs, click Microsoft Exchange Server 2010, and then click Exchange Management Console. Click OK to acknowledge that the servers are not licensed. In the left pane, expand Microsoft Exchange On-Premises, and then click Server Configuration. The server you just installed should always appear here, as should the list of roles you installed. In the left pane, click Toolbox. The Toolbox node includes tools that you can use to troubleshoot and repair Exchange Server. During installation, the only relevant tool is the Microsoft Exchange Server Best Practices Analyzer Tool. In the left pane, click Recipient Configuration. This shows all of the users and groups that are mailbox users or mail-enabled. Right-click Recipient Configuration, and then click New Mailbox. Accept the default setting of User Mailbox, and then click Next. Accept the default setting of New user, and then click Next. In the First name box, type TestUser. In the User logon name (User Principal Name) box, type TestUser. In the Password and Confirm password boxes, type Pa$$w0rd, and then click Next. 21. On the Mailbox Settings page, type TestUser as the Alias, and click Next to accept the default mailbox settings. 22. On the Archive Settings page, click Next. 23. Click New to create the new mailbox. 24. Click Finish. 25. Close the Exchange Management Console. 26. Click Start, point to All Programs, and then click Internet Explorer. In the Address bar, type and then press ENTER. In the Domain\User name box, type Adatum\TestUser. 29. In the Password box, type Pa$$w0rd, and then click Sign in. 30. Click OK to accept the default configuration for Outlook Web App. Create a new message and send it to TestUser: Click New in the toolbar. In the To box, type TestUser. In the Subject box, type Test Message. Click Send. 32. Verify the message was received by clicking Check Messages in the toolbar. 33. Close Microsoft Internet Explorer®. 77

Troubleshooting an Exchange Server 2010 Installation
Course 10135A Troubleshooting an Exchange Server 2010 Installation Module 1: Deploying Exchange Server 2010 To troubleshoot Exchange Server 2010 setup: ü Check the setup and event logs for errors ü Verify the server hardware and software requirements ü Verify DNS name resolution Verify Active Directory functional levels and permissions ü 78

Troubleshooting an Exchange Server 2010 Installation
The Exchange Server installation should complete successfully if you meet all prerequisites. However, if the installation does not complete properly, it is important for you to follow a consistent troubleshooting process. Troubleshooting Process Each time you troubleshoot any application or service, you should follow a consistent process, as this ensures that you do not miss steps and that problems are resolved quickly.

Potential Problems and Resolutions
Net.TCP Port Sharing Service not set to start automatically. You must set this service to start automatically. • Insufficient disk space. Your server might not have the necessary disk space to install Exchange Server To resolve this, either increase your server’s disk space or remove unnecessary files to create more free space. • Missing software components. Your server might not have all of the required software components for the server roles you want to implement. To resolve this, determine the required software components, download them if necessary, and install them.

• Incorrect DNS configuration. Exchange Server relies on global catalog servers to perform many operations, and uses DNS to find global catalog servers. If the DNS configuration is incorrect, your server might not be able to find a global catalog server. To verify the problem, use the dcdiag tool. To resolve the problem, ensure that the Exchange server and domain controllers are all using the appropriate internal DNS servers. • Incorrect domain functional level. All domains with Exchange Server 2010 recipients or servers must be at Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003 functional level. To resolve this problem, raise the domain functional level to the appropriate functional level.

Insufficient Active Directory permissions. When you install Exchange Server 2010, you need sufficient permissions to extend the Active Directory schema and modify the Active Directory configuration partition. To perform the initial schema extension, you must be a member of the Enterprise Admins and Schema Admins groups. • Insufficient Exchange permissions. To install Exchange Server 2010 into an existing organization, you must be a member of the Exchange Admins group. You also must run Setup.exe with the /PrepareLegacyExchangePermissions switch. Wait for replication throughout the Exchange Server organization before you continue.

Finalizing the Exchange Server Installation
Course 10135A Finalizing the Exchange Server Installation Module 1: Deploying Exchange Server 2010 Configure Exchange Server security ü Install and configure additional software ü Configure settings that are specific to server roles ü

Module Review and Takeaways
Course 10135A Module Review and Takeaways Module 1: Deploying Exchange Server 2010 Review Questions Common Issues and Troubleshooting Tips Real-World Issues and Scenarios Best Practices

Deploying Microsoft® Exchange Server 2010

Similar presentations

Presentation on theme: "Deploying Microsoft® Exchange Server 2010"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Deploying Microsoft® Exchange Server 2010

Similar presentations

Presentation on theme: "Deploying Microsoft® Exchange Server 2010"— Presentation transcript:

Similar presentations

About project

Feedback