Hi all,

here is Our current deployment:

Lync server 2010:

1 edge

1 FE

3 branch sites

1 Monitoring server

Lync server 2013:

3 FrontEnd

2 Edge

2 Mediation

3 Backend

Simple urls are still point to Legacy (2010) servers.

External settings of Edge 2013 servers have been define With different name (Access,WEB and AV) and DNS (internally and externally) is pointing to New 2013 servers (via KEMP and TMG).

ATM 2013 topology is using edge2010 server.

Seems like we have two options for replacing Edge servers,one is Rip and replace and the other one is side by side transition.

We would like to do rip and replace so we can keep old simple urls (so that we dont have to send notice to external partners about Our New Access edge info) and using 2013 edge servers for federation and keep users on 2010 servers,then move them in a controlled way.

What is the best way to do this?

Thanks!

I prefer use same simple URLs in 2013 also. You can test all ports with port testing utility on 2013 Edge servers and once everything works fine, you can switch DNS for simple URLs.

Hi Tek and thanks for reply,

If we do so,then the rest should be fine and leave as is (CMS,routing group and so on)?

Any fallpit that we might come over when do rip and replace?

thanks!

Hi,

From your description above, the purpose is no need to update the New Access Edge info to the external partners. So for those external partners who set federation type of Allowed Partner Server, you need to keep the SIP domain name and the Edge Server FQDN the same as before.

So base on my knowledge, you need to plan a down time, and firstly cancel the federation route for the Lync Edge 2010 Server. Delete the Lync Edge 2010 Server and publish the topology. Then deploy the Lync 2013 Edge Server with the same FQDN with Lync Edge 2010 Server. Then enable federation for it and point to the Lync Server 2013 FE Pool.

Best Regards,
Eason Huang

Hi Eason and thanks for reply,

when doing this switch,are there other stuff we need to have in consideration?

Mediation for example?

thanks!

I typically move all users to Lync 2013 first. Web services (simple URL's etc) can point to Lync 2010 and will redirect users moved to the Lync 2013 pool. Once you have moved all your users over can change your reverse proxy to point simple URL's to the Lync 2013 Front End. Next tackle the Edge; I would provision side by side with temporary IP's so that you can test functionality, then you can do your rip and replace and move IP/FQDN over.

You'll need to switch a few things in the topology to use the new Edge e.g. mediation and federation:

Hi all,

forgot about this thread until now.We did a co-existence mode,so created new simple URL for new edge and added name to the certificate.THen changed rule in TMG so that everything (exept meet and dial in) points to new front end.

When most of users where moved we point meet and dial in to new frontend servers.So far all is good.thanks all