Tchater maintenant avec le support
Tchattez avec un ingénieur du support

MessageStats 7.7.2 - Report Pack for Lync & Skype for Business User Guide

About This Guide Installing the Report Pack Configuring the Report Pack Managing your Database Using the Lync and Skype for Business Reports Appendix A: Configuring RPC through a Firewall

Identifying Federated Domains

Typically, you want users in your federations to appear in the reports as internal or federated users. Federations are stored on the Skype for Business or Lync Edge server which is in the DMZ. If you want the federated domains to be automatically discovered, you must open certain ports in the firewall to allow the information be retrieved from the Edge server. For more information, see Appendix A: Configuring RPC through a Firewall .

If your security policies do not allow you to provide access to the Edge server, you can manually add your federated domains to the report pack so that users in these domains are correctly reported.

If federated domains cannot be auto-discovered, and you have not manually added the federated domains, federated users are reported as public or external users.

To manually add federated domains
1
Expand the console treeview and select the Lync & Skype for Business Server node.
2
Right-click and select Federation Properties.
3
Click Add.
4
Enter the fully qualified domain name (FQDN) for the federated domain that you want to identify.
5
Click OK.
6
Repeat Step 3 to Step 5 until you have identified all your federations.
7
Click OK.

Excluding Specific Users from Reports

In some cases, you might want to exclude certain users from the Lync or Skype for Business Server reports. For example, you might want to exclude synthetic transactions from your reports. In Lync Server, synthetic transactions are scripts or commands that are used to simulate real users accessing a system.

Using the Exclude Users property page, you can select specific users, all users in a department, or all users in an office to exclude from reports. You can exclude users at the forest level.

Excluded users still appear in the Configuration | Lync & Skype for Business Enabled Users report. The excluded status of the user is indicated by the Excluded flag in the report.

To exclude users from reports
1
Expand the console treeview and select the Lync & Skype for Business Server node.
2
Right-click and select Exclude Users.
3
Enter the criteria for the users you want to exclude:
•
Enter all or part of the user name and click Find Users.
•
Enter all or part of the department name and click Find Departments.
•
Enter all or part of the office name and click Find Office.
 
* 
TIP: You can enter an asterisk (*) as a wild card to find all names that contain, start, or end with a specific set of characters.

The following examples show how you can use wild cards to find results:

•
Enter Sales* to find all departments that start with the word Sales.
•
Enter *HR to find all departments that end with HR.
•
Enter Mi*ce to find all user names that start with Mi and end with ce.
•
Enter *EURO* all office names that contain EURO.
The names that match your query are displayed in the Search Results column on the left.
4
In the left column, select the name of the user, department, or office that you want to exclude.
Use SHIFT-click to select a range of names or CTRL-click to select several individual names.
5
Click the arrow to add the selected items to the Excluded List on the right.
- OR -
Drag the selected items to the Excluded List
6
When all the users you want to exclude are in the Excluded List, click Apply and OK.
Excluded users remain excluded even if their display name, department, or office changes. However, if the user’s primary URI (Uniform Resource Identifier) is changed, you must add the user again to the excluded list.

For a list of the reports that do not show excluded users, see the chapter titled Using OCS/Lync Reports in the Report Pack for OCS/Lync Server User Guide.

To remove users from the exclusion list
1
Select the user, department, or office in the Excluded List on the right.
2
Press the Del key.
- OR -
Right-click and select Delete on the shortcut menu.

Specifying Chargeback Costs for Sessions and Conferences

You can specify the costs at which various types of peer-to-peer sessions (such as audio, video, desktop sharing, and instant messaging) or conferences are charged. The calculated values appear on reports so you can determine the chargeback amounts for users or departments.

You specify the chargeback costs for sessions and conferences for a Skype for Business or Lync pool, unlike the Voice Enterprise chargeback costs which are applied at the forest level.

Use the Chargeback Rates property page to enter the rate per minute, or the rate by volume (MB) or number of items, for the chargeback costs that should appear in reports.

To specify chargeback costs for sessions and conferences
1
Expand the treeview and select the Skype for Business or Lync pool for which you want to specify cost amounts.
2
Right-click and select Properties.
3
Click the Chargeback Rates tab.
4
If necessary, select a different currency symbol for the chargeback rates. The default value is $.
5
Enter the applicable values that are charged:
•
For peer-to-peer outgoing sessions, you can enter the cost amounts per minute for each session type for internal and federated users.
•
For peer-to-peer sessions such as instant messaging and file transfers, you can specify whether you want to calculate chargeback amounts by volume or by the number of messages or transfers.
•
For audio/video conferences, you can enter the cost rate per minute.
6
Click Apply.

Creating an Lync or Skype for Business Server Gathering Task

Tasks specify which information is gathered from the Skype for Business or Lync database instances and how often the gathering is repeated. To gather the data required for the reports, you must configure an report pack default gathering task.

You can create an Skype for Business or Lync gathering task only at the individual pool level. You cannot create a task that gathers Skype for Business or Lync data at the Exchange organization level.

Typically you schedule the report pack Default Lync & Skype for Business Server Gathering task to run every 24 hours. It is recommended that you run the task at off-peak times. The gathering queries the Skype for Business or Lync SQL database, and should be scheduled to run when your Lync or Skype for Business Server is not busy.

For the initial Default Lync & Skype for Business Server Gathering task, it is recommended you schedule the task to run on a weekend if your Lync or Skype for Business databases are large.

To create a report pack gathering task
1
Expand the Lync & Skype for Business Server node, select a server pool in the treeview, and select Create Task.
2
Enter a unique name for the task and select the template for the type of information that you want to collect:
•
Default Lync & Skype for Business Server Gathering
•
Lync & Skype for Business Conferencing Statistics
•
Lync & Skype for Business Enterprise Voice
•
Lync & Skype for Business Instant Messaging and File Transfer
•
Lync & Skype for Business Server Uptime Performance
•
Lync & Skype for Business Servers and Users
•
Lync & Skype for Business Peer-to-Peer Audio Calls, Video Calls, and Desktop Sharing Sessions
The Default Lync & Skype for Business Server Gathering task contains the Servers and Users, Enterprise Voice, Conferencing Statistics, Instant Messaging and File Transfer, Server Uptime Performance, Peer-to-Peer Audio Calls, Video Calls, and Desktop Sharing Sessions tasks.
3
Click Next.
4
Ensure that the task execution server that appears is the server on which the report pack task processor is installed and click Next.
5
Specify a schedule for the gathering task and click Next.
MessageStats provides two types of schedules: schedules that run once (at a specific time such as December 31 or Now), and schedules that repeat for a defined period (such as daily, weekly, or monthly).
6
Verify the logging level for the task logs and click Next.
Normally you leave logging set to the default logging level. If you contact Support for assistance, Support might request that you change your task logging level to troubleshoot technical issues.
7
Specify the account under which the gathering task is to run and click Next.
You can accept the defaults for task execution server, task schedule, task logging, and task account, or clear the Use Default Credentials to enter new values.
8
Click Finish to save the gathering task.
To change the properties of an existing task
1
Browse the tasks in the Tasks Summary View.
2
Right-click the task you want to configure and select Properties.
3
Step through the wizard to change the settings.

For information about which gathering tasks have a dependency on another gathering task, see Gathering Task Dependencies .

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation