Howdy,

In my last article I wrote about how to Migrate from Lync 2010 to Lync 2013, and configure the legacy Lync 2010 Edge to be used for the new Lync 2013 pool.

LAB infrastructure

So for this lab, I have the following deployed:

· DC01 is the domain controller

· Lync10-fe01 is Lync 2010 frontend standard edition

· Lync10-edg01 is Lync 2010 edge server

· Lync13-fe01 is Lync 2013 frontend standard edition

· Lync13-edg01 is Lync 2013 Edge server

One note to consider is that after adding your Lync 2013 Frontend to the pool, you must use Lync 2013 tools to manage Lync 2010 and 2013 servers.

Post Migration

The way I do it here, is what we call “Big Bang”, which basically assume that all users been migrated to the new Lync 2013 Pool and planning a down time, Migrate Certificates, IP-addresses and roles from the legacy Lync 2010 Edge to the new Lync 2013 Edge.

So before we start you need to prepare some notes about:

· Legacy Edge Internal and External NIC configurations “IP-addresses , gateways….etc.”

· Legacy Edge Static routing configured.

· Internal interface Certificate, Trusted Certificate authority certificate.

Remove the Legacy Lync 2010 Edge

On Lync 2013 front end, start the topology builder

· Right click your Lync Site name, then select “Edit Properties…”

·

· In Left menu, select “Federation Route” and then clear the box “Enable SIP Federation”

·

· Publish the Topology

· Now expand your Lync Server folder, go to the Edge Pools

· Right click your Lync 2010 Edge server and select “Edit Properties..”

·

· Clear the check box says “Enable Federation for this Edge Pool…”

·

· Click Ok

· Publish the topology

· Make sure that the Federation is disabled by checking the Edge 2010 properties

·

· Now expand your Lync 2010 Front end folder (Standard or enterprise depend on your deployment)

· Right click the Front end server and select “Edit Properties”

·

 

· Scroll down till you find

·

· “Associate Edge Pool” and uncheck the box

·

· Click ok.

· Do the same with the Lync 2013 Front end server

· Now Delete the Lync 2010 Edge server from the topology

·

· Publish the topology

·

Export the Certificates

If your new Lync 2013 Edge server FQDN is the same as the old one. Export the certificate from the Legacy Lync 2010 Edge server and copy them to the new Edge server.

Using MMC export both certificates on the new Lync 2013 Edge server.

Don’t forget to shut down the Old server after finishing this task

Add Lync 2013 Edge server to the Topology

You can use those two articles for deploying new Lync 2013 Edge server.

1- Deploy & Configure Lync Edge server Part-1

2- Deploy & Configure Lync Edge server Part-2

The only difference is that when it comes to the Request and Assign Certificate step you don’t need to Request new Certificate and you can directly Assign the exported Certificates.

Final tweaks

Now back to Lync 2013 Frontend and using the Topology builder.

· Right click your Lync site name and select “Edit Properties..”

·

·

· In left menu select “Federation Route”

· Check the box says “Enable SIP Federation” and select the New edge server from the drop down menu

·

 

· Click Ok

· Publish the topology

· Right Click your Lync 2013 Front End Server, select “Edit Properties..”

·

· Check the box says “Associate Edge Pool “for media…”

·

· Click Ok

· Do the same for Lync 2010 front end if you still have users hosted on the Lync 2010

· Publish the topology

So that’s it. Now you should start with testing the remote access and federation.