Re: ADC2003 Issue - Help!

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 11/04/04

  • Next message: Sharq: "Which book(s) should i buy?" 
    Date: Wed, 3 Nov 2004 21:43:32 -0500

    One way CA's are an unsupported option for Exchange 5.5 upgrade last I
    checked. There are many reasons for this, but..

    To fix this, it sounds like it would be best to remove the OU and clear the
    attributes on the 5.5 side. Create your two-way CA and re-initiate the
    replication.

    Fixing the duplicate issue both today and for future processes would be a
    grand idea IMHO.

    Al
    "dakang" <senorspooks@yahoo.es> wrote in message
    news:eac8deb8.0411030504.56e6becd@posting.google.com...
    > Hi,
    >
    > After cleaning up our Exchange 5.5 directory (removing duplicate
    > accounts etc.) back in August I successfully carried out a replication
    > from EX5.5 to AD.
    >
    > There was a one way CA, creating objects in AD, into a TEMPADC OU, but
    > new AD accounts did not create new objects in EX5.5. There was
    > another one way CA, replicating -modifications only- from AD back to
    > EX5.5\recipients.
    >
    > The service was stopped after the initial replication and we left it
    > like that because the real migration is not due to start until
    > December.
    >
    > I have now noticed that on the Exchange 5.5 side, somewhere in our org
    > has been busy assigning the same Primary NT account to multiple
    > mailboxes, some Aliases have changed and some mailboxes have been
    > deleted.
    >
    > Having cloned the machines in a test lab, I tried to run ADC tools and
    > received zillions of errors.
    >
    > My question is:
    >
    > 1>Can I simply fix all the duplicate NT account issues and start my
    > CAs, and they will update?
    >
    > 2> or do I have to delete ALL objects in TEMPADC OU and then rerun a
    > fresh full replication. Some of these accounts have already been
    > moved to new OUs.
    >
    >
    > This is quite urgent and I thank you in advance. I posted on the MS
    > boards but received no reply...

  • Next message: Sharq: "Which book(s) should i buy?"

    Relevant Pages

    • Re: OWA Email Display Issues
      ... Microsoft Exchange Server 2003. ... Why would enabling Gzip fix my OWA display issue? ... >Hi Matthew ... >> All of the domain user accounts that I've created are ...
      (microsoft.public.windows.server.sbs)
    • Re: ADC2003 Issue - Help!
      ... One way CA's are an unsupported option for Exchange 5.5 upgrade last I ... To fix this, it sounds like it would be best to remove the OU and clear the ... > accounts etc.) back in August I successfully carried out a replication ... > new AD accounts did not create new objects in EX5.5. ...
      (microsoft.public.exchange.setup)
    • ADC2003 Issue - Help!
      ... After cleaning up our Exchange 5.5 directory (removing duplicate ... new AD accounts did not create new objects in EX5.5. ... The service was stopped after the initial replication and we left it ... I have now noticed that on the Exchange 5.5 side, ...
      (microsoft.public.exchange.setup)
    • ADC2003 Issue - Help!
      ... After cleaning up our Exchange 5.5 directory (removing duplicate ... new AD accounts did not create new objects in EX5.5. ... The service was stopped after the initial replication and we left it ... I have now noticed that on the Exchange 5.5 side, ...
      (microsoft.public.exchange.design)
    • Re: Exchange 2000 to 2007 public folders
      ... PF replication is pretty hard to fix if it's not the obvious things. ... tracking logs to see if the message flow between the servers is healthy. ... have entered the free/busy registry key on the exchange 2000 box. ...
      (microsoft.public.exchange.admin)
    Loading