Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
如何从Exchange Server 2003/2007升级到Exchange Server 2010
UNC-300-2
赵建勋
ATS Global Account
微软(中国)有限公司
升级到Exchange Server 20010的价值在哪里?
如何升级到 Exchange Server 2010
• 基于角色管理和用户自主服务
• 基于 Web 的管理和远程 PowerShell
• 单一的平台实现可用性, 备份和恢复
• 保持用户连接时,联机移劢邮箱
• 从 SAN 到低成本的 DAS,多种选择存储方案
• 模块化服务器角色简化部署
• 连续复制技术的革新
• 2台服务器可以实现Exchange功能的冗余
• 每个数据库有16副本,减少备份频率
• 存储的部署方案选择更广泛
DB1
DB3
DB2
DB4
DB5
从磁盘和数据库故障中快速恢复
DB1
DB2
DB4
DB5
DB3
DB1
DB2
DB4
DB5
DB3
复制数据库到远程数据中心
北京 上海
• 语音邮件的文本预览加快邮件处理
• 可定制的呼叫接听规则和菜单选项
• 增强的会话视图方便邮箱导航
• MailTips(邮件小贴士) 帮劣避免不可传递的/指示错误的邮件
• 跨“三个屏幕”的全功能体验
• 与伙伴共享闲/忙信息
• 系列信息保护和控制工具
• 传输中自劢的权限管理策略
• 集成的归档, 保留和取证
• 颗粒的保留策略和依法保留策略
• 通过Forefront 提供多种反病毒扫描引擎
• 提供云计算平台服务或自建保护选择
改进 E2007 E2010
声明/签名 文本格式 添加AD属性+HTML
附件 大小、名称 +内容 (Office文档)
分类 基于分类操作 可以针对无类别操作
全新的 E2010
应用RMS 应用RMS加密
Moderation Review和审批流程
邮件类型 RMS加密、自劢回复、语音邮件、批准申请
Supervision Lists 基于收件人的允许/阻止列表
管理属性 自劢识别管理者并且应用策略
Exchange 2003 Server
10
企业版 5 个数据库
群集
企业版 50 个数据库 群集(CCR)
Exchange 2007 Server
企业版 100 个数据库
Exchange 2010 Server
标准版 5个数据库
无数据库容量限制
标准版 2 个数据库
75 GB 存储限制
标准版 5 个数据库
无数据库容量限制
升级到Exchange Server 20010的价值在哪里?
如何升级到 Exchange Server 2010
系统现状评估
Exchange 升级规划与设计
POC验证
部署实施
验收、推广和培训
AD现状评估
DCDiag
Exchange 现状评估
Exchange 最佳实践分析器
网络现状评估
客户端现状评估
Exchange 拓扑架构
软/硬件规划
准备Active Directory和域
角色 最大处理器配置 推荐处理器配置 最大内存配置 推荐内存配置
中心传输 12 cores 4 cores 16 GB 每核1 GB 或 8 GB (最少)
客户端访问 12 cores 8 cores 16 GB 每核2 GB 或 8 GB (最少)
邮箱 12 cores 8 cores 64 GB 4 GB 加 每邮箱2-6 MB
统一消息 12 cores 4 cores 16 GB 每核2 GB 或 4 GB (最少)
多角色混用 16 cores 8 cores 64 GB
8 GB加 每邮箱2-6 MB
Windows Server 2008 SP2 或R2 64位版本
标准版, 企业版
Windows Management Framework
Windows PowerShell v2.0
Windows Remote Management v2.0
.NET Framework 3.5 SP1
Internet Information Services (IIS)
详细信息:http://technet.microsoft.com/zh-cn/library/aa996719.aspx
Exchange 版本 Exchange 组织共存
Exchange 2000 Server 不支持
Exchange Server 2003 支持
Exchange 2007 支持
Exchange 2007 和 Exchange Server 2003 的混合组织 支持
Internet facing AD site Internal AD Site
Internet
Hub/CAS/UM/MBX
2003 or 2007
Hub/CAS/UM/MBX
CAS-CAS Proxy
第一步:首先升级面向Internet的站点
第二步:升级Exchange Server2003到SP2
Internet facing AD site Internal AD Site
Internet
Hub/CAS/UM/MBX
2010
Hub/CAS/UM/MBX
2003 or 2007
https://m
ail.contoso.com
https://legacy.contoso.com Hub/CAS/UM/MBX
CAS-CAS Proxy
第一步:首先升级面向Internet的站点
第三步:首先部署2010 CAS ,最后MBX
第二步: 升级Exchange Server2003到SP2
第四步
• Internet 主机名到CAS 2010
• 配置前端服务器的旧主机名和客户端访问服务器角色
•语音邮件的PBX/GW指向UM 2010
第五步:移动邮箱
1. 将现有 Exchange Server 2003/2007 服务器升级到 Exchange 2003
SP2/Exchange Server 2007 SP2
2. 按以下顺序部署 Exchange 2010 服务器:
a. 客户端访问
b. 集线器传输
c. 统一消息
d. 邮箱
3. 配置 Exchange 2003 前端服务器和 Exchange 2010 客户端访问服务器
4. 配置 Exchange 2010 集线器传输服务器和统一消息服务器
5. 将邮箱从 Exchange 2003 移劢到 Exchange 2010
所有用户访问OWA 通过CAS 2010 URL CAS 2010 将重定向到FE2003/CAS2007, user will get single sign-on and can keep using the same URL OWA 2010 will not support Public Folder (PF) access to folder stored only on MBX 2007 or MBX 2003 servers In Exchange Server 2003, OWA rendering happens on Mailbox servers—front end (FE) 2003 is an authenticating proxy + PF/Mailbox integration logic
Client - Outlook Web Access
Outlook Anywhere“X
SO
MAPI”
Mailbox 2007
With public folder
Mailbox 2010
With public folder
Mailbox 2003
With public folder
Mailbox 2007
With mailbox
Mailbox 2010
With mailbox
Mailbox 2003
With mailbox
FE 2003CAS 2010CAS 2007
“XS
O M
AP
I”
“XS
O M
AP
I”
“XS
O M
AP
I”
Proxy + PF/MBX
integrated logic
SSO Redirection SSO Redirection
Client – EAS, POP, IMAP
MBX
2003
MBX
2010
MBX
2007
CAS 2010POP/IMAP client
Pro
xy
“XS
O M
AP
I”
CAS 2007
Proxy
WM 5/6 WM 6.1
Redirect
“XS
O M
AP
I”
Client – EAS, POP, IMAP
In Exchange Server 2007 and 2010 (Beta), EAS/POP/IMAP are parsed on CAS
In Exchange Server 2003, EAS/POP/IMAP are parsed on the mailbox server—2003 front end server is only an authenticating proxy
将旧有Exchange 服务器移除组织
移除Exchange Server 2007服务器角色的顺序
后端服务器
前端服务器
在同一个站点中,移除Exchange Server 2007服务器角色的
顺序
邮箱
统一消息
中心传输
客户端访问
AutoDiscover
Exchange 2007 CAS SP2
AutoDiscover
Exchange 2010 CAS
AutoDiscover
AutoDiscover intranet clients
Outlook finds
AutoDiscover
using AD Site
SCNsFor users with Exchange
2010 mailbox, AutoDiscover
redirects to 2010 CAS
AutoDiscover Service
AutoDiscover Internet Clients
(Outlook, WM6.1+, ESW clients like Entourage)
· Internet AutoDiscover end point is
moved to CAS 2010 first in migration
· AutoDiscover 2010 supports lookups for
2007 mailbox and 2010 mailbox
Edge & HUB migration
28
MBX 2010
MBX 2007
MBX 2003
HUB 2007
HUB 2010
“XSO MAPI”
“XSO MAPI”
Incoming email
SMTP
Perimeter network
Edge 2007 SP2
Edge 2010
SMTP
Edge 2007 SP2 can proxy to Hub 2010
Edge servers can be upgraded to E2010 last
Moving Mailbox to Exchange Server 2010 (Beta)
Source mailbox can be used by users as normal during “online” moves.
Online mailbox move is only available for Exchange Server 2007 and above.
No OST resync after mailbox move
MAPI RPC used for all moves
Exchange 2003
Exchange 2007
Exchange 2010 CAS with
“Mailbox Replication Service”Exchange 2010
Mailbox Server
Online
Offline
Unified Messaging Transition
With private branch exchange/gateways (PBX/GWs): One Dial Plan, Redirect
With Office Communications Server:
2 Dial Plans, Direct
Public Folder
Co-existence support between mailbox server 2010 and mailbox server 2003/2007.
Co-existence with mailbox server 2000 is not supported
Outlook can read mailbox from one Exchange version (e.g. 2010) and public folder from another (e.g. 2003/2007). OWA 2010 only gives access to public folders with replica in mailbox server 2010.
Error message when accessing public folder with replica only on Exchange 2003/2007
This is different from OWA 2007, which had a redirection behavior, opening up OWA 2000/2003 for public folders on older mailbox servers in separate browser windows
Get-PublicFolderStatistics now captures last user access
疑问和解答
参考资源
网站名称 http://www.xxxx.com
网站名称 http://www.xxxx.com
网站名称 http://www.xxxx.com
网站名称 http://www.xxxx.com
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.