Exchange Server 2003
Recipient Update Service is responsible for adding SMTP email addresses to the system for a new or changed user.
Rebuild can take many hours (or days) to finish!
Setup & Troubleshooting Recipient Update Services http://support.microsoft.com/kb/822794/
SExchangeAL LDAP Operations MSExchangeAL Address List Synchronization MSExchangeSA Proxy Generation (Exchange 2003 only) To do this, follow these steps: 1. Start the Exchange System Manager tool. 2. If administrative groups are enabled, expand Administrative Groups, and then expand your administrative group. If administrative groups are not enabled, go to step 3. 3. Expand Servers, right-click the Exchange server that you want to configure diagnostic logging on, and then click Properties. 4. Click the Diagnostics Logging tab, and then click MSExchangeAL in the Services list. 5. In the Categories list, click LDAP Operations, click Maximum, click Address List Synchronization, and then click Maximum.
If you are running Exchange 2003, go to step 6. If you are not running Exchange 2003, go to step 7. 6. Click MSExchangeSA in the Services list, click Proxy Generation in the Categories list, and then click Maximum. 7. Click OK.
To see when the Last Full Update of the Exch. was started...
Use the ADSI Edit snap-in or LDP.exe to obtain the distinguished name of the Recipient Update Service that you want to troubleshoot:
Expand Configuration Container [DomainController.contoso.com], expand CN=Configuration,DC=contoso,DC=com,
expand CN=Services, expand CN=Microsoft Exchange, and then expand CN=OrganizationName.
Expand CN=Address Lists Container, and then click CN=Recipient Update Services (note you want the Domain one)
Then back to your win2k3 support tools cmd prompt: repadmin /showmeta "distinguishedName" >rusmeta.txt
eventvwr.msc Event ID box, type 8011, type Base 'DC in the Description box, and then click Find Next.
Searching directory ExampleDc1.Anders.co.local at base 'DC=Example,DC=co,DC=local' using filter '(&(USNChanged>=5058110)(uSNChanged<=5058111)((|(mailNickname=)(|(&(objectCategory=person)(objectSid=) (!(samAccountType:1.2.840.1135188.8.131.524:=3)))(&(objectCategory=person)(!(objectSid=*)))(&(objectCategory=group) (groupType:1.2.840.1135184.108.40.2064:=14))))))' and requesting attributes distinguishedName; objectGUID; LegacyExchangeDN; msExchADCGlobalNames; ObjectSID; ObjectClass; objectCategory; displayName; msExchHideFromAddressLists; hideDLMembership; ntsecuritydescriptor; showInAdvancedViewOnly; msExchALObjectVersion; showInAddressBook; msExchPolicyEnabled; givenName; sn; cn; mailNickname; targetAddress; initials; proxyAddresses; mail; textEncodedORAddress; msExchHomeServerName; msExchExpansionServerName; msExchCustomProxyAddresses; msExchPoliciesIncluded; msExchPoliciesExcluded; replPropertyMetaData; replicatedObjectVersion; ReplicationSignature; WhenChanged; WhenCreated; USNchanged; USNcreated; ObjectVersion; isDeleted; homeMDB; homeMTA; msExchMailboxGuid; msExchMailboxSecurityDescriptor; msExchResourceGUID; UserAccountControl; msExchUserAccountControl.
ASDIedit.msc (from win2k3 support tools) can allow you to see the uSNChanged # of a new test user you have created... And if the "showInAddressBook" attribute is populated (if not then the user may not have been found by the rebuild)...
e.g. 5,321,799 is great than the current 5,058,111 -> but hopefully it won't take much longer (12 hours to do 5 million)
Don't forget to turn the logging off afterwards
can we manually modify this? what are the consequences?
CN=All Users,CN=All Address Lists,CN=Address Lists Container, CN=Example Company,CN=Microsoft Exchange,CN=Services, CN=Configuration,DC=Example,DC=co,DC=local
CN=Customer contacts,CN=All Contacts,CN=All Address Lists,CN=Address Lists Container, CN=Example Company, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Example,DC=co,DC=local
CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=Example Company, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Example,DC=co,DC=local