imageA few days ago I drove a training for Tier 2 techs at the company devoted to the most common scenarios when we have to rely on mfcmapi heavily to fix the issue.

Being one of the greatest mfcmapi fans around I had a couple of tips to share and now I’d like to share them here as well.

Below are examples of troubleshooting scenarios best performed with MFCMAPI. They are well documented already and I don’t target to cover them in this article. I’d rather go ahead and share less known tips leaving those techniques for the next post.

I refer to the well-known basic operations with MFCMAPI as follows:

a.  Deleting corrupted Junk email rules

b.  Un-hiding hidden folders (or hide them)

c.  Deleting a delegate from mailbox

d.  Troubleshooting BlackBerry Enterprise Activation

e.  Troubleshooting Out Of Office

f.  Checking RefID of a message on BlackBerry

g.  Checking if the messages were marked by AV software or Outlook Junk email filter

 

A couple of tips every mfcmapi fan is aware about –

Always use online mode for a profile and check for a new version occasionally as frequently they contain either new features incorporated or bug fixes or bothSmile

I have selected the following techniques to discuss:
 

1.  Signature Issue and OWA Settings

2.  Autocomplete cache issue

3.  Restore from dumpster

4.  Delete/Create folders

5.  Restore messages/copy messages from folder to folder

6.  Item count

7.  Information about deleted items

Starting Monday I’m going to cover them gradually as I’m pretty certain mfcmapi is invaluable when dealing with low level mailbox problem and it’s second to none in such cases.

Stay tuned!

 

image

I’ve been taking part in a number of migrations from both on-premise installations and hosted solutions to the cloud in recent years.

It was pretty peculiar to find out how many folks around are still using legacy systems (from the standpoint of those who daily deal with cutting edge technology of course) like Exchange 2000 or even some POP servers with really limited functionality to say the least.

To strengthen my amusement was the fact that the most conservative businesses are the big organizations having access to bigger financial resources than SMBs. It is a kind of of ‘set it and forget it’ approach that, however, has its reasoning. Migration from such installations with hundreds of users actively using their emails usually takes at least a month an rarely turns to be completely painless. Moreover, many are skeptical to touch systems that ‘work’ and a bunch of new features and possibilities current messaging systems provide do not look very seducing under such circumstances.

And here comes product lifecycle that often becomes a change driver.

 image

Just a few months still remaining before the extended support ends for Exchange 2000 (not Conferencing server) that would inevitably mean certain difficulties for those maintaining in-house installations.

Exchange 2003 that is a flagship for most on-premise installations (yes, the number of Exchange 2007 installations is significantly smaller!) maintains its positions and will likely fall only to Exchange 2010 serving as another accelerator for a change.

These business if they prepare for the move will prepare moving to Exchange 2010 skipping Exchange 2007 due to not only a richer set of new features but also because of lower TCO and higher reliability.

image

Exchange 2007 is not going to retire soon apparently. However, some complexities involved in its deployment and some technology tremendously improved in Exchange 2010 (like storage design for example) do position the latter as a market leader and obvious market driver for years to come.

Having invested in Exchange 2010 the businesses may feel safe and quiet for a decade ahead:

image

Another trend worth mentioning is that more and more big organizations start outsourcing their messaging infrastructure to the cloud after they realize the cloud has become a reliable place for keeping sensitive data providing higher levels of safety, redundancy, reliability, support than many on-premise implementations. Lower TCO adds more value too.

Nice trend and I’m excited to see how the messaging evolves from mostly on-premise installations to the cloud based feature rich solutions benefitting businesses around the globe.

Exchange rocks!

© 2011 EHLO Me! Suffusion theme by Sayontan Sinha