+ All Categories
Home > Documents > Microsoft ® Lync Ignite Microsoft Lync 2013.

Microsoft ® Lync Ignite Microsoft Lync 2013.

Date post: 14-Dec-2015
Category:
Upload: nathaniel-pollen
View: 253 times
Download: 4 times
Share this document with a friend
Popular Tags:
38
Microsoft ® Lync Ignite Microsoft Lync 2013
Transcript
Page 1: Microsoft ® Lync Ignite Microsoft Lync 2013.

Microsoft® Lync Ignite

Microsoft Lync 2013

Page 2: Microsoft ® Lync Ignite Microsoft Lync 2013.

Microsoft Lync IgniteMigration, Coexistence, and InteroperabilityModule 04

Presenter NameTitle Microsoft Corporation

Page 3: Microsoft ® Lync Ignite Microsoft Lync 2013.

Introduction to Migration

Migration Step by Step

Client Interoperability

Q & A

Agenda

3

Page 4: Microsoft ® Lync Ignite Microsoft Lync 2013.

Introduction to Migration

Page 5: Microsoft ® Lync Ignite Microsoft Lync 2013.

MigrationMoving your production deployment from a previous version of Office Communications Server (OCS) 2007 R2/Lync 2010 to Lync Server 2013

UpgradeInstalling a newer version of software on a server or client computer

CoexistenceThe temporary environment that exists during migration when some functionality has been migrated to Lync Server 2013 and other functionality still remains on a prior version (OCS Server 2007 R2/Lync 2010)

InteroperabilityThe ability of your deployment to operate successfully during the period of coexistence

Terms

5

Page 6: Microsoft ® Lync Ignite Microsoft Lync 2013.

Lync Server 2013 infrastructure deployed side by side with existing infrastructure

Similar to previous migrationsIn-place upgrade not supported

Migrate side by side, site by siteEnsures service continuity, low end-user impactEnables rollback, resiliency to logistical issues

Build Pilot ProductionMinimize initial hardware requirementsTrial builds administrator and user confidence and minimizes risk

Migration Approach

6

Page 7: Microsoft ® Lync Ignite Microsoft Lync 2013.

Server supports migration from N-1 or N-2N (15): Lync 2013N-1 (14): Lync 2010*N-2 (13): Office Communications Server (OCS) 2007 R2*

Client support depends on workloadN-2 client (Communicator 2007R2) compatible against Lync Server 2013*N-1 client (Lync 2010) against Lync Server 2013*N client (Lync 2013) against Lync 2010 Server

Voice CoexistenceSupport Legacy Mediation Servers (N-1, N-2)Lync 2013 SBA cannot use the Lync 2010 Pool

Support Boundaries

* With Latest Updates7

Page 8: Microsoft ® Lync Ignite Microsoft Lync 2013.

Persistent Chat supports migration from:N-1 (14): Lync 2010* Group ChatN-2 (13): OCS 2007 R2* Group Chat

Persistent Chat Client supportN-1 chat client (Lync 2010) against Lync 2013 Persistent Chat ServerN-2 chat client (Communicator 2007 R2) against Lync 2013 Persistent Chat Server

Lync 2013 cannot connect to Legacy Group Chat Servers

Support Boundaries (Cont’d)

* With Latest Updates8

Page 9: Microsoft ® Lync Ignite Microsoft Lync 2013.

Voice Routing Coexistence

Home Server Mediation

Server

Lync Server 2013 15 15 Supported

Lync Server 2013—Lync Server 2010

15 14 Supported

14 15 Supported

Lync Server 2013—OCS 2007 R2

15 13 Supported

13 15 Not Supported

Mediation Server Next Hop Server Home Server

Lync Server 2013 15 15 15 Supported

Lync Server 2013—Lync Server 2010

15 15 14 Supported

14 14 15 Supported

Lync Server 2013—OCS 2007 R2

15 15 13 Supported

13 13 15 Supported

Outbound Calls

Inbound Calls

** Assume certified Gateways for the release of MS shown in the tables above

Lync 2010 Pool Lync 2013 Pool

Lync 2010 SBA

Supported Supported *

Lync 2013 SBA

Not Supported Supported

* Contents from 2010 SBA will write monitoring and archiving contents to Lync 2010 store

Survivable Branch Appliance (SBA)

9

Page 10: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Versions

Lync Server 2010Uses CMS (Central Management Store)Lync 2010 client, no Live Meeting clientEasy migration path

OCS 2007 R2No CMS Configuration stored in Active Directory (AD)Live Meeting and Office Communicator clientMigration to Lync Server 2013 similar to Lync 2010 migration

10

Page 11: Microsoft ® Lync Ignite Microsoft Lync 2013.

TopologyDownload existing topology in Lync Server 2013 Topology BuilderDefine new Lync 2013 Pool and publish the new topologyUse Lync Server 2013 Topology Builder, Lync 2010 topology builder cannot be used

ConfigurationData exists in Lync 2010 CMSLync Server 2013 uses Lync 2010 CMS instance

Users (Performed on Lync 2013 System)Via Lync Server Control PanelFrom Management Shell: Move-CsLegacyUserRollback from Management Shell: Move-CsUser

Migrating from Lync Server 2010

11

Page 12: Microsoft ® Lync Ignite Microsoft Lync 2013.

Migrating from OCS2007 R2

TopologyMerge topology using the Topology BuilderImports Legacy topology and conference directoriesRerun when Legacy topology changesPublish the new topology

ConfigurationMerge other configuration from Lync Management Shell:

Import-CsLegacyConfiguration Rerun when legacy configuration has changed with ReplaceExisting

UsersVia Lync Server Control PanelFrom Management Shell:

Move-CsLegacyUserRoll back from Management Shell:

Move-CsUser

Other Move-Cs cmdletsApplications:

Move-CsApplicationEndpointResponse Group:

Move-CsRgsConfigurationExchange UM contacts:

Move-CsExUmContactConferencing dirs:

Move-CsConferenceDirectory

• 12

Page 13: Microsoft ® Lync Ignite Microsoft Lync 2013.

Migration Step by Step

Page 14: Microsoft ® Lync Ignite Microsoft Lync 2013.

Prepare for deploymentPlan sequence: site-by-site and side-by-sideDeploy most recent updates, backup Legacy deploymentPrep Active Directory schema, prep, domain AD DS forest

Start in the first site, migrate pools side by sidePilot PoolPilot Edge and DirectorTake pool in productionTake Edge Servers in productionRepeat for remaining pools

Pick next site, repeat side by side

Overview of Migration Steps

14

Page 15: Microsoft ® Lync Ignite Microsoft Lync 2013.

Sequence deployment site by site

Migration and Coexistence Topologies

Start with site containing federated Edge

Scales down for nonglobal deployment

15

State 1: Plan sequence: site by site, side by side

Page 16: Microsoft ® Lync Ignite Microsoft Lync 2013.

Stage 1

PlanDefine migration strategySelect sites, locationsIdentify users and define migration groups

16

Page 17: Microsoft ® Lync Ignite Microsoft Lync 2013.

Stage 2

PrepareDeploy most recent updates (clients/server)Backup Legacy deploymentRun Best Practice Analyzer and ensure healthy deploymentUpgrade Active Directory Domain Services (AD DS) schema, forest, domain preparation

Apply updates

Apply updates

Apply updates

Legacy Pool

Upgrade schema

Production

Legacy Director

AD

Legacy Federation

Legacy Remote Access

Legacy Edge

17

Page 18: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Pilot

LatestPool

Legacy Director

AD

Front end

Back end

Legacy Pool

Legacy Edge

Legacy andLatest Federation

Stage 3Introduce first Lync Server 2013 PoolDeploy pilot Lync 2013 Pool side by side with existing deploymentActivation of Lync Server 2013 adds product references into Legacy Active DirectoryDoes not require deployment of all Front End ServersFor OCS 2007 R2 Only:

Merge 2007R2 topology onto CMS

Merge-CsLegacyTopology

Import the configuration items:

Import-CsLegacyConfiguration

18

Page 19: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Pilot

LatestPool

Legacy Director

AD

Front end

Back end

Legacy Pool

Legacy Edge

Legacy andLatest Federation

Stage 3

RoutingMixed version routing from Lync 2013 pool to Legacy DirectorExternal access through Legacy Director and Legacy Edge Server

19

Page 20: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Legacy Pool

Legacy Edge

Legacy Director

AD

Legacy Federation

Stage 4

Pilot with subset of usersSubset of users moved to Lync 2013 poolMajority of users remain on Legacy poolValidate functionality and interoperabilityDeploy Lync 2013 clients to some trial users on Lync 2013 pool, Legacy clients for others

Front End

Back End

Latest Pool

PilotR2 Only: Merge-CsLegacyTopology Import-CsLegacyConfigurationImport-CsLegacyConferenceDirectoryMove-CsLegacyUser

20

Page 21: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Pilot

Legacy Director

AD

LatestRemote Access

Legacy Pool

Legacy Edge

LatestPool

Front end

Back end

Latest Director

Latest Edge

Legacy andLatest Federation

Stage 5

Introduce the Lync 2013 Edge ServersDeploy Lync 2013 Edge Server in parallel to the existing Legacy deploymentOptional, deploy Lync 2013 Director

21

Page 22: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Pilot

Legacy Director

AD

LatestRemote Access

Legacy Pool

Legacy Edge

LatestPool

Front end

Back end

Latest Director

Latest Edge

Legacy andLatest Federation

Stage 5

Routing and ValidationRoute Lync 2013 remote access through Lync 2013 Director (if applicable)Route Lync 2013 federation through Legacy Edge Server and Director (if applicable)Keep federation and remote access through Legacy Edge Server and DirectorValidate all remote access scenarios (except Federation)

22

Page 23: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Production

Legacy Director

Legacy andLatest Federation

AD

LatestRemote Access

Legacy Pool

Legacy Edge

LatestPool

Front end

Back end

Latest Director

Latest Edge

Stage 6

Scale pool to productionExpand hardware in Lync Server 2013 Pool to handle remaining users from Legacy poolNo changes to existing routingNo changes to coexistence

23

Page 24: Microsoft ® Lync Ignite Microsoft Lync 2013.

Legacy Remote AccessProduction

Production

Legacy Director

Legacy andLatest Federation

AD

LatestRemote Access

Legacy Pool

Legacy Edge

LatestPool

Front end

Back end

Latest Director

Latest Edge

Stage 7

Move all users to new poolLync 2010 Legacy

Move-CsUserOCS 2007 R2 Legacy

Move-CsLegacyUsers

24

Page 25: Microsoft ® Lync Ignite Microsoft Lync 2013.

Production

Legacy Remote Access Pilot

LatestPool

Front end

Back end

Production

Legacy andLatest Federation

Production

Legacy Director

Legacy Pool

Legacy Edge

LatestPool

Front end

Back end

Production

Legacy Director

Legacy Pool

Legacy Edge

LatestRemote Access

Legacy andLatest Federation

LatestRemote Access

Legacy andLatest Federation

AD

AD

Legacy Remote Access

Legacy andLatest Federation

LatestPool

Front end

Back end

Latest Director

Latest Edge

LatestPool

Front end

Back end

Latest Director

Latest Edge

Stage 8 – Optional

Migrate other pools and sitesUsing the same methodology, migrate remaining pools within the first site and other sites

Page 26: Microsoft ® Lync Ignite Microsoft Lync 2013.

Stage 9Enable Lync 2013 Edge for productionRoute remote access to Lync 2013 edgeRoute federation through the Lync 2013 EdgeDeactivate Legacy Edge, unmerges Legacy from AD DSUninstall Legacy Edge, recover hardwareMerge Topology Wizard to remove Legacy topology from Lync Server 2013 CMS

Latest Pool

Production

Latest Director

AD

Legacy & Latest Federation

LatestRemote Access

Latest Edge

26

Page 27: Microsoft ® Lync Ignite Microsoft Lync 2013.

Post MigrationMigrate Dial-in Access NumbersMigrate Address Book (Company_Phone_Number_Normalization_Rules.txt)Configure the Meeting Join PageDeploy Lync 2013 ClientsRelocate the CMS

Additional ActionsArchiving and monitoring serversTrusted application serversEnterprise Voice, Mediation Servers, Gateways and SBAsAnd much more….

Additional Things to Consider and Do

27

Page 28: Microsoft ® Lync Ignite Microsoft Lync 2013.

Client Interoperability

Page 29: Microsoft ® Lync Ignite Microsoft Lync 2013.

Live Meeting (on-premises) migration

Lync 2013 client—Lync Server 2013 sign-in

Client deployment paths

Person-to-Person (P2P) interoperability

Scheduling

Conference/meeting join

In-meeting content

Client Interoperability

29

Page 30: Microsoft ® Lync Ignite Microsoft Lync 2013.

Lync 2013 removes the Live Meeting data Multipoint Control Unit (MCU) and therefore Live Meeting client supportUse OCS 2007 R2 Outlook Conferencing add-in for Live Meeting Service Meetings (or Live Meeting Service Web user interface [UI])

While OCS 2007 R2 client (and Outlook add-in) are installed:Users homed on OCS 2007 R2 or Lync 2010 Servers can continue to schedule and use Live Meeting

After Lync 2013 is installed and user is homed on Lync 2013 Server:Scheduling new Live Meetings is not available—use Lync Online MeetingLive Meetings previously on your calendar will not workUsers must reschedule their Live Meetings to Lync meetingsStand-alone tool planned to assist in migrating meetings in bulk

Live Meeting

30

Page 31: Microsoft ® Lync Ignite Microsoft Lync 2013.

Lync 2013 ServerSupports OCS 2007 R2 (migration purposes), Lync 2010, and Lync 2013 clients Lync Web App is supported only for Lync 2013 (and conferencing only)

Lync Server 2010New: Supports Lync 2013 client to allow customers to update Office to Office 2013 before upgrading Lync Servers to Lync 2013Also supports OCS 2007, OCS 2007 R2, Lync 2010 clients

Client Support

31

Page 32: Microsoft ® Lync Ignite Microsoft Lync 2013.

Minimum OS support for Lync 2013 is Windows 7 or later or Windows Server 2008 SP2 or later

Can deploy Lync 2013 client with Office install/upgrade or standalone

Two paths to deploy client:Office/Lync 2013 deployment first, then update Servers (assumes Lync 2010 Servers)Update Servers first, then deploy Office/Lync 2013

Client Deployment Strategy

32

Page 33: Microsoft ® Lync Ignite Microsoft Lync 2013.

Person to Person  Feature

Client IM Presence Voice VideoApp

Sharing*File Transfer**

Lync 2013 Rich Client X X X X X X

Lync 2013 Web App N/A – conference only until 15.1 which will support sign in

Lync 2013 Mobile X X X  X     

Lync 2013 Phone Edition X X      

Lync 2010 Rich Client X X X X X X

Lync 2010 Web App N/A—conference only

Lync 2010 Attendee N/A—conference only

Lync 2010 Attendant X X X      

Lync 2010 Mobile X X        

Lync 2010 Phone Edition X X      

Office Communicator 2007 R2 Rich Client X X X X X X

Public IM Connectivity (PIC) (AOL, Yahoo) X X        

PIC (Messenger) X X X X    

* App Sharing: Disable new features as appropriate, and handle OCS 2007 R2 Desktop only sharing** P2P File Transfer works differently with OCS 2007 R2 and Lync 2010 clients (both in IM region, but Lync 2010

uses a media channel)

Page 34: Microsoft ® Lync Ignite Microsoft Lync 2013.

SchedulingClient/Add-in Server Versions Details/Comments

Lync 2013 Outlook add-in for Outlook 2003, 2007, 2010, Outlook 2013

Lync Server 2013Lync Server 2010*

* Older versions need to maintain existing feature support (no new Lync 2013 features)

Lync 2013 web scheduling Lync Server 2013  

Lync 2010 Outlook add-inLync Server 2013Lync Server 2010

 

Office Communicator 2007 R2 Conferencing add-in

Lync Server 2013*Lync Server 2010OCS 2007 R2

*Needed for postmigration (before clients are upgraded)

New in Lync 2013 add-in: Attendee mute controls for audio and video

34

Page 35: Microsoft ® Lync Ignite Microsoft Lync 2013.

Join a Lync 2013 Conference

Lync 2013 clients can join Lync 2010 hosted meetings with scaled down, compatible functionality

Client Supported Auto-Join Comments/detailsLync 2013 Rich Client Y Y Auto-join via Join Launcher page

Lync 2013 Web App Y Y Auto-join if a Lync 2013 Rich client is not installed

Lync 2013 Mobile Y Y Auto-join via Join Launcher page

Lync 2013 Phone Edition

Y* Y *When tethered to Lync 2013 Rich client, supports audio

Lync 2010 Rich Client Y NAdmin configured on Join Launcher page to allow join and auto-join

Lync 2010 Web App N/A—joining to a Lync 2013 Server uses Lync 2013 Web App

Lync 2010 Attendee Supported as an option, but auto-joins with Lync 2013 Web App

Lync 2010 Mac Supported as an option, but auto-joins with Lync 2013 Web App

Lync 2010 Attendant N/A

Lync 2010 Mobile Supported

Lync 2010 Phone Edition

Supported

Office Communicator 2007 R2 Rich Client

Not supported. Lync 2013 Web App auto-joins instead, with A/V support

35

Page 36: Microsoft ® Lync Ignite Microsoft Lync 2013.

In Meeting Content—Lync Server 2013

* Navigate, not upload.

** View only for Office PowerPoint content when uploaded by a Lync 2013 Rich client

ClientPeople

PresenceChat

Voice Video Appshare

Lync 2010PP

T

Lync 2013PPT

FileTransfe

r

WhiteBoard Poll

Lync 2013 Rich Client X X X X X X X X X

Lync 2013 Web App X X X X X* X X X X

Lync 2010 Rich Client X X X X X X** X X X

Lync 2010 Attendee X X X X X X** X X X

36

Page 37: Microsoft ® Lync Ignite Microsoft Lync 2013.

Q & A

Page 38: Microsoft ® Lync Ignite Microsoft Lync 2013.

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.


Recommended