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

Unified Communications Diagnostics 8.6.3 - User Guide

About Unified Communications Diagnostics Getting Started Using the Management Console Introducing Management Console health tests Health tests available from the Exchange organization node
About the Exchange-based health tests Exchange Server Health Test Prerequisites for Exchange Delivery Health Tests Exchange Internal Server Delivery Health Test Exchange Internal Mailbox Delivery Health Test Exchange External Message Delivery Health Test Exchange Modern Message Delivery Health Test Exchange Storage Health Test Exchange Queue Health Test Internal Outlook Web Access (OWA) Availability Health Test External Outlook Web Access (OWA) Availability Health Test Exchange Replication Health Test Exchange System Health Test Active Directory Account Lockout Health Test Exchange Online Connectivity Health Test Exchange Online Mailbox Logon Health Test Exchange Online Message Delivery Health Test Office 365 Subscription Health Test BlackBerry Server Health Test BlackBerry Message Delivery Health Test Creating test mailboxes for Exchange Adding health sets for Exchange System health tests Configuring Exchange impersonation for the Modern Message Delivery health test Registering UC Diagnostics with the Microsoft Azure portal
Health tests available from the Lync/Skype for Business Environment Resolving Problems with Native Tools Launching the Diagnostic Console from the Management Console Launching UC Analytics from the Management Console Diagnosing Problems using the Diagnostic Console UC Diagnostics: Exchange 2007 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2010 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2013 Diagnostic Console (Plug In) UC Diagnostics: Exchange 2016 Diagnostic Console (Plug In) UC Diagnostics: BlackBerry Diagnostic Console (Plug In) UC Diagnostics: OCS Diagnostic Console (Plug In) UC Diagnostics: Lync 2013 or Skype for Business 2015 Diagnostic Console (Plug In) Reporting Using Web Reports Counters with Non-Zero Alarm Values

About the Management Console

The Management Console is a Microsoft Management Console (MMC) snap-in and hosts the administrative tools that you use to administer your networks, computers, services and other system components.

Your BlackBerry servers are located under the Exchange organizations in the treeview.

To open the Management Console
•
Click Start | Program Files | Quest | UC Diagnostics | UC Diagnostics Management Console

The Management Console consists of the following components:

 
Table 1. Management Console components.
Management Console Section
Description

Menu

Contains the standard menu items, plus others:

•
File — allows you to set console options
•
Action — allows you to connect to an organization or environment, group sites, set global filters, create a health test, force discovery, and import/export topologies
•
View — allows you to show and hide items in the Management Console
•
Windows — allows you to set the view of the current window and indicates what windows are open
•
Help — allows you to open help topics and view the version number of MMC and UC Diagnostics

Treeview

Allows you to:

•
configure Global Settings
•
view Web Reports
•
view organizations, groups, and servers. Groups are displayed as a collection of servers, and servers are displayed as icons within the collections in the topology

Results pane

Allows you to:

•
view the topology in a graphical format
•
drag and drop servers for better organization
•
view the status and details about discovery
•
view test results

Actions pane

Allows you see all the actions on the currently selected object

Properties Pane
•
Shows details of your selected server, such as:
Site name
Exchange, BlackBerry, OCS, Lync, or Skype for Business version
Operating System Version
Operating System Service Pack
•
Shows details of your selected link, such as:
Link name
Relation of the link from one server to another
•
Gives instructions on how to zoom, pan, and auto-arrange your topology layout

Connecting to Diagnostic Services

To use the Management Console, you must be connected to the Diagnostic Services. The Management Console automatically connects to the Diagnostic Services on the local host, if a Diagnostic Services server is available. If Diagnostic Services are not available, you are prompted to enter the name of the Diagnostic Services server.

Once you connect to a Diagnostic Services server, the connection is saved to an .msc file. Once you have connected to the Diagnostic Services for the first time, it is not necessary to do so again unless you wish to connect to Diagnostic Services located on a different server.

To connect to the Diagnostic Services
1
Right-click the UC Diagnostics node and select Select Different Diagnostic Services Server.
2
Enter the name of the Diagnostic Services Server.
3
Click OK.
The account used to run the Management Console must be a member of the Local Administrators group on the server where the Diagnostic Services are running, and must have sufficient rights to access the Spotlight Management Framework database. For more information, see the Unified Communications Diagnostics Deployment Guide.
How Management Consoles Share Information

Multiple consoles can be connected to the same Diagnostic Services simultaneously, and have full read/write access to all UC Diagnostics functionality. Changes made in one console appear in the other consoles. If different users edit the same test at the same time, the user who saves the changes last has these 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 an OCS environment.

When you connect to an Exchange organization, the Management Console discovers and displays your entire Exchange organization. Discovery is initially configured to run automatically once a day to detect changes to your environment.

For information about the permissions run diagnostic services on the BlackBerry, Exchange, OCS, Lync, or Skype for Business platforms, see the Unified Communications Diagnostics Deployment Guide.

For information about permissions required to access the SQL data and for information about cluster support, see the Unified Communications Diagnostics Deployment Guide.

Connecting to a Platform

The Management Console displays all your servers at a glance, whether they exist in a single location or span the globe. It is the framework where the layout of your servers are displayed, tests are performed, notifications are configured, and server data is displayed.

You can use the Management Console to connect to an Exchange, BlackBerry, OCS, Lync, Skype for Business, or Office 365 platform.

The first time you connect to a platform, all servers are discovered. Discovery locates your available servers, then gets the properties of those servers. Discovery can take some time depending on the size of your organization or environment. Discovery then occurs every 24 hours to check for changes you may have made.

If you select Repeat Discovery, discovery runs at the start time initially indicated, then runs at the new setting configured in the Every...hours box. This overrides the daily start time.

For more information on discovery, see the Unified Communications Diagnostics Deployment Guide.

To connect to an Exchange organization
1
Right-click the UC Diagnostics node and select Connect to an Exchange Organization.
2
Enter a global catalog (or domain name or Exchange server name).
For an Exchange Online hybrid deployment
a
If you have a hybrid Exchange and Exchange Online deployment, select the Exchange Online check box.
b
Enter a valid Office 365 user name for the tenant.
User name must be in email format (UserName@Domain.com). It can contain alphanumeric characters and only the following symbols -.,_ @.
c
Enter the password for the Office 365 credential.
3
If you are connecting to one of the Microsoft National clouds, you must enter the URL that is to be used for the remote PowerShell connection and the URL for the Azure AD Authorization Endpoint.
For example, to connect to Office 365 operated by 21Vianet in China, you could enter:
Remote PowerShell URL:
https://partner.outlook.cn/PowerShell-LiveID
Azure AD Authorization Endpoint URL:
https://login.chinacloudapi.cn/common
If you are connecting to Office 365 Global, the default connections can be used and the fields can be left empty.
4
Click OK.
If you are connecting to an Exchange cluster, you must use a virtual server name.
To connect to a native Office 365 environment
1
Right-click the UC Diagnostics node and select Connect to Office 365.
2
For Connection, enter a name to identify the Office 365 tenant to which you are connecting.
3
Enter a valid Office 365 user name for the tenant.
User name must be in email format (UserName@Domain.com). It can contain alphanumeric characters and only the following symbols -.,_ @.
4
Enter the password for the Office 365 credential.
5
If you are connecting to one of the Microsoft National clouds, you must enter the URL that is to be used for the remote PowerShell connection and the URL for the Azure AD Authorization Endpoint.
For example, to connect to Office 365 operated by 21Vianet in China, you could enter:
Remote PowerShell URL:
https://partner.outlook.cn/PowerShell-LiveID
Azure AD Authorization Endpoint URL:
https://login.chinacloudapi.cn/common
If you are connecting to Office 365 Global, the default connections can be used and the fields can be left empty.
6
Click OK.

For native Office 365, nodes for Exchange Online and Skype for Business Online are displayed if the licensing plan has these services enabled.

For hybrid environments, you can add the Exchange Online or Skype for Business Online credentials through the Exchange Connection properties or the Lync/Skype for Business Connection properties.

To connect to an OCS environment
1
Right-click the UC Diagnostics node and select Connect to an OCS Environment.
2
Enter a global catalog (or domain name or OCS 2007 or OCS 2007 R2 server name) and click Connect.
To monitor a mixed environment (Lync/Skype for Business and OCS), you must establish two connections to the same environment: one Lync/Skype connection and one OCS connection.
To connect to a Lync/Skype for Business environment
1
Right-click the UC Diagnostics node and select Connect to a Lync/Skype Environment.
2
Enter a Lync/Skype Pool FQDN and user credentials.
For a Skype for Business Online hybrid deployment
a
If you have a hybrid Lync/Skype for Business and Skype for Business Online deployment, select the Skype for Business Online check box.
b
Enter a valid Office 365 user name for the tenant.
User name must be in email format (UserName@Domain.com). It can contain alphanumeric characters and only the following symbols -.,_ @.
c
Enter the password for the Office 365 credential.
3
If you are connecting to one of the Microsoft National clouds, you must enter the URL that is to be used for the remote PowerShell connection and the URL for the Azure AD Authorization Endpoint.
For example, to connect to Office 365 operated by 21Vianet in China, you could enter:
Remote PowerShell URL:
https://partner.outlook.cn/PowerShell-LiveID
Azure AD Authorization Endpoint URL:
https://login.chinacloudapi.cn/common
If you are connecting to Office 365 Global, the default connections can be used and the fields can be left empty.
4
Click OK.
You can select a Lync/Skype Environment from the drop-down list of those to which you have previously connected.

The next time you run the Management Console and connect to the same environment, the environment is not rediscovered upon connecting. If changes are made to the environment and are not shown in the Management Console, right-click the connection node in the treeview and select Force Discovery.

To connect to a BlackBerry environment

You must be connected to an Exchange organization before you can connect to a BlackBerry domain.

1
Right-click the Exchange organization node and select Connect to BlackBerry Servers.
- OR -
If you are already connected to a BlackBerry domain, select Edit BlackBerry Servers Connection Properties.
2
In the Connect to BlackBerry Servers dialog box, click Add.
3
Enter the BlackBerry Database location and the BlackBerry Database name.
•
If you are using a BlackBerry database that is installed on a named SQL instance, you must specify the instance name, such as MyServer/MySQLInstance.
•
If the SQL instance hosting the BlackBerry database is configured to use a non-default port, you can specify the port number in the Database Location box separated by comma, such as: MyServer/MySqlInstance,1345 where 1345 is the port number.
•
You do not need to specify a port number if your alias is configured for the SQL named instance hosting BlackBerry database on the SQL server, or if the SQL Server Browser service is installed and running on SQL server.
4
Windows authentication is selected by default. If you prefer to use SQL authentication, select this option from the drop down menu and enter a valid user name and password.
5
Click OK.
To add multiple BlackBerry domains, repeat steps 2 through 5.
To modify a BlackBerry Server connection

Because BlackBerry server and Exchange organization discovery takes place at the same time, if you want to change BlackBerry connection properties, you must change them at the Exchange organization level.

1
Right-click the Exchange organization.
2
Select Edit BlackBerry Servers Connection Properties.
3
Make the required changes.
To add a generic server

In addition to servers that are automatically discovered, you may want to monitor other servers that are critical to the functioning of your environment, such as a domain controller server. To do this, you can manually add them to your organization/environment.

1
From the treeview in the Management Console, right-click an Exchange or BlackBerry organization or an OCS/Lync/Skype for Business environment, and select Add Generic Server.
2
Enter a server name and click OK.
These servers have the same functionality as other servers, such as the ability to create health tests, launch Computer Management, Services, and Event Viewer.
To delete generic servers
•
Right-click a generic server and click Delete.
To customize connection properties

You can customize your connection properties to allow discovery to occur at times other than every 24 hours.

•
Right-click the connection in the treeview and select Properties.

Use the View Connection Properties dialog box to change or customize parameters as necessary.

To disconnect from an organization/environment
1
From the treeview, right-click an organization or environment.
2
Select Disconnect from Organization if you are connected to an Exchange organization)
- OR -
Select Disconnect from Environment if you are connected to an OCS/Lync/Skype for Business environment.
Disconnecting from your organization/environment removes the organization/environment from the treeview only. No data is deleted. Scheduled tests are still executed, data is still collected, and discovery still runs.
To remove the organization/environment
1
From the treeview, right-click an organization or environment.
2
Select Remove Organization if you are connected to an Exchange organization
- OR -
Select Remove Environment if you are connected to an OCS/Lync/Skype for Business environment.
Removing your organization/environment stops UC Diagnostics from collecting any information about that organization/environment. All data, such as test results history, web report data, and test settings, related to the organization or environment is permanently deleted.
To remove a BlackBerry domain
1
From the treeview, right-click the Exchange organization node and select Edit BlackBerry Servers Connection Properties.
2
In the Connect to BlackBerry Servers dialog box, select a BlackBerry database.
3
Click Remove.

Importing and Exporting Topology Layout

You can export your current topology layout to be imported to another topology. In general, one topology layout is saved per grouping node in the .msc file. The Importing and exporting function allows you to have several possible topology layouts.

You cannot save different topology layouts over different grouping modes. For example, if you export a topology layout that was grouped by site, you cannot import that layout if your current topology layout is grouped by domain.

To export a topology layout
1
Right-click an organization in the treeview or right-click your topology layout.
2
Select Export Topology Layout.
3
Enter the name for the file and save it as a .topology file.
To import a topology layout
1
Right-click a server node in the treeview or right-click your topology layout.
2
Select Import Topology Layout.
3
Select the topology file you want to import.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation