Exchange 2007 MP

A few people have written about importing the MP into 2007 and some of the issues.!3D3B8489FCAA9B51!240.entry plus some trouble shooting.
And a problem with it on MOM 2005 at!A4408C121568CAA4!1631.entry if you are also running Exchange 2003.

I have been busy installing it with MOM 2005 ( a joy to work with again after SCOM 2007) as the organisation wants a fully supported solution. I have heard a rumour that the MP might be released in October for 2007. My view is that they are working on the MP in parallel with Exchange 2007 SP1. That would fit in with how the product groups work. Interestingly in some of the alerts when you go to the web site (there is limited info in the Knowledge tab and everything seems to point to the web – shape of things to come – not good if you have to run the server in a secure environment with no Internet access as some government agencies need to do) the articles mention SCOM 2007 as well as MOM 2005. First time the documentation has been written before the product!

Having read the MP guide I though that this would be better as there is no longer the Exchange MP Wizard – hurrah! But there are 2 manual configurations but it is done by PowerShell scripts already supplied on the Exchange server. Should be easy! But only if it works first time. The MP guide is a whopping 72 pages but the MOM MP bit does not start until page 42.

To monitor OWA, Active Synch and Web Services Connectivity then you need to run New-TestCasConnectivityUser.ps1 on the Exchange servers. And just like the old wizard you need to have Exchange and AD rights as it creates a user for each mailbox server named CAS_{GUID} where the GUID is the first half of the GUID for each mailbox server. If all the servers are in the same domain then the one script will do them all by piping in the mailbox servers (get-mailboxServer | .\new-TestCasConnectivityUser.ps1). If they are not you need to log into the servers in the other domain with the correct rights.

The MP Guide talks about running “set-owavirtualdirectory” but the organistion already had it set. The guide assumes that you have not set it up – or so I assume. They don’t mention what to do if you have set up OWA already. They should provide a test to check that it is OK.

That is the problem with some of the guides. They are very long but light in the area where you need the most help. This bit is just 1 page. I know someone from Microsoft UK who went to Redmond a few years ago to help write a white paper for a few weeks. The story about the process and how it was done was not encouraging. 😦

Although that was set up the alerts still came up and the alert mentioned running the set-CasConnectivityCredentials script. But that script does not exist. Although Lee Owens has investigated the issue and found that if he ran the first script again it sorted things out. We ran the script again and this time it worked and gave the user which was previously created the correct rights. Scary stuff from the Exchange team.

Another weird thing is that the Exchange MP complains about running SP2 on Windows!
Rule Path – Microsoft Exchange Server\Exchange 2007\Common Components\Best Practices Analyzer\
Rule – Pre-release software detected. – event 1875
Apparently the built in BPA can only deal with servers on SP1.

There is a good three part guide by Brazilian consultant Anderson Patricio that covers setting up the Exchange 2007 MP including MOM 2005 parts and even configuring an ISA 2006 server in a DMZ that is publishing Exchange. For people that know MOM some chunks will be a bit obvious but it is a good guide non the less. He provides a list of all cmdlets that MOM uses to gather information from the Exchange in part one. Very useful as the official guide does not mention them!

Monitoring Exchange Server 2007 using MOM 2005 (Part 1)
Monitoring Exchange Server 2007 using MOM 2005 (Part 2) Monitoring Exchange Server 2007 using MOM 2005 (Part 3)

Also useful

Can’t wait for the version for 2007. Hope they fix the bugs.


Comments are closed.

%d bloggers like this: