MS Exchange Needs a Reality Orientation
Category
Here's my answer to Microsoft pushing for Lotus Notes migrations into Exchange. First, though, let me sympathize with Microsoft's dilemma. Exchange offers a single server-stack lock-in that guarantees years of revenue for a company that is struggling to maintain its revenue stream. It's a pretty sweet deal, and they have even been willing to compete against their own partner channel with an offer of inexpensive e-mail hosting.
Microsoft is going to do whatever they can to win over new accounts. If you think your current messaging infrastructure is the right choice for your company, then I have some quick recommendations:
Now, you have strategy for creating value and future-proofing your company's messaging infrastructure. My Notes client is on Eclipse, relying on ODF with Symphony, and running Linux (where it fits). I support Mac, Linux and Windows for the users, and I can pick any OS for the back-end.
Here's my answer to Microsoft pushing for Lotus Notes migrations into Exchange. First, though, let me sympathize with Microsoft's dilemma. Exchange offers a single server-stack lock-in that guarantees years of revenue for a company that is struggling to maintain its revenue stream. It's a pretty sweet deal, and they have even been willing to compete against their own partner channel with an offer of inexpensive e-mail hosting.
Microsoft is going to do whatever they can to win over new accounts. If you think your current messaging infrastructure is the right choice for your company, then I have some quick recommendations:
- Expect the question to be asked. It would be absolutely irresponsible for any management team to ignore the possibility of reducing IT expenses. It's not personal, it's business and it's your career to take these concerns seriously.
- Make sure that you are already providing value. Sometimes it's envy, or novelty, or the desire to be in a larger herd which makes management easily lured over to alternatives. Those are all issues that can be handled with numbers of up-time, storage costs, conversion expenses, incredible customizations, applications, etc. However, if your company's messaging architecture isn't taking advantage of Domino/Sametime/Quickr, and there are critical systemic problems, you won't have a chance because you don't have credibility.
- The future looks dim for single-stack, propriety solutions. The big, mano-a-mano struggles between Exchange and Notes, Oracle and SQL-Server, Netware and Windows Server--these are over. Future-proofing requires being inclusive to a wide set of technologies that includes working in The Cloud and opting in for open-source. So . . . .
Did you know that Microsoft is losing Exchange accounts to open-source alternatives ? Now, that's an interesting topic to include when the migration discussion is being kicked about. It's called, "spitting in the soup." No one really wants to go any further.
Linux-based Exchange replacement helps 3 health care systems cut costs
Microsoft Exchange on Linux?!?
Major Web hosting provider launches low-cost groupware in U.S.
Now, you have strategy for creating value and future-proofing your company's messaging infrastructure. My Notes client is on Eclipse, relying on ODF with Symphony, and running Linux (where it fits). I support Mac, Linux and Windows for the users, and I can pick any OS for the back-end.
- 
