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

Adding health sets for Exchange System health tests

You can include additional health sets that you want to monitor for the specific Exchange System Health tests that you want to run.

To add health sets
1
Click <Add Health Sets> located under one the following Health Sets sections in the listview of the Exchange system health test that you select:
•
CustomerTouchPoints
•
ServiceComponents
•
ServerComponents
•
DependencyAvailability
2
Enter one health set per line you want to add and click OK.

For more information about health sets, see Exchange System Health Test .

Configuring Exchange impersonation for the Modern Message Delivery health test

The Exchange Modern Message Delivery Health test uses Exchange Web Services (EWS) to connect to the test source and target mailboxes. The test credentials that are used must have “Exchange Impersonation” permissions to all the test mailboxes.

Configuring impersonation for all users

You can configure Exchange impersonation for all users in an organization.

To configure a service account to impersonate all users in an organization
1
Open the Exchange Management Shell.
2
Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate to the specified user.
The following example shows how to configure Exchange Impersonation to enable a service account to impersonate all other users in an organization.
New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:serviceAccount
Configuring impersonation for specific users or groups

You can configured Exchange impersonation for specific users or groups.

To configure a service account to impersonate specific users or groups of users
1
Open the Exchange Management Shell.
2
Run the New-ManagementScope cmdlet to create a scope to which the impersonation role can be assigned. If an existing scope exists, you can skip this step.
The following example shows how to create a management scope for a specific group.
New-ManagementScope –Name:scopeName –RecipientRestrictionFilter:recipientFilter
3
Run the New-ManagementRoleAssignment cmdlet to add the permission to impersonate the members of the specified scope.
The following example shows how to configure Exchange Impersonation to enable a service account to impersonate all users in a scope.
New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:serviceAccount –CustomRecipientWriteScope:scopeName

Registering UC Diagnostics with the Microsoft Azure portal

If you are connecting to Office 365 and are using OAuth 2.0 modern authentication to connect through PowerShell and EWS, you must register the UC Diagnostics application with the Microsoft Azure portal site. Depending on the region from which you are accessing the Microsoft Azure portal site, the user interface can differ.

You can configure OAuth 2.0 authentication to be used for the Exchange Online Mailbox Logon health test and for the Exchange Online Message Delivery health test.

UC Diagnostics uses client credential flows (Application permissions). You must have global administrator permissions to register the UC Diagnostics application with Azure Active Directory,

To register UC Diagnostics with Azure Active Directory
1
In the Azure Active Directory Admin Center, click Azure Active Directory.
2
Under Manage, select App registrations.
3
Select Owned applications and click New registrations.
4
Enter the application name in Name (such as UC Diagnostics) and click Accounts in any organizational directory (Any Azure AD directory - Multitenant).
5
Click Register.
6
Select Overview and copy down the values that display for Application (client) ID and Directory (tenant) ID.
You will need this information to configure the UC Diagnostics Exchange Online Mailbox Logon Health and Exchange Online Message Delivery Health tests when using OAuth modern authentication.
7
Under Manage, select API permissions and click Add a permission.
8
Under Microsoft APIs scroll down to the Supported legacy APIs heading and click Exchange.
9
Click Delegated permissions and select the EWS.AccessAsUser check box under EWS.
10
Click Add permissions.
11
Under Configured Permissions, click Add a permission.
12
Select Exchange and click Application permissions.
13
Select the full_access_as_app check box and click Update permissions.
14
Click Grant admin consent for <Your Directory Name>. To perform this step, you must have administrator permissions.
After admin consent is granted, the status is green.
15
Under Manage, select Authentication and click Yes in the Advanced settings section.
16
Click Save.
17
Under Manage, select Certificates & secrets and click New client secret.
18
Enter a description in Description, select a time period for Expires, and click Add.
19
Copy down the client secret value that is displayed.
You will need this information to configure the UC Diagnostics Exchange Online Mailbox Logon Health and Exchange Online Message Delivery Health tests when using OAuth modern authentication.

 

Health tests available from the Lync/Skype for Business Environment

•
About the Lync/Skype for Business health tests
•
Lync/Skype Server Health Test
•
Lync/Skype Synthetic Transaction Health Tests
•
Lync/Skype Instant Messaging Health Test
•
Lync/Skype Instant Messaging Conference Health Test
•
Lync/Skype Peer-to-Peer Audio/Video Call Health Test
•
Lync/Skype Audio/Video Conferencing Health Test
•
Lync/Skype Presence Status Health Test
•
Lync/Skype Logon Registration Health Test
•
Lync/Skype Address Book Service Health Test
•
Lync/Skype Persistent Chat Message Health Test
•
Active Directory Account Lockout Health Test
•
Skype for Business Online DNS Connectivity Health Test
•
Office 365 Subscription Health Test
•
OCS Server Health Test
•
Creating a test user for the Lync/Skype Environment
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation