Download T - Windows IT Pro

CLIENT ACCESS SERVER ADMINISTRATION
Figure 3: Protocol logs for the RPC Client Access service
Table 5: Enabling Protocol Logging for the Client Access Server Services
Service
How to Enable
RPC Client Access
Edit the XML file named Microsoft.Exchange
.RpcClientAccess.Service.exe.config in the Exchange
Server\V14\bin folder. Ensure the following line is
included under the <appSettings> element:
<add key="ProtocolLoggingEnabled"
value="true"/>
Address Book Service
Edit the XML file named Microsoft.Exchange
.AddressBook.Service.exe.config in the Exchange
Server\V14\bin folder. Ensure the following line is
included under the <appSettings> element:
<add key="ProtocolLoggingEnabled"
value="true"/>
POP3 Service
Run the following command in EMS:
Set-PopSettings -ProtocolLogEnabled $true
IMAP4 Service
Run the following command in EMS:
Set-ImapSettings -ProtocolLogEnabled $true
settings. When you create the account,
you’re prompted for a one-time password.
You never need to know this password
again because Exchange manages it after
the account is created and because it’s
changed on a regular basis.
Diagnostic logging. To troubleshoot
at a level deeper, you can turn on diagnostic logging for several Client Access server
components. Exchange 2010 provides an
interface to use in EMC. You can access
the diagnostic logging interface for Client Access servers by selecting Server
Configuration, Client Access. Choose the
Client Access server that you want to
enable logging on and select Manage
Diagnostic Logging Properties from the
w w w. w i n d o w s i t p ro. c o m
Actions pane. The logs generated from
the diagnostic logging process are written to the Application log in the Windows
event logs.
Protocol logs. The RPC Client Access,
Address Book, IMAP4, and POP3 services
all offer the ability to turn on protocol
logging. Protocol logging lets you see the
conversation between the client that’s
trying to connect and the Client Access
server that’s responding. These logs are
stored as comma-separated files that can
be opened in any text editor. Some of the
information in the protocol logs is common across all the services, and some of
the information is unique to the service
you’re logging. Figure 3 shows the protocol
W e ’ r e i n I T w i t h Yo u
logs for the RPC Client Access service.
Note that this log contains some valuable
information that’s specific to RPC Client
Access troubleshooting, such as the client software (outlook.exe), the version
(12.0.4518.1014), and even which mode it’s
running in (cached).
Protocol logging is enabled on these
services either through the service’s configuration file or through EMS. The default
location for the logs is C:\Program Files\
Microsoft\Exchange Server\V14\Logging.
Table 5 describes how to enable the protocol logs.
For client protocols that use IIS (OWA,
Exchange Control Panel, Exchange ActiveSync, Exchange Web Service, Autodiscover,
Outlook Anywhere, and remote PowerShell), you can use the IIS logs to gather
similar log information. By default, these
logs are in the folder C:\inetpub\logs\LogFiles. Logging in IIS is enabled by default,
so no additional configuration is necessary
to use these logs.
Go Forth and Administer
Client Access servers comprise only a
single piece of your overall Exchange infrastructure—a lot of the focus in Exchange
administration leans toward data administration on mailbox servers. Administering
Client Access servers doesn’t require a lot
of time or attention, but you can spend a
lot of time troubleshooting if something
goes wrong. To prevent little problems
from turning into large outages, you should
proactively monitor and troubleshoot your
Client Access servers.
In this series I walked you through
various aspects of the Client Access server
role in Exchange 2010 to help you better
understand what it does and how to work
with it. The information I provided in the
series will help you effectively deploy and
manage a common Client Access server
implementation.
InstantDoc ID 129254
Ken St. Cyr
([email protected]) is a
solution architect at Microsoft with
more than 10 years of industry
experience. He’s a Microsoft Certified Master in Directory Services
and the author of Exchange Server
2010 Administration Instant Reference (Sybex).
Windows IT Pro
M AY 2 0 1 1
57