Chris, Thanks for the suggestion. Tried it this morning and Domainprep ran quite quickly (much more quickly than I've ever seen it run when truly prepping a domain for the first time)...
Unfortunately the problem persists. Further suggestions would be warmly welcomed. Joe Pochedley Weiler's Law - Nothing is impossible for the man who doesn't have to do it himself. -----Original Message----- From: Chris Scharff [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2003 3:49 PM To: Exchange Discussions Subject: Re: RUS not working to child domain? Might try rerunning domainprep as well in that domain... Don't think it would hurt anything anyway. On 07/24/03 14:41, "Joe Pochedley" <[EMAIL PROTECTED]> wrote: > Kind ladies and gentlemen, once again I come forth seeking your > assistance... > > A number of months ago we began integrating the systems of a company we > purchased with our own. As part of the consolidation we added their > network to our existing AD as a child domain. We consolidated email > servers to a single server. Adding Exchange mailboxes for their child > domain accounts went smoothly. Once the RUS to their child domain was > added, all the information replicated to the GAL just as I expected and > they had live mailboxes... Now, for some reason RUS no longer appears > to be working properly with the child domain... Changes to accounts > (spelling changes in names for instance) aren't reflected in the GAL and > new accounts in the child domain never appear in the GAL. RUS appears > to be working fine within the main domain though. > > I've tried to force an update and a rebuild in RUS, neither of which > made a difference. > > I've turned logging for MSExchangeAL (LDAP, Service Control, and Address > Book Synch) to Max, but I don't see any failures or warnings (just a lot > of informational messages which I've perused but can't discern anything > that looks like a problem). > > I've verified connectivity to the remote child DC which is configured in > the RUS (MSKB 294222) by both short name and FQDN. I even tried > changing to another DC in the child domain with no effect. > > I've removed and rebuilt the RUS to the child domain. > > I believe that the Exchange Enterprise Servers have proper permissions > all the way through the child domain per MSKB 328223 (they shouldn't > have changed since the initial accounts were put in, and everything > worked OK when I added the first 60 or so accounts)... > > I'm hoping someone else can give a suggestion as to where to investigate > next. Everything looks like it SHOULD be working properly. > > As always, thanks in advance for any assistance! > > Joe Pochedley > Weiler's Law - Nothing is impossible for the man who doesn't have to do > it himself. > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=e > nglish > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
