Enable or Disable Sending an Archiving Disclaimer to Federated Partners
Topic Last Modified: 2011-01-28
At the time you deployed your Edge Servers and enabled federation for your organization, you should have specified whether to automatically send the archiving disclaimer to federated partners. If you archive external communications, you should enable the sending of an archiving disclaimer. Use the procedure in this topic to change that configuration.
The following procedure assumes that you have already enabled federation for your organization. For details about enabling federation, see Enable or Disable Federation for Your Organization in the Deployment documentation or the Operations documentation.
To enable or disable sending an archiving disclaimer to federated partners
From a user account that is a member of the RTCUniversalServerAdmins group (or has equivalent user rights), or is assigned to the CsAdministrator role, log on to any computer in your internal deployment.
Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.
In the left navigation bar, click External User Access, click Access Edge Configuration.
On the Access Edge Configuration tab, click Global, click Edit, and then click Show details.
In Edit Access Edge Configuration, under Enable communications with federated users, select or clear the Send archiving disclaimer to federated partners check box to enable or disable automatically sending the archiving disclaimer.
To enable federated users to collaborate with users in your Lync Server 2010 deployment, you must have also configured at least one external access policy to support federated user access. For details, see Manage Federated Partner User Access in the Deployment documentation or the Operations documentation. For details about controlling access for specific federated domains, see Control Access by Individual Federated Domains in the Deployment documentation or Operations documentation.