Apparently a Recipient Update Service needs to be built for each site? This is a single domain, so you wouldn't think it necessary. Once we started doing this though, two way org level replication worked. Does this seem obvious to people, should I go feed myself to Narthyloptep (Cthulhu should feed on better) as a low calorie, low brain snack? or is this just one more example of a setting that you only find out about if you want to pay extra (via time and effort, helpful places like this, or PSS) for a product that works?
/Gordon -----Original Message----- From: Morrison, Gordon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 26, 2001 9:16 AM To: Exchange Discussions Subject: RE: ADC makes me go hrmmm....... Thanks, but that isn't the case, I am creating users with such creative names as "e2kserver1, user1", "e2kserver1, user2", etc. on the e2k servers. Does anyone happen to know of a Q-note for safely ripping out ADC and starting over? I suppose that I could rebuild the lab -again-, but it would be nice to be able to just back up this one step and start fresh. I started out with 2 way connectors, and when that didn't work, I tried using 2 one way connectors using the same e2k server thinking it would allow me to more clearly see where the process was breaking down. When that didn't work I tried using a 1 way connector on one of the other e2k servers hoping that would work. ugh. Also, does anyone know of a q-note that would explain in great detail the mechanism by which ADC works. I have found information about SIDhistory and about LDAP, but nothing about its process, sort of: step 1: connect to LDAP on 5.5, export list step 2: connect to e2k, export list step 3: compare fields x,y,z for matches, discard fields from both lists where matches occur step 4: massage 5.5 data for LDF import to e2k step 5: massage e2k data to csv for import to 5.5 step 6: import data This is my guess, but I would like to see it confirmed someplace. BTW, the end goal of my testing is to try and prove the feasibility of having a single 2 way ADC pulling from the ORG level of e2k and 5.5 and dumping into a specified OU/site on the other side, creating enabled accounts. It seems as though the tool has the capability to do this, and if so, would prevent the needless creation of a bazillion trusts and a bazillion individual site level ADC connections. <caffeine>I think the coffee is starting to kick in.</caffeine> /Gordon -----Original Message----- From: Mike Putley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 25, 2001 4:38 PM To: Exchange Discussions Subject: RE: ADC makes me go hrmmm....... Could it be this - The users used to exist in the 5.5 org but have been deleted? This will leave invisible tombstones of the users in 5.5 that the ADC will not delete. If this sounds like it might be you. Let me know and I'll show you how to advance the tombstone deletion time closer that the 3-4 days min that it will let you configure Mike -----Original Message----- From: Morrison, Gordon [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 25, 2001 2:01 PM To: Exchange Discussions Subject: ADC makes me go hrmmm....... In my lab I have set up two 1 way agreements. One pulls all items from my 5.5 directory and deposits it in an OU called "Legacy" as appropriate. This is great because it saves me from building bunches and bunches of ADCs to each site in my ORG. However... When I try to build an agreement to take my w2k org and dump it into one of my 5.5 sites, I only get the users on the first site. It builds the containers for the other sites and the system objects but no users. (I do have the 'users' check box checked.) I have also tried to move the connector to other servers and build w2k site level specific containers to no avail. Anybody else seen this or have any thoughts on other things I could tweak? /Gordon | | | | ___________________NOTICE____________________________ This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of Bain & Company shall be understood to be neither given nor endorsed by the Company. When addressed to Bain clients, any information contained in this e-mail is subject to the terms and conditions in the governing client contract. _____________________________________________________ _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] | | | | ___________________NOTICE____________________________ This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of Bain & Company shall be understood to be neither given nor endorsed by the Company. When addressed to Bain clients, any information contained in this e-mail is subject to the terms and conditions in the governing client contract. _____________________________________________________ _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] | | | | ___________________NOTICE____________________________ This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of Bain & Company shall be understood to be neither given nor endorsed by the Company. When addressed to Bain clients, any information contained in this e-mail is subject to the terms and conditions in the governing client contract. _____________________________________________________ _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]