Wednesday, September 26, 2012

Exchange 2010 SP3 is coming early next year!

Looks like MS will release Exchange 2010 SP3 in the new year:

Support for Exchange 2013 coexistence (schema update required) seems to be the big new feature.

Monday, July 16, 2012

Exchange 2013 Preview is out:

Now only 2 roles (back to 2000/2003 days)
No RPC client access - Outlook connects via RPC over HTTPS (wow)
More progress in trying to kill public folders
No co-existence with Exchange 2003

Lots of other things as well.  Interesting direction MS is going now, we'll see if
it's the right one in a few years.

Tuesday, June 05, 2012

Exchange 2010 Junk Email filter is broke... duh.

This has been broke for a while but just recently was documented by Microsoft:

Even though there is no resolution listed in the article I've been told by a trusted resource
that this fix is in Exchange 2010 sp2/ru3.

YMMV, be sure to test!

Tuesday, April 10, 2012

For those companies moving from Exchange 2003 to Exchange 2010, using groups to manage a particular distribution group membership is no longer an option as that feature was removed from 2010.  Microsoft has provided an 'as is' script to use as a workaround but why they felt it was ok to ship 2010 without this feature is crazy.  I understand the technical reasons but they should have resolved those before shipping as this is a basic feature.

The push for new features is great but that has to be balanced with providing a solid platform with all basic
functionality intact.  Now E15 is coming and many admins are still struggling with the upgrade to 2010.  
For those people using EAS from Autonomy, they just released version which supports sp2 for Exchange 2010.  Autonomy seems to be taking longer and longer for updates for EAS which is probably
their way of pushing people to their newer archive product.

It's been a while since I posted but this ones a doozy.  If these steps are not followed before installing sp2 for Exchange 2010, you can end up with a hosed server and the only fix is to install via /m:recoverserver.

Why Microsoft felt it only necessary to put this information in the the release notes and not make a big warning/post about it is beyond me.  Caveat Emptor.