Exchange 2010 支持终止路线图Exchange 2010 end of support roadmap

此文章适用于 Microsoft 365 企业版和 Office 365 企业版。 This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.

Exchange Server 2010 年 10 月 13 日终止支持。Exchange Server 2010 reached its end of support on October 13, 2020. 如果尚未开始从 Exchange 2010 迁移到 Microsoft 365、Office 365 或 Exchange 2016,那么现在该开始规划了。If you haven't already begun your migration from Exchange 2010 to Microsoft 365, Office 365, or Exchange 2016, now's the time to start planning.

停止 提供支持意味着什么What does end of support mean?

大多数 Microsoft 产品都有一个支持生命周期,在此期间它们获取新功能、Bug 修复、安全修补程序等。Most Microsoft products have a support lifecycle during which they get new features, bug fixes, security fixes, and so on. 此生命周期通常自产品初始发布起持续 10 年。This lifecycle typically lasts for 10 years from the product's initial release. 此生命周期的结束称为产品的停止支持。The end of this lifecycle is known as the product's end of support. 由于Exchange 2010 年 10 月 13 日终止支持,因此 Microsoft 不再提供:Because Exchange 2010 reached its end of support on October 13, 2020, Microsoft no longer provides:

  • 针对可能会出现的问题的技术支持。Technical support for problems that may occur.
  • 对可能会影响服务器稳定性和可用性的问题进行 Bug 修复。Bug fixes for issues that may impact the stability and usability of the server.
  • 针对可能导致服务器易受安全漏洞的漏洞进行安全修复。Security fixes for vulnerabilities that may make the server vulnerable to security breaches.
  • 时区更新。Time zone updates.

2010 Exchange 2010 的安装将在此日期之后继续运行。Your installation of Exchange 2010 will continue to run after this date. 但由于上述更改,我们强烈建议您尽快从 Exchange 2010 迁移。But because of the changes listed above, we strongly recommend that you migrate from Exchange 2010 as soon as possible.

有关即将停止提供支持的信息,请参阅帮助您从 Office 2010 服务器和客户端升级的资源For more information about nearing the end of support, see Resources to help you upgrade from Office 2010 servers and clients.

我的选项是什么?What are my options?

是时候探索你的选项并准备迁移计划了。It's a great time to explore your options and prepare a migration plan. 可执行下列操作:You can:

  • 完全迁移到Microsoft 365。Migrate fully to Microsoft 365. 使用转换、最小混合或完全混合迁移迁移邮箱。Migrate mailboxes using cutover, minimal hybrid, or full hybrid migration. 然后删除本地Exchange服务器和 Active Directory。Then remove on-premises Exchange servers and Active Directory.
  • 将 Exchange 2010 服务器Exchange本地服务器上迁移到 2016。Migrate your Exchange 2010 servers to Exchange 2016 on your on-premises servers.

重要

如果你的组织选择将邮箱迁移到 Microsoft 365但计划保留 DirSync 或 Azure AD 连接 以继续从本地 Active Directory 管理用户帐户,你需要在本地至少保留一个 Microsoft Exchange 服务器。If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep DirSync or Azure AD Connect in place to continue managing user accounts from on-premises Active Directory, you need to keep at least one Microsoft Exchange server on-premises. 如果删除Exchange服务器,将无法对 Exchange Online 中的 Exchange 收件人进行更改,因为授权源仍保留在内部部署 Active Directory 中。If you remove all Exchange servers, you won't be able to make changes to Exchange recipients in Exchange Online because the source of authority remains in your on-premises Active Directory. 需要在那里进行更改。Changes need to be made there. 在此方案中,有以下选项:In this scenario, you have the following options:

  • 建议: 如果在 2020 年 10 月 13 Microsoft 365将邮箱迁移到 Microsoft 365 并升级服务器,请使用 Exchange 2010 连接到 Microsoft 365 并迁移邮箱。Recommended: If you migrated your mailboxes to Microsoft 365 and upgraded your servers by October 13, 2020, use Exchange 2010 to connect to Microsoft 365 and migrate mailboxes. 接下来,将 Exchange 2010 迁移到 Exchange 2016,并停止使用任何剩余的 Exchange 2010 服务器。Next, migrate Exchange 2010 to Exchange 2016, and decommission any remaining Exchange 2010 servers.
  • 如果您未在 2020 年 10 月 13 日之前完成邮箱迁移和内部部署服务器升级,请首先将本地 Exchange 2010 服务器升级到 Exchange 2016。If you didn't complete the mailbox migration and on-premises server upgrade by October 13, 2020, upgrade your on-premises Exchange 2010 servers to Exchange 2016 first. 然后使用 Exchange 2016 连接到Microsoft 365并迁移邮箱。Then use Exchange 2016 to connect to Microsoft 365 and migrate mailboxes.

备注

虽然这稍微复杂一些,但您也可以将邮箱迁移到 Microsoft 365,同时将本地 Exchange 2010 服务器迁移到 Exchange 2016。It's little more complicated, but you can also migrate mailboxes to Microsoft 365 while migrating your on-premises Exchange 2010 servers to Exchange 2016.

以下是避免对 2010 年 2010 年停止提供支持的三Exchange Server路径。Here are the three paths you can take to avoid the end of support for Exchange Server 2010.

Exchange Server 2010 升级路径

以下各节更详细地探讨每个选项。The following sections explore each option in more detail.

迁移到 Microsoft 365Migrate to Microsoft 365

将电子邮件迁移到 Microsoft 365是帮助你停用 2010 年 2010 Exchange最佳且最简单的选项。Migrating your email to Microsoft 365 is the best and simplest option to help you retire your Exchange 2010 deployment. 通过迁移到 Microsoft 365,你可以从旧技术到当前功能进行单个跃点,包括:With a migration to Microsoft 365, you can make a single hop from old technology to current features, including:

  • 合规性功能,如保留策略、In-Place和诉讼保留、就地电子数据展示等。Compliance capabilities such as Retention Policies, In-Place and Litigation Hold, in-place eDiscovery, and more.
  • Microsoft Teams。Microsoft Teams.
  • Power BI。Power BI.
  • 重点收件箱。Focused Inbox.
  • MyAnalytics。MyAnalytics.

Microsoft 365还首先获取新功能和体验,因此组织可以立即开始使用它们。Microsoft 365 also gets new features and experiences first, so your organization can start using them right away. 此外,也无需担心:Also, you won't have to worry about:

  • 购买和维护硬件。Purchasing and maintaining hardware.
  • 支付热和冷服务器费用。Paying to heat and cool your servers.
  • 保持最新的安全、产品和时区修补程序。Keeping up to date on security, product, and time-zone fixes.
  • 维护存储和软件以支持合规性要求。Maintaining storage and software to support compliance requirements.
  • 升级到新版本的 Exchange。Upgrading to a new version of Exchange. 你始终使用最新版本的 Exchange Microsoft 365。You're always on the latest version of Exchange in Microsoft 365.

如何迁移到Microsoft 365?How should I migrate to Microsoft 365?

根据您的组织,有一些选项可以Microsoft 365。Depending on your organization, you have a few options to get to Microsoft 365. 首先,需要考虑一些方面,例如:First, you need to consider a few things, such as:

  • 需要移动的席位或邮箱数。The number of seats or mailboxes you need to move.
  • 希望迁移持续多久。How long you want the migration to last.
  • 在迁移过程中,是否需要在本地安装和部署Microsoft 365无缝集成。Whether you need a seamless integration between your on-premises installation and Microsoft 365 during the migration.

此表显示了迁移选项以及决定使用哪种方法的最重要的因素。This table shows your migration options and the most important factors that determine which method to use.

迁移选项Migration option 组织规模Organization size 期限Duration
直接转换迁移Cutover migration 少于 150 个席位Fewer than 150 seats 一周或更少A week or less
最小混合迁移Minimal hybrid migration 少于 150 个席位Fewer than 150 seats 几周或更久A few weeks or less
完全混合迁移Full hybrid migration 多于 150 个席位More than 150 seats 几周或更久A few weeks or more

以下各节概述了这些方法。The following sections give you an overview of these methods. 有关详细信息,请参阅 确定迁移路径For more information, see Decide on a migration path.

直接转换迁移Cutover migration

在直接转换迁移中,迁移所有邮箱、通讯组、联系人等,Office 365日期和时间进行迁移。In a cutover migration, you migrate all your mailboxes, distribution groups, contacts, and so on, to Office 365 at a set date and time. 完成后,您将关闭内部部署服务器,Exchange以独占方式Microsoft 365服务器。When you're done, you shut down your on-premises Exchange servers and start using Microsoft 365 exclusively.

对于没有很多邮箱、希望快速访问 Microsoft 365并且不想处理其他方法的复杂性的小组织来说,转换迁移是很好的选择。Cutover migration is great for small organizations that don't have many mailboxes, want to get to Microsoft 365 quickly, and don't want to deal with the complexity of the other methods. 但应在一周或更之后完成。But it should be completed in a week or less. 并且它要求用户重新配置其Outlook配置文件。And it requires users to reconfigure their Outlook profiles. 虽然转换迁移最多可迁移 2,000 个邮箱,但我们建议您最多使用 150 个邮箱。Cutover migration can migrate up to 2,000 mailboxes, but we recommend you use it for a maximum of 150. 如果尝试迁移更多邮箱,在截止时间之前转移所有邮箱的时间可能会用完,并且 IT 支持人员可能会因请求帮助用户重新配置邮箱而Outlook。If you try to migrate more, you could run out of time to transfer all the mailboxes before your deadline, and your IT support staff may get overwhelmed with requests to help users reconfigure Outlook.

下面是有关转换迁移的要考虑的一些内容:Here are things to consider about cutover migration:

  • Microsoft 365 TCP 端口 443 Outlook Anywhere 连接到 Exchange 2010 服务器。Microsoft 365 will need to connect to your Exchange 2010 servers by using Outlook Anywhere over TCP port 443.
  • 所有内部部署邮箱都将移动到Microsoft 365。All on-premises mailboxes will be moved to Microsoft 365.
  • 您需要具有用户邮箱的读取访问权限的本地管理员帐户。You'll need an on-premises administrator account that has read access to your users' mailboxes.
  • 要Exchange的 2010 接受域Microsoft 365需要添加为服务中的已验证域。The Exchange 2010 accepted domains that you want to use in Microsoft 365 need to be added as verified domains in the service.
  • 从开始迁移到开始完成阶段,Microsoft 365定期同步Microsoft 365和内部部署邮箱。Between when you start the migration and when you begin the completion phase, Microsoft 365 will periodically synchronize the Microsoft 365 and on-premises mailboxes. 这样,您即可完成迁移,而无需担心电子邮件会遗留在本地邮箱中。This lets you complete the migration without worrying about email being left behind in your on-premises mailboxes.
  • 用户将收到其帐户的新临时Microsoft 365密码。Users will receive new temporary passwords for their Microsoft 365 account. 第一次登录邮箱时,用户需要更改它们。They'll need to change those when they sign in to their mailboxes for the first time.
  • 您需要一个Microsoft 365许可证,其中包含Exchange Online迁移的每个用户邮箱的邮箱。You'll need a Microsoft 365 license that includes Exchange Online for each user mailbox you migrate.
  • 用户需要在每个设备上设置新的 Outlook 配置文件,并再次下载他们的电子邮件。Users will need to set up a new Outlook profile on each of their devices and download their email again. 要下载的电子邮件Outlook可能会有所不同。The amount of email that Outlook will download can vary. 有关详细信息,请参阅在 Outlook中脱机工作For more information, see Work offline in Outlook.

若要了解有关转换迁移的更多信息,请参阅:To learn more about cutover migration, see:

最小混合迁移Minimal hybrid migration

在最小混合或快速迁移中,您可以在几周内将几百个邮箱Microsoft 365迁移。In a minimal hybrid, or express, migration you move a few hundred mailboxes to Microsoft 365 within a few weeks. 此方法不支持高级混合迁移功能,如共享忙/闲日历信息。This method doesn't support advanced hybrid-migration features like shared free/busy calendar information.

最少混合迁移非常适用于需要花时间将邮箱迁移到 Microsoft 365,但仍计划在几周内完成迁移的组织。Minimal hybrid migration is great for organizations that need to take more time to migrate their mailboxes to Microsoft 365, but still plan to complete the migration within a few weeks. 你可以从更高级的完全混合迁移获得一些好处,而无需任何复杂性。You get some of the benefits of the more advanced full-hybrid migration without much of the complexity. 您可以控制在给定时间要迁移的邮箱数和邮箱数。You can control how many and which mailboxes to migrate at a given time. Microsoft 365使用内部部署帐户的用户名和密码创建邮箱。Microsoft 365 mailboxes will be created with the user names and passwords of the on-premises accounts. 而且,与转换迁移不同,用户不必重新创建其Outlook配置文件。And, unlike cutover migrations, your users don't have to recreate their Outlook profiles.

下面是有关最小混合迁移的要考虑的一些内容:Here are things to consider about minimal hybrid migration:

  • 您需要在本地 Active Directory 服务器和服务器之间执行一次目录Microsoft 365。You'll need to do a one-time directory synchronization between your on-premises Active Directory servers and Microsoft 365.
  • 用户将能够使用与邮箱Microsoft 365相同的用户名和密码登录到其邮箱。Users will be able to sign in to their Microsoft 365 mailbox with the same user name and password as before their mailbox.
  • 您需要一个Microsoft 365许可证,Exchange Online迁移的每个用户邮箱的邮箱。You'll need a Microsoft 365 license that includes Exchange Online for each user mailbox that you migrate.
  • 用户无需在大部分设备上设置新的 Outlook 配置文件,尽管某些较旧的 Android 手机可能需要新的配置文件。Users won't need to set up a new Outlook profile on most of their devices, though some older Android phones might need a new profile. 用户无需重新下载其电子邮件。Users won't need to redownload their email.

有关详细信息,请参阅使用最小混合快速将Exchange邮箱迁移到Office 365。For more information, see Use Minimal Hybrid to quickly migrate Exchange mailboxes to Office 365.

完全混合Full hybrid

在完全混合迁移中,您拥有数百个(最多数万个)的邮箱,并且您将部分或全部移动到 Microsoft 365。In a full hybrid migration, you have many hundreds, up to tens of thousands, of mailboxes, and you move some or all to Microsoft 365. 由于这些迁移通常是长期迁移,因此混合迁移可以:Because these migrations are typically longer-term, hybrid migrations make it possible to:

  • 向本地用户显示本地用户的忙/闲日历Microsoft 365,反之亦然。Show on-premises users the free/busy calendar information for users in Microsoft 365, and vice versa.
  • 请参阅统一的全局地址列表,其中包含内部部署和内部部署Microsoft 365。See a unified global address list that contains recipients in both on-premises and Microsoft 365.
  • 查看Outlook的完整收件人属性,而不管他们是在本地还是Microsoft 365。View full Outlook recipient properties for all users, regardless of whether they're on-premises or in Microsoft 365.
  • 使用 TLS 和证书Exchange内部部署服务器Office 365之间的安全电子邮件通信。Secure email communication between on-premises Exchange servers and Office 365 using TLS and certificates.
  • 在本地服务器和服务器Exchange发送Microsoft 365视为内部邮件,从而使这些邮件能够:Treat messages sent between on-premises Exchange servers and Microsoft 365 as internal, enabling them to:
    • 由面向内部邮件的传输和合规性代理正确评估和处理。Be properly evaluated and processed by transport and compliance agents targeting internal messages.
    • 绕过反垃圾邮件筛选器。Bypass anti-spam filters.

完全混合迁移最适合希望保持混合配置数月或数月以上的组织。Full hybrid migrations are best for organizations that expect to stay in a hybrid configuration for many months or more. 您将获得本节前面列出的功能,以及目录同步、更好的集成合规性功能,以及使用联机邮箱移动将邮箱Microsoft 365移动邮箱的功能。You get the features listed earlier in this section, plus directory synchronization, better integrated compliance features, and the ability to move mailboxes to and from Microsoft 365 using online mailbox moves. Microsoft 365成为本地组织的扩展。Microsoft 365 becomes an extension of your on-premises organization.

有关完全混合迁移需要考虑的一些内容:Things to consider about full-hybrid migration:

  • 它们并不适合所有组织。They aren't suited to all organizations. 由于完全混合迁移的复杂性,拥有少于几百个邮箱的组织通常看不到证明所涉及工作量和成本合理的好处。Due to the complexity of full hybrid migrations, organizations with less than a few hundred mailboxes don't typically see benefits that justify the effort and cost involved. 在这种情况下,我们建议你改为考虑使用"转换"或"最小混合迁移"。In such cases, we recommend that you consider cutover or minimal hybrid migration instead.
  • 你需要在本地 Active Directory 服务器Azure Active Directory (Azure AD) 连接设置目录Microsoft 365。You need to set up directory synchronization using Azure Active Directory (Azure AD) Connect between your on-premises Active Directory servers and Microsoft 365.
  • 用户将能够使用登录到本地Microsoft 365时使用的相同用户名和密码登录其邮箱。Users will be able to sign in to their Microsoft 365 mailbox with same user name and password they use when they sign in to the local network. (此功能需要 Azure AD 连接密码同步和/或 Active Directory 联合身份验证服务) 。(This functionality requires Azure AD Connect with password synchronization and/or Active Directory Federation Services).
  • 您需要一Microsoft 365许可证,其中包含Exchange Online迁移的每个用户邮箱的邮箱。You need a Microsoft 365 license that includes Exchange Online for each user mailbox you migrate.
  • 用户无需在大部分设备上设置新的 Outlook 配置文件,尽管某些较旧的 Android 手机可能需要新的配置文件。Users don't need to set up a new Outlook profile on most of their devices, although some older Android phones might need a new profile. 用户无需重新下载其电子邮件。Users won't need to redownload their email.

重要

如果你的组织选择将邮箱迁移到 Microsoft 365但计划保留 DirSync 或 Azure AD 连接 以继续从本地 Active Directory 管理用户帐户,你需要在本地至少保留一个 Exchange 服务器。If your organization chooses to migrate mailboxes to Microsoft 365 but plans to keep DirSync or Azure AD Connect in place to continue managing user accounts from on-premises Active Directory, you need to keep at least one Exchange server on-premises. 如果Exchange服务器的所有收件人,将无法对Exchange中的收件人Exchange Online。If all Exchange servers are removed, you won't be able to make changes to Exchange recipients in Exchange Online. 这是因为授权源仍保留在本地 Active Directory 中,并且需要在那里进行更改。This is because the source of authority remains in your on-premises Active Directory and changes need to be made there.

如果完全混合迁移适合您,请参阅以下有用资源:If a full hybrid migration sounds right for you, see the following helpful resources:

升级到本地部署Exchange Server版本Upgrade to a newer version of Exchange Server on-premises

我们强烈建议您通过完全迁移到 Microsoft 365 获得最佳值和用户体验。We strongly believe that you get the best value and user experience by migrating fully to Microsoft 365. 但我们了解,某些组织需要将一些 Exchange 服务器保留在本地。But we understand that some organizations need to keep some Exchange Servers on-premises. 这可能是由于法规要求、保证数据不存储在外数据中心中、由于你具有在云中无法满足的独特设置或要求,或者因为您仍使用本地 Active Directory 而需要 Exchange 来管理云邮箱。This might be because of regulatory requirements, to guarantee data isn't stored in a foreign datacenter, because you have unique settings or requirements that can't be met in the cloud, or because you need Exchange to manage cloud mailboxes because you still use Active Directory on-premises. 在任何情况下,如果在本地Exchange,应确保 Exchange 2010 环境至少升级到 Exchange 2013 或 Exchange 2016。In any case, if you keep Exchange on-premises, you should ensure your Exchange 2010 environment is upgraded to at least Exchange 2013 or Exchange 2016.

为了获得最佳体验,我们建议将剩余的本地环境升级到 Exchange 2016。For the best experience, we recommend that you upgrade your remaining on-premises environment to Exchange 2016. 如果你想要直接从 Exchange Server 2010 到 Exchange Server 2016,无需安装 Exchange Server 2013。You don't need to install Exchange Server 2013 if you want to go straight from Exchange Server 2010 to Exchange Server 2016.

Exchange 2016 包含早期版本的 Exchange。Exchange 2016 includes all the features of previous releases of Exchange. 虽然某些功能仅在 Microsoft 365 中可用,但它最匹配 Microsoft 365。It most closely matches the experience available with Microsoft 365, although some features are available only in Microsoft 365. 查看你缺少的一些内容:Check out just a few of the things you've been missing:

Exchange版本Exchange release 功能Features
Exchange 2013Exchange 2013 简化的体系结构将邮箱、客户端访问、边缘传输 (服务器角色的数量减少为三) Simplified architecture reduces the number of server roles to three (Mailbox, Client Access, Edge Transport)
数据丢失防护策略 (DLP) ,有助于防止敏感信息泄露Data loss prevention policies (DLP) that help keep sensitive information from leaking
改进Outlook Web App体验Improved Outlook Web App experience
Exchange 2016Exchange 2016 2013 Exchange及 ... 中的功能Features from Exchange 2013 and …
将服务器角色进一步简化为仅邮箱和边缘传输Further simplified server roles to just Mailbox and Edge Transport
改进了 DLP,并集成了SharePointImproved DLP along with integration with SharePoint
改进了数据库恢复能力Improved database resilience
联机文档协作Online document collaboration
注意事项Consideration 详细信息More information
支持结束日期End of support dates 与 Exchange 2010 一样,Exchange版本都有自己的支持结束日期:Like Exchange 2010, each version of Exchange has its own end-of-support date:

Exchange 2013 年 4 月 - 2023 年 4 月Exchange 2013 - April 2023
Exchange 2016 年 10 月 - 2025 年 10 月Exchange 2016 - October 2025

支持结束日期越早,需要执行另一个迁移越早。The earlier the end-of-support date, the sooner you'll need to perform another migration. 2023 年 4 月比您想象得要近很多!April 2023 is a lot closer than you think!
2013 Exchange 2016 的迁移路径Migration path to Exchange 2013 or 2016 无论选择 2013 Exchange 2016,从 Exchange 到较新版本的迁移路径都是相同的Exchange 2013 Exchange版本:The migration path from Exchange 2010 to a newer version is the same whether you choose Exchange 2013 or Exchange 2016:

将 Exchange 2013 或 2016 安装到现有 Exchange 2010 组织中。Install Exchange 2013 or 2016 into your existing Exchange 2010 organization.
将服务和其他基础结构移动到 Exchange 2013 或 2016。Move services and other infrastructure to Exchange 2013 or 2016.
将邮箱和公用文件夹移动到 Exchange 2013 或 2016 停止使用其余 Exchange 2010 服务器。Move mailboxes and public folders to Exchange 2013 or 2016 Decommission remaining Exchange 2010 servers.
版本共存Version coexistence 迁移到 Exchange 2013 或 Exchange 2016 时,可以将任一版本安装到现有 Exchange 2010 组织中。When migrating to Exchange 2013 or Exchange 2016, you can install either version into an existing Exchange 2010 organization. 这使您能够在 2013 或 Exchange 2016 Exchange安装一台或多台服务器,并执行迁移。This enables you to install one or more Exchange 2013 or Exchange 2016 servers and do your migration.
服务器硬件Server hardware 服务器硬件要求自 2010 Exchange已更改。Server hardware requirements have changed from Exchange 2010. 确保你的硬件兼容。Make sure your hardware is compatible. 在此处了解有关每个版本的硬件要求更多信息:Find out more about hardware requirements for each version here:

Exchange 2016 系统要求Exchange 2016 system requirements
Exchange 2013 系统要求Exchange 2013 system requirements

随着性能Exchange以及较新服务器中的计算能力和存储容量的提升,您可能需要更少的服务器来支持相同数量的邮箱。With the significant improvements in Exchange performance and the increased computing power and storage capacity in newer servers, you'll likely need fewer servers to support the same number of mailboxes.
操作系统版本Operating system version 每个版本支持的最低操作系统版本为:The minimum supported operating system versions for each version are:

Exchange 2016 - Windows Server 2012Exchange 2016 - Windows Server 2012
Exchange 2013 - Windows Server 2008 R2 SP1Exchange 2013 - Windows Server 2008 R2 SP1

有关操作系统支持详细信息,请参阅Exchange可支持性矩阵。You can find more information about operating system support at Exchange Supportability Matrix.
Active Directory 林功能级别Active Directory forest functional level 每个版本支持的最低 Active Directory 林功能级别为:The minimum supported Active Directory forest functional levels for each version are:

Exchange 2016 - Windows Server 2008 R2 SP1Exchange 2016 - Windows Server 2008 R2 SP1
Exchange 2013 - Windows Server 2003Exchange 2013 - Windows Server 2003

有关林功能级别支持的信息,请参阅Exchange可支持性矩阵。You can find more information about forest functional level support at Exchange Supportability Matrix.
Office客户端版本Office client versions 每个版本的Office支持的最低客户端版本为:The minimum supported Office client versions for each version are:

Exchange 2016 - Office 2010 (最新更新) Exchange 2016 - Office 2010 (with the latest updates)
Exchange 2013 - Office 2007 SP3Exchange 2013 - Office 2007 SP3

有关支持性矩阵Office客户端支持Exchange详细信息Find more information about Office client support at Exchange Supportability Matrix.

使用以下资源来帮助进行迁移:Use the following resources to help with your migration:

Office 2010 客户端和服务器以及 Windows 7 的选项摘要Summary of options for Office 2010 client and servers and Windows 7

有关 Office 2010 客户端和服务器以及 Windows 7 的升级、迁移和移动到云选项的直观摘要,请参阅终止支持海报For a visual summary of the upgrade, migrate, and move-to-the-cloud options for Office 2010 clients and servers and Windows 7, see the end of support poster.

停止支持 Office 2010 客户端和服务器以及 Windows 7 海报End of support for Office 2010 clients and servers and Windows 7 poster

此单页海报说明了响应 Office 2010 客户端和服务器产品以及 Windows 7 到达支持结尾的各种途径,并突出显示了 Microsoft 365 企业版 中的首选路径和选项支持。This one-page poster illustrates the various paths you can take to respond to Office 2010 client and server products and Windows 7 reaching end of support, with preferred paths and option support in Microsoft 365 Enterprise highlighted.

您还可以下载 此海报 ,以 11 x 17 格式的信件、 (或文) 打印。You can also download this poster and print it in letter, legal, or tabloid (11 x 17) format.

如果需要帮助,如何?What if I need help?

如果你要迁移到 Microsoft 365,你可能有资格使用我们的 Microsoft FastTrack 服务。If you're migrating to Microsoft 365, you might be eligible to use our Microsoft FastTrack service. FastTrack 提供了最佳做法、工具和资源,使迁移到 Microsoft 365尽可能无缝。FastTrack provides best practices, tools, and resources to make your migration to Microsoft 365 as seamless as possible. 最好有一位支持工程师,负责将你完成从规划和设计到迁移最后一个邮箱的阶段。Best of all, you'll have a support engineer walk you through from planning and design to migrating your last mailbox. 有关 FastTrack 的更多信息,请参阅Microsoft FastTrack。For more about FastTrack, see Microsoft FastTrack.

如果在迁移到 Microsoft 365 期间遇到问题,并且不使用 FastTrack,或者正在迁移到较新版本的 Exchange Server,可以使用以下资源:If you run into problems during your migration to Microsoft 365 and you aren't using FastTrack, or you're migrating to a newer version of Exchange Server, here are some resources you can use:

帮助从 Office 2010 服务器和客户端升级的相关资源Resources to help you upgrade from Office 2010 servers and clients