Exchange 2013 发行说明Release notes for Exchange 2013

适用于: Exchange Server 2013Applies to: Exchange Server 2013

欢迎使用 Microsoft Exchange Server 2013!Welcome to Microsoft Exchange Server 2013! 本主题包含成功部署 Exchange 2013 需要了解的重要信息。This topic contains important information that you need to know to successfully deploy Exchange 2013. 请在开始部署之前,完整阅读本主题。Please read this topic completely before beginning your deployment.

本主题包含以下各部分:This topic contains the following sections:

  • 安装和部署Setup and deployment

  • Exchange 命令行管理程序Exchange Management Shell

  • 邮箱Mailbox

  • 公用文件夹Public folders

  • 邮件流Mail flow

  • 客户端连接Client connectivity

  • Exchange 2010 共存Exchange 2010 coexistence

安装和部署Setup and deployment

  • msExchProductId 不反映安装的 Exchange 2013 的发行版 Exchange 扩展 Active Directory 架构并为 Exchange 准备 Active Directory 后,会更新多个属性以显示准备工作已完成。msExchProductId doesn't reflect release version of Exchange 2013 installed After Exchange extends your Active Directory schema and prepares Active Directory for Exchange, several properties are updated to show that preparation is complete. 其中一个属性是命名上下文中容器下的 msExchangeProductId。 CN=<your organization>, CN=Microsoft Exchange, CN=Services, CN=Configuration, DC=<domain> ConfigurationOne of these properties is msExchangeProductId under the CN=<your organization>, CN=Microsoft Exchange, CN=Services, CN=Configuration, DC=<domain> container in the Configuration naming context. 如果正在安装的 Exchange 2013 版本中未引入任何 Active Directory 架构更改,则该属性不会更新或显示意外值。If no Active Directory schema changes are introduced in the release of Exchange 2013 you're installing, this property won't be updated or may show an unexpected value. 如果值与所安装的 Exchange 2013 版本不匹配,则可能会导致混淆。This could cause confusion if the value doesn't match the version of Exchange 2013 being installed.

    此行为应作为 msExchProductId 的值不反映所安装的 Exchange 2013 的版本。This behavior is expected as the value of msExchProductId doesn't reflect the version of Exchange 2013 being installed. 此属性反映上次对 Active Directory 架构进行更改的 Exchange 2013 版本。This property reflects the version of Exchange 2013 that last made changes to the Active Directory schema. 为了避免混淆,我们建议您按照准备Active Directory域的"如何知道这有效?"部分中的步骤操作,以验证 Active Directory 已更新并且已准备好安装 Exchange 2013 版本。To avoid confusion, we recommend that you follow the steps in the How do you know this worked? section of Prepare Active Directory and domains to verify that your Active Directory has been updated and is ready for the release of Exchange 2013 you're installing.

  • 安装程序错误地请求 .NET Framework 4.0: 如果尝试在未在计算机上安装 .NET Framework 安装 Exchange 2013,安装程序会错误地请求安装 .NET Framework 4.0,但实际上需要 .NET Framework 4.5 或更高版本。Setup incorrectly requests .NET Framework 4.0: If you try to install Exchange 2013 without .NET Framework installed on the computer, Setup incorrectly requests that you install .NET Framework 4.0 when, in fact, .NET Framework 4.5 or later is required.

    若要解决此问题,请安装 .NET Framework 4.5 或更高版本。To work around this issue, install .NET Framework 4.5 or later. 无需安装 4.0 .NET Framework 4.0。You don't need to install .NET Framework 4.0. 有关先决条件的完整列表,请参阅 Exchange 2013 prerequisitesFor a complete list of prerequisites, see Exchange 2013 prerequisites.

  • 累积 更新安装过程中将覆盖 Exchange XML 应用程序配置文件:安装 Exchange 累积更新或 Service Pack 时,将覆盖在 Exchange XML 应用程序配置文件(例如,客户端访问服务器上 web.config 文件或邮箱服务器上 EdgeTransport.exe.config 文件)中自定义的 Exchange 或 Internet Information Server 每服务器设置。Exchange XML application configuration files are overwritten during cumulative update installation: Any customized Exchange or Internet Information Server per-server settings you make in Exchange XML application configuration files, for example, web.config files on Client Access servers or the EdgeTransport.exe.config file on Mailbox servers, will be overwritten when you install an Exchange Cumulative Update or Service Pack. 请务必保存此类信息,以便在安装累积更新后,您可以轻松地重新配置服务器。Make sure that you save this information so you can easily re-configure your server after the install. 安装 Exchange 累积更新或 Service Pack 后,必须重新配置这些设置。You must re-configure these settings after you install an Exchange Cumulative Update or Service Pack.

  • 使用委派管理权限安装 Exchange 会导致安装程序失败 仅当委派安装角色组成员的用户尝试在预先设置的服务器上安装 Exchange 时,安装程序失败。之所以发生这种情况,是因为委派安装组缺少在 Active Directory 中创建和配置特定对象所需的权限。Installing Exchange using Delegate Admin permissions causes Setup to fail When a user who's a member of only the Delegated Setup role group attempts to install Exchange on a pre-provisioned server, Setup will fail. This happens because the Delegated Setup group lacks the permissions required to create and configure certain objects in Active Directory.

    若要解决此问题,请执行下列操作之一:To work around this issue, do one of the following:

    • 将安装 Exchange 的用户添加到“域管理员 Active Directory”安全组。Add the user installing Exchange to the Domain Admins Active Directory security group.

    • 通过属于组织管理角色组成员的用户安装 Exchange。Install Exchange using a user that's a member of the Organization Management role group.

若要详细了解如何安装 Exchange 2013,请参阅 规划和部署For more information about how to install Exchange 2013, see Planning and deployment.

Exchange 命令行管理程序Exchange Management Shell

  • 命令行管理程序意外加载 Exchange 2007 或 Exchange 2010 cmdlet 以前,在 Exchange 2013 服务器上打开命令行管理程序将导致命令行管理程序打开与本地服务器或运行 Exchange 2013 的另一台服务器的连接。The Shell unexpectedly loads Exchange 2007 or Exchange 2010 cmdlets Previously, opening the Shell on an Exchange 2013 server would result in the Shell opening a connection to the local server or another server running Exchange 2013. 建立连接后,将加载 Exchange 2013 cmdlet。When the connection is made, Exchange 2013 cmdlets are loaded. 从 Exchange 2013 CU11 开始,命令行管理程序将连接到已登录用户邮箱所在的 Exchange 服务器。Starting with Exchange 2013 CU11, the Shell will connect to the Exchange server where the logged on user's mailbox is located. 如果登录用户没有邮箱,命令行管理程序将连接到 SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} 仲裁邮箱所在的服务器。If the logged on user doesn't have a mailbox, the Shell will connect to the server where the SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} arbitration mailbox is located. 目标服务器可以是任何受支持的 Exchange 版本。The target server can be any supported version of Exchange. 这意味着,如果登录用户的邮箱 (或仲裁邮箱(如果用户没有邮箱) 位于 Exchange 2010 服务器上),则命令行管理程序将连接到该服务器并加载 Exchange 2010 cmdlet。This means if the logged on user's mailbox (or the arbitration mailbox if the user has no mailbox) is located on an Exchange 2010 server, the Shell will connect to that server and load Exchange 2010 cmdlets. 这可能会阻止您执行某些任务,因为 Exchange 2010 cmdlet 无法管理 Exchange 2013 配置或服务器。This may prevent you from performing certain tasks because Exchange 2010 cmdlets can't manage Exchange 2013 configuration or servers.

    从 Exchange 2013 CU11 开始,此行为是设计使的。Starting with Exchange 2013 CU11, this behavior is by design. 若要确保命令行管理程序加载 Exchange 2013 cmdlet,请移动登录用户的邮箱到 Exchange 2013。To make sure the Shell loads Exchange 2013 cmdlets, move the logged on user's mailbox to Exchange 2013. 如果登录用户没有邮箱,将 SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} 仲裁邮箱移动到 Exchange 2013 服务器。If the logged on user doesn't have a mailbox, move the SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c} arbitration mailbox to an Exchange 2013 server.

    若要详细了解如何移动仲裁邮箱,请参阅 Exchange 团队博客上的 Exchange 命令行 管理程序 和邮箱定位。For details and information on how to move the arbitration mailbox, see Exchange Management Shell and Mailbox Anchoring on the Exchange Team blog.


  • 运行不同版本的 Exchange 的邮箱服务器可以添加到同一数据库可用性组****Add-DatabaseAvailabilityGroupServer cmdlet 和 Exchange 管理中心错误地允许将 Exchange 2013 服务器添加到基于 Exchange 2016 的数据库可用性组 (DAG) ,反之亦然。Mailbox servers running different versions of Exchange can be added to the same database availability group The Add-DatabaseAvailabilityGroupServer cmdlet and the Exchange admin center incorrectly allow an Exchange 2013 server to be added to an Exchange 2016-based database availability group (DAG), and vice versa. Exchange 仅支持将运行相同版本的邮箱服务器(例如 Exchange 2013 与 Exchange 2016)添加到 DAG。Exchange supports adding only Mailbox servers running the same version (Exchange 2013 versus Exchange 2016, for example) to a DAG. 此外,Exchange 管理员中心会在可添加到 DAG 的服务器列表中同时显示 Exchange 2013 和 Exchange 2016。Additionally, the Exchange admin center displays both Exchange 2013 and Exchange 2016 servers in the list of servers available to add to a DAG. 这将允许管理员无意中将运行不兼容版本的 Exchange 的服务器添加到 DAG(例如,将 Exchange 2013 服务器添加到基于 Exchange 2016 的DAG)。This could allow an administrator to inadvertently add a server running an incompatible version of Exchange to a DAG (for example, adding an Exchange 2013 server to an Exchange 2016-based DAG).

    此问题暂无解决办法。向 DAG 添加邮箱服务器时,管理员必须非常用心。仅将 Exchange 2013 服务器添加到基于 Exchange 2013 的 DAG,仅将 Exchange 2016 服务器添加到基于 Exchange 2016 的 DAG。若要区分各个 Exchange 版本,可以查看 Exchange 管理中心内服务器列表中的“版本”列。下面列出了 Exchange 2013 和 Exchange 2016 服务器版本:There is currently no workaround for this issue. Administrators must be diligent when adding a Mailbox server to a DAG. Add only Exchange 2013 servers to Exchange 2013-based DAGs, and only Exchange 2016 servers to Exchange 2016-based DAGs. You can differentiate each version of Exchange by looking at the Version column in the list of servers in the Exchange admin center. The following are the server versions for Exchange 2013 and Exchange 2016:

    • Exchange 2013 15.0(生成号 xxx.xx)Exchange 2013 15.0 (Build xxx.xx)

    • Exchange 2016 15.1(生成号 xxx.xx)Exchange 2016 15.1 (Build xxx.xx)

  • 以前的 Exchange 版本迁移时邮箱大小增加:将邮箱从以前版本的 Exchange 移动到 Exchange 2013 时,报告的邮箱大小可能会增加 30% 到 40%。Mailbox size increase when migrating from previous Exchange versions: When you move a mailbox from a previous version of Exchange to Exchange 2013, the mailbox size reported may increase 30 percent to 40 percent. 邮箱数据库使用的磁盘空间没有增加,只有每个邮箱使用的空间属性已增加。Disk space used by the mailbox database has not increased, only the attribution of space used by each mailbox has increased. 邮箱大小增加是由于所有项目属性均包含在配额计算中,从而可以更精确地计算邮箱中项目所消耗的空间。The increase in mailbox size is due to the inclusion of all item properties into quota calculations, providing a more accurate computation of space consumed by items within their mailbox. 此增加可能会导致一些用户在将邮箱移动到 Exchange 2013 时超过其邮箱大小配额。This increase may cause some users to exceed their mailbox size quotas when their mailbox is moved to Exchange 2013.

    若要防止用户超过其邮箱大小配额,请增加数据库或邮箱配额值以适应新的配额计算。To prevent users from exceeding their mailbox size quotas, increase the database or mailbox quota values to accommodate the new quota calculation. 若要配置数据库或邮箱配额值,请分别使用 Set-MailboxDatabaseSet-Mailbox cmdlet 上的 IssueWarningQuota、ProhibitSendQuotaProhibitSendReceiveQuota 参数。 To configure database or mailbox quota values, use the IssueWarningQuota, ProhibitSendQuota, and ProhibitSendReceiveQuota parameters on the Set-MailboxDatabase and Set-Mailbox cmdlets, respectively.

  • Outlook 2007 和 Outlook 2010 客户端可能无法下载脱机通讯簿:如果无法从 Internet 访问脱机通讯簿 (OAB) 内部 URL,则 Outlook 2007 和 Outlook 2010 客户端可能无法下载 OAB。Outlook 2007 and Outlook 2010 clients may be unable to download the Offline Address Book: If the Offline Address Book (OAB) internal URL isn't accessible from the Internet, Outlook 2007 and Outlook 2010 clients may be unable to download the OAB.

    若要解决 Outlook 2007 和 Outlook 2010 客户端的此问题,请使 OAB 内部 URL 可从 Internet 访问。To work around this issue for Outlook 2007 and Outlook 2010 clients, make the OAB internal URL accessible from the Internet. Outlook 2013 不受此问题的影响。Outlook 2013 isn't affected by this issue.

  • 在现有的 Exchange 组织中安装 Exchange 2013 可能会导致所有客户端下载 OAB:将第一个 Exchange 2013 服务器安装到现有 Exchange 2007 或 Exchange 2010 组织中可能会导致组织的所有客户端下载 OAB 的新副本,从而导致网络饱和和服务器性能问题。Installing Exchange 2013 in an existing Exchange organization may cause all clients to download the OAB: Installing the first Exchange 2013 server into an existing Exchange 2007 or Exchange 2010 organization may cause all clients in the organization to download a new copy of the OAB, resulting in network saturation and server performance issues. 出现此问题的原因是:Exchange 2013 在组织中创建一个取代 Exchange 2007 或 Exchange 2010 OAB 的新默认 OAB。This issue occurs because Exchange 2013 creates a new default OAB in the organization that supersedes the Exchange 2007 or Exchange 2010 OAB. 未分配特定 OAB 或位于未分配特定 OAB 的邮箱数据库的邮箱将下载新的默认 OAB。Mailboxes that don't have a specific OAB assigned, or that are located on a mailbox database that doesn't have a specific OAB assigned, will download the new default OAB.

    若要阻止客户端在安装 Exchange 2013 时下载 OAB 的新副本,请为每个邮箱或邮箱所在的邮箱数据库分配 OAB。To prevent clients from downloading a new copy of the OAB when Exchange 2013 is installed, assign an OAB to every mailbox or to the mailbox database the mailboxes are located on. 必须在组织中安装 Exchange 2013 之前完成此操作。This must be done prior to Exchange 2013 being installed in the organization.

  • 用户可能会路由到对请求的 OAB 不负责的 OAB 生成邮箱:Exchange 2013 CU5 及更高版本的 CU 已更改 OAB 链接到 OAB 生成邮箱方式。Users may be routed to an OAB generation mailbox that's not responsible for the requested OAB: Exchange 2013 CU5 and later CUs have changed how OABs are linked to OAB generation mailboxes. 此更改使用户可以路由到对用户所请求的 OAB 不负责的 OAB 生成邮箱。This change makes it possible for a user to be routed to an OAB generation mailbox that isn't responsible for the OAB that the user is requesting. 如果以下所有条件均成立,可能会发生这种情况:This can happen if all of the following are true:

    • 您的组织中具有多个 OAB 生成邮箱。You have more than one OAB generation mailbox in your organization.

    • 升级客户端访问服务器之前,升级托管 OAB 生成邮箱的邮箱服务器。You upgrade the Mailbox servers that host OAB generation mailboxes before you upgrade your Client Access servers.

    • 你要将 Exchange 2013 服务器从 CU5 之前的发行版升级到更高版本 (例如,从 Exchange 2013 CU3 升级到 Exchange 2013 CU6) 。You're upgrading your Exchange 2013 servers from a release prior to CU5 to a later release (for example, upgrading from Exchange 2013 CU3 to Exchange 2013 CU6).

    • 客户端访问服务器在 CU5 之前运行版本。Your Client Access servers are running a release prior to CU5.

    若要解决此问题,请确保先将客户端访问服务器升级到 Exchange 2013 CU6 或更高版本,然后再升级邮箱服务器。To work around this issue, make sure that you upgrade your Client Access servers to Exchange 2013 CU6 or later before you upgrade your Mailbox servers. 这将确保客户端访问服务器知道如何将请求代理到负责生成用户的 OAB 的 OAB 生成邮箱。This will make sure the Client Access servers know how to proxy the requests to the OAB generation mailbox that is responsible for generating the user's OAB.

    若要详细了解 Exchange 2013 CU5 中的 OAB 更改,请参阅OAB Improvements in Exchange 2013 Cumulative Update 5。To read more about the OAB changes in Exchange 2013 CU5, see OAB Improvements in Exchange 2013 Cumulative Update 5.

公用文件夹Public folders

  • 未经授权的发件人无法再 向启用邮件的公用文件夹发送邮件:在 Exchange 2013 CU6 之前,未经授权的发件人可能会向已启用邮件的公用文件夹发送邮件。Unauthorized senders can no longer send messages to mail-enabled public folders: Prior to Exchange 2013 CU6, unauthorized senders could send messages to mail-enabled public folders. 这允许外部发件人向已启用邮件的公用文件夹发送邮件,而不考虑在公用文件夹上设置的权限。This allowed the possibility for external senders to send mail to mail-enabled public folders regardless of the permissions set on the public folder.

    从 Exchange 2013 CU6 开始,如果希望外部发件人将邮件发送到已启用邮件的公用文件夹,至少需要向 匿名 用户授予" 创建项目" 权限。Starting with Exchange 2013 CU6, if you want external senders to send mail to a mail-enabled public folders, the Anonymous user needs to be granted at least the Create Items permission. 如果已设置启用邮件的公用文件夹,并且尚未设置,外部发件人将收到传递失败通知,并且邮件不会传递到已启用邮件的公用文件夹。If you've set up mail-enabled public folders and haven't done this, external senders will receive a delivery failure notification and the messages won't be delivered to the mail-enabled public folder.

    可以使用命令行管理程序或 Outlook 设置匿名用户的权限。要了解如何设置匿名用户的权限,请参阅对公用文件夹启用或禁用邮件You can use the Shell or Outlook to set the permissions on the Anonymous user. To read more about how to set permissions on the Anonymous user, see Mail-enable or mail-disable a public folder.

  • 可以从旧版 Exchange 服务器迁移到 Exchange 2013 的公用文件夹的最大数量为 500,000。The maximum number of public folders that can be migrated to Exchange 2013 from legacy Exchange servers is 500,000. 有关公用文件夹迁移详细信息,请参阅使用批处理迁移将公用文件夹从以前版本迁移到Exchange 2013。For more information about public folder migration, see Use batch migration to migrate public folders to Exchange 2013 from previous versions.

邮件流Mail flow

  • 客户端访问服务器的 TransportAgent cmdlet 需要本地 Windows PowerShell:-TransportAgent * cmdlet 存在一个问题,该 cmdlet 阻止这些 cmdlet 使用 Exchange 命令行管理程序在客户端访问服务器上安装、卸载和管理传输代理。TransportAgent cmdlets on Client Access servers require local Windows PowerShell: An issue exists with the *-TransportAgent cmdlets that prevents those cmdlets from installing, uninstalling, and managing transport agents on Client Access servers using the Exchange Management Shell. 若要在客户端访问服务器上安装、卸载和管理传输代理,必须手动加载 Exchange Windows PowerShell 管理单元,然后运行 * -TransportAgent cmdlet。To install, uninstall, and manage transport agents on Client Access servers, you must manually load the Exchange Windows PowerShell snap-in and then run the *-TransportAgent cmdlets. 如果您尝试使用 Exchange 命令行管理程序安装、卸载或管理传输代理,则所做的更改将应用于您连接到的 Exchange 2013 邮箱服务器。If you attempt to install, uninstall, or manage transport agents using the Exchange Management Shell, your changes will be applied to the Exchange 2013 Mailbox server you're connected to.

    若要在客户端访问服务器上安装、卸载或管理传输代理,请对要管理的客户端访问服务器执行以下操作:To install, uninstall, or manage transport agents on Client Access servers, do the following on the Client Access server you want to manage:


    不支持 Microsoft.Exchange.Management.PowerShell.SnapIn Windows PowerShell *-TransportAgent cmdlet 外加载管理单元和运行的 cmdlet,这可能会导致 Exchange 部署受到无法修复的损坏。Loading the Microsoft.Exchange.Management.PowerShell.SnapIn Windows PowerShell snap-in and running cmdlets other than the *-TransportAgent cmdlets is not supported and may result in irreparable damage to your Exchange deployment.
    您必须是客户端访问服务器上要安装、卸载或管理传输代理的本地管理员。You must be a local Administrator on the Client Access server where you want to install, uninstall, or manage transport agents. 我们不支持修改对 Exchange 文件、目录 (Active Directory) ACL 的访问控制列表。We do not support the modification of access control lists (ACLs) on Exchange files, directories, or Active Directory objects.


    仅在客户端访问服务器上执行以下过程。Perform the following procedure on Client Access servers only. 如果要在邮箱服务器上管理传输代理,Windows PowerShell Exchange 邮箱   管理单元。You don't need to load the Exchange Windows PowerShell snap-in if you want to manage transport agents on Mailbox servers.

    1. 打开一个新的Windows PowerShell窗口。Open a new Windows PowerShell window.

    2. 运行以下命令。Run the following command.

      Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn
    3. 正常执行传输代理管理任务。Perform transport agent management tasks as normal.

    4. 在要管理的每个客户端访问服务器上重复此过程。Repeat this procedure on each Client Access server you want to manage.

客户端连接Client connectivity

  • 未加入域的客户端的 NTLM 身份验证失败:当满足以下条件时,客户端(如 Windows Live Mail 和 Exchange 2013)之间的身份验证可能会失败:NTLM authentication fails for non-domain joined clients: Authentication between a client, such as Windows Live Mail, and Exchange 2013 may fail when the following conditions are true:

    • 然后,客户端使用的身份验证方法是 NTLM。Then authentication method the client uses is NTLM.

    • 计算机未加入域。The computer isn't joined to the domain.

    若要解决此问题,可以执行下列操作之一:To work around this issue, you can do one of the following:

    • 将运行客户端的计算机加入域。Join the computer the client is running on to the domain.

    • 将客户端使用的身份验证类型从 NTLM 更改为基于 TLS 的基本身份验证。Change the authentication type the client uses from NTLM to Basic Auth over TLS.

  • 当与 Send-MailMessage cmdlet: Generic Security Service 应用程序接口 (GSSAPI) 一起使用 Send-MailMessage cmdlet(包括在默认安装的 Windows PowerShell 中)将经过身份验证的邮件发送到 Exchange 2013 时,GSSAPI 身份验证将失败。GSSAPI authentication fails when used with the Send-MailMessage cmdlet: Generic Security Service Application Program Interface (GSSAPI) authentication may fail when the Send-MailMessage cmdlet, which is included with default installs of Windows PowerShell, is used to send authenticated mail to Exchange 2013. 发生这种情况时,您将在 Exchange 2013 客户端访问服务器的应用程序事件日志中看到一个条目,该服务器接收了包含以下信息的连接: When this happens, you'll see an entry in the Application event log on the Exchange 2013 Client Access server that received the connection with the following information:

    • 来源:MSExchangeFrontEndTransportSource: MSExchangeFrontEndTransport

    • 事件 ID:1035Event ID: 1035

    • 说明:接收连接器客户端前端 的 IllegalMessage 入站身份验证失败,出现错误 <server name> 。Description: Inbound authentication failed with error IllegalMessage for Receive connector Client Frontend <server name>. 身份验证机制是 Gssapi。The authentication mechanism is Gssapi. 尝试对 Exchange 进行身份验证的客户端的源 IP 地址是 [ <client IP address> ] 。The source IP address of the client who tried to authenticate to Exchange is [<client IP address>].

    若要解决此问题,您需要从 Exchange 2013 客户端访问服务器的客户端接收连接器 Integrated 中删除身份验证方法。To work around this issue, you need to remove the Integrated authentication method from the client receive connector on your Exchange 2013 Client Access servers. 若要从客户端接收连接器中删除身份验证方法,请在每个 Exchange 2013 客户端访问服务器上运行以下命令,该服务器可以接收来自运行 Integrated Send-MailMessage cmdlet 的计算机的连接:To remove the Integrated authentication method from a client receive connector, run the following command on each Exchange 2013 Client Access server that could receive connections from computers running the Send-MailMessage cmdlet:

    Set-ReceiveConnector "<server name>\Client Frontend <server name>" -AuthMechanism Tls, BasicAuth, BasicAuthRequireTLS
  • 当您升级到 Exchange 2013 SP1 时,MAPI over HTTP 可能会遇到性能不佳的问题:如果您从 Exchange 2013 累积更新升级到 Exchange 2013 SP1 并启用 MAPI over HTTP,则使用协议连接到 Exchange 2013 SP1 服务器的客户端可能会遇到性能不佳的问题。MAPI over HTTP may experience poor performance when you upgrade to Exchange 2013 SP1: If you upgrade from an Exchange 2013 cumulative update to Exchange 2013 SP1 and enable MAPI over HTTP, clients that connect to an Exchange 2013 SP1 server using the protocol may experience poor performance. 这是因为在从累积更新升级到 Exchange 2013 SP1 期间未配置必需的设置。This is because required settings aren't configured during an upgrade from a cumulative update to Exchange 2013 SP1. 如果从 Exchange 2013 RTM 升级到 Exchange 2013 SP1,或者安装了新的 Exchange 2013 SP1 或更高版本的服务器,则不会发生此问题。This issue doesn't occur if you upgrade to Exchange 2013 SP1 from Exchange 2013 RTM or if you install a new Exchange 2013 SP1 or later server.


    只有在客户端访问服务器上启用了 MAPI over HTTP 协议时,这才成为问题。This is only an issue if the MAPI over HTTP protocol is enabled on your Client Access servers. 默认情况下处于禁用状态。It's disabled by default. 如果 MAPI over HTTP 被禁用,客户端将改为使用 RPC over HTTP 协议。If MAPI over HTTP is disabled, clients use the RPC over HTTP protocol instead.

    若要解决此问题,请执行下列操作:To work around this issue, do the following:

    1. 在运行客户端访问服务器角色的服务器上,在 Windows 命令提示符中运行以下命令:On servers running the Client Access server role, run the following commands in a Windows Command Prompt:

      set AppCmdLocation=%windir%\System32\inetsrv
      set ExchangeLocation=%ProgramFiles%\Microsoft\Exchange Server\V15
      %AppCmdLocation%\appcmd.exe SET AppPool "MSExchangeMapiFrontEndAppPool" /CLRConfigFile:"%ExchangeLocation%\bin\MSExchangeMapiFrontEndAppPool_CLRConfig.config"
      %AppCmdLocation%\appcmd.exe RECYCLE AppPool "MSExchangeMapiFrontEndAppPool"
    2. 在运行邮箱服务器角色的服务器上,在 Windows 命令提示符中运行以下命令:On servers running the Mailbox server role, run the following commands in a Windows Command Prompt:

      set AppCmdLocation=%windir%\System32\inetsrv
      set ExchangeLocation=%ProgramFiles%\Microsoft\Exchange Server\V15
      %AppCmdLocation%\appcmd.exe SET AppPool "MSExchangeMapiMailboxAppPool" /CLRConfigFile:"%ExchangeLocation%\bin\MSExchangeMapiMailboxAppPool_CLRConfig.config"
      %AppCmdLocation%\appcmd.exe RECYCLE AppPool "MSExchangeMapiMailboxAppPool"
      %AppCmdLocation%\appcmd.exe SET AppPool "MSExchangeMapiAddressBookAppPool" /CLRConfigFile:"%ExchangeLocation%\bin\MSExchangeMapiAddressBookAppPool_CLRConfig.config"
      %AppCmdLocation%\appcmd.exe RECYCLE AppPool "MSExchangeMapiAddressBookAppPool"

Exchange 2010 共存Exchange 2010 coexistence

  • 通过 Exchange 2013 客户端访问服务器代理时,访问 Exchange 2010 邮箱的请求可能不起作用:在某些情况下,未安装任何更新汇总的 Exchange 2013 和 Exchange 2010 Service Pack 3 (SP3) 客户端访问服务器之间的代理请求可能无法正常工作,并出现错误。Requests to access Exchange 2010 mailboxes may not work when proxied through Exchange 2013 Client Access servers: In some situations, the proxy request between the Exchange 2013 and Exchange 2010 Service Pack 3 (SP3) Client Access servers without any update rollups installed may not work correctly and an error appears. 如果满足以下所有条件,可能会发生这种情况:This can happen if all of the following conditions are true:

    • 具有 Exchange 2013 邮箱的用户尝试使用下列方法之一打开 Exchange 2010 邮箱:A user with an Exchange 2013 mailbox tries to open an Exchange 2010 mailbox using one of the following methods:

      • " 打开另一个邮箱 "选项Outlook Web App -OR-The Open Another Mailbox option in Outlook Web App -OR-

      • Exchange 管理 中心中的"其他用户"选项The Another user option in the Exchange admin center

      • 用户连接到的客户端访问服务器正在运行 Exchange 2013。The Client Access server the user connected to is running Exchange 2013.

      • Exchange 2010 客户端访问服务器从 Exchange 2010 或以前的 Exchange 2010 Service Pack 的 (RTM) 版本升级到 Exchange 2010 SP3。The Exchange 2010 Client Access server was upgraded to Exchange 2010 SP3 from the release to manufacturing (RTM) version of Exchange 2010 or a previous Exchange 2010 service pack.

    如果上述所有条件都为 true,则用户无法访问其他用户的 Exchange 2010 Outlook Web App选项,并且可能会显示一个空白页。If all the conditions above are true, the user won't be able to access the other user's Exchange 2010 Outlook Web App options and a blank page may appear.

    若要解决此问题,请在每个 Exchange 2010 服务器上安装 Exchange 2010 SP3 更新汇总 1 或更高版本。To work around this issue, install Exchange 2010 SP3 Update Rollup 1 or later on each Exchange 2010 server.