Re: Taking too long for Connection Agreement to replicate

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Erik Alvar (ealvar_at_0spam0netzero.net)
Date: 04/18/04


Date: Sat, 17 Apr 2004 18:26:02 -0700

Run DS/IS consistency adjuster in 5.5 per the documentation.

E
"Michael" <mmai@inxight.com> wrote in message
news:1a57901c42322$bad99b60$a601280a@phx.gbl...
> We've successfully upgraded our NT 4.0 environment to
> Windows 2003. We are in the process of upgrading Exchange
> 5.5 to Exchange 2003. However, I run into some problems in
> the lab environment:
> We have one Exchange 5.5 server running on a NT 4.0 member
> server (NT SP6a & Exchange SP 4), the DC is Windows 2003.
> I run the Exchange Deployment Tools (EDT)in the DC. I am
> in Phase 2, Step 6 where the ADC Connection Agreement
> Wizard is. The Connection Agreement has been running for
> more than 15 hours now, however, when I click on the
> Verify button, it says "Warning: Active Directory still
> cotains objects that are not replicated to Exchang 5.5
> directory..."
>
> The question is just how long does it take to replicate?
> Our network is not that big, we have less than two hundred
> people.
>
> Also, where should I run the EDT, should it be on a DC, a
> member server running W2k/W2k3 or someelse? It seems to be
> very confusing: In the begining of the EDT, it mentions
> that the server should be a W2k/W2k3 (but no mention about
> being a DC), but then I read somewhere that the ADC (which
> is part of EDT) should be ran on a DC. Which is true?
>
> Any feedback if much appreciated!
>
> Michael
> .



Relevant Pages

  • OT - Re: SBS2003 | Windows Server 2008 - Exchange 2007
    ... situation - I did not make something worse (this particular environment is ... that the SBS box holds all five FSMO Roles ... that the SBS box is a Global Catalog Server ... MS Exchange or MS SQL would clearly not be covered by the SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: Restoring Exchange 2000 cluster to "standard" Exchange 2000 En
    ... install of Exchange with the computer named EX04. ... Exchange with a different name, do the restore of the databases, then rename ... the Exchange server to the correct name. ... Our previous environment was an environment that wasn't built up using ...
    (microsoft.public.exchange.admin)
  • Re: Restoring Exchange 2000 cluster to "standard" Exchange 2000 En
    ... install of Exchange with the computer named EX04. ... the Exchange server to the correct name. ... Our previous environment was an environment that wasn't built up using ...
    (microsoft.public.exchange.admin)
  • Re: 2 DC and 1 Exchange and ADVICE
    ... Michael Abbaticchio ... MVP for Exchange Server ... > MVP for Microsoft Exchange Server ...
    (microsoft.public.exchange.admin)
  • Re: Restore Exchange server from copy
    ... The tool only works in a single domain controller environment. ... remove Exchange again and rebuild it with the proper names.. ...
    (microsoft.public.exchange.admin)