:::: MENU ::::

Lync 2010 to Lync 2013 Migration completed … Almost… A Missing Step from Technet Migration Guide

We are nearly completed in our project to move Lync from 2010 to Lync 2013.  The project has gone amazingly smooth.  The step by step documents and tools on the Technet Migration from Lync Server 2010 to Lync Server 2013 have proven to be a great guide.

Our “test” or “lab” migration was done on our good friend Dustin Cassady’s environment simply because he hadn’t yet rolled it into production for his staff and he hadn’t yet deployed enterprise voice.  It made sense to migrate him before adding enterprise voice and then turn around and migrate.  So with that knowledge we proceeded to upgrade the Northwoods Lync infrastructure.  Since you can read about the process and plan your own deployment I won’t bore you with all the details but simply say our process was:

  • Spin up a new Lync 2013 Pool
  • Move a handful of users to the new pool.
  • Realize we forgot to run the Exchange ExchUCUtil for the new pool and fix voicemail for those users.
  • Enjoy fun with Certificates
  • Learn about the new WebApps Server Role
  • Spin up a new Survivable Branch Pool
  • Again forget to run the ExchUCUtil for the new pool and fix voicemail for those users.
  • Migrate all Gateways, Common Area phones & Analog Extensions
  • Migrate all users to the new Pool
  • Test new mobility and Windows8 Clients
  • Decommission the old environment

All of this went pretty smooth except for two three pieces:
Reponses Groups Fail to Migrate
Migrating UM Messaging Contacts not Documented
Migrating Unassigned Numbers not Documented (added 5/28/13)

Reponses Groups Fail to Migrate
Our first area of heartburn was Phase 9 Step 1, Migrate Response Groups.  I followed the steps, all groups moved but they didn’t work.  A bit of clarification, the Workflows and Queues of the Response Groups worked fine, but calls would not alert the agents in the groups.  We had to delete the groups and re-create them.  With new Groups everything worked great.

Migrating UM Messaging Contacts not Documented
The second area of heartburn is the fact that Technet doesn’t include the step of moving Exchange UM Messaging Contact Objects.  This step is in the OCS 2007 to Lync 2013 guide here, but that step is never mentioned in the Lync 2010 to Lync 2013 guide.  This caused a problem for us when we started Phase 8 of the Migration Guide and started to shut down the 2010 pool.  We stopped all 2010 services and then calls would ring 4 times and disconnect rather than the Auto Attendant answering.  In the Lync logs we saw a 504 Server Time-Out error. 
Lync Logs

And kudos to Dustin Hannifin asking a great question “Did you run UCUMUTil on the 2013 pool”… Well of course I had, but I didn’t to think to check which pool the objects were homed to… sure enough they were homed to the old 2010 pool which was powered off.
(Contact Server Pool was NCC-…)
Contact 2010

So starting the Front End service on the 2010 server and one powershell command later, all Contact Objects were homed on the 2013 pool and  the auto attendants were once again answering calls.
(Contact Server pool is now NWP-….)
Contact 2013

Steps can be found here to migrate the Contact object or use the following powershell command:
Get-CsExUmContact -Filter {RegistrarPool -eq “pool01.contoso.net”} | Move-CsExUmContact -Target pool02.contoso.net

Migrating Unassigned Numbers not Documented (Added 5/28/2013)
Like the contact objects the technet article doesn’t mention moving unassigned telephone numbers from the 2010 pool to the 2013 pool.  The steps and instructions of moving the Unassigned number can be found in the Lync Server 2013 Resource Kit Tools Documentation.  After installing the Resource kit the powershell command will move the unassigned number groups from the 2010 pool to the 2013 pool.


2 Comments

So, what do you think ?

UA-2932131-1