A multi-tenant Exchange deployment is defined in this document as one where the system has been configured to host multiple and discrete organizations or business units (the tenants) that ordinarily do not share e-mail, data, users, global address lists, or any of the other commonly used objects in Exchange. 

This document does not provide step-by-step instructions about how to achieve multi-tenancy with Exchange 2010 SP2, but provides information on the challenges and problems that need to be solved, and offers advice and direction to ensure the Exchange environment that you build can be supported by Microsoft.

Download Link: http://www.microsoft.com/download/en/confirmation.aspx?id=28192


The purpose of this blog post is to explain the next step in the evolution of our thinking regarding /hosting mode. After hearing feedback about the importance of these features, we have concluded that the best approach to multi-tenant hosting on Exchange is to use the on-premises configuration as the basis for a hosting infrastructure. As such, no additional features will be added to /hosting mode, and it will not be carried forward into the next version of Exchange. Here are a few key facts you'll need to know:

  • /hosting mode will be supported through the standard support lifecycle for Exchange 2010. It will still be available in SP2 and any future service packs or roll-ups. No additional functionality or features will be added to /hosting mode, however, and we don't recommend using /hosting mode going forward due to its reduced feature set and the fact that it will add complexity to future upgrades.
  • Multi-tenant hosting on the next version of Exchange will be supported, in a similar fashion to theapproach we will take with Exchange 2010 SP2.
  • Migrating from Exchange 2010 /hosting mode to the on-premises configuration of Exchange (2010 or future versions) will require deployment into a separate forest.
  • Microsoft will publish guidelines for hosting a multitenant environment using the on-premises configuration. Microsoft will also publish a step-by-step process for upgrading from Exchange 2007 HMC or migrating from Exchange 2010 SP1 /hosting to Exchange 2010 SP2 using the on-premises configuration.
  • Hosting automation tools and control panel solutions will be provided by our hosting ISV partners. We are working closely with them to ensure their solutions meet our hosting guidelines (and will therefore be supported).
1. ESE - Extensible Storage Engine 可扩展存储引擎

众所周知,Exchange 的邮件数据库文件是 .edb,实际上是ESE 数据库,它采用 B+ tree 平衡树结构来存储数据,如下图所示,树的根级别的节点个数与树的叶级别的节点个数总是相同的。因此,树是平衡的。详情这里不再展开,感兴趣的可以自行查找相关资料。

Exchange-2010-Btree.jpg
Figure 1 - 平衡树结构示意图

目前,有四个正在使用的 ESE 版本:
ESE97 Exchange Server 5.5 中的数据库引擎。
ESENT 用于 Active Directory 和许多其他 Microsoft Windows 组件的数据库引擎。与 ESE 的其他版本(它们使用 5 MB 日志文件和 4 KB 页大小)不同,ESENT 的 Active Directory 实现使用 10 MB 日志文件和 8 KB 页大小。
ESE98 Exchange 2000 Server 和 Exchange Server 2003 (32位)的数据库引擎,使用 5MB的日志文件和 4KB 页大小,
ESE for Exchange 2007/2010 Exchange Server 2007/2010 的数据库引擎,ESE98的改进版本。Exchange 2007 使用1MB的日志文件和8 KB 页大小。而在 Exchange 2010 中,使用 1MB 的日志文件和32 KB 页大小。

越小的日志文件和页大小可以提供更快的读写访问速度和更好的灾难容忍度。


I am running with Website panel for managing Exchange 2010 SP1 with /hosting switch, but I got failed when creating some organizations. 

Get-Organization shows the OrganizationStatus is "PendingCompletion", I tried 
Remove-Organization even with -Force, no luck. It always says 

"You can't remove organization "xxxxx" because it isn't active.
    + CategoryInfo          : InvalidArgument: (:) [Remove-Organization], OrganizationPendingOperationException
    + FullyQualifiedErrorId : 6D503EE2,Microsoft.Exchange.Management.Deployment.RemoveOrganization"
久违了,最近时间太忙,连博客服务器都忘记开了。
今天重新开机,升级到 4.37。
我会继续在这分享技术和心得,谢谢大家捧场。
昨天想试试在现有的 OCS 2007 R2 的基础上部署 Lync Server 2010 试试看,装好 Topology Builder 之后,新建了一个拓扑,然后把该填的都填了,发布的时候老是报SQL错,很是郁闷,后来终于在log中找到了错误原因:

 Script result: ERROR_VALIDATE_BAD_SQL_VERSION

Error: Script failed (code "ERROR_VALIDATE_BAD_SQL_VERSION") when installing "CentralMgmtStore" on "LyncServer01.mail2any.local". For details, see the following log file: "C:\Users\Administrator.Mail2any\AppData\Local\Temp\Create-CentralMgmtStore-LyncServer01.mail2any.local-[2010_12_22][16_11_55].log"

Error: An error occurred: "Microsoft.Rtc.Common.Data.SqlConnectionException" "Cannot open database "xds" requested by the login. The login failed.
Login failed for user 'Mail2Any\Administrator'."

 

看到这个 Bad Version 版本错误提示,我才想起来原来部署 OCS 2007 R2 的时候,后端数据库用的是 SQL Server 2008,而 Lync Server 2010需要至少 SQL Server 2008 SP1 才行,于是乎打上 SP1 补丁,顺利通过发布。SQL Server的版本需求:

  • Standard or Enterprise Edition of SQL Server 2005 with Service Pack 3
  • Standard or Enterprise Edition of SQL Server 2008 with Service Pack 1
  • Standard or Enterprise Edition of SQL Server 2008 R2
     
公司部署了个新的 IIS 站点,需要强制在 Https 下面访问,但是又不希望关掉80端口的 Http 请求,这样对用户体验来讲不好,最好是能强制所有的 Http 请求都会被重定向到 Https 上面去,显然, IIS 自带的 "HTTP Redirect" 已经不能满足这个需求,我们这里使用 IIS 7.0 下面的重定向扩展 URL Rewrite Module 来做。

1. http://www.iis.net/download/URLRewrite 到这里下载,有分 32 和 64 位版本。

2. 安装完后,可以在 IIS 站点管理的根目录下面看到多了个 URL Rewrite。

3. 双击打开,你会看到一个规则配置的页面。

4. 点击 "Add Rules" 添加规则,选择默认的"Blank Rule" 作为模板。

How to make your computer remember your Microsoft Communicator 2007 R2 and Outlook 2007 password (如何让你的电脑在非域环境中记住 OC 2007 R2 和 Outlook 的密码)

我们知道,在域的环境中,使用 OC 和 Outlook 都可以使用 Windows 的集成验证来完成用户验证过程,也能很方便的记住密码自动登录,但是如果你的电脑没有在域环境中或者工作站所在的域与 Exchange/OCS 所在的域没有联系呢? 这个时候,你甚至连"保存密码"的复选框都看不到,怎么办?

微软在9月17日在网站上放出了 CRM 2011 (也就是CRM5.0)的 beta 版本,我就先来个简单的快读安装图解,一睹为快,下个月会写点新版 CRM 的使用感受。

下载:

Microsoft Dynamics CRM 2011 Beta

Microsoft Dynamics CRM 2011 Software Development Kit (SDK)

Microsoft Dynamics CRM 2011 Beta Implementation Guide

 

界面一览

今天有空把所有的 Exchange 服务器从 2010 RTM 升级到了 2010 SP1 了, 升级完了后发现了2个小问题:

  1. OWA打开正常,但是点到 ECP 的时候报 403 访问拒绝错误
  2. 某台 Exchange 打开 EMS 时报错如下:

[server.mydomain.local] Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId : PSSessionOpenFailed

 

1. 这个错误在经过仔细排查后发现, 取消在IIS虚拟目录里面ecp的 "Require SSL" 就可以了,原来是之前为了做 SSL Offloading,把这个SSL的要求取消了,但是 Exchange 2010 SP1的安装程序在升级的时候又给加上去了,所以就报错了。

2..这个错误在网上查了好久,都没发现有用的答案,包括重装 WinRM IIS 扩展,重新配置 PowerShell 虚拟目录,运行 WinRm QuickConfig 等等,都没有用,最后发现问题还是出在IIS上面,Default Web Site 一开始给禁用了,而且默认的端口也从80改到了8080,EMS在打开的时候需要访问 Default Web Site 下面 PowerShell 的虚拟目录,找不到,报错,改回去80,错误解决。

 

Recent Comments

Close