I’m supposed to be working on something else, but I couldn’t resist the urge to answer Ed’s post on the Microsoft Office Communicator launch, which in turn is in response to this Microsoft Monitor piece (which, by the way, contains a couple of errors).
First, let’s consider public IM connectivity. Right now, if you want to interoperate with (say) AOL, you have to install AIM or an AIM-compatible client on your desktops… at which point you lose the security and compliance capabilities that Live Communications Server and Sametime/Workplace both offer. On the other hand, if you have a genuine business need for public IM connectivity, you can use the PIC feature of Live Communications Server to interoperate (selectively) with MSN Messenger, AIM, and Yahoo! Messenger users and still maintain both security and compliance. It’s true that PIC is currently priced as a subscription. Ask yourself this: why did AOL suddenly decide to allow a competitor to interoperate? Normally their MO is to break interoperating clients as soon as they can get away with it. Are they getting a cut of the revenue? I don’t know, but it certainly wouldn’t surprise me.
Next, let’s take Ed’s point that the Microsoft collaboration platform has more than one piece (he actually uses the phrase “jigsaw puzzle”). Back in the day, Microsoft’s claim was simple: Exchange does it all. They have since repented of that, instead delivering a broad suite of collaboration and communication tools that you can mix and match. You can deploy them together or separately. If you don’t need, e.g., SharePoint Portal Server, fine– don’t buy it. There’s significant stand-alone value in each of the components. In fact, I’m seeing a groundswell of interest in Live Meeting and Live Communication Server deployment among customers that aren’t currently using Exchange. Why? Neither of those products require Exchange, and both add measurable business value.
Now, it’s also true that the more pieces of the MS platform you deploy, the more capability you get. This is no different from Workplace, except that many of Microsoft’s platform components are more mature than their Workplace equivalents. It’s a little disingenuous of Microsoft Monitor to claim that you have to buy all of the features; that’s like saying that I have to buy the Hemi when I buy a Dodge Magnum (well, OK, I would have to buy the Hemi, but that’s another blog post).
About those Microsoft Monitor article mistakes: I count two simple typos (“Instanbul” and the confusion between SharePoint Portal and Windows SharePoint Services) and a misunderstanding of the Outlook/LCS connection. You can deploy Outlook 2003 without Exchange 2003 (in fact, you can even use Outlook 2003 against Notes/Domino servers, using either MS’ or IBM’s connectors). Every Exchange 2003 CAL includes an Outlook license, but Outlook is also licensable separately.