Enable Diagnostic Logging on a Unified Messaging Server

Applies to: Exchange Server 2010

You can use the Shell or a registry editing tool to enable diagnostic logging on a Microsoft Exchange Server 2010 Unified Messaging (UM) server. By default, diagnostic logging is enabled on a UM server but is set to the lowest level. However, if you're troubleshooting an issue on a UM server, you may have to increase the diagnostic logging level to help you locate the source of the problem.

Event Viewer maintains logs about program, security, and system events on your computer. These logs include errors and events that occur on a UM server. You can use Event Viewer to view and manage the event logs, gather information about hardware and software problems, and monitor Unified Messaging errors and events. Although Event Viewer is a Microsoft Windows operating system tool and not a Microsoft Exchange tool, Event Viewer is useful when you troubleshoot problems with Unified Messaging. For more information about Unified Messaging errors and events, see Error and Event Reference for Unified Messaging Servers.

Looking for other management tasks related to UM servers? Check out Managing Unified Messaging Servers.

Use Registry Editor to enable diagnostic logging on a Unified Messaging server

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "UM server" entry in the Unified Messaging Permissions topic.

1. Start Registry Editor (regedit).

2. Locate the following registry key: HKeyLocalMachine\System\CurrentControlSet\services\MSExchange Unified Messaging\Diagnostics

3. In the details pane, double-click the appropriate registry value, and then use the following values to configure the appropriate logging level:

   Logging level	Value
   Expert	7
   High	5
   Medium	3
   Low	1
   Lowest	0

Use the Shell to enable diagnostic logging on a Unified Messaging server

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "UM server" entry in the Unified Messaging Permissions topic.

This example enables diagnostic logging for the UMCore DWORD value.

Set-EventlogLevel "MyUMServer\MSExchange Unified Messaging\UMCore" -level <Lowest | Low | Medium | High | Expert>

This example enables diagnostic logging for the UMWorkerProcess DWORD value.

Set-EventlogLevel "MyUMServer\MSExchange Unified Messaging\UMWorkerProcess" -level <Lowest | Low | Medium | High | Expert>

This example enables diagnostic logging for the UMManagement DWORD value.

Set-EventlogLevel "MyUMServer\MSExchange Unified Messaging\UMManagement" -level <Lowest | Low | Medium | High | Expert>

This example enables diagnostic logging for the UMService DWORD value.

Set-EventlogLevel "MyUMServer\MSExchange Unified Messaging\UMService" -level <Lowest | Low | Medium | High | Expert>

This example enables diagnostic logging for the UMClientAccess DWORD value.

Set-EventlogLevel "MyUMServer\MSExchange Unified Messaging\UMClientAccess" -level <Lowest | Low | Medium | High | Expert>

This example enables diagnostic logging for the UMCallData DWORD value.

Set-EventlogLevel "MyUMServer\MSExchange Unified Messaging\UMCallData" -level <Lowest | Low | Medium | High | Expert>

This example lets you see the current logging level for a Unified Messaging server.

Get-EventlogLevel "MyUMServer\MSExchange Unified Messaging"

For more information about syntax and parameters, see Set-EventLogLevel.

Other Tasks

After you enable diagnostic logging on a Unified Messaging server, you may also want to:

• Enable Tracing for Unified Messaging
• Testing Unified Messaging Server Functionality