Chatta subito con l'assistenza
Chat con il supporto

Unified Communications Diagnostics 8.6.3 - Deployment Guide

Installing and upgrading Unified Communications Diagnostics Technical Information for UC Diagnostics for Exchange Technical Information for Office 365 Technical Information for UC Diagnostics for BlackBerry Technical Information for UC Diagnostics for OCS Technical Information for UC Diagnostics for Lync/Skype for Business Troubleshooting

UC Diagnostics software prerequisites

The following section provides the software prerequisites for UC Diagnostics components.

Operating System

One of the following:

Database

One of the following:

Diagnostic Services (Health Tests) for all Environments

MDAC 2.8 comes with your operating system. If MDAC is removed, UC Diagnostics cannot run.

The following prerequisites are needed for Exchange 2007:

The following prerequisites are needed for Exchange 2010 or 2013:

The following prerequisites are needed for Exchange 2016:

The following prerequisites are needed for BlackBerry:

The following prerequisites are needed for Lync/Skype for Business:

The following prerequisites are needed for Office 365:

For more information, see Diagnostic Services (Health Tests) for all Environments.

Diagnostic Console for all Environments

Microsoft .NET Framework 4.5.1

EMC 2007 SP 1 or later

Microsoft PowerShell 2.0 or later

Microsoft PowerShell 2.0 or later

Microsoft PowerShell 2.0 or later

Microsoft PowerShell 2.0 or later

Microsoft PowerShell 2.0 or later

Web Reports

For installing Web Reports, you need one of the following:

For viewing Web Reports, you need:

Requirements for specific operating systems:

Rights and Privileges

Local Windows Administrator privileges are required on the computer on which UC Diagnostics is installed.

SQL Server installation prerequisites

If you are installing the SQL database on the same computer as other UC Diagnostics components or if you are installing the SQL database remotely, the following permissions are required:

Installer user

dbcreator and db_owner roles

Using the installer

If you install the Spotlight Management Framework database using the Installation wizard, the installer user account must have a SQL Server login with the dbcreator server role.

During installation, the installer automatically grants the db_owner database role to the installer user for the Spotlight Management Framework database.

Manually installing the database

If you manually install the Spotlight Management Framework database using the scripts, you must have a SQL Server login for the installer user account. You must grant the db_owner database role to the account for Spotlight Management Framework database.

For more information to manually install Spotlight Management Framework database, see Manually installing the Management Console database .

Service account

Server roles/database roles required for the UC Diagnostics service account at installation time are as follows:

Using the installer

If you install Spotlight Management Framework database using Installation wizard, you must have a SQL Server login for the UC Diagnostics service account. During installation, the Installer automatically grants the db_owner database role to the service account for the Spotlight Management Framework database.

Manually installing the database

If you manually install the Spotlight Management Framework database using the scripts, you must have a SQL Server login for the service account and grant the db_owner database role to the account for the Spotlight Management Framework database.

For more information to manually install Spotlight Management Framework database, see Manually installing the Management Console database .

SQL database operating prerequisites

After the UC Diagnostics SQL database is installed, the following operating permissions are required:

Management Console user

db_Owner for Spotlight Management Framework database

Service Account

db_Owner for Spotlight Management Framework database

Diagnostic Console operating recommendations

The Diagnostic Console is not intended to be operated continuously for long periods of time. The console frequently retrieves a large amount of data from a server. This places excessive stress on a server, affecting its performance. It also consumes critical system resources, which can affect the stability of UC Diagnostics over a long time period.

Consider the following recommendations:

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione