Last week we released Exchange Server 2010 Service Pack 1. It has received some great feedback and reviews from customers, experts, analysts, and the Exchange community.
The starting point for...
Updated Jul 01, 2019
Version 2.0
Blog Post
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
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