I take its safe to deploy a new Edge pool in a new site without impacting on operations? I already have a site with the live Edge server to which all simple URLS point to but I'm now at a stage I want to introduce the new Edge pool which will eventually come the live site and it will use the same simple URLS as the current one.

As along as I don't swing over the external and internal DNS records I'm pretty sure this won't have any impact but thought I'd ask the question here before I commit! :)

• Edited by SimonCotton Monday, July 14, 2014 11:17 AM

Simple URLs should point to reverse proxy server other than Lync Edge Server.

If you refer to the FQND for Lync Edge Service, you cant use the same FQDNs for different Lync Edge pool as the first one.

I think there's some confusion. The Simple URLs point to the reverse proxy (such as meet.domain.com, dialin.domain.com, etc) These are set globally and you do not need to change them.

When creating a new Edge you need to set the address on the Access Edge, if you're doing a co-existence scenario (i.e adding an additional Edge pool) these must be unique or Topology Builder won't accept it. It is possible to reuse those existing URL if you were doing a straight cut-over (usually for the purposes of saving money on buying an additional UCC Cert) Having said that these addresses (unlike the simple URLs) are transparent to the end-user

If you are going from Lync 2013 Std to Lync 2013 EE, there actually is no need to rebuild your Edge - just make the next hop the EE pool (unless of course you're going from a standalone Edge to an Edge Pool.) 

Simple URLs should point to reverse proxy server other than Lync Edge Server.

If you refer to the FQND for Lync Edge Service, you cant use the same FQDNs for different Lync Edge pool as the first one.