Converse agora com nosso suporte
Chat com o suporte

Unified Communications Diagnostics 8.6.2 - 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

Deployment recommendations for the Management Console

Consider the following recommendations before you install the Management Console, depending on the number of Exchange or Skype for Business/Lync servers you have.

 
Table 5. Deployment recommendations based on number of servers monitored.
If You are Monitoring
RecommendationS

1 - 50 Exchange servers
•
All components can be installed on a single dedicated computer
•
Console can be installed with the other components or on your desktop computer
•
Any of supported databases should be sufficient

50 - 100 Exchange servers
•
Diagnostic Services should be installed on a dedicated computer
•
Database should be installed on a separate computer from the Diagnostic Services
•
SQL Express Edition is not recommended
•
If Web Reports is frequently used or test monitoring intervals are less than 30 minutes, Web Reports should be installed separately from the Diagnostic Services
•
Console can be installed with the Diagnostic Services or on your desktop computer

100 or more Exchange servers
•
Diagnostic Services should be installed on a dedicated computer
•
Database should be installed on a separate computer from the Diagnostic Services
•
SQL Express Edition is not recommended
•
If Web Reports is moderately or frequently used or test monitoring intervals are less than 30 minutes, Web Reports should be installed separately from the Diagnostic Services
•
Console should be installed separately from the Diagnostic Services

1 - 50 Skype/Lync/OCS servers
•
All components can be installed on a single dedicated computer
•
Console can be installed with the other components or on your desktop computer

50 or more Skype/Lync/OCS servers
•
Diagnostic Services should be installed on a dedicated computer
•
Database should be installed on a separate computer from the Diagnostic Services
•
If Web Reports is frequently used or test monitoring intervals are less than 30 minutes, Web Reports should be installed separately from the Diagnostic Services
•
Console can be installed with the Diagnostic Services or on your desktop computer

If you are monitoring more than 100 servers or operating in a mixed environment, you might need a more distributed installation or additional UC Diagnostics installations. Please contact Support for advice.

Factors to consider during deployment

When deploying UC Diagnostics, consider the following factors:

•
Multiple diagnostic consoles can be connected to the same Diagnostic Services simultaneously, and have full read/write access to all UC Diagnostics functionality.
•
The Diagnostic Services, database, and the Web Report components must be deployed 1-for-1. The database can only support one instance of Diagnostic Services.
•
The Diagnostic Services and Management Console components can be deployed 1-to-many (or many-to-many). So one Diagnostic Services computer can support multiple Management Consoles computers (connected at the same time), and one Management Console computer could connect to multiple Diagnostic Services computers (using separate instances of the MMC snap-in).
•
The Diagnostic Console is completely independent from the Management Console, and can be deployed however you want.
 

if you access the same Diagnostic Services server from multiple consoles, consider these additional factors:

•
Different users can manage or edit the same tests at the same time. If different users edit the same test, the user who saves the changes last has the settings preserved.
•
Information such as discovery, tests, credentials, test settings, custom groups, and global settings are shared amongst the Management Consoles
•
Global filters, Topology layout, and Group By settings are not shared amongst the Management Consoles

Different Management Consoles can be connected to different organizations. For example, one Management Console can be connected to an Exchange organization, while another is connected to a Skype for Business environment.

Generally, due to the few BlackBerry servers most users have, your BlackBerry configuration is unlikely to put a significant load on your deployment. Use the performance guidelines for the other environments to determine how best to deploy your Management Console.

About cluster support

UC Diagnostics supports running health tests on servers in a clustered environment. However, UC Diagnostics only monitors virtual nodes; it does not detect failover. Windows clusters are not supported as a separate plug-in.

While you can run all health tests on clusters, the Exchange Replication Health test explicitly reports on clusters in Exchange 2007 and later organizations.

 
Table 6. Types of clusters that are supported for different servers.
Server type
Type of cluster supported

Exchange 2007
•
Local Continuous Replication (LCR)
•
Cluster Continuous Replication (CCR)
•
Standby Continuous Replication (SCR)
•
Single Copy Cluster (SCC)

Exchange 2010/2013/2016/2019
•
Database Availability Group (DAG)

BlackBerry
•
High Availability (HA) architecture

OCS/Lync/Skype for Business
•
Network Load Balancing (NLB)
•
Component Load Balancing (CLB)

Installing components on multiple computers

You can install the Management Console components on separate computers if you have a large organization. For information on installing the components on a single computer, see the Unified Communications Diagnostics Evaluator Guide.

Limitations and recommendations

You cannot install UC Diagnostics on a domain controller.

If you are using anti-virus software, you must exclude the UC Diagnostics directories from the anti-virus software.

If you are installing for the first time or upgrading each component on its own computer, install the components in the following order:

1
Database
2
Diagnostic Services
3
Web Reports
4
Console

If you are upgrading, you must perform the upgrade on each computer in the specified order where you have each component installed.

If your Diagnostic Services, Web Reports, or database components are deployed across multiple computers and you must upgrade them individually, manually stop the IIS services, the Spotlight Distributed Collector services, and the Spotlight Diagnostic Test Engine. If you installed the Diagnostic Services and Database on a single computer, or if you installed your database on a remote computer, you do not have to stop these services.

You can install the Diagnostic Console at any time.

To install components on multiple computers
1
Log on to your computer using an account that has local administrative privileges.
2
Download UC Diagnostics, and click Autorun.exe in the root directory.
3
Click the Install tab.
4
Click the Unified Communications Diagnostics link.
5
If you are installing UC Diagnostics for the first time, click Next in the Welcome to Unified Communications Diagnostics Setup Wizard dialog box, read and accept the license agreement, then click Next.
If you are upgrading from a previous version of UC Diagnostics, you do not need to uninstall the previous versions. When you install UC Diagnostics, click Next in the Welcome to the Unified Communications Diagnostics Upgrade Wizard dialog box, read and accept the license agreement, then click Next.
6
Indicate the features you want to install on the local hard drive, and click Next.
The following table identifies the different configuration pages that appear, depending on the features that you have selected for the local computer:
 
Table 7. Configuration pages for each component.
Component
Configuration Pages Displayed

Console
•
None

Diagnostic Services
•
SQL Server to allow you to specify the location of your SQL Server database.
•
Server Account Setup to allow you to enter the credentials under which discovery and test all run by default. This must be a local administrator.

The database can be installed before or at the same time you install the Diagnostic Services.

Database
•
SQL Server to allow you to specify the server where the database instance should be installed.

If you are installing the database on a remote computer, ensure remote connections are enabled on the SQL Server, and you have sufficient rights to create/modify the database.

If you are using SQL Server Always On, you must specify an availability group listener that connects to the primary replica.

NOTE: If you are upgrading from a previous version to version 8.6.2, click Yes to use the existing database. If you are installing UC Diagnostics 8.6.2 for the first time, you do not see this dialog box. For more information on upgrading your database, For more information, see Manually upgrading the Management Console database.

Web Reports
•
SQL Server to allow you to specify the location of your SQL Server database.
•
Select Web Site to allow you to select the default Web Site or another Web Site where Web Reports will be installed.
•
Web Reports Optional Settings to allow you to set criteria for subscriptions, such as SMTP server and sender email address. Subscriptions allow you to schedule when you want specific reports to run.

The database can be installed before or at the same time you install Web Reports.

NOTE: If you are installing Web Reports on a remote computer, you must use SQL Authentication.
7
Click Install to begin the installation.

Manually installing the Management Console database

You can manually install your database using the Install Scripts from the Install tab of the Autorun dialog box.

To manually install your database
1
Open Microsoft SQL Server Management Studio (or similar application to open SQL scripts).
2
Click File | Open | File.
3
Open CreateDatabase.sql.
4
Select Query | Execute.
5
Repeat steps 3 and 4 to install the following SQL script files in the following order:
•
UserFunctions.sql
•
DatabaseSchema.sql
•
ImportData.sql
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação