As with all its other products, Microsoft provides support for migrations from previous versions. This article series describes step by step migration from Lync Server Standart / Enterprise 2010 to Lync Server Standart / Enterprise 2013 process. In this article inlude fromLync Server 2010 Enterprise to Lync Server 2013 Enterprise migration.
The focus this article is the following;
- Step 1: Before You Begin the Migration
- Step 2: Plan Your Migration from Lync Server 2010
- Step 3: Prepare for Migration
- Step 4: Deploy Lync Server 2013 Pilot Pool
- Step 5: Move test users to the Pilot Pool
- Step 6: Add Lync Server 2013 Edge Server to Pilot Pool
- Step 7: Move from Pilot Deployment into Production
- Step 8: Complete Post-Migration Tasks
- Step 9: Decommission Legacy Pools
My Lab Overview:
First, let’s describe my typical current environment. As you can see below the lab that I build include 4 Legacy Servers (Lync Server 2010 Enterprise), 1 Domain Controller, 4 new Lync 2013 Servers.
| NO | Hostname | Operation Systems | Roles |
| 1 | oi-dc2012.oiboran.lync | Windows Server 2012 DataCenter | Domain Controller, DNS, DHCP, Certification Authority |
| 2 | oi-lync2010fe.oiboran.lync | Windows Server 2008 R2 | Lync Server 2010 Front End Enterprise Edition |
| 3 | oi-lync2010beck.oiboran.lync | Windows Server 2008 R2 | Lync Server 2010 BackEnd Server / SQL 2008 R2 Sp2 |
| 4 | oi-lync2010ma.oiboran.lync | Windows Server 2008 R2 | Lync Server 2010 Monitoring and Archiving Server / SQL 2008 R2 Sp2 |
| 5 | oi-lync2010edge.oiboran.lync | Windows Server 2008 R2 | Legacy Edge- External Users |
| 6 | oi-lync2013fe.oiboran.lync | Windows Server 2012 DataCenter | Lync Server 2013 Front End Enterprise Edition |
| 7 | oi-lync2013back.oiboran.lync | Windows Server 2012 DataCenter | Lync Server 2013 BackEnd Server / SQL 2012 |
| 8 | oi-lync2013ma.oiboran.lync | Windows Server 2012 DataCenter | Lync Server 2013 Monitoring and Archiving Server / SQL 2012 |
| 9 | oi-lync2013edge.oiboran.lync | Windows Server 2012 DataCenter | External Users |
Legacy enterprise pool Host A record:pool2010.oiboran.lync
Lync 2013 Enterprise pool Host A record:pool2013.oiboran.lync
Step 1: Before You Begin the Migration
The recommended and supported migration procedure for Lync Server 2013 is side-by-side migration. This article describes why you should use side-by-side migration and also includes information about coexistence testing.
Side-By-Side Migration
In nearly every migration, you should use the side-by-side migration path. In a side-by-side migration, you deploy a new server with Lync Server 2013 alongside a corresponding server that is running Lync Server 2010, and then transfer operations to the new server. If it becomes necessary to roll back to Lync Server 2010, you have only to shift operations back to the original servers. Be aware that in this situation any new meetings scheduled with upgraded clients will not work, and the clients would also need to be downgraded.
Coexistence Testing
After you have deployed Lync Server 2013 in parallel with Lync Server 2010, the deployment represents a coexistence testing state of Lync Server 2013 and Lync Server 2010. While in this state, it is important to test and ensure that services are started, each site can be administered, and clients can communicate with current and legacy users. Prior to the migration of all users, it is very important that you understand the state of each deployment and ensure that each deployment is functional and working properly. Typically, the coexistence testing phase exists throughout the pilot testing of Lync Server 2013. Legacy users are moved to Lync Server 2013 for a period of time to ensure that application compatibility and features and functions are working properly. After pilot testing, users and applications are moved to the production version of Lync Server 2013, and the legacy pools and applications of Lync Server 2010 are retired.
Step 2: Plan Your Migration from Lync Server 2010
User Migration
A generally accepted best practice for migrations is to create several test users and use them to conduct systems tests. After you have successfully moved and tested those accounts, you should identify a group of pilot production users and move their accounts and conduct validation tests on them. When you get satisfactory results, you can move the rest of your users to the new deployment.
I created 5 Lync Enable Users which are using Lync 2010 clients for migration tests.
Migrating Archiving and Monitoring Servers
If you deployed Archiving Server and Monitoring Server in your Lync Server 2010 environment, you can deploy these servers in your Lync Server 2013 environment after you migrate your Front End pools. If archiving and monitoring functionality are critical to your organization, however, you should add archiving and monitoring to your Lync Server 2013 pilot pool before you migrate so that the functionality is available during the migration process.
If you want archiving and monitoring functionality during the migration process, keep the following considerations in mind:
Archiving data and monitoring data are not moved to the Lync Server 2013 deployment. The data you back up prior to decommissioning the legacy environment will be your history of activity in the Lync Server 2010 environment.
The Lync Server 2010 version of Archiving Server and Monitoring Server can be associated only with a Lync Server 2010 Front End pool. In Lync Server 2013, Archiving and Monitoring are no longer server roles, but services integrated into the Lync Server 2013 Front End pool.
During the time that your legacy and Lync Server 2013 deployments coexist, the Lync Server 2010 version of Archiving Server and Monitoring Server gather data for users homed on Lync Server 2010 pools. Archiving and Monitoring in Lync Server 2013 gather data for users homed on Lync Server 2013 pools.
If you use a third-party archiving and monitoring solution in conjunction with Archiving and Monitoring in Lync Server 2013, consult with your vendor about when and how you need to integrate the third-party solution with Lync Server 2013.
In this lab we have archiving and monitoring server that is oi-lync2010ma.oiboran.lync (Instance names: lyncarc – lyncmon)
Migrating Group Chat Servers
If you deployed Group Chat Server in your legacy Lync Server 2010 environment, you must deploy Lync Server 2013 Persistent Chat Server. Group Chat Server and Persistent Chat Server can coexist, but content (for example, chat rooms, etc.) is not shared across these servers. To access the legacy Group Chat Server content from Persistent Chat Server, you must migrate the Group Chat Server to Persistent Chat Server.
Administering Servers after Migration
In general, you must use the administrative tool that corresponds to the server version that you want to manage. You cannot install the Lync Server 2010 and the Lync Server 2013 administrative tools on the same computer. Also, the Lync Server 2013 Control Panel is not installed automatically on each server. After a Lync Server 2013 pilot pool is deployed, you cannot use Lync Server 2010 Topology Builder or Lync Server 2010 Control Panel to manage any Lync Server 2013 resources. You must use Lync Server 2013 tools to manage Lync Server 2013 and Lync Server 2010 resources.
Migrating Multiple Sites and Pools
Lync Server 2013 supports multi-site and multi-pool deployments. The process of migrating multiple pools from Lync Server 2010 to Lync Server 2013 requires the following considerations:
1. After deploying a Lync Server 2013 pilot pool, you need to define a subset of pilot users that will be moved to the Lync Server 2013 pool, and a methodology for validating the functionality of the users. For example, after moving a user to the pilot pool, verify the user’s conference policy has moved to Lync Server 2013.
2. After deploying an Edge Server in the pilot pool, you need to validate that external users can communicate with the Lync Server 2013 pool.
3. After transitioning the federated routes from Lync Server 2010 Edge Servers to the pilot Lync Server 2013 Edge Servers, you need to validate that federated users can communicate with the Lync Server 2013 pool.
4. After moving all the users and non-user contact objects, you need to validate that the Lync Server 2010 pool is empty.
5. After verifying that the Lync Server 2010 pool is empty, you can then deactivate the pool.
Migrating XMPP Federation
Previous versions of Lync Server and Office Communications Server provided an extensible messaging and presence protocol (XMPP) gateway that could be deployed as a separate server role to allow federating with XMPP deployments. In Lync Server 2013, the XMPP functionality can be deployed as a feature. XMPP functionality is installed in two parts: as an XMPP proxy that runs on the Lync Server 2013 Edge Server, and the XMPP Gateway that runs on the Lync Server 2013 Front End Server.
From a migration perspective, a Lync Server user account can be moved to a Lync Server 2013 pool and continue to use the legacy XMPP gateway. This is possible only when the XMPP federated partner is not configured in Lync Server 2013.
In summary, if Lync Server 2010 has been deployed with the Office Communications Server 2007 R2 XMPP Gateway and XMPP federation has been enabled for legacy Lync Server 2010 users, to migrate the XMPP federation to Lync Server 2013:
1. Deploy a Lync Server 2013 pool.
2. Deploy a Lync Server 2013 Edge server.
3. Move all users to the Lync Server 2013 pool
4. Create XMPP access policies and certificates for the Edge Server.
5. Enable XMPP federation in Lync Server 2013.
6. Update the DNS entries to point to the Lync Server 2013 XMPP Gateway.
Step 3: Prepare for Migration
Apply Lync Server 2010 Updates
Before you migrate to Lync Server 2013, updates must be applied to your Lync Server 2010 environment. For the most up-to-date information about Lync Server 2010, see Updates Resource Center for Lync athttp://go.microsoft.com/fwlink/p/?linkid=232630
To install updates for Lync Server 2010, I follow theMethod 1 Cumulative Server Update Installer.
Run LyncServerupdateInstaller.exe package and restart FE servers.
Configure DNS Records for Pilot Pool Deployment
Prior to deploying the Lync Server 2013 pilot pool, you must update the DNS Host A entries for the pilot pool. To successfully complete this procedure, you should be logged on to the server or domain as a member of the Domain Admins group or a member of the DnsAdmins group.
To configure DNS Host A records
1. On the Domain Name System (DNS) server, click Start, click Administrative Tools, and then click DNS.
2. In the console tree for your domain, expand Forward Lookup Zones, and then right-click the domain in which Lync Server 2013 will be installed.
3. Click New Host (A or AAAA).
4. Click Name, type the host name for the Lync Server 2013 pool (the domain name is assumed from the zone that the record is defined in and does not need to be entered as part of the A record).
5. Click IP Address, type the IP address for the Front End pool.
6. Click Add Host, and then click OK.
7. When you are finished, click Done.
Run Best Practices Analyzer
The Lync Server 2010 Best Practices Analyzer tool gathers configuration information from an Lync Server 2010 deployment and determines whether the configuration is set according to Microsoft best practices. You can install the tool on a client computer that runs Microsoft .NET Framework 3.5 Service Pack 1, or directly on the server that runs Lync Server 2010. We recommend that you install and run this tool on a client computer. The Lync Server 2010 Administrative Tools should also be installed locally on the client computer so that the Best Practices Analyzer can collect a full set of data.
You can download the Lync Server 2010 Best Practices Analyzer from the Microsoft Download Center athttp://go.microsoft.com/fwlink/p/?linkid=246173
Back Up Systems and Data
Before you begin the migration to Lync Server 2013, we strongly recommend that you perform a full system backup and document your existing system, including an inventory of user accounts that are homed on each pool, so that you can roll back to Lync Server 2010 if it becomes necessary. Multiple tools and programs are available for backing up and restoring data, settings, and systems.
Refer following link for Lync 2010 Backup Instructions.
Verify Lync Server 2010 Services are started
1. From the Lync Server 2010 Front End Server, navigate to the Administrative Tools\Services applet.
2. Verify that the following services are running on the Front End Server:
Review the Lync Server 2010 topology in Lync Server Control Panel
1. Log on to the Front End Server with an account that is a member of the RTCUniversalServerAdmins group or a member of the CsAdministrator or CsUserAdministrator administrative role.
2. Open the Lync Server Control Panel.
3. Select Topology. Verify that the various servers in your Lync Server 2010 deployment are listed.
To review Lync Server 2010 users in Lync Server Control Panel
1.Open the Lync Server Control Panel.
2. Select Users and then click Find.
3. Verify that the Registrar Pool column points to the Lync Server 2010 pool for each user listed.
To verify Lync Server 2010 Edge and Federation Settings
1. Start Topology Builder.
2. Select Download Topology from existing deployment.
3. Choose a file name and save the topology with the default .tbxml file type.
4. Expand the Lync Server 2010 node to reveal the various server roles in the deployment.
5. Select the site node and verify if a Site federation route assignment value is set.
6. Next, select the Standard Edition Server or Enterprise Edition front end pool. Determine if an Edge pool has been configured for Media belowAssociations.
7. Finally, select the Edge pool and identify if a Next hop pool is configured belowNext hop selection.
Verify legacy XMPP Federated Partner Configuration
1. From the legacy XMPP server, navigate to the Administrative Tools\Services applet.
2. Verify that the Office Communications Server XMPP Gateway service is started.
Step 4: Deploy Lync Server 2013 Pilot Pool
This section covers the steps required to deploy a pilot pool of Lync Server 2013. The deployment of Lync Server 2013 requires using Topology Builder to define your topology and the components you want to deploy, preparing your environment for deployment of the Lync Server 2013 components, publishing your topology design on the first Front End Server, and then installing and configuring Lync Server 2013 software for the components for your deployment. When completed, your Lync Server 2013 pilot pool deployment will coexist with an existing Lync Server 2010 pool.
Prepare Active Directory for Lync Server
To prepare Active Directory for Lync Server 2013
1.On the Lync Server 2013 Front End Server, run following command on Windows PowerShell and restart FE Server. (Front End Servers require .NET 3.5, which is not installed by default on Windows Server 2012. To install it, put your Windows Server 2012 installation media in Drive D and type the following)
Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client, BITS -Source D:\sources\sxs
Add-WindowsFeature windows-identity-foundation
On the Lync Server 2013 Front End Server, run Lync Server 2013 Setup.
Specify the location for the Lync Server 2013 installation files.
Check “I accept the terms …” and click OK.
2. Select Prepare Active Directory. (Complete all steps)
Step1: Prepare Schema – Click Run
Step 1: Prepare Schema completed.J
To verify that the schema extension have been successfully replicated in your Active Directory Domain Services (AD DS) forest, do the following:
1. Log on to a domain controller (other than the domain controller that holds the schema master role) in your Active Directory Domain Services (AD DS) forest, where the schema extensions were applied as a member of the Enterprise Admins group.
2. Open ADSI Edit: Click Start, click Administrative Tools, and then click ADSI Edit.
Tip: Alternatively, click Start, then click Run, type adsiedit.msc to start ADSI Edit.
3. In the Microsoft Management Console (MMC) tree, if it is not already selected, click ADSI Edit.
4. On the Action menu, click Connect to.
5. In the Connection Settings dialog box under Select a well known Naming Context, select Schema, and then click OK.
6. Under the schema container, search for CN=ms-RTC-SIP-SchemaVersion. If this object exists, and the value of the rangeUpper attribute is 1150 and the value of the rangeLower attribute is 3, then the schema was successfully updated and replicated. If this object does not exist or if the values of the rangeUpper and rangeLower attributes are not as specified, then the schema was not modified or has not replicated.
Note: If your check of the replication of the schema does not yet show a successful replication, wait approximately 15 minutes and then check again. Active Directory replication is based on a loose consistency model and some replication latency can occur, based on a number of factors in the server and infrastructure.
Step 3: Prepare Current Forest, click Run
Specify domain where the universal group will be created. I selected “Local domain”
Step 3: Prepare Current Forest completedJ
Verify Replication of Forest Preparation
To confirm that the replication of the Global Catalog and the creation of objects during Forest Preparation have been successful, do the following:
1. On a domain controller (preferably in a remote site from the other domain controllers), in the forest where the Forest Preparation was run, open Active Directory Users and Computers.
2. In Active Directory Users and Computers, expand the domain name of your forest or a child domain.
3. Click the Users container on the left side pane and look for the Universal group CsAdministrators in the right side pane. If CsAdministrators (among eight other new Universal groups that begin with Cs) is present, replication of the Forest Preparation has been successful.
4. If the group(s) is not yet present, you can force the replication or wait 15 minutes and refresh the right side pane. When the groups are present, replication is complete.
Tip: If you want to review the log files that are created by the Lync Server Deployment Wizard, you can find them on the computer where the Deployment Wizard was run, in the Users directory of the Active Directory Domain Services (AD DS) user who ran the step. For example, if the user logged in as the domain administrator in the domain Contoso.net, the log files are located in:
C:\Users\Administrator.domain\AppData\Local\Temp
Step 5: Prepare Current Domain, Click Run
Step 5: Prepare Current Domain completedJ
Verify Replication in the Domain
To verify replication of the domain preparation accomplished in Step 1: Prepare Schema, it is necessary to run a cmdlet from the Lync Server Management Shell. To run the Windows PowerShell cmdlet, log on to a computer that is a member of the domain that you have prepared, and as a member of the Domain Admins group. Do the following:
1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.
2. In the Windows PowerShell, type the following:
Get-CsAdDomain [-Domain <Fqdn>] [-DomainController <Fqdn>] [-GlobalCatalog <Fqdn>] [-GlobalSettingsDomainController <Fqdn>]
Get-CsAdDomain -Domain oiboran.lync -GlobalSettingsDomainController oi-dc2012.oiboran.lync
Note: The parameter GlobalSettingsDomainController enables you to indicate where global settings are stored. If your settings are stored in the System container (which is typical with upgrade deployments that have not had the global setting migrated to the Configuration container), you define a domain controller in the root of your Active Directory Domain Services (AD DS) forest. If the global settings are in the Configuration container (which is typical with new deployments or upgrade deployments where the settings have been migrated to the Configuration container), you define any domain controller in the forest. If you do not specify this parameter, the cmdlet assumes that the settings are stored in the Configuration container and refers to any domain controller in Active Directory.
If you do not specify the Domain parameter, the value is set to the local domain. This cmdlet returns a value of LC_DOMAIN_SETTINGS_STATE_READY if domain preparation was successful.
Step 7: Add users to provide administrative to the Lync Server Control Panel
Create Lync Server Control Panel Administrators
To grant access to the Lync Server 2013, do the following:
1. Log on as a member of the Domain Admins group or the RTCUniversalServerAdmins group.
2. Open Active Directory Users and Computers, expand your domain, right-click the Users container, and then click Properties.
3. In CSAdministrator Properties, click the Members tab.
4. On the Members tab, click Add. In Select Users, Contacts, Computers, Service Accounts, or Groups, locate the Enter the object names to select. Type the user name(s) or group name(s) to add to the group CSAdministrators. Click OK.
5. On the Members tab, confirm that the users or groups that you selected are present. Click OK.
Download Topology From Existing Deployment
When creating a Lync Server 2013 pool, you will use the Central Management Store that is associated with Lync Server 2010. When you start Topology Builder on first use and subsequent edit sessions, you are prompted for the location where you want Topology Builder to load the current configuration document. Because you already have a Lync Server 2010 topology defined and have established the Central Management store, you should choose to download a topology from an existing deployment. Topology Builder will read the database and retrieve the current definition.
To download a topology from an existing deployment
1.Open the Lync Server Deployment Wizard.
2.From the Lync Server 2013 – Deployment Wizard page, click Install Administrative Tools.
3.Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013 , and then click Lync Server Topology Builder.
4.Select Download Topology from existing deployment.
5. Choose a file name and save the topology with the default .tbxml file type.
6. Expand the Lync Server node, as shown, to reveal the various server roles in the deployment.
Deploy Lync Server 2013 Pilot Pool
One of the first steps required for migration to Lync Server 2013 is to deploy a pilot pool. The pilot pool is where you test coexistence of Lync Server 2013 with your Lync Server 2010 deployment. Coexistence is a temporary state that lasts until you have moved all users and pools to Lync Server 2013.
When you deploy a pilot pool, you use the Define New Front End Pool wizard. You should deploy the same features and workloads in your Lync Server 2013 pilot pool that you have in your Lync Server 2010 pool. If you deployed Archiving Server, Monitoring Server, or System Center Operations Manager for archiving or monitoring your Lync Server 2010 environment, and you want to continue archiving or monitoring throughout the migration, you need to also deploy these features in your pilot environment. The version you deployed to archive or monitor your Lync Server 2010 environment will not capture data in your Lync Server 2013 environment.
Note: The following procedure discusses features and settings you should consider as part of your overall pilot pool deployment process. This section only highlights key points you should consider as part of your pilot pool deployment. For detailed steps, refer to the Deploying Lync Server 2013 deployment guide.
To deploy a Lync Server 2013 pilot pool
1.Log on to the computer where Topology Builder is installed as a member of theDomain Admins group and the RTCUniversalServerAdmins group.
2.Expand the tree until you reach Lync Server 2013 Enterprise Edition Front End pools.
3.Right click Enterprise Edition Front End pools, and select New Front End Pool.
4.Enter the pool FQDN. When you define your pilot pool, you can choose to deploy an Enterprise Edition Front End pool or a Standard Edition server. Lync Server 2013 does not require that your pilot pool features match what was deployed in your legacy pool.
Warning: The pool or server fully qualified domain name (FQDN) that you define for the pilot pool must be unique. It cannot match the name of the currently deployed Lync Server 2010 pool, or any other servers currently deployed.
5.On the Select features page, select the check boxes for the features that you want on this Front End pool. For example, if you are deploying only instant messaging (IM) and presence features, you would select the Conferencing check box to allow multiparty IM, but would not select the Dial-in (PSTN) conferencing, Enterprise Voice, or Call Admission Control check boxes, because they represent voice, video, and collaborative conferencing features
6.On the Select collocated server roles page, we recommend you collocate the Mediation Server in Lync Server 2013. When merging a legacy topology with Lync Server 2013, we require that you first collocate the Lync Server 2013 Mediation Server. After merging the topologies and configuring the Lync Server 2013 Mediation Server, you can decide to keep the collocated Mediation Server or change it to a stand-alone server in your Lync Server 2013 deployment.
7.On the Associate server roles with this Front End pool page, during pilot pool deployment, do not choose the Enable an Edge pool to be used by the media component of this Front End pool option. This is a feature you will enable and bring online in a later phase of migration. Keep this setting cleared for now.
8.On the Define SQL Server store page, click New, and specify the FQDN of the SQL server – Named instance.
9.On the Define the File Store page, use previously defined file store or create new one.
10.On the Specify Web Services URL page, type External Base URL (use legacy Lync 2010 External Base URL)
11.On the Select an Office Web Apps Server page, click New, and specify the FQDN of the application server.
12.On the Define the Archiving SQL Server store page, when defining the SQL Server store for both Lync Server Archiving and Monitoring, select the SQL Server instance created earlier for Lync Server 2013.
13.On the Define the Monitoring SQL Server store page, type required information.
14.To publish your topology, right-click the Lync Server node, and then click Publish Topology.
link:http://www.oiboran.com/?p=1073