Check out the most comprehensive, actively managed Lync blog roll in the known universe, your one-stop source for links to over 100 of the very best Lync blogs. Here you will also find weekly blog highlights and a feed for a dozen of the top blogs.
Lync Server Support Home
Top Lync Solutions RSS Feed
Microsoft Senior Support engineers walk you through real-life support cases, giving you an insider’s view into the systematic approach they use to troubleshoot Lync Server issues.
These short videos focus on specific tasks and show you how to accomplish them for Microsoft Lync Server 2010.
Microsoft's federated Edge server is being upgraded, which includes an IP address change.
Author: Tom Laciano
Publication date: March 8, 2011
Updated: April 29, 2014
Modification date: April 21, 2011
Product versions: Lync Server 2010, Lync Server 2013
Effective May 9th, 2014, at 8:00 PM PST:
The federated Edge server that supports Instant Messaging and conferencing with external companies will be upgraded. The sipfed A records (sipfed.microsoft.com IN A) must be updated in your deployment to reflect the change and avoid interruption in federation with Microsoft.
After the server migration, the IP address for the microsoft.com SIP domain will change to 18.104.22.168. External companies who are federated with Microsoft may need to make changes to their infrastructure outlined under Instructions below in order for the federation to continue to function successfully.
Notify your contact with the external company that the IP address for the microsoft.com SIP (sipfed.microsoft.com) domain is changing to 22.214.171.124. Depending on how their infrastructure is configured, they may need to make one of the following changes:
Companies configured as direct federations using IP address (not sipfed.microsoft.com) will need to update their configuration to the new IP address.
Companies using their firewall(s) to filter by IP address will need to update their Access Control List (ACL) to the new IP address
Note: External companies that are configured as an Enhanced federation and have configured their firewall(s) to Allow All (inbound and outbound) on TCP:5061 according to Microsoft's recommendations will not need to make any changes. They will experience a brief interruption in their ability to contact Microsoft employees through Lync or Communicator while the A record in DNS is automatically updated to reflect the new IP address.
Recognizing many customers require change control, one suggestion to consider ensuring connectivity with Microsoft during this change is to keep the existing firewall rule and adding a new rule for the changed IP address. Approaching the transition in this manner will further reduce failed Instant Messaging and Presence updates during the actual transition as well protect the communications in the event of delayed implementation or a need to roll back the change.
Customers that originally configured their federation route with Microsoft to use an IP address will have to modify that entry and possibly firewall rules to ensure communications continue successfully.
We apologize for the inconvenience this has caused you.
To learn more, check out the following articles:
Keywords: federation, federate, Lync, OCS, Office communications Server