How to troubleshoot the Exchange Recipient Update Service

The Exchange Recipient Update Service ensures that address list memberships are accurate by updating them across organizations to reflect any changes that have been made. In an Exchange 2003 environment, every domain that contains an Exchange server requires a RUS. Although this service focuses primarily on address list memberships, it also can be a factor in public folder replication problems.

More Exchange Recipient Update Service resources: Expert Advice: How to use the Recipient Update Service Best Practices Guide: Exchange Server recipient policies and Recipient Update Service (RUS) Tip: Exchange Recipient Update Service and proxy addresses

Ensuring that objects contain the correct email address is another part of RUS's job. Even if a public folder is not mail enabled, per se, public folder hierarchy and content changes are replicated between Exchange servers using email messages. These messages are sent to an internal email address that uses the format servername-IS@domain.com. If you set up a new Exchange server, and the RUS is not functioning on the server, then this email address may not be written to the public folder store, and could cause public folder replication to fail.

This guide offers a step-by-step approach to troubleshooting the Exchange Recipient Update Service, including validating server names, investigating DNS issues, enabling diagnostic logging, analyzing event logs, using the ADSI Edit utility to troubleshoot the RUS, and verifying RUS updates.

If you have any comments or questions about the information presented herein, please send an email to editor@searchexchange.com.

TROUBLESHOOTING THE RECIPIENT UPDATE SERVICE

 Home: Introduction
 Step 1: Validate server names for the Exchange Recipient Update Service
 Step 2: Diagnose DNS-related Exchange Recipient Update Service problems
 Step 3: Enable diagnostic logging for the Exchange Recipient Update Service
 Step 4: Find Exchange Recipient Update Service Event ID log entries
 Step 5: Troubleshoot the Exchange RUS with ADSI Edit and 8011 events

ABOUT THE AUTHOR:

Brien M. Posey, MCSE Brien M. Posey, MCSE, is a Microsoft Most Valuable Professional for his work with Exchange Server, and has previously received Microsoft's MVP award for Windows Server and Internet Information Server (IIS). Brien has served as CIO for a nationwide chain of hospitals and was once responsible for the Department of Information Management at Fort Knox. As a freelance technical writer, Brien has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal Web site at http://www.brienposey.com.

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft Exchange Server Distribution Lists and Global Address Lists Is it possible to set up an auto-reply message for Exchange DLs? Share and sync calendar data between two Exchange Server sites How to export Global Address List data to Microsoft Office Access Can I display a distribution list name without showing member names? Exchange Global Address List FAQs Access contacts in an LDAP or X.500 directory from OWA Merge separate Exchange 5.5 and 2003 Global Address Lists Display names truncate in Exchange 2003 Global Address List New account in Active Directory not showing up in Exchange Global Address List How to create dynamic distribution groups in Exchange Server 2007 Microsoft Exchange Server and Active Directory Deployment tool errors during a migration from Exchange 5.5 to Exchange 2003 Can't create mailboxes after virtualizing Microsoft Exchange Server Tools to bulk modify Active Directory users in Exchange Server 2003 Email sent to a PDA doesn't get saved in Exchange Server mailbox How to verify Exchange Server email forwarding Remove Exchange 2007 public folder stores from a Mailbox Server role A network connection problem or an offline server prevented delivery of the message Create Exchange user and mailbox accounts on a Windows 2000 PDC Error 1053: Exchange System Attendant service could not start Forward Exchange Server email to an ISP using Active Directory Microsoft Exchange Server and Active Directory Research Microsoft Exchange Server 2003 Keeping the old server name after migrating to Exchange Server 2003 Can OWA 5.5 users access email from Exchange Server 2003? Deployment tool errors during a migration from Exchange 5.5 to Exchange 2003 Microsoft Exchange Server 2003 database recovery methods Microsoft Exchange Server mailbox recovery using database portability Recovering an Exchange Server 2003 store on a disaster recovery box Creating disk space for an Exchange Server 2003 priv1.edb database How to lock down an SMTP relay to prevent spam in Exchange Server 2003 Tool helps identify inbound Exchange Server email flow issues Configure SMTP relay restrictions in Exchange Server 2003 to stop spam Microsoft Exchange Server 2003 Research

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary User Principal Name  (SearchExchange.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary