Microsoft® Lync™ Server 2010: Architecture

▪

▪ Topology related investments

▪ Manageability enhancements

▪ Virtualization

▪ DNS load balancing

▪ Authentication enhancements

▪ Location Infrastructure

▪ Cloud Integration

▪ Q&A

▪ Unified Communications Roadmap

▪

▪ Manageability enhancements

▪ Virtualization

▪ DNS load balancing

▪ Authentication enhancements

▪ Location Infrastructure

▪ Cloud Integration

▪ Q&A

▪ Schematized definition of deployment topology

▪ Configuration of Lync Server 2010 services and Policies managed by central store

Example Service Representation

Service

depends on

depends on

installed on

Site A, AVConfServices, 1

Site A, User Services, 1

Site A, Meditation Server, 1

Site A, Pool A

▪ Replication of policies/ configuration to all topology nodes (including Edge)

▪ Validation tools help prevent misconfiguration

Data Center

Lync

Server

Pool Edge

Server

SBA

Branch Office

Components Functionality Go-To Market

Windows Server® 2008 R2

Mediation Server Registrar

PSTN Gateway

Normal/Failover mode

SIP Registrar SIP Proxy and Routing engine

PSTN connectivity

Voicemail routing PSTN re-routing

Centrally provisioned Up to 1000 user support

OEM (Embedded channel)

5 partners: • AudioCodes

• HP

• Dialogic • NET

• Ferrari

WAN

PSTN

Director

Archiving

Monitoring

Mediation Front end

Back end

AV Conf

Edge

UM

SCOM

Group Chat

Standard Edition

Enterprise Edition

Pools

Data Center

Sites

Global Microsoft

Redmond

Tukwila-1 Tukwila-2

Dublin

Dublin-1

Central Site

Small or Trial Deploy Single Data Center Multiple Data Centers

Branch Office Site

▪ Smaller organizations not requiring resiliency can choose a

Standard Edition Server (SE), a single server with all roles

consolidated on that server functioning

▪ Organizations who need resiliency will choose an Enterprise

Edition Pool (EE), defining a pool of multiple servers comprised

of front end and back end roles

▪ “Paired” Standard Edition can offer failover between two SE

servers for lower cost and reduced functionality.

▪ Additional Server roles required include Archiving, Director,

Edge and Monitoring

▪ Branches without redundant WANs will purchase a

Survivable Branch Appliance to handle voice resiliency

in the branch office

▪ Branches with a redundant WAN connection, still require

basic PSTN termination with SIP Gateway.

▪ Standard Edition Server can be utilized for improved

Quality of Experience (QoE) in large, distant “branches”

(truly a Central Site) with lots of conferencing utilization.

▪ Not all branches will require resiliency – for smaller

branches, use Remote User Connectivity over public

internet or 3G/4G network.

Typical Use

Departmental deployment of reduced criticality and scale

Enterprise deployments where multi-site high-availability is not a requirement

Huge deployments of a geographically dispersed workforce

Central Site

Central Site has a Standard Edition Server

Single Central Site with an Enterprise Edition Pool

Multiple Central Sites of Enterprise Edition Pools

Branch Office Site

Branch Offices for Survivability or PSTN interconnect

Branch Offices for Survivability or Public Switched Telephone Network (PSTN) interconnect

Branch will be combination of SE, SBA and PSTN-only

Pool-level Resiliency

Multi-site Resiliency

Sites that do not host a pool Sites which host a pool of either SE or EE

Edge Server

HTTP reverse proxy

Survivable Branch Appliance

tiny.contoso.com CA/DNS

Exchange UM Server

PSTN Gateway(s)

All Server Roles

WAN

Small < 5000 users

This example 5,000 users, 3 servers

1667 users/server

Small Standard Edition central site Branch through

Edge

Small with

Branches

250-

5,000 Standard Edition central site

Single branch, with

SBA

Small with

Failover

Two Standard Editions - “Paired” Standard Edition to support

inexpensive failover Any

Central Site Standard Edition

Branch A

PSTN

DNS Load Balancing

Edge Server Pool

HTTP reverse proxy

Survivable Branch Appliance

WAN

Single Datacenter < 100,000 users

This example 20,000 users, HA, 14 servers,

1429 users/server

Central Site Enterprise Edition

Branch A

contoso.com CA/DNS

Exchange UM Server

PSTN Gateway(s)

retail.contoso.com File Share

Director Pool

AV Conferencing Pool

Front End Pool

Monitoring Pool

DNS Load Balancing

Branch B

PSTN

PSTN Gateway

Single DC Enterprise Edition, Single Data Center Branch through Edge

DC with

Branches

1,000 –

30,000 Enterprise Edition, Single Data Center

Two branches, one SBA, one PSTN

Interconnect

Survivable Branch Appliance

WAN

Central Site 1 - Enterprise Edition

Branch A

Edge Server Pool

HTTP reverse proxy

contoso.com CA/DNS Exchange UM Server

NA.contoso.com

File Share

DNS Load Balancing

Director Pool

AV Conferencing Pool

PSTN

PSTN Gateway

Edge Server Pool

HTTP reverse proxy

Monitoring and Archiving

Pool Front End Pool

DNS Load Balancing

Standard Edition

SIP Trunking

Central Site 2 - Enterprise Edition

EU.contoso.com CA/DNS

File Share AV Conferencing Pool

Front End Pool

DNS LB

PSTN Gateway(s)

Branch C

PSTN Gateway

“Branch” B

Global Very Large

10,000+ Unlimited

• Two

Data

Centers

with EE

• One

Central

Site with

an SE

• Enterpris

e Edition,

> Two

Data

Centers

• Standard

Editions

• Some

SBA

• Some

PSTN

• Survivabl

e Branch

Applianc

es

• Branch

with

Standard

Edition

Global, Multi-Site Unlimited

This example Site 1: 18 servers

Site 2: 11 servers

2413 users/server (central sites only)

▪ Unified Communications Roadmap

▪ Topology related investments

▪

▪ Virtualization

▪ DNS load balancing

▪ Authentication enhancements

▪ Location Infrastructure

▪ Cloud Integration

▪ Q&A

▪ Unified Communications Roadmap

▪ Topology related investments

▪ Manageability enhancements

▪

▪ DNS load balancing

▪ Authentication enhancements

▪ Location Infrastructure

▪ Cloud Integration

▪ Q&A

▪ Unified Communications Roadmap

▪ Topology related investments

▪ Manageability enhancements

▪ Virtualization

▪

▪ Authentication enhancements

▪ Location Infrastructure

▪ Cloud Integration

▪ Q&A

Lync Server 2010 DNS LB - DNS Configuration OCS 2007 R2 HLB - DNS Configuration

For a Lync Server 2010 Pool ocspool1.contoso.com with 3 FEs: FE1, FE2, FE3

DNS FQDN DNS A Record

IP

Web VIP Ocsweb1.contoso

.com

172.24.32.150

Pool ocspool1.contoso

.com

172.24.32.151

Pool ocspool1.contoso

.com

172.24.32.152

Pool ocspool1.contoso

.com

172.24.32.153

FE FE1.contoso.com 172.24.32.151

FE FE2.contoso.com 172.24.32.152

FE FE3.contoso.com 172.24.32.153

DNS FQDN DNS A Record IP

Pool

VIP

ocspool1.contoso.c

om

172.24.32.150

FE FE1.contoso.com 172.24.32.151

FE FE2.contoso.com 172.24.32.152

FE FE3.contoso.com 172.24.32.153

Po

ol D

NS A

En

trie

s

Mach

ine D

NS A

En

trie

s

▪ Unified Communications Roadmap

▪ Topology related investments

▪ Manageability enhancements

▪ Virtualization

▪ DNS load balancing

▪

▪ Location Infrastructure

▪ Cloud Integration

▪ Q&A

▪ Allow PIN based sign on for devices

▪ Lync Server 2010 signed certificates to access Lync Server 2010 Web services

▪ User certificate to access EWS

▪ Unify PIN for devices and CAA

▪ PIN Management portal in Lync Server 2010 along with appropriate notifications

EXTERNAL

NETWORK

AUTH (SIP URI, Cert)

Lync User Services

Lync Registrar

200 OK

5. TLS to Lync Registrar FQDN

6. REGISTER (SIP URI) Supported; Cert

SIP 401ww-authenticate: Cert

7. REGISTER (SIP URI) Authorization: Cert, Cert Param

INTERNAL

NETWORK

ONLY

DHCP Server/ Lync Registrar

1a. DHCP Option 43 & 120

1b. Lync Cert WS URL & Lync Registrar FQDN

INTERNAL

NETWORK

ONLY

Lync Cert Provisioning Web Service

2a. Http: Get Cert Chain

2b. Http: Download Cert Chain

3a. Https: Resolve User (Ext/Phone #, Pin)

3b. Https: SIP URI

4a. Https: Get and Publish Cert (SIP URI, Pin, CSR)

4b. Https: Lync Signed Cert

▪ Unified Communications Roadmap

▪ Topology related investments

▪ Manageability enhancements

▪ Virtualization

▪ DNS load balancing

▪ Authentication enhancements

▪

▪ Cloud Integration

▪ Unified Communications Roadmap

▪ Topology related investments

▪ Manageability enhancements

▪ Virtualization

▪ DNS load balancing

▪ Authentication enhancements

▪ Location Infrastructure

▪

Agenda

Connected business and optimized IT

▪ Consistent user experience across delivery options

▪ Common architecture and data model across deployments

▪ Flexibility in deployment – meets your complex needs

▪ Adaptability in deployment – enables changes at any time

Hosted Service

Rapid scalability Advanced manageability

On-Premises

Control and ownership Customization

▪

▪

▪

▪

▪

microsoft.com/communicationsserver

Technical Library

NextHop

DrRez

DrRez on Twitter

▪ Check out Microsoft TechNet resources for Lync Server and Exchange Server