Mark a Microsoft SIP Processing Language (MSPL) application as critical or not critical in Lync Server 2013
Topic Last Modified: 2012-11-01
Microsoft SIP Processing Language (MSPL) server applications are script-only applications that use the MSPL scripting language instead of the Microsoft Lync 2010 API. Some MSPL server applications are specified as critical. If a script is critical, the script must start during system startup in order for Lync Server 2013 to start. If the script fails while Lync Server is running, the server does not shut down, but it stops sending traffic to the script, and it writes errors in the event log.
You can use Lync Server Control Panel to mark Microsoft SIP Processing Language (MSPL) server applications as critical or unmark them.
Not all scripts support this option. For example, the DefaultRouting script is marked as critical, and this option cannot be changed for DefaultRouting.
From a user account that is a member of the RTCUniversalServerAdmins group (or has equivalent user rights), or assigned to the CsServerAdministrator or CsAdministrator role, log on to any computer that is in the network in which you deployed Lync Server 2013.
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.
In the left navigation bar, click Topology and then click Server Application.
On the Server Application page, click a column heading to sort the applications, if needed, and then click the server application that you want to modify.
Click Mark as critical or Unselect as critical (that is, if the script supports this option).