You are on page 1of 47

Module 12

Planning a Migration to Lync Server 2013

MVA Jump Start

Module Overview
Overview of Coexistence and Migration
Migration Steps Planning for Clients and Devices Designing a Client Migration and Device Migration Strategy

Lesson 1: Overview of Coexistence and Migration


Overview of Migration
Migration Approach Support Boundaries Pre-requisites for Migration Overview of Service Migration

Voice Routing Coexistence


Migrating from Legacy Versions

Overview of Migration
Lync Server 2013 migration refers to migrating users and devices,

and not upgrading

The benefits of migration versus upgrading are huge

Migration results in clean installation where there are no leftovers

from earlier versions

Migration in Lync Server 2013 may also be migrating from an

existing voice infrastructure to Lync Server 2013

Terms
Migration Moving your production deployment from a previous version of Office Communications Server 2007 R2/Lync 2010 to Lync Server 2013
Upgrade Installing a newer version of software on a Server or client computer Coexistence The 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 (Office Communications Server 2007 R2/Lync 2010) Interoperability The ability of your deployment to operate successfully during the period of coexistence

Migration Approach Lync Server 2013 infrastructure deployed side-by-side with existing infrastructure
Similar to previous migrations In place upgrade not supported

Migrate Side-by-side, Site-by-site


Ensures service continuity, low end user impact Enables rollback, resiliency to logistical issues

Build Pilot Production


Minimize initial hardware requirements Trial builds administrator and end user confidence and minimizes risk

Support Boundaries
Server supports migration from N-1 or N-2

N (15): Lync 2013 N-1 (14): Lync 2010* N-2 (13): Office Communications Server (OCS) 2007 R2* N-1 client (Lync 2010) against Lync Server 2013 N client (Lync 2013) against Lync 2010 Server

Client support depends on workload


Voice Coexistence

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

* With latest Updates

Support Boundaries
Persistent Chat supports migration from

N-1 (14): Lync 2010* Group Chat N-2 (13): Office Communications Server (OCS) 2007 R2* Group Chat

Persistent Chat Client support

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

Lync 2013 cannot connect to Legacy Group Chat Servers

* With latest Updates

Pre-requisites for Migration


Topology requirements
Microsoft OCS 2007 R2 / Lync 2010 Server and Client updates Microsoft SQL Server

Telephony pre-requisites

Overview of Service Migration


Company ISV/developed applications
Microsoft Unified Communications Application Server Response Groups

Dial-in Conferencing
Exchange Server Unified Messaging

Voice Routing Coexistence


Outbound Calls
Home Server
Lync Server 2013 Lync Server 2013 Lync Server 2010 Lync Server 2013 OCS 2007 R2 15 15

Survivable Branch Appliance (SBA)


Mediation Server
15 14 Supported Supported Lync 2010 SBA Lync 2013 SBA Lync 2010 Pool Supported Not Supported Lync 2013 Pool Supported * Supported

14
15 13

15
13 15

Supported
Supported Not Supported

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

Inbound Calls
Mediation Server Lync Server 2013 Lync Server 2013 Lync Server 2010 Lync Server 2013 OCS 2007 R2 15 15 14 15 15 13 Next Hop Server 15 15 14 15 15 13 Home Server 15 14 15 13 13 15 Supported Supported Supported Supported Supported Supported

Migrating from Legacy Versions


Lync Server 2010 Uses CMS (Central Management Store) OCS 2007 R2 No CMS (Central Management Store)

Lync 2010 client, no Live Meeting client


Easy migration path

Configuration stored in Active Directory


Live Meeting and Office Communicator client Migration to Lync Server 2013 similar to Lync 2010 migration

Migrating From Lync Server 2010


Topology
Download existing topology in Lync Server 2013 Topology Builder Define new Lync 2013 Pool & publish the new topology Use Lync Server 2013 Topology Builder, Lync 2010 topology builder cannot be used

Configuration

Data exists in Lync 2010 (CMS) Lync Server 2013 uses Lync 2010 CMS instance Via Lync Server Control Panel From Management Shell: Move-CsLegacyUser Rollback from Management Shell: Move-CsUser

Users (Performed on Lync 2013 System)

Migrating From Office Communicator Server 2007 R2


Topology
Merger topology using the Topology

Users
Via Lync Server Control Panel From Management Shell: Move-CsLegacyUser Roll back from Management Shell: Move-CsUser

builder

Imports Legacy topology and

conference directories

Rerun when Legacy topology changes Publish the new topology

Configuration

Merge other configuration from Lync Management Shell: Import-CsLegacyConfiguration Rerun when legacy configuration has changed with -ReplaceExisting

Lesson 2: Migration Steps


Overview of Migration Steps
Defining a Site and Server Migration Strategy Process of Migrating to Lync Server 2013

Additional Considerations
Deactivating and Migrating Office Communications Server 2007 R2 Best Practices for Designing a Migration Strategy

Discussion: Best Practices for Pilot Implementation

Overview of Migration Steps Prepare for deployment


Plan sequence: site-by-site and side-by-side Deploy most recent updates, backup Legacy deployment Prep Active Directory schema, prep, domain AD DS forest Pilot Pool Pilot Edge and Director Take Pool in production Take Edge Servers in production Repeat for remaining Pools

Start in the first site, migrate pools side-by-side


Pick next site, repeat side-by-side

Defining a Site and Server Migration Strategy

Sequence deployment Start with site containing site by site federated Edge

Scales down for non-global deployment

Process of Migrating to Lync Server 2013 Stage 1


Plan
Define migration strategy Select sites, locations Identify users and define migration groups

Process of Migrating to Lync Server 2013 Stage 2


Prepare
Deploy most recent updates
Legacy Remote Access Legacy Federation

(Clients/Server) Backup Legacy deployment Run Best Practice Analyzer and ensure healthy deployment Upgrade AD DS schema, forest, domain preparation

Production

Apply updates

Legacy Edge Legacy Director

Apply updates

Apply updates

Legacy Pool

Upgrade schema

Active Directory

Process of Migrating to Lync Server 2013 Stage 3


Introduce first Lync Server 2013 Pool
Deploy pilot Lync 2013 Pool side-by-side

Legacy Remote Access

Legacy & latest Federation

with existing deployment

Production
Legacy Edge Legacy Director

Pilot

Activation of Lync Server 2013 adds

product references into Legacy Active Directory End Servers

Does not require deployment of all Front For OCS 2007 R2 Only:
Merge 2007R2 toplogy onto CMS Merge-CsLegacyTopology Import the configuration items:ImportCsLegacyConfiguration

Lync front end pool

Legacy Pool

Active Directory

Process of Migrating to Lync Server 2013 Stage 4


Routing
Mixed version routing from Lync

2013 Pool to Legacy Director

Legacy Remote Access

Legacy & latest Federation

External access through Legacy

Production
Legacy Edge Legacy Director

Pilot

Director and Legacy Edge Server

Lync front end pool

Legacy Pool

Active Directory

Stage 4 continued
Pilot with subset of users

Subset of users moved to Lync 2013 Pool Majority of users remain on Legacy Pool Validate functionality and interoperability Deploy Lync 2013 clients to some trial users on Lync 2013 Pool, Legacy clients for others

Production
Legacy Edge
Legacy Director

Pilot
R2 Only: Merge-CsLegacyTopology Import-CsLegacyConfiguration Import-CsLegacyConferenceDirectory Move-CsLegacyUser

front end pool

Legacy Pool

Back end

Active Directory

Process of Migrating to Lync Server 2013 Stage 5


Introduce the Lync 2013 Edge Servers
Deploy Lync 2013 Edge Server in

Legacy Remote Access

Legacy & latest Federation

Latest Remote Access

parallel to the existing Legacy deployment Director

Production
Legacy Edge Legacy Director

Pilot
Latest Edge

Optional, deploy Lync 2013

Latest Director front end pool

Legacy Pool

Back end Active Directory

Stage 5 continued
Routing & Validation
Route Lync 2013 remote access through
Legacy Remote Access

Lync 2013 Director (if applicable)

Legacy & latest Federation

Latest Remote Access

Route Lync 2013 federation through

Legacy Edge Server and Director (if applicable) through Legacy edge Server and Director (except Federation)

Production
Legacy Edge
Legacy Director

Pilot
Latest Edge

Keep federation and remote access

Validate all remote access scenarios

Latest Director front end pool

Legacy Pool

Back end Active Directory

Process of Migrating to Lync Server 2013 Stage 6


Scale Pool to production
Expand hardware in Lync Server
Legacy Remote Access
Latest Remote Access Legacy & latest Federation

2013 Pool to handle remaining users from Legacy Pool

Production
Legacy Edge Legacy Director

Pilot
Latest Edge

No changes to existing routing No changes to coexistence

Latest Director front end pool

Legacy Pool

Back end Active Directory

Process of Migrating to Lync Server 2013 Stage 7


Move all users to new Pool
Lync 2010 Legacy

Legacy Remote Access

Latest Remote Access

Legacy & latest Federation

Move-CsUser
Move-CsLegacyUsers

OCS 2007 R2 Legacy

Production
Legacy Edge Legacy Director

Pilot
Latest Edge

Latest Director front end pool

Legacy Pool

Back end Active Directory

Process of Migrating to Lync Server 2013 Stage 8


Migrate other Pools and Sites
Using the same methodology, migrate remaining Pools within the first site and

other sites

Process of Migrating to Lync Server 2013 Stage 9


Enable Lync 2013 Edge for production
Route remote access to Lync 2013 edge Route federation through the Lync

Latest Remote Access

Legacy & latest Federation

Production
Latest Edge

2013 edge

Deactivate Legacy Edge, unmerges

Legacy from AD DS hardware

Uninstall Legacy Edge, recover Merge Topology Wizard to remove

Latest Director

Legacy topology from Lync Server 2013 CMS Latest Pool

Active Directory

Additional Considerations

Post Migration
Migrate Dial-in Access Numbers Migrate Address Book (Company_Phone_Number_Normalization_Rules.txt) Configure the Meeting Join Page

Deploy Lync 2013 Clients


Relocate the Central Management Store

Additional Actions
Archiving and Monitoring Servers Trusted Application Servers Enterprise Voice, Mediation Servers, Gateways and SBAs And much more.

Deactivating and Migrating Office Communications Server 2007 R2


To ensure that Active Directory settings are cleaned up when removing the Office Communications Server 2007 R2 environment, you need to:
Deactivate server roles to remove associated Active Directory objects

Remove Enterprise Pools (if using Enterprise Edition)


Uninstall server components Clean up file shares and databases

Best Practices for Designing a Migration Strategy


Pilot user groups
Edge routing Firewall

DNS-based load balancing support


Dual administration during coexistence

Discussion: Best Practices for Pilot Implementation


How do you select pilot users?
How do you get feedback from users? How can helpdesk be used in a pilot?

Lesson 3: Planning for Clients and Devices


Discussion: Assess Business Requirements for Clients and Devices
Types of Lync Server 2010 Clients and Devices Coexistence Options for Clients

Planning for Client Version Policies


Planning for Device Support and Device Requirements

Discussion: Assess Business Requirements for Clients and Devices


Identify the types of clients
Evaluate the functionality Examine the client and device usage

Assess the deprecation or replacement of features

Types of Lync Server 2010 Clients and Devices Lync 2013 Server
Supports Lync 2010 and Lync 2013 clients Compatible with OCS 2007 R2 Lync Web App is supported only for Lync 2013 (and conferencing only)

Lync Server 2010


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

Coexistence Options for Clients


Evaluate the affect on users and the client software:
Changes to Online Meetings in Lync Server 2013 Default Lync Server 2013 Meeting Options

Lync Server 2013 Meeting Clients


Migrating Existing Meetings and Meeting Content User Experience during Migration - Before installing Lync Server 2013 User Experience during Migration - After installing Lync Server 2013

Meetings with Federated Organizations that Use Previous Clients


Lync Server 2013 Compatibility with Meetings on Earlier Versions of Office Communications

Server Configuring the Meeting Join Webpage

Planning for Client Version Policies


Client Version Policies enable you to define a set of rules that specify the client

versions that your Lync Server 2013 environment supports. When planning for use of Client Version Policies, evaluate the client versions that are currently in use in the environment that you want to migrate to Lync Server 2013. When migrating your users to Lync Server 2013, plan for deploying the new client software to these users. After deploying Lync 2013 client software, build policies that disallow using the previous version clients outright, or direct these to download links for updated client software.

Planning for Device Support and Device Requirements


System and Infrastructure Requirements for Lync Devices

Power over Ethernet LLDP-MED

Network & Port Requirements


DNS Requirements DHCP Requirements

Certificates

Lesson 4: Designing a Client Migration and Device Migration Strategy


Designing Group Policy
Designing Policies for Devices Designing a Software Deployment Strategy

Client Deployment Strategy


Live Meeting Best Practices for Client, Device, and User Migrations

Designing Group Policy To design your Group Policy and in-band provisioning settings, you should:
Evaluate current Group Policy settings Review available client configuration options in Lync Server 2013 Determine the changes that are needed to current policy settings Configure bootstrapping policies for Lync Server 2013 Configure Lync 2013 client policies

Designing Policies for Devices When you design policies for phone devices, you should consider the following:

The usage profile of the phone devices for which you are designing policies The physical locations where the devices will be located The calling features that should be enabled or disabled Enabling of hotdesking if common area phones are deployed

Designing a Software Deployment Strategy When designing for the deployment of Web App and Attendee clients, you should:
Decide if you want to support both types of clients Always aim to leverage existing software distribution method, which may be in use in your environment Adhere to corporate policies for software distribution Decide whether to provide the standard download links or links that are hosted on your environment

Client Deployment Strategy 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

Live Meeting
Lync 2013 removes the Live Meeting data multipoint control unit (MCU) and therefore Live Meeting client support

Use OCS 2007 R2 Outlook Conferencing add-in for Live Meeting Service Meetings (or Live Meeting Service Web user interface [UI]) Users homed on OCS 2007 R2 or Lync 2010 Servers can continue to schedule and use Live Meeting Scheduling new Live Meetings is not available - use Lync Online Meeting

While OCS 2007 R2 client (and Outlook add-in) are installed:

After Lync 2013 is installed and user is homed on Lync 2013 Server:

Live Meetings previously on your calendar will not work


Users must reschedule their Live Meetings to Lync meetings Standalone tool planned to assist in migrating meetings in bulk

Best Practices for Client, Device, and User Migrations


The Lync Server 2013 environment should be fully configured before migrating

users Do not deploy Lync 2013 clients prior to moving users Educate users on the new conferencing clients prior to deployment Move users in logical groups Always do pilot client, device and user migrations Ensure consistent security update levels for clients and devices across your deployment.

Module Review and Takeaways


Review Question(s)
Real-world Issues and Scenarios Tools

2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics 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.