Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Carlos — Wed, 17 Oct 2012 23:20:59 GMT

could you tell where I can download VISIO charts I see on your blog, please, I would be very helpful. I leave you my email in case you send it to me.

c.moreno.reymundo @ gmail.com

Greetings.

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Genabel — Fri, 08 Jun 2012 12:44:56 GMT

Byron, there is a typo in the user names right at the beginning.

It would be also nice to describe a scenario where the central signalling and local media Edge servers are used - for p2p and conferencing calls. Federation would complete the picture.

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Byron Spurlock — Thu, 24 May 2012 18:26:59 GMT

In this scenario the Redmond and Singapore deployments are in different sites. Remote traffic is kept regionalized for Web Conferencing and Audio\Video traffic for the respective pools. Once a client signs in they are passed through to their respective pool. Each Lync Front End pool has a corresponding Edge pool it is associated with, done through Lync topology builder. After the client signs into Lync they are passed (through in band provisioning) the Edge server information to allow the client to leverage the Edge server assigned to users pool. By this process, for two pools that are separated geographically users in the respective pools will utilize the Edge server to allow "remote traffic" to stay regionalized. Now there is the possibility where two users in separate pools hold a conversation with each and the traffic is not regionalized, but that occurs with core Lync scenarios as well, for example Lync conferencing.

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Marc W. — Thu, 24 May 2012 17:37:09 GMT

Byron, does this assume both sites are in the same Lync 2010 site or different sites? If they are in different sites, what is the assumption on how "remote traffic is kept regionalized whenever possible."

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

SMS Bradley — Thu, 24 May 2012 05:02:06 GMT

Really glad to see so much interest in this article. Part 2 is in the works. Great job, Byron!

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Byron Spurlock — Mon, 21 May 2012 13:41:32 GMT

Thanks for the comments.

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Linus — Fri, 18 May 2012 04:09:53 GMT

Excellent article .Edge deployment is an integral part of Lync deployment . Thanks

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

rafallan — Thu, 17 May 2012 07:00:18 GMT

Really nice! It is a "must to know" for all Lync engineers!

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

Byron Spurlock — Wed, 16 May 2012 03:04:50 GMT

Kswail thanks for comment, note taken about updating supported topologies regarding Geo-DNS solutions.

re: Lync Server 2010 Geographically Dispersed Edge Topology: Part 1

kswail — Tue, 15 May 2012 21:26:40 GMT

Interesting topic, and one which we touch on regularly in my organization.

That being said, it is sad that Microsoft does not support geo-ip solutions to ensure that external users are directed to the edge closest to them regardless of what pool they are assigned to. Please consider updating your supported topologies to include external geo-dns solutions.