I will simply say that my long term use of the ADC was not a pleasant experience. The the way the ADC ran was somewhat akin to how the Army is... Different parts would pass out at different times... If you do intend to use it long term, say greater than 90 days or so, I would definitely recommend monitoring that it is actually processing stuff. You can do that by watching the USN of the servers it is talking to and the USNs it is recording in the config container under the agreements. If those values have a delta that just gets bigger and bigger, most likely the ADC is NOT working even though the service may be running and not throwing errors. joe
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mikael Svennungsson Sent: Wednesday, May 05, 2004 5:14 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] ADC setup Al and Paul, Thanks for feedback on MIIS. Agree on ADC, we will only have the ADC up and runnning during our coexistence period until everything is migrated (allways tend to take a year or so to cover all small sub-orgs. ;-)) Due to our experience on the X400 connector behaviour for the E2K3 users, we might need to skip the ADC for this sub-org since an X500 address could be needed (or we just script that part). But thats an Exchange issue and out of scope for this forum ;-) Regards, /MS _____ From: [EMAIL PROTECTED] on behalf of Cotter, Paul M. Sent: Wed 2004-05-05 16:03 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] ADC setup Just to note - the full version of MIIS is not needed, the IIFP will do fine, and it's free. GAL synchronization is a core scenario for MIIS (including the IIFP) and there are lots of examples etc. of how to set this up in the online help. Paul _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mulnick, Al Sent: Wednesday, May 05, 2004 8:04 AM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] ADC setup One thing you should additionally be aware of Mikael. The ADC is *NOT* intended to be used for joining two organizations for any other reason than to aid migration. This is not a permanent solution. You should investiage MIIS if you need a long term solution for joining two organizations. Trust me on that ;) _____ From: Mikael Svennungsson [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 05, 2004 5:18 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] ADC setup Hi all, Problem Solved. The ADC CA is up and running. (X400 still to set up) Please note that the ADC between DomB and E55 in DomC should be setup with the "Inter Organizational onnection Agreement" in the Advanced tab. There was an irritating flaw during the naming of the servers. The Domain was called XXXODOM (O=letter) The PDC was called XXXO1 (O=letter) The Exchange was called XXX02 (0=number) (and yes, I did not configure this name :-)) Using XXXO2 (O=letter) in lmhost file gave an error when trying to find objects when setting up the CA. and the error on duplicate names. Sorry guys, but we were four persons looking into the problem not see this obvious one. The difference between O and 0 is small in Exchange 5.5 admin :-). A set in a command prompt made it visible. Regards, /MS _____ From: [EMAIL PROTECTED] on behalf of joe Sent: Wed 2004-05-05 05:17 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] ADC setup I think the simplest way to work this would be to do a network trace and look at what bombs. If it is name res, you will see it quickly on the WINS/DNS/Broadcast calls. If it is not name res you will see it make it past that stuff and fail on something else, most likely it sounds like on some kind of call to retrieve some specific object. joe _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mikael Svennungsson Sent: Tuesday, May 04, 2004 5:56 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] ADC setup Dear all, I would like your advice concerning a setup of ADC. We have two different Exchange organizations that we want to interconnect. Our idea is to set up a X400 connector to handle mailrouting and using ADC to synchronize the directories. When setting up tha ADC-CA we run into problems that might be related to nameresolution (?). The error message is "no such object on server" when we try to choose the E5.5 container. We have added the E5.5 server as a "plain" IP entry in the lmhost file as well as added the domain and the pdc. Adding the E5.5 server in the other WINS (as Unique) gives the same error. Trying to do a net use to the E5.5 netbios name from the AD exchange box gives a error message complaining over duplicate names. Any suggestions? I am on the right track when looking for netbios name resolution problems? Any other way to acheve the same result? Tech stuff: Three Domains: DomA (NT4), DomB( W2K3), DomC (NT4)( this is the new one) DomA-DomB two-way trust (same WINS) and DomB-DomC two-way trust (using LMHOST entries) Two Ex-orgs EoA (for DomA and DomB) , EoC (for DomC), different Org and Site names DomA-E5.5, DomB-E2K3, DomC-E5.5 ADC CA's up and running between Ex in DomA and DC in DomB DomA and DomB sharing WINS, DomC separate WINS Want to create ADC between DomB and E55 in DomC. Accounts used: domain admin and exch system admin. X400 between EoA and EoC to handle mail routing TIA, /MS =========================================================== Important: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. ===========================================================
<<attachment: winmail.dat>>
