Module Overview
Overview of Coexistence and Migration
Migration Steps Planning for Clients and Devices Designing a Client Migration and Device Migration Strategy
Overview of Migration
Lync Server 2013 migration refers to migrating users and devices,
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
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
Voice Coexistence
Support Legacy Mediation Servers (N-1, N-2) Lync 2013 SBA cannot use the Lync 2010 Pool
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
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
Telephony pre-requisites
Dial-in Conferencing
Exchange Server Unified Messaging
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
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
Via Lync Server Control Panel From Management Shell: Move-CsLegacyUser Roll back from Management Shell: Move-CsUser
builder
conference directories
Configuration
Merge other configuration from Lync Management Shell: Import-CsLegacyConfiguration Rerun when legacy configuration has changed with -ReplaceExisting
Additional Considerations
Deactivating and Migrating Office Communications Server 2007 R2 Best Practices for Designing a Migration Strategy
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
Sequence deployment Start with site containing site by site federated Edge
(Clients/Server) Backup Legacy deployment Run Best Practice Analyzer and ensure healthy deployment Upgrade AD DS schema, forest, domain preparation
Production
Apply updates
Apply updates
Apply updates
Legacy Pool
Upgrade schema
Active Directory
Production
Legacy Edge Legacy Director
Pilot
Does not require deployment of all Front For OCS 2007 R2 Only:
Merge 2007R2 toplogy onto CMS Merge-CsLegacyTopology Import the configuration items:ImportCsLegacyConfiguration
Legacy Pool
Active Directory
Production
Legacy Edge Legacy Director
Pilot
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
Legacy Pool
Back end
Active Directory
Production
Legacy Edge Legacy Director
Pilot
Latest Edge
Legacy Pool
Stage 5 continued
Routing & Validation
Route Lync 2013 remote access through
Legacy Remote Access
Legacy Edge Server and Director (if applicable) through Legacy edge Server and Director (except Federation)
Production
Legacy Edge
Legacy Director
Pilot
Latest Edge
Legacy Pool
Production
Legacy Edge Legacy Director
Pilot
Latest Edge
Legacy Pool
Move-CsUser
Move-CsLegacyUsers
Production
Legacy Edge Legacy Director
Pilot
Latest Edge
Legacy Pool
other sites
Production
Latest Edge
2013 edge
Latest Director
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
Additional Actions
Archiving and Monitoring Servers Trusted Application Servers Enterprise Voice, Mediation Servers, Gateways and SBAs And much more.
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)
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.
Certificates
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
After Lync 2013 is installed and user is homed on Lync 2013 Server:
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.
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.