{"id":550,"date":"2013-10-14T21:47:59","date_gmt":"2013-10-14T19:47:59","guid":{"rendered":"http:\/\/blog.lync2013.org\/?p=550"},"modified":"2014-05-13T13:04:12","modified_gmt":"2014-05-13T13:04:12","slug":"migrateocs2007","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=550","title":{"rendered":"Personal experience and pain points migrating OCS 2007 R2 to Lync 2013"},"content":{"rendered":"

I was recently involved in an OCS 2007 R2 to Lync Server 2013 migration and I thought it would be a good idea to share my experience, with a specific focus on what went wrong, unexpected, or undocumented.<\/span><\/p>\n

I won\u2019t get into the details on how to migrate. This is already widely documented on a number of blogs as well as TechNet (http:\/\/technet.microsoft.com\/en-us\/library\/jj205375.aspx<\/a>).<\/span><\/p>\n

ENVIRONMENT: OCS 2007 R2. Two-node Enterprise pool, no external deployment (edge servers). Polycom CX-700 phones. Two Sonus (NET) VX 1200 gateways terminating an ISDN-30 trunk each and used as hybrid gateways (that is, they served as mediation servers and no OCS mediations are present). OCS is the main voice platform for the customer. No other PBX or phones were present.<\/span><\/p>\n

Below were my pain points in order of occurrence.<\/span><\/p>\n

\n

 <\/p>\n

TOPOLOGY MERGE<\/span><\/h5>\n

Adding the Lync pool was a nifty and painless work, until topology merge. Next steps, that is, merging the topology and importing legacy configuration to Lync is where I had suspected some possibly unpredictable results due to the hybrid gateways model in OCS 2007 R2. I have struggled finding specific documentation about migrating such scenario. Biggest question mark is would Lync pool be able to use media gateway based mediation? I assumed that could be a no.<\/span><\/p>\n

Merging topologies on the topology builder was an apparently straightforward step with the following warnings on the log:<\/span><\/p>\n

2013-09-25 14:04:56 INFORMATION :\u00a0 No new Mediation Server added to the Office Communications Server 2007 \/ Office Communications Server 2007 R2 deployment.
\n<\/em>Cannot find any Office Communications Server 2007 \/ Office Communications Server 2007 R2 “MediationServer” in the deployment
\n<\/em>List of Office Communications Server 2007 \/ Office Communications Server 2007 R2 “Trusted application server” roles being migrated<\/em><\/span><\/p>\n

Cluster fully qualified domain name (FQDN) “vx1.contoso.local”
\n<\/em>Computer fully qualified domain name (FQDN) “vx1.contoso.local”<\/em><\/span><\/p>\n

2013-09-25 14:04:56 INFORMATION:\u00a0 UCMA application with the cluster fully qualified domain name (FQDN) “vx1.contoso.local” does not depend on a pool.
\n<\/em>2013-09-25 14:04:56 INFORMATION:\u00a0 UCMA application with the cluster fully qualified domain name (FQDN) “vx2.contoso.local” does not depend on a pool.<\/em><\/span><\/p>\n

The result was media gateways being added as trusted application entries in the BackCompatSite.<\/span><\/p>\n

\n

 <\/p>\n

IMPORT LEGACY CONFIGURATION<\/span><\/h5>\n

As no OCS 2007 R2 mediations servers were detected in the legacy topology, I wondered how the legacy configuration import procedure would react, and I was ready to redo the voice configuration in Lync if required. I run:<\/span><\/p>\n

Import-CsLegacyConfiguration<\/strong><\/em><\/span><\/p>\n

I got the following warning for each route and gateway:<\/span><\/p>\n

2013-09-25 14:10:23 WARNING:\u00a0 Cannot find a Mediation Server with the fully qualified domain name (FQDN) “vx2.contoso.local”. Run “Merge-CsLegacyTopology” cmdlet before using this cmdlet or make sure that a PSTN route is pointing to a valid Mediation Server. Skipping creation of a Lync Server 2013 PSTN route setting with the name “Emergency Services”. numberPattern:\u00a0 “^(+999$)”<\/em><\/span><\/p>\n

It seemed, Lync was expecting to see domain-joined \u201cproper\u201d mediation servers in the topology but that was not the case.<\/span><\/p>\n

The result on Lync topology and configuration was the following:<\/span><\/p>\n