Man On The Way

    Yesterday I found there are 2 exchange servers alway running CPU at 100%. I ran task manager to find 'monitoringhost.exe' process utiled all CPU resource.
    Monitoringhost.exe is the agent for System Center Operations Manager 2007 that is installed on clients. We are lucky that there is a patch on Microsoft Website.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;954903

    Download this hotfix and install it on your SCOM2007 management server, then upate agents on all servers should fix this issue.

I have 2-node SQL Server 2005 Cluster which configured as Active/Passive mode, let say A node and P node. I already install 1 CRM instance on this cluster before. Now I wanna to install a second 2-node cluster  on these 2 servers, this time, A node will act as the passive node of 2nd cluster, P node will act as the active node. So I have to install them under named instance. After sql server installation, i patched SP3.
now the environment is below (All running 64-bit platform, OS is Windows Server 2008 x64, SP1):
Cluster 1   CRMSQLVS01 (192.168.10.101)
Active Node: A (192.168.10.1)
Passive Node: B (192.168.10.2)
Instance name: MSSQL (Default Instance)

Cluster 2   CRMSQLVS02  (192.168.10.102)
Active Node: B  (192.168.10.2)
Passive Node: A (192.168.10.1)
Instance name CRMSQL2 (Named Instance)
        All services are running fine. So I start install another instance on Cluster 2. On Server Server page, I type 'CRMSQLVS02\CRMSQL2', finally it gave me a error message: 'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)', i read some posts which searched via search engine,
http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/02/27/unable-to-connect-to-a-sql-server-named-instance-on-a-cluster.aspx
        I use portqry.exe -n yourservername -p UDP -e 1434 to check UDP connection, both worked on each server's physical ip, but failed on cluster virtual server ip.
        Finally, i found a workaround on MS Forum.
http://social.microsoft.com/forums/en-US/crmdeployment/thread/30bd2f37-27a5-4598-8183-d5780e05b1e4/

create the following key in the registry:

Install SQL Server 2005 on a Windows Server 2008, when use your browser to access http://localhost/reports, you received below error msg:
"An error occurred while parsing the configuration file. The ReportServerVirtualDirectory element is missing. "
After doing some search&research, this is the workaround.

Lookin the RSWebApplication.config for the "<ReportServerVirtualDirectory>"

It will look something like this

<ReportServerVirtualDirectory></ReportServerVirtualDirectory>

change to

<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>

Description of Update Rollup 3 for Hosted Messaging and Collaboration 4.5

http://support.microsoft.com/?id=969820

Here is a brief description on what is included in this Rollup 3. This isn't a big update. It consists of,

• All the updates in HMC 4.5 Rollup 2 and,

This update rollup fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• When you create a Public folder, useDatabaseQuotaDefaults is automatically set to true.
• Exchange 2007 Resource Manager::DeallocateConsumerUserMailbox did not flush all candidates in HMC 4.5

This has been released a while ago but in case you missed this.

http://support.microsoft.com/?id=961991

Please take note that, this hotfix, although it is named as an rollup, it does not include RU4. Hence, you will need to first deploy RU4 before you deploy this hotfix.

转自 http://blogs.technet.com/provtest/archive/2009/01/01/hmc-4-5-and-exchange-2007-sp1-part-5-autodiscover-in-the-multi-tenancy-environment.aspx 很好的文章,贴过来收藏,hehe.

Introduction

So, we have covered quite a fair bit by now. In part #1, we talked about how we can properly partition the Active Directory so that each company or tenant can coexist in the same environment but yet remain isolated and segregated. In part #2, we talked about how we have tweaked the address list so that each tenant will only see what they are supposed to see. In part #3, we further explore how Offline Address Book needs to be tweaked in to work in a multi-tenant environment and in part #4, we discussed about how Out-of-Office doesn't work completely out of the box in a hosted Exchange environment and what HMC has introduced to make it work better.

So, what's next?

转自 http://blogs.technet.com/provtest/archive/2008/12/26/hmc-4-5-and-exchange-2007-sp1-part-3-internal-and-external-out-of-office.aspx 很好的文章,贴过来收藏,hehe.

Internal and External OOF in HMC Environment

So, the 4th main customization that HMC introduces to Exchange 2007 is the OOF Transport Agent. What is OOF? Here is the text book definition, "The Out-of-Office (OOF) feature is commonly used by end-users to let other people know when they are not available to respond to e-mail." Now, I don't intend to go into the working of OOF in Exchange 2007 because I think there are better articles out there that talk about it.

Here, I want to briefly explain how Exchange 2007 OOF, out of the box isn't really working complete in a HMC environment and how we make it work.

转自 http://blogs.technet.com/provtest/archive/2008/12/18/hmc-4-5-and-exchange-2007-sp1-part-3-offline-address-book-generations.aspx 很好的文章,贴过来收藏,hehe.

Introduction 

In the last part, we discussed about Address List segregation, which is an important concept to understand in Hosted Exchange environment. It is my belief that if you understand that clearly, you have understood 70% of the Hosted Exchange concept in HMC. The rest will be just easy. :)

In this part, we will continue to discuss about Offline Address Book (OAB) Generations in a HMC environment. I don't intend to talk about the OAB generation process in Exchange 2007 because I think Dave Goldman's web log has covered most of them (http://blogs.msdn.com/dgoldman/default.aspx). Now, for those who are interested to know more, I think the following is a good starting point (although the content is mainly Exchange 2003, the whole OAB generation process hasn't changed much)

Overview of the OABgen process
http://blogs.msdn.com/dgoldman/archive/2005/03/31/Overview-of-the-OABgen-process.aspx

My primary objective in this blog is to discuss about the customization of OAB components in Exchange 2007 SP1 done by HMC.

转自 http://blogs.technet.com/provtest/archive/2008/12/10/hmc-4-5-and-exchange-2007-sp1-part-2.aspx 很好的文章,贴过来收藏,hehe.

Introduction 

In part #1, I spent a fair bit of time explaining how HMC was introduced into Exchange as part of the multi-tenant enablement process for service provider. I also spent some time discussing about how the Active Directory was partitioned and what the primary attributes that are essential to the Exchange 2007 SP1 multi-tenant enablement.

So far, there wasn't anything complicated about it. Now, I am going to move on to the 2nd part of the customizations, which is probably one of the more important ones, that is the Address List Segregation.

Let's look at what address lists we need to segregate and why. Address list is about contact information which is very important because it makes managing and finding your contacts (internal as well as external) easier and hence makes communication easier. There are a few places where you will use Outlook to locate the contact information,

在把 Virtual Server 2005 的虚拟机迁过去 Windows Server 2008 Hyper-V 以后,原来有些虚拟机开了 undo disk 的,发现在 Hyper-V 中没有合并选项,于是又重新安装了 Virtual Server 2005 SP1, 但是合并的时候失败,出错提示如下:

"Virtual Server was unable to commit the changes made during the current session of "[VPC NAME]". The cause of this problem is that the parent virtual hard disk is a part of a saved state. Your changes will be kept for the next time you start this virtual machine."

解决方法如下:

If you search google for this, you come up with almost nothing.  But there's a critical post right here about it.  It spells out exactly what you need to do, but foolishly I ignored it and kept looking for a better solution, since I didn't understand the concept of "inspecting" a virtual disk.

The basic steps are:

1. Rename the undo disks to *.vhd.  This turns them into a virtual drive in the eyes of Virtual Server.
2. Click on the Inspect option in the Virtual Disk section of Virtual Server.  There should be an option to then merge the disk.
3. Select a new disk to merge into.  If you try merging into the original parent, Virtual Server will just give you the above error again.
4. Take your newly merged virtual disk and replace it in the virtual machine (i.e. replace the parent that was couldn't be merged to before).