October 5, 2007 at 4:16 pm
Don't get me wrong - the Outlook client install is usually the most straightforward way to do this. It's just that once the client is installed, the ONLY part you use is the Extended MAPI Object Interface. There used to be a LONG time ago a "free-standing MAPI support" install, but that's long since disappeared. Our network admin guy installs the outlook client, and then puts a global policy on the server, preventing the running of Outlook.exe. Your mileage may vary (if you're a programmer - you don't NEED the client to get into the mail).
You do have other options (on occasion), such as installing the Exchange Server Utilities, which also adds Extended MAPI support to your system. Or if you're using something like Small Business Server - you'd already have that support (because of Exchange being on the server). Of course - since you probably don't plan on administering Exchange from your SQL server - you will probably prefer to have a mail client (i.e. Outlook) than another admin utility.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply