The Microsoft Lync Server 2010 communications software protocol workloads poster shows the protocols that are used by each workload in Lync Server 2010, describing relationships, dependencies, the servers that initiate connections, and certificate requirements. This poster provides a snapshot of the network connections between server roles. You can download this poster from here. The latest update is version 5.12. This version adds details to the Enterprise Voice workload quadrant based on feedback from Lync experts.
NOTE Microsoft Lync Server 2010 Protocol Workloads Poster version 5.15 is now available here.
Author: Rui Maximo
Publication date: November 2010
Revision date: June 6, 2012
Product version: Microsoft Lync Server 2010
The Microsoft Lync Server 2010 Protocol Workloads Poster is an update of the Office Communications Server 2007 R2 protocol poster, which was released in 2009 and is still available. So many customers and professionals liked it and found it useful that they requested I update it for Lync Server 2010. Encouraged by the positive feedback, I made it a priority to release an updated poster for Lync Server.
Since the initial release early the week of November 15, 2010, customers and UC professionals sent in e-mails with positive comments and valuable feedback regarding inaccuracies and enhancements. Providing accurate information is important—every effort is made to quickly update the poster so that erroneous information isn’t disseminated.
To help you track the latest update of the poster, you’ll notice a version number in the upper-left corner of the poster. The current and latest update is marked as version 5.12. This version updates adds more detailed traffic information to the Enterprise Voice workload based on feedback from Richard Pasztor and Thomas Binder.
As the “guardian” of this poster, I’m committed to keeping the poster updated. You can download the poster from here. Hope you like it!
View this poster at Zoom.IT.
Isn't eye-candy enough to serve as a purpose? You can print it and hang it in your office. Co-workers passing by will immediately be impressed by your technical prowess, and your manager will suddenly, to your surprise, give you a raise. We've heard customer stories reporting unexpected good luck coming their way. So, go ahead and plaster this protocol poster on your wall, and let the goodwill shower down on you.
In addition to good fortune, this poster provides an understanding of the protocols and ports used for each workload. By isolating the protocols for each media, you can gain a better understanding of how Lync Server works. This deeper understanding can help you troubleshoot problems with a specific media in your Lync Server deployment.
Because certificate configuration can be confusing, this poster also details which settings to define in the server certificate request. If you don't find these settings defined in the certificate issued, it is an indication that the server certificate wasn't properly requested from the certification authority (CA).
Domain Name System (DNS) is a configuration step that can often be missed and is prone to misconfiguration, particularly for Edge servers. The poster lists the DNS configurations that are needed for Lync Server.
Last, but not least, this poster has useful links to where you can obtain additional resources, such as articles, the Microsoft Office Communications Server 2007 R2 Resource Kit book, product documentation, and useful tools. You'll notice a Microsoft Tag. Take a picture with your mobile phone, and the picture will automatically resolve the embedded URL to NextHop. Here you'll find lots of useful technical articles and a community of like-minded technical professionals, such as yourself. The Microsoft Tag application must be installed on your phone. If you're not familiar with Microsoft Tag, you can get more information at http://microsoft.com/tag.
The Microsoft Lync Server 2010 Protocol Workloads Poster summarizes the protocols, ports, and certificate and DNS requirements for each workload in Lync Server. Having a visual snapshot of how the product works can be useful. If you would like to provide feedback, you can reach me at email@example.com.
Stay tuned for Microsoft Lync Server 2010 Firewall Poster to be released. I've heard that many customers (that's you, yes, you) would like to have it. Please check back on NextHop or follow DrRez on Twitter for an announcement of when it will be published.
Keywords: Enterprise Voice; IM; presence; conferencing; application sharing; CAC; certificate; central management store; Edge Server; Mediation Server; Exchange UM; Mobility Server; Monitoring Server; Group Chat Server; Director; XMPP gateway; sip; rtp; srtp; stun; turn; psom; https; mtls; tls; dns;
<p>2 questions about it:</p>
<p>1] on the A/V and Web Conferencing Work load. There is a 'C' on the external clients what type of client is it repsenting?</p>
<p>2] I saw a few "old" MOC icons on some of the workloads. It this to demostrate interop between the MOC client and Lync?</p>
<p>Also great Lync event today.</p>
<p>Thanks Jon! :-) The latest version of the poster is on it's way, with these issues resolved. Should be live shortly.</p>
<p>I especially like being able to zoom in and out and get a nice feel for the overall picture as well as the details.</p>
<p>Nice poster :-)</p>
<p>I have one question:</p>
<p>Why would you have e SAN entry on the public cert called sip.<domain> when you do not have sip.<domain> in public DNS?</p>
<p>Thanks for your feedback. You have a keen eye. The lack of a public DNS A record for sip.<sip-domain> is an omission. I've corrected that in the next version (to be released at a future date). Good catch!</p>
<p>Any information/graphics on the Lync Mobile Client connectivity? </p>
<p>Information regarding the Lync Mobile client connectivity will be added shortly after that's released. Once I have more information about it. There's a good possibility that I'll create a separate poster for it given the complexity and lack of space available in the current protocol poster.</p>
<p>Thanks for your inquiry. Keep checking back regularly for updates or follow Dr.Rez's tweets (<a rel="nofollow" target="_new" href="http://www.twitter.com/DrRez">http://www.twitter.com/DrRez</a>). He's really good at keeping a pulse on what's happening in Lync and broadcasting it. I'm about to release version 5.9 of the protocol poster. I've added and fixed the CAC traffic.</p>
<p>It appears the latest release (10-26-2011) says the version should be 5.9 but in the actual documents (both pdf and vsd) show the version is 5.7. I have the 5.7 version and I can tell the differences so I'm sure it's just something that was missed, but wanted to bring it to your attention.</p>
<p>Excelent poster. It has been a big help.</p>
<p>In the enterprice voice section the media connection from front end/mediation servers to a gateway shows being 60,000 - 64,000. From the documentation and traces I have seen this should be 49,152- 57,500</p>
<p>Hi the deepzoom image is only 5.9 i have created a 5.10 deepzoom here <a rel="nofollow" target="_new" href="http://zoom.it/36Qq">http://zoom.it/36Qq</a> please update the post. </p>
<p>Great work on the poster :)</p>
<p>Would also be nice if you include the traffic of push notifications for Mobile Clients, because it can be confusing and would be nice to visualize instead :)</p>
<p>Your poster states we need STUN 3478 from Edge to FE but technet <a rel="nofollow" target="_new" href="http://technet.microsoft.com/en-us/library/gg425891">technet.microsoft.com/.../gg425891</a> says we don't need it.</p>
<p>Could you please check which information is right?</p>
<p>Also in the TechNet the port STUN 3478 is needed for internal communication.</p>
<p><a rel="nofollow" target="_new" href="http://technet.microsoft.com/en-us/library/gg425891">technet.microsoft.com/.../gg425891</a></p>
<p>hi Holger, </p>
<p>I'm not sure I understand your question. Could you clarify?</p>
<p>sorry it was my answer to willi's question.</p>