Lync Server 2010 External User Access Security Overview

re: Lync Server 2010 External User Access Security Overview

J S — Fri, 28 Sep 2012 14:32:01 GMT

Hi, when do you expect to re-publish this article?

Regards,

James.

re: Lync Server 2010 External User Access Security Overview

Acid-Guy — Fri, 21 Sep 2012 16:04:10 GMT

Hi Petri

Lync is SIP based application. The user login information is exchanged when the session is established. From sa ecurity stand point the directory server acts another layer to protect the front-end servers so I would say as far as possible its good have directory server in the topology. Yes I do agree not all the traffic travels through the Director server however these connections are only established after the connecting user/endpoint has identified themselves or the conference.

does this answer you question?

re: Lync Server 2010 External User Access Security Overview

Petri X — Fri, 21 Sep 2012 11:47:56 GMT

When we can expect to see simple external solution? Now we have:

- reverse proxy, is publishing web services, directly from the back end

- clients needs direct access to the edge

- some connections goes to directory server

- some connections goes to back end and perhaps A/V conference

Plus the number of ports in all above connections...

Plus mobile service...

You say that directory server is required because of security reasons, but at the same time there is plenty of other connection which don't care of the director role.

From old fashion security guys (firewall is all) looks scary when they see Lync's requirements.

re: Lync Server 2010 External User Access Security Overview

Susan S. Bradley - MSFT — Wed, 19 Sep 2012 23:53:34 GMT

Excellent article, thanks Edwin!

re: Lync Server 2010 External User Access Security Overview

Igor Kravchenko — Wed, 19 Sep 2012 20:57:15 GMT

Good article. Thank you.