I have 2 sites, one of which is the Edge pool is the federation route and the other site does not have Federation or XMPP federation enabled. Both sites run Lync 2013 EE pool and Edge Pool.
As part of moving users over to test a new site, federated contacts do not show their presence, I believe this is due to the fact that the users home pool is not set up for federation.
Can I switch this on safely without breaking other things? When I adjust the site settings to use another federated route my topology validation comes back with:
• Warning: The topology contains more than one Federated Edge Server. This can occur during migration to a higher version of the product. In that case, only one Edge Server would be actively used for federation. Verify that the external DNS SRV record points to the correct Edge Server. If you want to deploy multiple federation Edge Server to be active concurrently (that is, not a migration scenario), verify that all federated partners are using Office Communications Server 2007 R2 or later. Verify that the external DNS SRV record lists all federation enabled Edge Servers.
• Warning: The topology contains more than one XMPP Federated Edge Server. This can occur during migration to a higher version of the product. In that case, only one Edge Server would be actively used for XMPP external federation. Verify that the external DNS SRV record points to the correct Edge Server.
I'd like to maintain federation on Site 1 whilst testing that federation works in the new Site 2 without breaking comms for users in Site 1. Just wondering if its ok to ignore these warnings?
Any advice is appreciated!