Exchange 2010 SP1 FAQ and Known Issues

re: Exchange 2010 SP1 FAQ and Known Issues

Dejan Foro — Tue, 16 Nov 2010 14:09:20 GMT

And here is another serious SP1 problem to add to the list:

Mailbox migration does not work from Exchange 2003 to Exchange 2001 SP1 where mailbox users have mailbox folder structure in an non/English language.

The following error is reported:

Error: MapiExceptionInvalidEntryId: Unable to SetSearchCriteria. (hr=0x80040107, ec=-2147221241)

And accordin to this post it seems to affect quite a number of people http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/89902f00-4b84-4f10-b909-121a81241c85

In my case I am trying to move mailboxes from Exchange 2003 to Exchange 2010 SP1.
Mailbox DB is clean, I can move the mailboxes to another Exchange 2003 database as well as to Exchange 2010 RU4 machine.

However move to Exchange 2010 SP1 does not work. Neither from Exchange 2003 or Exchange 2010 RU4.

So it is clearly an SP1 bug.

And I also have to concur with the frustrations that other colleagues are facing here.

As someone dealing with Microsoft technologies for 17 years of which 12 years specialised on Exchange I have to say that I am highly dissapointed with the quality of both softwarea and partner support Microsoft is delivering lately, it really seems to be on its lowest ever. (Some smart manager probably had some creative ideas that money could be saved by outsourcing testing and support to China ?)

We as a MS partner company are taking heavy hits in the field because of this both in revenue and customer satisfaction.

One recent example:
I just got of a project where we failed to implmenet Forefront TMG/Exchange Edge/Forefront Security 2010 for Exchange on a new server, because of numerous incompatibilities and bugs we encountered. It is a bluntant example that Microsoft is not testing or capabale to ensure compatibiliy among its own products.

Parnter Support also was a killer. They advised that installing Exchange is not supported on TMG (althoguh TMG requries Exchange Edge as prerequisite). They were also unable to provide information in which order should SPs and updates for Exchange/TMG and Forefront to be installed and they refered me to paid break/fix support where I shuld pay 500 USD for that information (and that was before install so noting broken to be fixed, just looking for general advice whcih falls under free partner support)

End result: We had to fail back to an old ISA 2006 and 3rd party product. Customer wasted serious money for licencing, we have lost 6 days of consulting which we can not charge meaning approx 10.000 USD direct damage for us in lost revenue plus travel and expenses .

Now with the same customer we are having this problems with mailbox moves plus I just got informed by the customer that for some mailboxes iPhone syncronisation is failing on Exchange 2010 SP1 as well and that they are swamped with spam (Exchange 2010 SP1 plus Forefront security 2010 for Exchange)

I could continue with similar examples for several other Microsoft products, but this is not place for it. I just wanted to give you a picture of pain we are getting in the field every time you guys at Microsoft mess up something with the sofware.

As a 6x Microsoft MVP I am stading embarrased in front of my customer and my emplyer and have to recommend things like failing back to old version and/or using products from other vendors.

Bottom line: bad software kills business.

The current testing process obviously has to be rediesigned to include at minimum testing with non English language settings and compatilbitiy with Microsoft s own products products that Exchange is supposed to integrate with namely ISA/TMG, Forefront Security For Exchange , Forefront DPM, OCS/LYNC.

Otherwise you will have same as with Vista, people will simply back out, wait for next version or even switch to other vendors.

Regards,
Dejan Foro

re: Exchange 2010 SP1 FAQ and Known Issues

Ian Eiloart — Mon, 15 Nov 2010 15:45:58 GMT

The x-originating-ip header is useful. I like to rate-limit users who are not on campus (because phishers are never on campus), but haven't seen how to do this with Exchange users before.

Unfortunately, you didn't use "X-originating-ip" (note the capitalisation. Although "X-" has no special protection since rfc822 was obsoleted, it seems that there is some code out there that expects RFC5322 message headers to be either registered headers, or to begin "X-" (not "x-").

Still, I'll be able to rewrite (or strip) the offending headers before they leave campus.

re: Exchange 2010 SP1 FAQ and Known Issues

Ru i ned — Sun, 14 Nov 2010 18:38:49 GMT

Rune does indeed appear to be an Exchange knowledge powerhouse. It sounds like a dark day for MS if he is going to " look for competitors offers"...MS could potentially lose TENS OF DOLLARS from this.

re: Exchange 2010 SP1 FAQ and Known Issues

Gary D — Fri, 12 Nov 2010 16:39:59 GMT

I bet the company that Rune is working for is so proud to have such a professional working for them. Though I agree MS missed the mark on this SP release, I do not belive showing ones ignorance with such unprofessional comments forced on all those who monitor this blog helps the situation one bit.

re: Exchange 2010 SP1 FAQ and Known Issues

Rune — Fri, 12 Nov 2010 02:10:08 GMT

(comment edited, explicit words removed by blog team)

Are u **** kidding me MS? I just installed hotfix rollup 4 and had a **** of issues, after uninstalling and FIXING it all I decided it might be time to update to SP1 - however after wasting a bunch of hours fixing the above mentioned **** by MS I decided I might just google SP1 to see and then this comes up - AWESOME!!! well done MS you made my day easy - no need to update, means I don't need to waste more time on your useless software. What happened to Exchange? It used to be better? At least I don't recall wasting countless hours on fixing shit that should never have been released.... time to look for other email providers... I will run SP0 for the lifetime of 2010 and look for competitors offers.
****

re: Exchange 2010 SP1 FAQ and Known Issues

Travis — Thu, 11 Nov 2010 21:24:48 GMT

In case anyone is still having issues with the GAL being empty..my issue was due to the msExchQueryBase DN value that I set in ADSI for each user to restrict the GAL in OWA...this value isn't used anymore in SP1 and causes Outlook to show an empty GAL..simply remove/clear the value

http://www.waronerrors.com/kb/global-address-list-is-empty-after-exchange-2010-sp1-installation-when-configured-for-address-list-segregation.aspx

re: Exchange 2010 SP1 FAQ and Known Issues

Lin — Thu, 11 Nov 2010 10:36:30 GMT

Does SP1 includes a fix which we can replicate free/busy information between Exchange 2003 organization and Exchange 2010 sp1 organization by using Inter-Org Replication tool?
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=e7a951d7-1559-4f8f-b400-488b0c52430e

My understand is that we can replicate public folder but free/busy info is not.

http://blogs.msexchange.org/walther/2009/12/02/exchange-2010-and-interorg-iorepl/

Appreciate for your response.

re: Exchange 2010 SP1 FAQ and Known Issues

Lukas — Thu, 11 Nov 2010 09:37:08 GMT

Great blog but maybe it would be appropriate to tell us too which services are required for successful installation because after I installed all hotfixes and prepared system w2k8r2 I'v got an error relating to disabled Microsoft .NET Framework NGEN v2.0.50727_X64 service. It was because Security Configuration Wizard gather it "not needed" and set the startup type to Disabled.

Regards,
Lukas

re: Exchange 2010 SP1 FAQ and Known Issues

JamesC — Mon, 08 Nov 2010 20:10:48 GMT

In regards to the Outlook 2003 and Shared calendars/accounts. Recently ran into this problem and discovered that setting the 2003 Accounts to "Cached" mode on the client, allowing it to build the OST and then restarting the client (thats 2 restarts after setting the check box), I was able to access the folder.

My testing included setting up a MAPI profile to access the shared account directly to verify permissions.

Once that was done, it was just trial and error till I found the right combo.

This is only a stop gap for our environment, as Cached mode is not something we want to do on our desktop systems so would appreciate a resolution. However I dont think the problem is going to be on the exchange side, but more on the office client side.

Our upgrade to Office 2010 is coming next fiscal year anyway, so it may be a moot point.

re: Exchange 2010 SP1 FAQ and Known Issues

Hans — Sat, 06 Nov 2010 11:56:42 GMT

Buggiest upgrade I have ever done.

If I knew, what I know now, I would hold of upgrading to SP1