Using Best Practices Analyzer to scan your Lync Server 2013 deployment for potential issues

 

Topic Last Modified: 2012-10-21

To run a Best Practices Analyzer scan, you must specify the following:

  • Credentials   To run a scan, you must log on to a computer on which Best Practices Analyzer is installed by using an account that is a member of the local Administrators group. Additionally, you need to log on by using a user account that has the user rights and permissions required to run the appropriate scans, or you must specify credentials that have the appropriate user rights and permissions when you run Best Practices Analyzer. For details, see Group memberships and user rights requirements for Best Practices Analyzer in Lync Server 2013.

  • Scope of scan   To specify the scope of the scan, select the categories and servers that you want to scan. You can select all categories, one or more categories, or one or more servers within a specific category in your Lync Server environment.

  • Type of scan   Currently, the Health Check scan is the only type of scan available (selected by default). The Health Check scan generates a report that includes errors, warnings, and other information for all servers specified in the scope.

  • Network speed   Network speed options include Fast LAN (100 Mbps or more), LAN (10 Mbps), Fast WAN (1.5 Mbps), or WAN (64 kbps). The estimated time to complete the scan is based on this setting. This setting is also used to set the time-out period. During the scan, the Best Practices Analyzer waits for a response from a server for a specified time. If it does not receive a response within the specified time-out period, it moves to the next server in the scan. On slower networks, this specified time-out period is longer to account for longer network latencies. We recommend that you select the slowest link in your topology for this parameter so that the tool does not time out too quickly.

To scan your Lync Server 2013 deployment

  1. Log on to a computer on which Best Practices Analyzer is installed by using an account that is a member of the local Administrators group, and has other required user rights and permissions.

  2. Click Start, point to All Programs, click Microsoft Lync Server 2013, and then click Best Practices Analyzer.

  3. On the Welcome screen, click Select options for a new scan.

  4. On the Connect to Active Directory page, verify the name specified in Active Directory Server, and then do one of the following:

    • To run a scan using the credentials that you used to log on to the computer, click Connect to the Active Directory server.

    • To specify different credentials that you want to use for Active Directory Domain Services, Edge Server, or Exchange Server, click Show advanced logon options, select each check box for which separate credentials are required, specify the credentials for each selected check box, and then click Connect to the Active Directory server.

    Note

    Before beginning the scan, Best Practices Analyzer performs a network and permissions check to ensure that the specified account credentials are valid and that Best Practices Analyzer can connect to Active Directory Domain Services. If the tool is running on a workgroup server, the tool also verifies that it can connect to Edge Servers in the perimeter network (that is, if they are included in the scan).

  5. On the Start a new Best Practices scan page, select the options that you want to include in the scan, specify the network speed, and then click Start scanning.

  6. On the Scanning Completed page, click View a report of this Best Practices scan.

  7. On the View Best Practices Report page, do one of the following:

    • To view reports in a list organized by server component, click List Reports, and then click either the All Issues tab or the Informational Items tab.

    • To view reports as a hierarchical list organized by types of results, click Tree Reports, and then click either the Detailed View tab or the Summary View tab.

    • To view other reports, click Other Reports.