RE: RUS not working to child domain?
Joe, When you restart the SA are there any errors generated? If the RUS is going to spit out any initialization errors...this is when you would see them (learned this the hard way when I put a RUS on a mailbox server that also hosted over 5000 mailboxes a year or so ago). Initialization errors tend to only occur when the SA is started (a reason to not put a RUS on a mailbox server). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Pochedley Sent: Friday, July 25, 2003 11:21 AM To: Exchange Discussions Subject: RE: RUS not working to child domain? Neil, Thanks for the quick rundown, but none of those appear to be the problem: 1. All DC's listed in RUS are available from the Exchange server. No problem with connectivity either by FQDN or short name (netbios name). 2. I've checked all the way to the individual object in AD. Exchange Enterprise Servers have permissions to the users in question. The Exchange Server in question is part of the Exchange Enterprise Servers. 3. No third party address generators are installed. No event errors in the event log with logging set to max. 4. No problems with Dist. lists with hidden membership. Again, no errors in the event log. And the hunt continues... Thanks though. Joe Pochedley Weiler's Law - Nothing is impossible for the man who doesn't have to do it himself. -Original Message- From: Neil Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2003 10:39 AM To: Exchange Discussions Subject: RE: RUS not working to child domain? 4 commons ways RUS can break are below. They may not all be appropriate to you, but I've cut & pasted them from a word doc of mine. :-) 1) RUS configuration references a deleted DC or E2K server, or the servers defined in RUS configuration are flakey at best. Browse both entries and choose alternates, if available. 2) Inheritable permissions are removed on an OU and the RUS is no longer able to reach the objects within it. (Q297124) 3) RUS is unable to generate email addresses because it is unable to locate a third party email address generator (DLL file). This can occur in mixed environments where an Exchange 5.5 server had fax software or the like installed. Exchange 2000 builds its recipient policies based on Ex55 site addressing (which includes the third party address). Since the DLL does not exist on the E2K server used by the RUS, the RUS will fire Event IDs 2035, 2037, and 2027 if MSExchangeAL logging is set to max. (Q286356) 4) If the RUS encounters a distribution list that has its membership hidden, it will not be able to stamp it with mail attributes and will go to sleep. (Q287137) Neil -Original Message- From: Joe Pochedley [mailto:[EMAIL PROTECTED] Posted At: 25 July 2003 15:32 Posted To: Swynk Exchange List Conversation: RUS not working to child domain? Subject: RE: RUS not working to child domain? 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 disc
RE: RUS not working to child domain?
Neil, Thanks for the quick rundown, but none of those appear to be the problem: 1. All DC's listed in RUS are available from the Exchange server. No problem with connectivity either by FQDN or short name (netbios name). 2. I've checked all the way to the individual object in AD. Exchange Enterprise Servers have permissions to the users in question. The Exchange Server in question is part of the Exchange Enterprise Servers. 3. No third party address generators are installed. No event errors in the event log with logging set to max. 4. No problems with Dist. lists with hidden membership. Again, no errors in the event log. And the hunt continues... Thanks though. Joe Pochedley Weiler's Law - Nothing is impossible for the man who doesn't have to do it himself. -Original Message- From: Neil Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2003 10:39 AM To: Exchange Discussions Subject: RE: RUS not working to child domain? 4 commons ways RUS can break are below. They may not all be appropriate to you, but I've cut & pasted them from a word doc of mine. :-) 1) RUS configuration references a deleted DC or E2K server, or the servers defined in RUS configuration are flakey at best. Browse both entries and choose alternates, if available. 2) Inheritable permissions are removed on an OU and the RUS is no longer able to reach the objects within it. (Q297124) 3) RUS is unable to generate email addresses because it is unable to locate a third party email address generator (DLL file). This can occur in mixed environments where an Exchange 5.5 server had fax software or the like installed. Exchange 2000 builds its recipient policies based on Ex55 site addressing (which includes the third party address). Since the DLL does not exist on the E2K server used by the RUS, the RUS will fire Event IDs 2035, 2037, and 2027 if MSExchangeAL logging is set to max. (Q286356) 4) If the RUS encounters a distribution list that has its membership hidden, it will not be able to stamp it with mail attributes and will go to sleep. (Q287137) Neil -Original Message- From: Joe Pochedley [mailto:[EMAIL PROTECTED] Posted At: 25 July 2003 15:32 Posted To: Swynk Exchange List Conversation: RUS not working to child domain? Subject: RE: RUS not working to child domain? 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
RE: RUS not working to child domain?
4 commons ways RUS can break are below. They may not all be appropriate to you, but I've cut & pasted them from a word doc of mine. :-) 1) RUS configuration references a deleted DC or E2K server, or the servers defined in RUS configuration are flakey at best. Browse both entries and choose alternates, if available. 2) Inheritable permissions are removed on an OU and the RUS is no longer able to reach the objects within it. (Q297124) 3) RUS is unable to generate email addresses because it is unable to locate a third party email address generator (DLL file). This can occur in mixed environments where an Exchange 5.5 server had fax software or the like installed. Exchange 2000 builds its recipient policies based on Ex55 site addressing (which includes the third party address). Since the DLL does not exist on the E2K server used by the RUS, the RUS will fire Event IDs 2035, 2037, and 2027 if MSExchangeAL logging is set to max. (Q286356) 4) If the RUS encounters a distribution list that has its membership hidden, it will not be able to stamp it with mail attributes and will go to sleep. (Q287137) Neil -Original Message- From: Joe Pochedley [mailto:[EMAIL PROTECTED] Posted At: 25 July 2003 15:32 Posted To: Swynk Exchange List Conversation: RUS not working to child domain? Subject: RE: RUS not working to child domain? 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&t
RE: RUS not working to child domain?
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]
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]
