Client Machine Account replication delays

From: John Woodward (anonymous_at_discussions.microsoft.com)
Date: 04/23/04 

Date: Fri, 23 Apr 2004 09:41:02 -0700

We've created a forest of three separate domains to minimize intercontintal network traffic, but that still leaves each with a very wide coverage area.

We're creating new machine accounts programatically on the PDCE in each domain, but replication to the distributed DCs can take many hours before some new accounts are available to be joined.

It would be awkward to create accounts directly on the site DCs as there are hundreds scattered around the world and many of the intermediate links are quite slow.

Is there any way to direct only the client's "Join" process to use the domain's PDCE to resolve the machine account, while subsequent restarts rely on a site DC?

Thanks

Relevant Pages

  • Re: Client Machine Account replication delays
    ... You may be able to use nltest and/or netdom from the ... > We're creating new machine accounts programatically on the PDCE in each ... but replication to the distributed DCs can take many hours before ... > It would be awkward to create accounts directly on the site DCs as there ...
    (microsoft.public.win2000.active_directory)
  • Re: Client Machine Account replication
    ... > We've created a forest of three separate domains to minimize ... > We're creating new machine accounts programatically on the PDCE in ... > domain's PDCE to resolve the machine account, ...
    (microsoft.public.windows.server.active_directory)