Unified Communications Analytics 8.8.3

Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

Navegación de contenido

Prerequisites for your installation

Overview Supported environments

Supported browsers

Architecture

Information stored by the Storage Engine

Deployment options Hardware minimum requirements

Software prerequisites

Prerequisites for the UC Analytics services Web site prerequisites

Firewall configuration: ports for data collection Planning for deployment Determining where to install services What files need to communicate through software firewalls? What files should be excluded from anti-virus software? About UC Analytics configuration

Installing UC Analytics

Types of installations

Upgrading from 8.1 or later

Considerations before you install

About a pilot installation About a production installation

Accounts used during installation Performing a pilot installation Performing a production installation

Installing a second Storage Engine after installation Installing additional collector roles

Activating the UC Analytics license Setting up the web site for HTTPS

Configuring UC Analytics

About administration settings How do I set a user to be a product administrator? Configuration process overview Modifying the initial target environment Adding multiple Active Directory forests Configuring UC Analytics for resource forests Adding a target environment for native Office 365 Setting the time period for retaining data Setting the start date for data collection Adding and configuring data sources

Entering multiple values in a field Recommendations for collecting from Office 365

How often do collections update the data? Viewing the collection job status Forcing a data source collection to run now Renaming a data source

When would I use the Delete Data option?

Managing data sources through batch operations Managing credentials used by multiple data sources Identifying your internal domains Classifying domains for message traffic Setting where data calculation for insights is performed Excluding <none> values from insights Excluding today's data in insights Setting time zone usage for all users Granting full access to Admin Settings Granting users access to data Setting working hours for rooms Accessing the UC Analytics web site

Adding data sources for Active Directory or Azure Active Directory

Adding data sources for different target environments Permissions needed to collect Active Directory data Adding data sources for Active Directory / Office 365 (hybrid)

Creating an Domain Controller data source Creating a data source for Office 365 user subscription configuration

Adding data sources for native Office 365

Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online

Permissions needed to collect Exchange on-premises or hybrid data

Permissions needed to collect from native Exchange Online Creating an Exchange Configuration data source

Best practices for gathering performance Using dynamic distribution groups to select target mailboxes What types of mailboxes are excluded? Can I enter the Domain Users group as the target for the data collection? Troubleshooting the Exchange configuration collection

Creating an Exchange Tracking Logs data source Creating an Exchange Mailbox Contents data source

Tips for better performance for mailbox contents collection

Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections? Creating an Exchange IIS Logs data source Creating an Exchange Mailbox Content Summary data source Creating an Exchange Calendar data source Creating an Exchange Public Folders data source Adding Exchange Online hybrid data sources for hybrid Office 365

About AD synchronization methods for hybrid Exchange Online About PowerShell collection method options Creating an Exchange Online Hybrid User Configuration data source Creating an Exchange Online Hybrid Mailbox Configuration data source

Adding Exchange Online data sources for native Office 365

Creating an Exchange Online Native User Configuration data source Creating an Exchange Online Native Mailbox Configuration data source Creating an Exchange Online Mailbox Contents data source Creating an Exchange Online Mailbox Content Summary data source Creating an Exchange Online Calendar data source Creating an Exchange Online Public Folders data source

Setting chargeback costs for Exchange Setting thresholds for Exchange metrics Omitting words when filtering by subject or body

Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync

Permissions needed to collect Skype for Business/Lync data

Permissions needed for Skype for Business/Lync configuration data source Permissions needed for Skype for Business/Lync CDR data source Permissions needed for Skype for Business/Lync QoE data source

Creating a data source for Skype for Business/Lync configuration Creating a data source for Skype for Business/Lync CDR Database Creating a data source for Skype for Business/Lync QoE Database Setting call classifications for Skype for Business/Lync Setting chargeback costs for Skype for Business/Lync Setting thresholds for Skype for Business/Lync metrics

Adding new threshold classifications

Adding data sources, chargeback, and thresholds for Cisco

Permissions needed to collect Cisco data

Permissions needed for the Cisco configuration data source Permissions needed for the Cisco CDR logs data source

Creating a data source for Cisco configuration Creating a data source for Cisco CDR logs Setting call classifications for Cisco Setting chargeback costs for Cisco Setting thresholds for Cisco metrics

Managing which insights can seen by users

Enabling a Company Home Page Setting insight visibility settings

Configuring and managing subscriptions

What are insight subscriptions? Configuring settings for subscriptions Managing user subscriptions

Making changes to your deployment

Options available in the Deployment Manager Changing the service account Deploying a second Storage Engine Deploying additional collectors Using the Tools menu for support activities

Appendix A:Configuring Exchange and Office 365

Overview Setting impersonation for Exchange 2013/2016/2019 Configuring impersonation for Office 365 Registering UC Analytics with the Microsoft Azure portal Installing the Exchange Online PowerShell module Setting up a multi-forest environment with a one-way trust

Appendix B:Configuring the Skype for Business or Lync Server

Configuring Lync Server 2010

1. Adding the SQL store for monitoring 2. Installing the Monitoring role 3. Enabling Call Detail Recording (CDR) 4. Starting the monitoring services

Configuring Lync Server 2013 or Skype for Business 2015/2019

1. Associating the store with the Front-End pool 2. Updating the Lync or Skype for Business Server 3. Enabling and configuring monitoring 4. Starting the monitoring services

Appendix C:Configuring IIS Log Files to capture ActiveSync or OWA events

Configuring IIS Logging on the Exchange CAS and Mailbox servers

Configuring IIS if Exchange is hosted on Windows 2003 Server Configuring IIS Logging if Exchange is hosted on Windows Server 2008 or later

What ActiveSync events are collected and displayed in the insights?

Appendix D:PowerShell cmdlets used by data sources

Exchange Configuration data source Exchange and Exchange Online Public Folders data sources Skype for Business/Lync Configuration data source Exchange Online Hybrid and Native User Configuration data sources Exchange Online Hybrid and Native Mailbox Configuration data sources Exchange Online Mailbox Contents data source Office 365 User Subscription Configuration data source

Appendix E:Backup and recovery options

Backing up and restoring your data using scripts

Supported scenarios About the backup and restore batch files

Prerequisites

Step 1: Edit the backup.bat file parameters for your installation Step 2: Run the backup batch file Step 3: Edit the restore batch file Step 4a: Restore the storage data in an existing installation Step 4b: Restore the storage data to a new installation

Scheduling the backup batch file to run automatically Performing a manual backup of the storage folder before upgrade Moving your storage location Recommendations for disaster recovery

Appendix F:Custom configurations

Setting LDAP connections to use LDAPS (LDAP over SSL) Modifying the Data Query Availability job run Modifying collection days for data collections from log files Changing initial collection days for Exchange (Online) Mailbox Contents data sources Changing default values for formatted .csv or .tsv file exports Excluding insight date range and filters from subscription emails Changing the PowerShell wait time after transient errors Changing the PowerShell reconnect interval for Exchange Online Mailbox Configuration jobs Modifying timeout values for EWS collection jobs Setting a custom title page for exported or subscription insights Changing the interval time before job status is purged Configuring remote PowerShell to use the required proxy settings Overriding PowerShell credential winnowing Registry settings that affect service shutdown and startup

Appendix G: Questions and answers about UC Analytics

Introduction

How often do the data collections actually gather data and when do they run? When I view insights that show internal vs. external traffic, there is no data for internal traffic. Why? Why are my OWA insights not showing any data? Why did an insight show no data for a 30-day range though I initially set the data source to collect 30 days back? If I collect both Exchange Tracking Logs andExchange Mailbox Contents, are there duplicate items? If I collect message data only from the Exchange tracking logs, is the message Send Date and delivery time available? What are the differences between the ExchangeMailbox Contents and Exchange Tracking Logs data sources? Why do I get an error when collecting Exchangeconfiguration from multiple Exchange versions? Why do I have to specify domain name when doing a multi-forest collection? What insights are affected by the "Calculate insight data on server side" option?

Firewall configuration: ports for data collection

When you configure your firewall, UC Analytics requires access to the following TCP and UDP ports for Exchange 2010 and later:

Table 10. Ports required for data collection.

•

•

Microsoft file sharing SMB (Server Message Block)

TCP/UDP 445

•

Domain Controllers

•

Exchange Servers

Direct-hosted SMB traffic and user authentication

TCP/UDP 88

•

Domain Controllers

•

Exchange Servers

Kerberos authentication

TCP/389 (DC) or TCP/3268 (GC)

•

Domain Controllers

•

Exchange Servers

LDAP (Lightweight Directory Access Protocol) connection

TCP/636 (DC) or TCP/3269 (GC)

•

Domain Controllers

•

Exchange Servers

LDAP (Lightweight Directory Access Protocol) connection over SSL

TCP/UDP 53

•

Domain Controllers (DNS role)

DNS (Domain Name System)

TCP/UDP 137

•

Domain Controllers

•

Exchange Servers

WINS (Windows Internet Name Service)

TCP Port 80

•

Exchange Servers

Remote PowerShell for Exchange (also required access to the IIS PowerShell virtual directory on your Exchange servers)

TCP Port 443

•

Skype for Business / Lync

•

Office 365

Remote PowerShell for Skype for Business / Lync (also required access to the IIS OcsPowerShell virtual directory on your Skype for Business / Lync Servers)

TCP 5985 (HTTP) and 5986 (HTTPS)

•

Exchange Servers

•

Skype for Business / Lync Servers

•

Office 365

WinRM (Windows Remote Management) service

If you have implemented an intelligent firewall, you can configure the firewall to allow the specific types of network access (SMB, LDAP, and so on) that UC Analytics requires instead of access to specific ports.

Ports used for service-to-service communication in a distributed installation

In a distributed installation where you have a multiple UC Analytics servers deployed and there are firewalls between the UC Analytics servers, certain ports are required for service-to-service communication.

•

For the Storage Engine and the Query Engine, open the following TCP ports: 1223, 7100, 7101, 7299, 9042, 9260, and 10099.

•

For the Data Engine, open the following TCP ports: 1336 and 1337.

Planning for deployment

When you are planning your deployment, you must determine the number of servers across which you are deploying UC Analytics. You also must determine how much storage is required for the number of mailboxes from which you are collecting data.

For additional information see the UC Analytics Deployment Sizing.xlsx spreadsheet which can be found under Documentation in the autorun.exe.

Determining where to install services

It is not recommended that you install any UC Analytics services on the same server where core MessageStats or UC Diagnostics is installed.

If you are installing the UC Analytics services on several computers, consider the following information:

•

Data collection performance is better if the Data Engine service is located near to the Exchange server and to the Skype/Lync CDR database server.

•

Ideally, you would install UC Analytics on a computer that is in the same forest as the Exchange servers from which you are collecting data. However, you can install in a forest that is separate from the forest that contains your Exchange servers. For information about configuring multi-forest environments, see Adding multiple Active Directory forests .

•

You can install UC Analytics on a virtual machine (VM) but, to obtain optimal performance for a production installation, it is recommended that you install on a physical machine.

•

The Storage Engine service nodes automatically synchronize with each other. If you install two Storage Engine services, it is better to have them collocated when possible for performance reasons.

•

It is best to have all the UC Analytics services located as close as possible. At a minimum they should all be within the same site.

•

For security considerations, all services are recommended to be installed within the intranet. For information about configuring the web site for https, see Setting up the web site for HTTPS .

•

For small to mid-size installations. UC Analytics can be installed on a single computer.

•

For large installations, use one of the recommended deployments provided in the installer. For additional information see the UC Analytics Deployment Sizing.xlsx spreadsheet which can be found under Documentation in the autorun.exe.

What files need to communicate through software firewalls?

Software firewalls, such as Windows Firewall, can prevent the code in the UC Analytics processes from performing necessary network input and output. Such firewalls must be configured to allow the UC Analytics Data Engine to communicate with the Query Engine and to communicate with your Exchange, Active Directory, Cisco, and Skype for Business resources.

The files that can be affected by a software firewall are as follows:

•

C:\Program Files\Quest\UC Analytics\Storage Engine\bin\prunsrv.exe

•

C:\Program Files\Quest\UC Analytics\Query Engine\bin\prunsrv.exe

•

C:\Program Files\Quest\UC Analytics\Data Engine\UC.Analytics.Insights.DataEngine.Service.exe

•

C:\Program Files\Quest\UC Analytics\Data Engine\UC.Analytics.Insights.DataEngine.BulkDataExport.exe

•

C:\Program Files\Quest\UC Analytics\DeploymentManager.exe

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

Seleccione su producto:

Con el fin de ofrecerle un mejor servicio, complete el campo Motivo del chat:

Soluciones recomendadas para su problema

Unified Communications Analytics 8.8.3 - Deployment Guide

Firewall configuration: ports for data collection

Planning for deployment

Determining where to install services

What files need to communicate through software firewalls?