Monday, October 18, 2010

Rehoming System Attendant (SA) mailbox on Exchange 2010

If the dabase is deleted where the System attendant (SA) i placed, Microsoft has a fine article for Re homing the SA mailbox, in Exchange 2007.
The article called "The System Attendant homeMDB attribute is missing" is here:

It's a refference from the Best practise analyzer which will tell if there's a server where the SA is missing a homemdb value.

But I havent found an article for Exchange2010, where the path to the databases are slightly different.

In Adsi Edit you should instead use this path:

  • Configuration []
  • CN=Configuration,DC=contoso,DC=com
  • CN=Services
  • CN=Microsoft Exchange
  • CN=
  • CN=Administrative Groups
  • CN=Exchange Administrative Group (ID)
  • CN=Databases

The new path is is obviously because the Storage groups are gone in Exchange 2010, and the databases are now global instead of dedicated to a server.

Tuesday, October 5, 2010

Exchange 2010 Sp1 Experiences

SP1 has been out for a month now - and here's my experiences so far.
Please comment, if you have any :-)

Of course SP1 is unavoidable because of all the new features and bugfixes.
But had a litte trouble after the upgrades.

Every Nokia mobile running Mail For Exchange (MFE/Mail4Exchange) had problems.
Some could be solved running a Full Resync, several times, but most had to delete the MFE profile and recreate it.
This was with various Nokia models, and most of them was running newest version of MFE.
This is most likely a Nokia problem, but will still prevent me from installing SP1 for customers with a lot of Nokia users.

The only other "problem" i had, was that Backup Exec required to be updated to "Backup Exec 2010 R2", and this of cource requires you to buy a new license, unless you have subscription on the product

Beside from that I haven't experienced anything that's not in the Exchange teams own blog: