2.9 Discovering Lync Resources

Use the Discovery_Lync Knowledge Script to discover all known resources on a Lync server. The script discovers Lync Enterprise and Standard editions, Mediation servers, and Edge servers. When AppManager discovers a Lync component, that component is displayed under the relevant server in the TreeView on the left side of the AppManager window.

Before running discovery, ensure you have set up the proper user permissions on the various Lync servers and SQL servers you will be using. For more information, see Setting Up User Permissions for Lync.

The default interval for this script is weekly; the default is Sundays at 3 A.M.

If you delete or add a resource object, or if you make any other kind of change that might affect the monitoring of your resources, run the Discovery_Lync Knowledge Script again to update your list of resource objects. In addition, if you are running this module on AppManager 8 or later, you can use the delta discovery feature in Control Center to run discovery on a schedule to more quickly detect changes to your environment.

Set the Values tab parameters as needed:

Description	How To Set It
General Settings
Job Failure Notification
Event severity when job fails	Set the event severity level, from 1 to 40, to indicate the importance of an event that is raised when the discovery job fails. The default is 5.
Raise event if discovery succeeds?	Select Yes to raise an event when the discovery process is successful. The default is unchecked.
Event severity when discovery succeeds	Set the event severity level, from 1 to 40, to indicate the importance of an event that is raised when discovery succeeds. The default is 25.
Raise event if discovery succeeds with warnings?	Select Yes to raise an event when the discovery process succeeds but generates some warnings. The default is Yes.
Event severity when discovery succeeds with warnings	Set the event severity level, from 1 to 40, to indicate the importance of an event that is raised when discovery succeeds with warnings. The default is 15.
Raise event if discovery fails?	Select Yes to raise an event when the discovery process fails. The default is Yes.
Event severity when discovery fails	If you set this Knowledge Script to raise an event when the job fails, set the event severity level for a failed discovery. The default is 10.
Set up supplemental database?	Select Yes to set up Lync supplemental database to store call quality detail records (audio, video, and application sharing calls) on a server where SQL database exists. You need to configure the SQL server credentials in the Security Manager to create a supplemental database. For more information, see Configuring Security Manager Settings for the Supplemental Database.
Raise event if database setup succeeds?	Select Yes to raise an event if creation of the Lync supplemental database is successful. The default is unselected.
Event severity when database setup succeeds	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the Lync supplemental database is created successfully. The default is 25.
Raise event if database setup fails?	Select Yes to raise an event if creation of the Lync supplemental database fails. The default is unselected.
Event severity when database setup fails	Set the event severity level, from 1 to 40, to indicate the importance of an event in which the Lync supplemental database is not created. The default is 15. It is possible that the supplemental database was not created because of one of the following reasons: The Discovery job was run with the Set up supplemental database parameter selected on a computer other than a front-end pool server The Discovery job was run on a computer with the Set up supplemental database parameter selected on which SQL Server is not installed The Discovery job was run on a computer with the Set up supplemental database parameter selected where Lync supplemental database was already created
Start pruning job on supplemental database?	Select Yes to create a SQL job that deletes data from the supplemental database. The SQL job runs every night. The default is Yes. Data is deleted from the supplemental database based on the value you specify in the Number of days to keep call detail records parameter.
Number of days to keep call detail records	Specify the number of days’ worth of call detail records to keep in the Lync supplemental database. Data older than what you specify is discarded. The default is 7 days. You can specify a maximum of 30 days.
SQL Server Information
SQL Server \instance name	Specify the SQL Server name where you want to create the new Lync Server supplemental database along with the instance if any. If you specify both the SQL Server instance name for this parameter and the SQL Server database user name in the following parameter, these values must match the values you specified in Configuring Security Manager Settings for the Supplemental Database. If this field is left blank, then the script uses the default SQL server on the agent computer to create the supplemental database in the Lync agent where you run the discovery or the Lync_SetupSupplementalDB script. If SQL database is not present on Lync agent, then the script fails to create the database. If you do not specify the instance name, the script creates the database in the default instance.
SQL database user name	Specify the user name for the SQL Server where you want to create the new Lync Server supplemental database. Leave this parameter blank to use Windows authentication instead of SQL authentication.