Exchange 2003 SP2 was released to the Web early this morning.
It’s a good idea to install this (after a backup and testing) as there are a number of fixes in this as you can see by looking at the fix list at KB article 906669. If you look at the list you will see a lot of articles that seem to apply to Exchange 2000 and not 2003. Actually, this usually means that the fix was released for Exchange 2000 before it was ported to Exchange 2003. So the article still says Exchange 2000, but applies to Exchange 2003 as well.
Also it would be a real good idea to take a look at the “Read Me” notes at http://support.microsoft.com/kb/906671. You will see that if you are looking to enable the new feature Sender ID on your server you will want to get the Windows 2003 hotfix for the SMTP service. Otherwise the server could stop responding. Unfortunately, until Windows 2003 SP2 is released you will need to call Microsoft for this fix. I know you wish it was available for download publicly… The good news is that you shouldn’t get charged for the support call.
- Windows Server 2003 may stop responding when you enable the “Sender ID Filtering” setting on an SMTP virtual server in Exchange Server 2003 SP2
The new feature to enable or disable MAPI access per user is a neat feature if you want to limit people to only being able to access in cached mode. The downside is that doing this for every user using ADSIEdit can get old really quick. Here is a tip:
- The new version of ADModify.net (2.1) will do this much easier for you.
And as always, running the newest version of EXBPA after the install would be a great idea.
Update: Corrected link to http://support.microsoft.com/kb/906671