Client Machine Account replication delays

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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

Thank
 
John-

You may be able to use nltest and/or netdom (probably nltest) from the
reskit/support tools to do this. I wouldn't want to be quoted on that,
though. :)

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com


John Woodward said:
We've created a forest of three separate domains to minimize
Click to expand...
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
Click to expand...
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
Click to expand...
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
Click to expand...
domain's PDCE to resolve the machine account, while subsequent restarts rely
on a site DC?
 
Thanks.

While the Support Tools help doesn't mention it, NETDOM JOIN does indicate that you can specify the specific DC as part of the domain indication. (/domain:domain\dc

I'll test it out.
 
Back
Top