Re: AD user replication

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Cary Shultz [A.D. MVP] (cwshultz_at_mvps.org)
Date: 05/15/04 

Date: Sat, 15 May 2004 07:21:50 -0400

Damien,

This is *possibly* a really simply solution. Opps. I said it now I have to
provide the solution. Not a problem.

Did you install the ESM on the first Domain Controller ( the one without
Exchange 2000 on it )? I am guessing that you did not. If you say, "Cary,
but I did!" then I would suggest to you that when you create a user that you
consider using the ADUC from Start | Programs | Microsoft Exchange rather
than the ADUC from Start | Programs | Administrative Tools. Also, on DC1
when you install the ESM I would strongly suggest that you also install the
Exchange 2000 SP.

I would venture to suggest that when you create the user on DC1 that you are
not really creating the 'mailbox' attributes.

Now, if this is completely incorrect ( I am making the above assumption
because a lot of people do this ) and you are using the ADUC from Start |
Programs | Microsoft Exchange and you are for sure creating the 'mailbox'
attributes then I might ask how much time you are giving it ( the created
user account object ) to show up on DC2. I ask because I have seen it many
times where it can take up to two hours for it to show up on the other DC.
And if we are dealing with multiple Sites it can take a bit longer. And
that is with everything being absolutely correct as far as Replication is
concerned.

If this is not the case ( meaning, you have used the ADUC from Start |
Programs | Microsoft Exchange and multiple hours have passed and still no
user on DC2 ) then I might suggest that you take a look at the Support Tools
( hopefully you have them installed already ) and look at replmon and
repadmin as well as dcdiag and netdiag. These four tools will help you.

Marin has a good idea as well. I typically do not like to delete things,
though, until I have explored other avenues.

HTH,

Cary

<anonymous@discussions.microsoft.com> wrote in message
news:d68201c439f1$087bf720$a301280a@phx.gbl...
> Thanks Marin,
>
> The DNS is not a problem, that does work. DNS Resolution is
> working great and the SRV's match in DNS. I'll try deleting
> the Rep connections and see how that goes.
>
> Damien
> >-----Original Message-----
> ><snip>
> >First, make sure that both DCs can find the other DC's SRV
> records and
> >resolve its name to an IP address, I.e. your DNS is
> absolutely solid.
> >Try deleting the replication connections and either
> recreating them
> >manually of forcing the KCC to rebuild them.
> >
> >HTH
> >--
> >Cheers,
> > Marin Marinov
> > MCT, MCSE 2003/2000/NT4.0,
> > MCSE:Security 2003/2000, MCP+I
> >-
> >This posting is provided "AS IS" with no warranties, and
> confers no
> >rights.
> >.
> >

Relevant Pages

  • Re: Exchange 2003 Server installation errors
    ... What you can try is booting the Windows 2000 Server installation and trying ... I attempted to install exchange server 2003 on a Win2K3 ... Event Category: Microsoft Exchange Setup ... or message DLL files to display messages from a remote computer. ...
    (microsoft.public.exchange.setup)
  • Re: In-place Win to SBS upgrade
    ... There is no such object on the server. ... ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT ... - This version of Microsoft Exchange Server 2003 can only be installed on Microsoft Windows Server 2003 for Small Business Server. ... Prerequisites for Microsoft Exchange Messaging and Collaboration Services failed: The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Install" because: ...
    (microsoft.public.windows.server.sbs)
  • Re: Disributing CDO 1.2.1 libraries.
    ... > The end user already has Exchange. ... If they have not paid for ESM ... >>> the ESM to get CDO installed, but it does NOT recommend redistributing ... >> the conclusion was that even if you don't install Outlook, ...
    (microsoft.public.win32.programmer.messaging)
  • MSExchange no longer running
    ... Microsoft Exchange Server information store ID no: ... MSExchangeSA DSACCESS returned an error'0x80004005' on DS notification. ... on each client pc. ... again & will the new install of SBS2003 pickup the emails that have been ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 Server installation errors
    ... I would wipe / Install Windows server on the computer in question - then it ... I attempted to install exchange server 2003 on a Win2K3 machine. ... Exchange Server component Microsoft Exchange Messaging and Collaboration ... or message DLL files to display messages from a remote computer. ...
    (microsoft.public.exchange.setup)