지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Test prerequisites

The following permissions are needed to run the management console for OCS. The required permissions apply to both OCS 2007 and OCS 2007 R2 servers.

 
Table 1. Permissions required for OCS health tests.
Scope
Permissions required for diagnostic services account

Domain
•
Member of RTCUniversalServerAdmins

Database Server
(Back-End, Archiving, Quality of Experience Monitoring Server)

Ensure database is remotely accessible

NOTE: Use Surface Area Configurator to enable TCP/IP and named pipe access.

Edge Servers

Add a user account with the same login credentials as the service account. Make the account a local administrator on the Edge Server.

OCS Health Tests

UC Diagnostics contains the following health tests that each monitor one part of your OCS 2007 or OCS 2007 R2 servers:

To monitor a mixed Lync/Skype and OCS environment, you must establish two connections to the same environment - one as a Lync/Skype connection and the other as a OCS connection.

•
OCS Server Health Test

OCS Server Health Test

The OCS Server health test allows you to monitor the basic health of all your OCS servers. It is recommended that you configure two server health tests - one test without monitoring event logs set with an interval of 30 minutes and a second test for monitoring event logs that runs only once a day. For more information on test settings, see the Unified Communications Diagnostics User Guide.

This test allows you to monitor the following types of information:

•
Network availability
•
Operating system disk space usage
•
Any Performance Counter
•
Any Windows service
•
Any Event Log entry

The required configurations and permissions also apply to OCS 2007 R2 servers.

Test prerequisites

See the following tables for the test targets, required configuration, and the required permissions for this test.

You can run the test against the following target servers.

 
Table 2. OCS server health test targets.
OCS server version
Server type

All

All servers

NOTE: OCS Server Health test does not monitor federated partners.

The following configuration is required on each OCS server.

 
Table 3. OCS server health test configuration.
OCS server version
Configuration required

All
•
Enable WMI on each OCS server
•
Enable remote access to any back-end databases
NOTE: For information about SQL server prerequisites, see SQL database operating prerequisites .

The following permissions are required on the OCS servers.

 
Table 4. OCS server health test permissions.
OCS server version
Permissions required for test credentials

All
•
Member of Local Administrators group on each OCS server to have:
Read access to operating system drive to retrieve disk space
Read access to Windows system directory to access Event Logs
Read access to Service Control Manager
Read access to Registry to access Performance Counters and Event Logs
Read access to Back-End database tables (rtc and rtcdyn)
Read access to Back-End stored procedures (rtc and rtcconfig)
•
db_datareader rights to any Back-End databases

You can become a member of RTCUniversalServerAdmin to update the Back-End databases to give the db_datareader user role for the rtc, rtcconfig, and rtcdyn tables.

NOTE: For information about SQL server prerequisites, see SQL database operating prerequisites .

As an alternative, you can:

1
Create a new Security Group (OCS Diagnostic Users).
2
Map OCS Diagnostic Users into the Back-End Database and provide a User Mapping to the rtc, rtcconfig, and rtcdyn databases with the public and db_datareader role.
3
Add OCS Diagnostic Users to the RTCUniversalReadOnlyAdmins group.
4
Add OCS Diagnostic Users to the Power Users and Performance Monitor Users security group on each OCS server through a GPO or some other mechanism.

OCS Diagnostic Console Technical Information

The Diagnostic Console provides you with a real-time representation of the messaging system processes and components within OCS 2007 or OCS 2007 R2. You can diagnose and resolve issues using the Diagnostic Console.

The Diagnostic Console can perform real-time monitoring on Front-End and Conferencing servers only.

Diagnostic Console software prerequisites

The following software must be installed on the UC Diagnostics computer.

 
Table 5. OCS diagnostic console software prerequisites.
OCS server version
Software required on UC Diagnostics computer

All

Microsoft .NET Framework 4.5.1 or later

Required permissions on OCS servers

The following configuration is required on each OCS server.

 
Table 6. OCS diagnostic console permissions.
OCS role
Permissions required on OCS servers

All
•
Member of Local Administrators group on each OCS server
•
Member of RTCUniversalServerAdmins

The required software and permissions apply to both OCS 2007 and OCS 2007 R2 servers.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택