Exchange Server 2013 管理实战指南

需积分: 9 125 浏览量更新于2024-07-18 1 收藏 25.57MB PDF 举报

"Pro Exchange Server 2013 Administration" 本书是针对有一定经验的IT专业人员，特别是Exchange管理员，旨在指导他们如何在本地部署和管理Exchange Server 2013。书中涵盖了从基础到高级的各种主题，以帮助读者熟练掌握这一企业级邮件服务器的运维技能。 1. **介绍Exchange Server 2013** - 第一章介绍了Exchange Server 2013的基本概念，包括其架构、设计目标和主要改进，如统一的消息传递平台、增强的性能和可扩展性。 2. **安装Exchange Server 2013** - 第二章详细讲解了Exchange Server 2013的安装过程，包括系统需求、预安装准备、安装选项以及安装后的验证步骤，让读者了解如何在企业环境中正确部署Exchange Server。 3. **共存与迁移** - 第三章讨论了与其他Exchange版本（如Exchange 2007、2010）的共存策略，以及如何进行升级或迁移项目，确保业务连续性。 4. **客户端访问服务器** - 第四章专注于客户端访问服务器的角色，解释了owa (Outlook Web App)、ActiveSync和其他客户端协议的工作原理，以及如何配置和优化这些服务以提高用户访问体验。 5. **邮箱服务器** - 第五章深入探讨了邮箱服务器，包括邮箱数据库的管理、存储策略、高可用性和灾难恢复方案，确保数据安全和高效运行。 6. **管理Exchange Server 2013** - 第六章介绍了Exchange Server的日常管理任务，如用户和组的管理、权限分配、策略制定以及日志和报告工具的使用。 7. **备份、恢复与灾难恢复** - 第七章详细阐述了Exchange Server 2013的备份策略、恢复技术，以及在灾难发生时的应对措施，强调了数据保护的重要性。 8. **监控Exchange Server 2013** - 第八章讲解了监控工具和方法，如性能计数器、日志分析和警报设置，帮助管理员及时发现并解决性能问题。 9. **故障排查Exchange 2013** - 最后一章提供了Exchange Server 2013的故障排查指南，包括常见的问题诊断和解决步骤，帮助读者快速定位并修复问题。此外，书中的作者和技术审阅者都具有丰富的实践经验，他们分享了关于Exchange Server 2013的实用技巧和最佳实践。考虑到Exchange Server 2013持续更新，书中也提醒读者关注累积更新，以获取最新的功能和改进。通过这本书的学习，读者可以全面提高在Exchange Server 2013环境中的管理能力。

CHAPTER 1 ■ INTRODUCTION TO EXCHANGE SERVER 2013

Exchange Server 2013 Architecture

Exchange Server 2013 at RTM is using so-called building blocks; there are two such building blocks:

• Client Access Server The Client Access server (CAS) is the server where all clients connect.

The CAS consists of three parts: client access front end (CAFE), front end transport (FET), and

the UM call router (UMCR). The CAS performs authentication and proxies the client request

to the appropriate Mailbox server, where the actual client mailbox is located. The CAS in

Exchange Server 2013 is sometimes also referred to as the front end, although according to the

book, UMCR is not officially a front end.

• Mailbox Server The Mailbox server is the server where the actual mailbox data is stored.

Clients do not access the Mailbox server directly; all requests are routed through the CAS.

The Mailbox server in Exchange Server 2013 is sometimes also referred to as the back end.

In Exchange Server 2007 and Exchange Server 2010, the Hub Transport server and the Unified Messaging server

were also dedicated servers. These four servers were tightly coupled and used RPC for inter-server communication.

Although this works fine, it presents some challenges when it comes to a multi-datacenter environment and to site

resiliency. One of the design goals for Exchange Server 2013 was to remove the tight coupling of the server roles and

replace them with a more loosely coupled mechanism.

The four servers are no longer available in separate server roles, but are incorporated into the Mailbox server role.

When installing the latter, note that the Hub Transport and Unified Messaging functions are automatically installed.

The Mailbox server contains most of the business logic of Exchange Server 2013, and this is the server where all the

processing takes place for all mailboxes located on that Mailbox server.

The Client Access Server

The Client Access server (CAS) performs only authentication of a client request, and after authentication, the request

is proxied to the Mailbox server where the destination mailbox is located. The CAS in itself does not perform any

processing with respect to mail data. Compared to previous versions of Exchange Server CAS, in Exchange Server

2013 it is basically a “thin” server. According to Microsoft, its connections are stateless (not clueless, though). But the

connections are not really stateless, because the SSL connection is terminated at the CAS and then processed. If a CAS

goes offline, all connections are terminated and they have to be set up again on another CAS (which would not be

the case in a true stateless setup). The reason that Microsoft calls it “stateless” is that there’s no persistent storage on

Exchange Server 2013 CAS.

Unlike Exchange Server 2010 and Exchange Server 2007, the CAS no longer communicates with the Mailbox

server using RPC; the original client request is instead proxied to the Mailbox server. If the initial request from the

client to the Client Access server is from Outlook Web App (so HTTPS), the protocol between the CAS and the Mailbox

server is also HTTPS. Note that the request from Internet to the CAS is using the regular port 443, but that the proxied

request to the Mailbox server is using port 444.

CHAPTER 1 ■ INTRODUCTION TO EXCHANGE SERVER 2013

This architecture means that the actual Exchange Server 2013 servers are now loosely coupled, which offers huge

advantages when multiple offices or multiple datacenters are used.

Note ■ The SMTP protocol can be seen as a client in this scenario, as well. Outbound SMTP can be also routed through

the Client Access server.

As stated before, the CAS is a “thin” server and does not store any information from the sessions, except for the

default logging in IIS, of course. This is true for both regular client requests and SMTP requests. SMTP requests are

accepted on the CAS, but the message itself is not stored on the CAS as it is on an Exchange 2010 Edge Ttransport

server, for example.

The front-end transport service that is responsible for handling SMTP messages on the CAS doesn’t store

messages on the server itself, but passes the SMTP messages directly to the appropriate Mailbox server where

the intended recipient’s mailbox is located, or to a downlevel Hub Transport server if the recipient is located on a

downlevel Mailbox server. The front-end transport service does not inspect message content.

Because of the stateless connections from clients, the load-balancing solution needed when multiple CAS are

used doesn’t have to be a layer 7 load balancer, as used to be the case in Exchange 2010; Exchange Server 2013 works

fine with (much simpler) layer 4 load balancers.

The Mailbox Server

The Mailbox server is where all the processing regarding messages takes place. Clients connect to the CAS, but the

requests are proxied or redirected to the appropriate Mailbox server. All message rendering takes place on the Mailbox

server, in contrast to Exchange Server 2010, where all rendering took place on the CAS. To achieve this, there’s also a

CAS component on the Mailbox server.

SMTP Transport is now also located on the Mailbox server and consists of three separate services:

The Transport service•

The Mailbox Transport Delivery service•

The Mailbox Transport Submission service.•

Figure 1-5. The front-end and back-end architecture in Exchange Server 2013

CHAPTER 1 ■ INTRODUCTION TO EXCHANGE SERVER 2013

The Transport service can be seen as the successor to the “old” Hub Transport server, and it handles all SMTP

message flow within the organization, such as routing, queueing, bifurcation, message categorization, and content

inspection. Important to note is that the Transport service never communicates directly with the Mailbox databases.

Communication between the Transport service and the Mailbox database is performed by the Mailbox Transport

Delivery service and the Mailbox Transport Submission service. These services connect directly to the Mailbox

database (using RPC!) to deliver or retrieve messages from the Mailbox database. As with the Front End Transport

Service, the Mailbox Transport service does not queue any messages on the Mailbox server; the Transport service

(notice the absence of the word mailbox) does queue information on the Mailbox server. (The transport mechanism is

covered in detail in Chapter 3.)

The most important part of this, of course, is the mailbox components that run on the Mailbox server. The

information store, or store process, is the process responsible for handling all mailbox transactions and for storing

these transactions in a Mailbox database. The database is not a relational database like SQL Server; it’s running on its

own engine, the extensible storage engine or ESE. The ESE databases have been fully optimized for the past 15 years

for use with Exchange Server, so they perform very well and also are very reliable. The ESE database is a transactional

database using a database, log files, and a checkpoint file. (I’ll get back to database internals in Chapter 4.)

The engine in Exchange Server 2013 is completely rewritten in managed code (i.e. C#) and in Exchange Server

2013, there’s now one store process for each Mailbox database. So if one store process can crash, resulting in the

accompanying database crash as well, the other databases on the server are unaffected.

The Exchange Replication service is another important service running on the Mailbox server. This service is

responsible for replicating mailbox data from one Mailbox database on one Mailbox server to a Mailbox database

running on another Mailbox server. The collection of Mailbox server replication data between sources is called the

database availability group, or DAG. A DAG can take up to 16 Mailbox servers where there’s only one active Mailbox

database copy, and up to 15 passive Mailbox database copies.

The database in Exchange Server 2013 has been greatly improved compared to earlier versions. For instance,

Exchange Server 2013 now generates 50% fewer IOs per second (IOPS compared with Exchange Server 2010),

making it now possible to store multiple databases, including its log files, on one physical disk. This is something that

Microsoft never recommended doing in the past, but now it is a viable solution. Of course, this is recommended only

when there are multiple copies of a Mailbox database available for recovery purposes.

Clients

Clients are the most important part of every messaging system, since this is the interface the users are using. In Exchange

Server 2013, there are a lot of major improvements and changes that are worth noticing.

Widely used are Outlook clients, but Outlook clients also uses Autodiscover and Exchange Web Services (EWS)

for communicating with Exchange Server 2013. OWA and Activesync clients are also widely used. All three are

running on the HTTPS protocol.

The last two client protocols are POP3 and IMAP4; these are legacy protocols but still in use by (old) clients or

sometimes by business applications.

Outlook Clients

One of the most important changes in Exchange Server 2013 is that Outlook no longer uses direct MAPI (RPC over

TCP); Exchange Server 2013 is accessible only using Outlook Anywhere, with RPC rather than HTTPS. This change

reflects the loose coupling of the Exchange Server 2013 roles, as explained in the previous section. Direct MAPI is

pretty rigid and it requires a fast and reliable network connection. Also, routing problems that occur when multiple

datacenters are used contributed to this decision. So, only RPC over HTTPS, also known as Outlook Anywhere, is used

by Outlook clients, both internally and externally.

CHAPTER 1 ■ INTRODUCTION TO EXCHANGE SERVER 2013

I have mentioned Outlook 2013, but Outlook 2010 SP1 (with April 2012 Cumulative Update) and Outlook 2007

SP3 (with July 2012 Cumulative Update) are also fully supported in combination with Exchange Server 2013—but

again, only with Outlook Anywhere. Outlook 2007, 2010, and 2013 rely heavily on the Autodiscover functionality.

Autodiscover is used not only for creating the Outlook profile during the initial startup of the Outlook client but also

hourly to request the latest configuration information from Exchange Server 2013.

Outlook 2007, 2010, and 2013 also rely heavily on EWS. Using EWS, the Outlook client can request free/busy

information, set an out-of-office message, or download the offline address book. The tricky part here is that when

Autodiscover is not functioning correctly, the Outlook client will not get the appropriate information from the

Exchange 2013 server, resulting in a nonworking EWS environment, for example.

Since HTTPS is playing such an important role in an Exchange Server 2013 environment, SSL certificates have an

even more important role than they did in previous versions of Exchange Server. If there’s no proper SSL certificate on

the Exchange Server 2013, CAS will most likely result in Outlook clients not being able to connect at all. As mentioned

earlier in this chapter, Outlook 2003 clients are no longer supported. The oldest supported Outlook client working

against an Exchange Server 2013 environment is Outlook 2007.

Outlook clients can run in cached mode or in online mode, where cached mode is the default (and preferred)

mode. When running in cached mode, Outlook is working with a copy of the mailbox on the local machine, and

all changes are made to this “cached” copy. Outlook automatically synchronizes this copy in the background with

the mailbox on the Exchange Server. All processing takes place on the Outlook client’s workstation, and not on

the Exchange Server, thereby reducing processor cycles and (expensive) disk IO on the Exchange Server. Note that

Outlook 2007 and Outlook 2010 will store a complete copy of the mailbox on the workstation’s hard disk. Outlook 2013

can be adjusted to prevent a full copy on the local hard disk.

When running in online mode, Outlook is working directly against the Exchange Server, and there’s no copy of

the mailbox on the local workstation. It’s obvious that this will increase the load on the Exchange Server, plus the

Outlook client will always need to be online. Offline working—for example, while traveling—is not possible in this

scenario. Outlook running in online mode can be seen when it is used in a terminal server environment, although

Outlook 2010 running in cached mode on a terminal server is fully supported nowadays.

Outlook Web App Clients

Outlook Web App, or OWA, is the webmail client for Exchange Server 2013. A native part of Exchange Server 2013,

it offers a rich client and a similar look and feel as for Outlook 2013. At the same time, OWA has a consistent view

across different browsers on different operating systems. You can run OWA on IE9 and get the same user experience

as when running OWA in a browser on an iPad or on Windows Surface. The Microsoft Exchange Team blog contains

an interesting blog post about OWA running on different devices; see http://tinyurl.com/c2cdhru.

New in Exchange Server 2013 is the option to use OWA offline, with integrated apps for OWA that enrich the user

interface and offer additional functionality.

Microsoft is offering cross-browser supportability, so besides Internet Explorer, Mozilla Firefox 17 or later, Google

Chrome 24 or later, and Apple Safari 5 or later are fully supported for use with Exchange Server 2013. Of course, the

latest versions of these browsers support most features, but for an up-to-date overview of available functionality per

browser version, navigate to the Microsoft Technet site at http://tinyurl.com/buxyby9.

OWA Offline

In the past, a commonly requested feature was to be able to use OWA offline. This is now possible with Exchange Server

2013. For this feature to work, you need at least Internet Explorer 10, Safari 5.1(Mac only) or later, or Chrome 24 or later.

If your browser is capable of supporting offline OWA, it’s just a matter of selecting Offline Settings from the

settings menu in OWA, as shown in Figure 1-6, and you’re ready to go.

剩余408页未读，继续阅读

justinleee

粉丝: 0
资源: 4

Exchange Server 2013 管理实战指南

Mastering Microsoft Exchange Server 2013

Exchange Server 2010 Administration

Exchange Server 2013

exchange server 2010 administration pocket consultant part4

exchange server 2010 administration pocket consultant part 5

exchange server 2010 administration pocket consultant part2

exchange server 2010 administration pocket consultant part1

exchange server 2010 administration pocket consultant part3

Exchange Server 2013 SN

Exchange Server 2013概览

最新资源