Is Microsoft Lync ready for the enterprise? It’s a question that just won’t die. Certainly it seems to be selling well, and it represents a fairly unique solution. But Lync is so different that many just don’t know what to make of it.
On one hand, Lync offers smooth integration with a Microsoft infrastructure – Windows, Active Directory, Office, Exchange, and SharePoint. It has rich APIs and a high profile developer network. On the other hand, its voice features are somewhat limited, it requires partners to complete its solution (endpoints and applications such as contact center), has a very complex architecture, and it is the only enterprise telephony solution that does not support standard SIP endpoints.
Matt Brunk and I took on the debate on NoJitter last January. In that piece I had taken the PRO Lync position. But despite my elegant prose – the debate lingers. Last week, Joe Schurman posted on Network World the case that it is not enterprise ready. His feature Microsoft Lync is NOT “Enterprise Ready” was posted on Network World, but has since disappeared. No real explanation of why Joe has turned so viciously against his former cause or why the article is gone – but fellow Network World columnist Julie Bork noted the existence of the post and confirms his Lync expertise:
Schurman currently works as director of Avaya’s Unified Communications; however, until recently, he was one of the more well-known advocates of Microsoft’s Unified Communications products and it is fair to say that Schurman knows Lync well. He is a six-time Microsoft UC MVP who penned two books on Microsoft’s unified communication technology…However, earlier this year Schurman grew so frustrated with Lync’s telephony technology, as well as Microsoft’s SDK and other developer support, that he bailed on Microsoft altogether…
So what did Joe say? I have the entire post below (it’s long). Certainly he raises some valid points, but the tone is emotional and some of his points are pretty weak. For example, he boldly announces that “Microsoft Lync is actually a hardware-centric solution.” Yes, it is a sad fact that all premise based solutions – even virtual ones – still require hardware. It’s also true that softphones require hardware too. It’s a conspiracy I tell you.
Joe points out correctly that Lync uses multiple servers in separate roles. He lists 14 servers, but mistakenly states each requires its own separate physical server. That is simply untrue. Lync requires a minimum of 4 server roles, but all can be on a single physical server. It is these types of issues that cause his post to lose some credibility, however, many of his facts are correct.
I get his basic point though. I too have been critical of Microsoft in the past because they often imply they are unique in UC as a provider of a “software based” solution. I do consider them a provider of a “software based” solution, but I don’t think that is unique. Avaya often gets stereotyped as a hardware company, but they run on Dell or HP industry standard servers (as does Microsoft), have their phones produced by third parties (as does Microsoft), and seem mostly focused on their software experience and capabilities (as does Microsoft).
So is Joe correct? That’s for you to decide. However, while some of his points are valid, I might offer that those that live in an Avaya house should be cautious about throwing stones.
The original article is posted below courtesy of Google Cache.
Continue Reading →