The Edge Server upgrade process is actually
the easiest part of the overall migration process; it’s a direct
replacement. A Lync 2010 Edge Server can proxy connections for both
Lync Server 2010 Front End pools and OCS 2007 R2 pools, meaning there
is no need to run both versions of Edge in parallel during the
coexistence period.
However, because the Lync Edge Server can use just
one external IP address and the OCS 2007 R2 Edge Server requires three,
there are some design considerations. This section covers the changes that
need to be made for migrating from the OCS 2007 R2 Edge Server to a
Lync 2010 Edge Server.
Configure Internal Pools
After
a successful Edge Server installation, the next step is to set the
internal pools to use it. The easiest way is to reset the global Edge
Server and Federation settings using the OCS 2007 R2 management
console, as shown in Figures 1 and 2.
Note
If the administrator chose to overwrite the global settings with pool-specific settings, those need to be changed, too.
Under Pool Settings, the administrator needs to point the AV Authentication service to the new Edge Server, as shown in Figure 3. This needs to be done for each pool.
Repoint DNS Records
Finally, the administrator must repoint the appropriate DNS records to the new Edge Server, such as sip.companyabc.com. The SRV records required and what they should be changed to follows:
Note
If an organization has partners that do not use open
federation, they will need to update their Edge Server federation
settings with the name of the new Lync Edge Server.
It is a good idea to test the edge services at this time before upgrading the internal servers.
