Udostępnij za pośrednictwem


Enabling or disabling critical mode in Lync Server 2013 to block or allow IM and web conferencing sessions if Archiving fails

 

Topic Last Modified: 2013-02-23

In Lync Server 2013 Control Panel, you use Archiving configurations to enable and disable critical mode. This includes the following Archiving configurations:

  • A global configuration that is created by default when you deploy Lync Server 2013.

  • Optional site-level and pool-level configurations that you can create and use to specify how archiving is implemented for specific sites or pools.

You initially set up Archiving configurations when you deploy Archiving, but you can change, add, and delete configurations after deployment. For details about how Archiving configurations are implemented, including which options you can specify and the hierarchy of Archiving configurations, see How Archiving works in Lync Server 2013 in the Planning documentation, Deployment documentation, or Operations documentation.

Note

To use archiving, you must configure Archiving policies to specify whether to enable archiving for internal communications, for external communications, or for both for users homed on Lync Server 2013. By default, archiving is not enabled for either internal or external communications. Prior to enabling Archiving in any policies, you should specify the appropriate Archiving configurations for your deployment and, optionally, for specific sites and pools, as described in this section. For details about enabling Archiving, see Configuring and assigning Archiving policies in Lync Server 2013 in the Deployment documentation.
If you decide after you deploy Archiving that you want to use Exchange Server integration to store archiving data and files on Exchange 2013 servers and all your users are homed on your Exchange 2013 servers, you should remove the SQL Server database configuration from your topology. You must use Topology Builder to do this. For details, see Changing Archiving database options in Lync Server 2013 in the Operations documentation.

To enable or disable blocking of IM and web conferencing sessions if archiving fails

  1. From a user account that is assigned to the CsArchivingAdministrator or CsAdministrator role, log on to any computer in your internal deployment.

  2. 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 2013 administrative tools.

  3. In the left navigation bar, click Monitoring and Archiving, and then click Archiving Configuration.

  4. Click the name of the appropriate global, site, or pool configuration in the list of archiving configurations, click Edit, click Show details, and then do the following:

  5. To set how archiving behaves when a failure occurs, select or clear the Block instant messaging (IM) or web conferencing sessions if archiving fails check box.

  6. Click Commit.

Enabling and Disabling Critical Mode by Using Windows PowerShell Cmdlets

You can enable or disable critical mode using the Set-CsArchivingConfiguration cmdlet. You can run this cmdlet from either the Lync Server 2013 Management Shell or from a remote session of Windows PowerShell. For details about using remote Windows PowerShell to connect to Lync Server, see the Lync Server Windows PowerShell blog article "Quick Start: Managing Microsoft Lync Server 2010 Using Remote PowerShell" at https://go.microsoft.com/fwlink/p/?linkId=255876.

To enable critical mode

  • To enable critical mode, set the value of the BlockOnArchiveFailure property to True ($True). For example:

    Set-CsArchivingConfiguration -Identity "site:Redmond" -BlockOnArchiveFailure $True
    

To disable critical mode

  • To disable critical mode, set the value of the BlockOnArchiveFailure property to False ($False). For example:

    Set-CsArchivingConfiguration -Identity "site:Redmond" -BlockOnArchiveFailure $False
    

For more information, see the Help topic for the Set-CsArchivingConfiguration cmdlet.