20336 b 01 architecture and design approach

34
Microsoft ® Official Course Webinar Introducing MS Lync 2013 With Abu Z - Feb 25, 2015

Upload: unitek-eduation

Post on 18-Jul-2015

101 views

Category:

Education


1 download

TRANSCRIPT

Page 1: 20336 b 01 architecture and design approach

Microsoft® Official Course

WebinarIntroducing MS Lync 2013

With Abu Z - Feb 25, 2015

Page 2: 20336 b 01 architecture and design approach

Deployment Options

Microsoft Office 365, Lync Online

Partner-hosted multi-tenant

Single domain and directory

Users split–server/online

Lync Server 2013

Private cloud/dedicated

CloudHybrid On-Premises

Enabling gradual migration and coexistence between Lync private and public cloud

Page 3: 20336 b 01 architecture and design approach

Lync Server 2013 Architecture

InternalExternal Perimeter Network

Reverse

proxy

Lync

Edge

Hybrid

Federated

Network

Public

Providers

PSTN

ADMIIS

Identity

EdgeMore Secure

Federation and

Interoperability

External User

Ingress

PoolFewer,

Consolidated

Servers

Virtualized and

Higher Scale

ServicesConsolidated

Archiving

SCOM, AD, DFS

Exchange

Voicemail/

Archive

SCOM

Monitoring

DFS

Files Store

Office Web Apps

Web Access

SQL

CDR/QoE/

ReportDB

UC End Points

EE Pool Back-end

Front-end

IP-PSTN

Gateway

Persistent

Chat (optional)

Mediation Server

(optional)

PBX

Page 4: 20336 b 01 architecture and design approach

Lync Server 2013 Server Roles

Mediation Server

Front-End Server Back-End Server

Director

Persistent Chat

Compliance Back-

End Server

Standard Edition Server

Edge Server

Lync Server 2013

Server Roles

Persistent Chat

Back-End Server

Persistent Chat

Server

Page 5: 20336 b 01 architecture and design approach

Standard Edition Server

• Standard Edition server is designed for small

organizations, and for pilot projects of large

organizations.

• It enables many of the features of Lync Server,

including the necessary databases, to run on a

single server. This enables you to have Lync Server

functionality at a lower cost, but does not provide

a true high-availability solution.

• The Standard Edition server enables you to use

instant messaging (IM), presence, conferencing,

and Enterprise Voice, all running on one server.

For a high-availability solution, use Lync Server

Enterprise Edition.

Page 6: 20336 b 01 architecture and design approach

Front-End and Back-End Server

• Lync Server Enterprise Edition, the front-end

server is the core server role, and runs many basic

Lync Server functions.

• The front-end servers, along with the back-end

servers, are the only server roles required in any

Lync Server Enterprise Edition deployment.

• Front-End pool is a set of front-end servers,

configured identically, that work together to

provide services for a common group of users.

•A pool of multiple servers running the same role

provides scalability and failover capability.

Page 7: 20336 b 01 architecture and design approach

Front-End Server Features

•User authentication and registration.

• Presence information and contact card exchange.

•Address book services and distribution list

expansion.

• IM functionality, including multiparty IM

conferences.

•Web conferencing, PSTN dial-in conferencing and

A/V conferencing (if deployed).

•Application hosting, for both applications included

with Lync Server (for example, Conferencing

Attendant and Response Group application), and

third-party applications.

Page 8: 20336 b 01 architecture and design approach

Front-End Server Features

• Optionally, Monitoring, to collect usage information in the form of call

detail records (CDRs) and call error records (CERs). This information

provides metrics about the quality of the media (audio and video)

traversing your network for both Enterprise Voice calls and A/V

conferences.

• Web components to supported web-based tasks such as web

scheduler and join launcher.

• Optionally, Archiving, to archive IM communications and meeting

content for compliance reasons.

• In Lync Server 2010 and prior versions, Monitoring and Archiving were

separate server roles, not collocated on the front-end server.

• Optionally, if Persistent chat is enabled, Persistent Chat Web Services

for Chat Room Management and Persistent Chat Web Services for File

Upload/Download.

• Front-end pools are also the primary store for user and conference

data.

Page 9: 20336 b 01 architecture and design approach

Front-End Server Features

• one front-end pool in the deployment also runs

the Central Management Server, which manages

and deploys basic configuration data to all servers

running Lync Server.

• The Central Management Server also provides

Lync Server Management Shell and file transfer

capabilities.

Page 10: 20336 b 01 architecture and design approach

Back-End Server Features

• Back-end servers are database servers running

Microsoft SQL Server that provide the database

services for the front-end pool. The back-end

servers serve as backup stores for the pool users,

and for conference data, and they are the primary

stores for other databases such as the Response

Group database.

• You can have a single back-end server, but a

solution that uses SQL Server mirroring is

recommended for failover. Back-end servers do

not run any Lync Server software.

Page 11: 20336 b 01 architecture and design approach

Edge Server Features

• Edge Server enables your users to communicate

and collaborate with users outside the

organization’s firewalls. These external users can

include the organization’s own users who are

currently working offsite users from federated

partner organizations, and outside users who have

been invited to join conferences hosted on your

Lync Server deployment.

• Edge Server also enables connectivity to public IM

connectivity services, including Windows Live,

AOL, Yahoo!, and Google Talk.

Page 12: 20336 b 01 architecture and design approach

Edge Server Features

• Edge Server also enables mobility services, which supports

Lync functionality on mobile devices. Users can use

supported Apple iOS, Android, Windows Phone, or Nokia

mobile devices to perform activities such as sending and

receiving instant messages, viewing contacts, and viewing

presence.

• Edge Servers also include a fully-integrated Extensible

Messaging and Presence Protocol (XMPP) proxy, with an

XMPP gateway included on front-end servers. You can

configure these XMPP components to enable your Lync

Server 2013 users to add contacts from XMPP-based

partners (such as Google Talk) for instant messaging and

presence.

Page 13: 20336 b 01 architecture and design approach

Mediation Server Features

• Mediation Server is a necessary component for

implementing Enterprise Voice and dial-in conferencing.

• Mediation Server translates signalling, and in some

configurations, media between your internal Lync Server

infrastructure and a public switched telephone network

(PSTN) gateway, IP-PBX, or a Session Initiation Protocol

(SIP) trunk.

• You can run Mediation Server collocated on the same

server as front-end server, or separated into a stand-alone

Mediation Server pool.

Page 14: 20336 b 01 architecture and design approach

Director Server Features

• Directors can authenticate Lync Server user requests, but

they do not host user accounts or provide presence or

conferencing services.

• Directors are most useful to enhance security in

deployments that enable external user access.

• The Director can authenticate requests before sending

them to internal servers.

• In the case of a denial-of-service attack, the attack ends

with the Director and does not reach the front-end servers.

Page 15: 20336 b 01 architecture and design approach

Persistent Chat Server Features

• Persistent chat enables users to participate in multiparty,

topic-based conversations that persist over time.

• The Persistent Chat front-end server runs the persistent

chat service.

• The Persistent Chat back-end server stores the chat

history data, and information about categories and chat

rooms.

• The optional Persistent Chat Compliance back-end server

can store the chat content and compliance events for the

purpose of compliance.

• Servers running Lync Server Standard Edition can also run

Persistent chat collocated on the same server. You cannot

collocate the Persistent Chat front-end server with

Enterprise Edition front-end server.

Page 16: 20336 b 01 architecture and design approach

Lync Server 2013 Clients

Lync 2013 Web App

Lync Server 2013

Clients

Lync 2013 Lync 2013 Basic

Lync 2013 Mobile

Lync 2013 Phone

Edition

Page 17: 20336 b 01 architecture and design approach

Lync Server 2013 Administrative Tools

Administrative tools and enhancements in Lync

Server 2013 include:

• Lync Server Deployment Wizard

• Lync Server Control Panel

• Lync Server Management Shell

• Lync Server Topology Builder

• Central management database

• Role-based access control

• DNS load balancing

• Lync Centralized Logging Service

Page 18: 20336 b 01 architecture and design approach

Central Management Database

The Central Management Database:

• Provides a robust, schematized storage of the data

needed to define, set up, maintain, administer,

describe, and operate a Lync Server 2013

deployment

•Validates data to ensure configuration consistency

•Replicates read-only copies of data to all servers in

the topology, including Edge Servers

•Central Management Database replicates

configuration changes to all the servers in your

deployment. Therefore, configuration changes

that you make in location are updated to all

servers of your Lync Server 2013 solution.

Page 19: 20336 b 01 architecture and design approach

Session Initiation Protocol–Based Foundation

• SIP is an application-layer control or signaling

protocol for creating, modifying, and terminating

sessions among one or more participants

• Sessions include Internet-based telephone calls,

multimedia distribution, and multimedia

conferences

• SIP-related RFCs and over 200 IETF Internet drafts

and proposed standards form the basis of the

Microsoft Unified Communications design

Page 20: 20336 b 01 architecture and design approach

Lync 2013 Hybrid Coexistence

Active

Directory

Lync 2010

Pool

Microsoft

Federation

Gateway

Lync

Federation Edge

AD FS v2

(Geneva)

DirSync–provisioning, GAL

Federation for SSO

Lync Hybrid Interoperability

Integration between local

IT systems and the cloud

Office 365Exchange Online

Lync Online

SharePoint Online

Legacy OCS

2007 R2

Lync 2010+ Pool Directory Sync

Edge

Same as

Exchange

Page 21: 20336 b 01 architecture and design approach

Enterprise Voice in Lync Server 2013

Enhanced Routing

• Support for M:N – MS:GW (a gateway can point to multiple Mediation

servers)

• Improved Caller ID management

• Improved delegate routing

• Response Group Manager

• Inter-trunk routing (session management)

Hosted Voice

• Lync-to-Phone, IP phone devices in Office 365

• Hybrid model–on-premises servers with user being stored in the cloud

IPv6

• Support for IPv6 in all Lync components

VDI

• Support for VDI for audio and video

Page 22: 20336 b 01 architecture and design approach

Lync 2013 Features

Lync 2013 Features

Enhanced user interface Video enhancements–Multiparty video

Me area Administrative enhancements

Contact card Call park and retrieve

Privacy enhancements Pre-call and in-call diagnostics

Sharing feature enhancements Improved device handling

Polling Emergency services support

Improved meeting join experience Call handling

Conferencing attendance and

scheduling

Enhanced phone experience

PSTN dial-in conferencing

enhancements

Office and Windows 8 integration

Page 23: 20336 b 01 architecture and design approach

Lync 2013 Feature Descriptions

Feature Description

Polling Enhances collaboration by enabling presenters to quickly

determine participants’ preferences

Conferencing attendance

and scheduling

Sending invitation is simplified through a shorter http://

URL, which mobile users can also use to join conferences

PSTN dial-in conferencing

enhancements

Users can join calls with minimal prompts and can wait in

the lobby if the receiver is not available to pick up the call

Video enhancements Provides support for full screen, panoramic video,

multipoint video, subscription video, and Video Graphics

Array (VGA) video in conferences

Administrative

enhancements

Delegates do not have to switch between Lync 2013 and

Attendant console

Call handling Delegates can support their manager easily because of

shared lines

Emergency services

support

When a caller makes an emergency call, emergency

responders can retrieve the physical location of the phone

from which the call was placed

Page 24: 20336 b 01 architecture and design approach

Lync 2013 Feature Descriptions

Feature Description

Enhanced phone

experience

Includes a tally of call logs and voice mail that alerts the user

of activity

Microsoft Office and

Windows 8 integration

Users can start IM or phone conversations from Microsoft

Office applications, without having to switch to Lync 2013

Contact card Offers extended contact card options with information about

the user, the organization, or distribution groups

Privacy enhancements Users can assign various levels of access, depending on their

relationship with contacts them, such as Family or Workgroup

Sharing feature

enhancements

Provides users desktop sharing, application sharing, meeting

recording, playback, whiteboard, and annotation tools

Call park and retrieve Calls can be sent to a general holding area for pickup or

retrieval, by the appropriate response group or individual

Pre-call and in-call

diagnostics

Alert users when the network quality is poor so that the user

can choose to take the call from a landline phone or mobile

phone

Improved device

handling

Allows multiple devices, including USB devices for calls

Page 25: 20336 b 01 architecture and design approach

Lync Server 2013 Conferencing Clients

Feature/capability Lync

2013

Lync Win Store

App

Lync 2013

Basic

Lync Web App

Add computer audio X X X X

Add video X X X X

View multiparty video X X X

Use in-meeting presenter controls X X X

Access detailed meeting roster X X X

Participate in multiparty IM X X X

Share the desktop (if enabled) X X (Needs plug-in)

Share a program (if enabled) X X (Needs plug-in)

Add anonymous participants (if enabled) X X

Use dial-in audio conferencing X X X X

Initiate a meeting X X

Add Microsoft PowerPoint files X X X

Navigate Microsoft PowerPoint files X X X

Use OneNote meeting notes X X

Use a whiteboard X X X

Conduct polls X X X

Share files x X X

Page 26: 20336 b 01 architecture and design approach

External User Scenarios

Access Edge Server

Access Edge Server

Adatum.com Contoso.com

Federated UsersInternal Users

Remote UserAnonymous User

XMPP Partner PIC User

Page 27: 20336 b 01 architecture and design approach

External User Capabilities

Scenario Remote

User

Federated

User

PIC Anonymous

User

XMPP

Presence

IM peer-to-peer

IM conferencing

Collaboration

A/V peer-to-peer

*

A/V conferencing

File transfer

Communications capabilities by type of user:

* = For PIC A/V peer-to-peer support, you must use thenew version of Skype.

Page 28: 20336 b 01 architecture and design approach

Phases in a Lync Server 2013 Deployment

EnvisionInitial State

Environment

End State

Environment

Scenarios

PlanPlanning

Infrastructure

Requirements

Planning Lync

Server 2013

Requirements

Planning

External Access

Planning

Enterprise

Voice

StabilizeTesting

Considerations

Deploy

Preparing Active

Directory

Deploying the

Clients

Deploying Lync Server

2013 Server PoolConfiguring, Archiving,

and Monitoring

Deploying

External User

Access

Deploying

Enterprise Voice

Validating the

Deployment

OperateMaintaining the

Lync Server 2013

Environment

Maintaining the

Client Experience

Troubleshooting

Page 29: 20336 b 01 architecture and design approach

Sequence of Lync Server 2013 Deployment Phases

Order of Lync Server 2013 Deployment Phases:

1. Internal Deployment

2. PSTN Dial-in Conferencing

3. External Deployment

4. Enterprise Voice or PBX integration

Page 30: 20336 b 01 architecture and design approach

Assessing Exchange Server Integration and Updating the Design

To support Lync 2013 integration, both Lync 2013

and Microsoft Outlook 2013 read and write

information directly to Exchange Server.

You need to plan for Exchange Server interfaces

used by Lync 2013 and Microsoft Outlook 2013.

You need to plan for:• Exchange Server communication interfaces based on their function.

• Publishing Free/Busy information.

• Controlling integration.

• Lync 2013 and Exchange Server compatibility.

Page 31: 20336 b 01 architecture and design approach

Assessing Client Integration and Updating the Design

You need to assess and determine the requirements

for client integration that may include the

following:

• Client features

• Client deployment

• Hardware and software

• Policies and in-band settings

• Compatibility of client versions

Page 32: 20336 b 01 architecture and design approach

Assessing Voice Requirements and Updating the Design

You need to assess and determine voice

requirements, and the options for voice

deployment may include:

• Using SIP-to-PSTN gateways, which include Survivable

Branch Appliances (SBA)

• Direct SIP by using PBX

• SIP-to-PSTN Gateway to PBX

• SIP Trunking

• Current dialing habits and dial plans

• Devices

Page 33: 20336 b 01 architecture and design approach

Module Review and Takeaways

•Review Question(s)

•Real-world Issues and Scenarios

• Tools

Page 34: 20336 b 01 architecture and design approach

Q & A

•Questions about Microsoft Lync 2013?

• Please type any questions you have.

Unitek [email protected]