The MAPI/CDO download package now works on Windows Server 2008 and Vista. The main blocker to getting this to work was the fact that in Windows Server 2008 and Vista, mapi32.dll was marked as a system file. Any attempt to replace it would be blocked or undone. Exchange's MAPI has always replaced mapi32.dll with its own version, so it couldn't work on those operating systems.
The fix is modify Exchange's MAPI to take advantage of the MAPI Stub Library mechanism. We moved Exchange's MAPI binaries out of system32/syswow64 and placed them under C:\Program Files\ExchangeMAPI ("Program Files (x86)" on a 64 bit machine). We also renamed Exchange's mapi32.dll binary. It's now called ExMAPI32.dll.
Update: Looks like the Ehlo blog picked this up. Welcome Ehlo readers! I was involved in getting this update done, so lemme know if you have any questions.
Any time period for 64 bit MAPI release ??
There have been no announcements regarding a 64 bit MAPI.
Has anything else changed in this update or is it just introducing Windows Server 2008/Vista support?
In addition to the session 0 isolation issue, we also fixed an unreported crash scenario. The move from system32 to program files is a fairly large and potentially destabilizing move though. You should definitely test your applications with this update.
Well, that didn't take long. We just released of the latest MAPI download this weekend and yesterday
It appears that one of the new dll's is changing the current working directory of the loading process to "C:\Program Files\ExchangeMAPI" and breaking some applications.
Also, adding this directory to the path will not work in all/most cases since windows\system32 precedes it. Uninstalling the previous version (7974) did not remove the dll's from the windows\system32 directory... perhaps that is why the current working directory is changed?
I didn't think we were changing the working directory, but I'll check on that. On the uninstall, if an application was using the DLLs then they'd have to be scheduled for deletion on reboot - perhaps that's why the uninstall failed?
I just did a quick test program and its MAPIInitialize() that's changing the directory.
is there a new version of MERGEINI that would work with WS 08?
Wow - haven't seen that tool in ages. All it does is simple text manipulation. In fact, since mapisvc.inf is nothing more than a .ini file, the Windows INI functions work (http://msdn.microsoft.com/en-us/library/ms725501(VS.85).aspx). See HrSetProfileParameters in the MFCMAPI code.
I just installed Backup Exec 12 on my 2008 server running Exchange 2007. I have been bouncing back and forth between Microsoft and Symantec trying to get v12 to restore mail boxes. Symantec is blaming MAPI and Microsoft insists MAPI is configured properly. Based on your notes everything appears correct, but Symantec believes that having MAPI32.DLL and MAPISTUB.DLL (both v1.0.2536) in the SysWOW64 folder is an issue. I am stuck in the middle with no clue what to do.
Send me a mail with your case number and I can check on the status from our side.
Sorry for not posting this sooner - I just found out about it today. As I noted previously , we recently
We recently released a downloadable Exchange System Manager (ESM) for Exchange 2003 which can be installed
The ESM for Vista won't install on a W2K8/x64
machine. It complains "You are not running Vista". Will there be an update to correct his?