Man On The Way

Today Microsoft released Update Rollup 2 for Microsoft Exchange Server 2010. RU2 comes 3 months after the release of RU1. The list of included fixes is not as long as with RU1, but RU2 does contain some important additional fixes over RU1:

• 977633 Certain third-party IMAP4 clients cannot connect to Exchange Server 2003 mailboxes through an Exchange Server 2010 CAS server
• 979431 The POP3 service crashes when a user connects to a mailbox through the POP3 protocol and the user is migrated from an Exchange Server 2003 server to an Exchange Server 2010 server
• 979480 Users cannot receive new messages if they access mailboxes that are moved to another Exchange Server 2010 RU1 server by using IMAP4 clients
• 979563 Exchange Server 2010 Push Notifications does not work
• 979566 A 0×85010014 error is generated when linked mailbox users try to synchronize their mailboxes with mobile devices in a CAS-CAS proxying scenario in Exchange Server 2010
• 980261 This fix introduces the supports for Exchange Server 2010 page patching when a "-1022″ disk I/O error is generated
• 980262 Event ID 2156 is logged on a computer that is running Exchange Server 2010

The related knowledgebase article (KB979611) can be found here. You can download Exchange 2010 Rollup 2 directly from here.

Description of Update Rollup 3 for Hosted Messaging and Collaboration 4.0

http://support.microsoft.com/kb/979702/en-us

Microsoft released an update rollup that is dated December 2009. This update fixes issues that may occur in the following components of Microsoft Solution for Hosted Messaging and Collaboration 4.0:

• Exchange 2007 Resource Manager Namespace
• Exchange 2007 Resource Manager Web Services
• Hosted Email 2007 Namespace
• Hosted Email 2007 Web Services
• Managed Email 2007 Namespace
• Managed Email 2007 Web Services
• Exchange 2007 Mobility Provider
• Exchange 2007 Provider
• Unified Messaging 2007 Provider
• Hosted SharePoint 2007 Namespace
• Managed SharePoint 2007 Namespace
• Hosted SharePoint Web Service
• Managed SharePoint Web Service
• DNS Provider

This will enable HMC 4.0 to support Exchange 2007 SP2!

Description of Update Rollup 6 for Hosted Messaging and Collaboration 4.5

http://support.microsoft.com/kb/979704

Microsoft has released an update that is dated December 2009. This update fixes issues in the following components in Microsoft Solution for Hosted Messaging and Collaboration 4.5.

• Exchange 2007 Resource Manager Namespace
• Exchange 2007 Resource Manager Web Services
• Hosted Email 2007 Namespace
• Hosted Email 2007 Web Services
• Managed Email 2007 Namespace
• Managed Email 2007 Web Services
• Exchange 2007 Mobility Provider
• Exchange 2007 Provider
• Unified Messaging 2007 Provider

Additionally, this update also includes native 64-bit versions of the following components:

• Exchange 2007 Mobility Provider

In order to get Exchange 2007 SP2 supported, do install this UR.

Description of Update Rollup 5 for Hosted Messaging and Collaboration 4.5

http://support.microsoft.com/kb/977174/en-us

Microsoft has released an update that is dated October 30, 2009. This update fixes issues in the following components in Microsoft Solution for Hosted Messaging and Collaboration (HMC) 4.5 and includes all fixes released in previous rollup packages RU1, RU2, RU3 andRU4.

• ResourceManageDatabase.msi
• Exchange2007ResourceManagerWS.msi
• HostedSharePoint2007WS.msi
• Exchange2007ResourceManagerNS.msi
• HostedSharePoint2007NS.msi

答题原则：

 

                                  选安全，选礼貌；

                                  遵章守纪最重要，

                                   除了撞车用急刹，

                                   稳住方向看好道。

                                   标志标线不难记，

                                   根据意思辨路标；

                                   方型辅助兰指示，

                                   红色禁止黄警告；

                                   看标线，有诀窍，

                                   颜色虚实要分牢；

                                   中心黄色同向白，

                                   黄线禁止和警告，

                                   实线绝对不能越，

                                   虚线可以适当绕；

                                   ※※※※※※※※※※※※※※※※※※※

答题诀窍：　　

凡是里面有"严禁、禁止、不得、必须、公安机关交通管理部门、车管所、回收企业"的是必选的或者是对的；凡是有"也行、不需要"是不能选或者是错的。

Today, one of my clients reported that, the reporting service cannot started.
They didn't change anything and database service is running fine.

Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 12/10/2009
Time: 11:53:21 PM
User: N/A
Computer: ABC
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

The Reporting Services logs mostly just repeat that "The Report Server Windows service 'ReportServer' is not running." ...

This article is from Dell TechCenter Wiki

This section documents creating multipath connections to iSCSI LUNs on a Dell PowerVault MD3000i using the Microsoft iSCSI Initiator plus Dell's MD3000i iSCSI software. The server connecting to the MD3000i iSCSI LUN was server r3win2950b running 64-bit Windows Server 2003 R2. As shown below each MD3000i controller had two iSCSI ports, with one each in the 10.10.20 and 10.10.22 subnets. The r3win2950b connected to both
network subnets.



The MD3000i uses its own Device Specific Module code and thus required special installation of the Microsoft iSCSI Initiator. Therefore, on the server being connected to MD3000i (r3win2950b in this case), the existing Microsoft iSCSI Initiator instance was uninstalled and the server was rebooted. Then the Microsoft initiator was installed from Initiator-2.04-build3273-amd64fre.exe. All installation options except Microsoft MPIO Multipathing Support for iSCSI were selected:

Things have been busy for me and i haven't had the time to complete this series in a timely fashion. In part #1, we briefly talked about what's in the PlanManager and ResourceManager databases from a very high level. In the next few parts, we will go in a little bit further to discuss how HMC manage the resource allocation in Exchange, SharePoint and also OCS.

Before we get into that, I think it is essential to talk about how HMC database, PlanManager is linked with the Active Directory. It is important to understand that it isn't the purpose of this article to discuss about the database schema but I will discuss briefly how they are linked.

This article was original posted by Kip.Ng onhttp://blogs.technet.com/provtest/archive/2009/07/20/planmanager-and-resourcemanager-part-1.aspx

I believe one of the most mysterious parts of HMC is about the MPS engine and the Resource Management databases. Between last December and January, I blogged about how different products (Exchange, SharePoint and OCS) integrate in a HMC Solution. However, understanding just the integration points without knowing the resource management portion definitely does not paint a complete picture of what HMC is.

Since then, I have received requests to discuss a bit about the resource management in HMC and what those databases that shipped with HMC are storing and being used. So, in my next few entries, I intend to spend some time talking about the following,

1.       PlanManager and ResourceManager - Overall Concept

2.       HMC Resource Management and Active Directory

3.       HMC Resource Management and Exchange

4.       HMC Resource Management and Windows SharePoint Services

5.       HMC Resource Management and Office Communication Servers

1. How to get mailbox size:
Get-Mailbox | Get-MailboxStatistics | select-object  DisplayName, @{Name="Size (MB)"; Expression={ "{0:N2}" -f ($_.TotalItemSize/1.0MB)}}