Re: Forcing Intersite Group Policy Replication AD 2003



Thanks Jorge,

Now suppose I wanted to force a replication from DC3 to overwrite info on
DC2? I guess I get confused as to what determines which DC is
'upstream'...is it because a DC is in the default first site? So if you
create a CO, what determines which DC is upstream or which DC will take
precedence on replication conflicts/overwriting info on the other..by
USN/timestamp?

Hope I am explaining properly...


"Jorge de Almeida Pinto [MVP - DS]"
<SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx> wrote in message
news:uFQ92cDBHHA.3620@xxxxxxxxxxxxxxxxxxxxxxx
for NTFRSUTL to work make sure you use the correct upstream replication
partner for FRS....

OK, let me explain what I mean...

HUB site
DC1
DC2

BRANCH site
DC3

when going into sites and services (while targeting DC3) and looking for
COs beneath the NTDS Settings object, lets say you see a CO that use DC2
as the inbound replication partner for DC3.

for NTFRSUTL to work make sure you also use DC2 as the source DC and not
DC1

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Liam C" <Liam@xxxxxxxxxxxxxxxx> wrote in message
news:%23TwOVeCBHHA.4024@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,

Took me a while, but I've been able to figure out how to force a group
policy replication to remote branch office DC's using the ntfrsutl
utility.

The problem is that this works if I do it from one of our 2 servers at
headquarters (default first site), but there are times when I need to
make changes at a remote DC and I want changes to replicate back to
headquarters here. This seems to take quite a while--around the default
of 60 minutes which I have set through 'sites and services.' The ntfrs
utility has no effect going the other way...

Can anyone think of a reason why? DNS is fine, DCDIAG, etc..all looks
good. The whole USN thing and which version overrides the other is still
a mystery to me...Is there a hierarchical order of which DC would take
precedence for gpo version or is it simply by timestamp?

Thanks in Advance





.



Relevant Pages

  • Re: LDAP/AD Problems Related to WAN?
    ... the userenv.log file on either DC2 or DC3. ... However DC3 still has an event for FRS saying ... The File Replication Service is having trouble enabling replication from DC2 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Forcing Intersite Group Policy Replication AD 2003 (AGAIN)
    ... DC2 ... intra site replication is unscheduled and quick ... If you want to see which DC is used by DC3, ... BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx ...
    (microsoft.public.windows.server.active_directory)
  • Re: Should I Demote to Fix Replication?
    ... I guess I should have turned DC2 off first in order to ensure that DC3 ... replication, and then demote DC2. ... DC2 seems "happier" but it does not have all the latest accounts. ...
    (microsoft.public.win2000.active_directory)
  • Re: Forcing Intersite Group Policy Replication AD 2003
    ... intra site replication is unscheduled and quick ... BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx ... Now suppose I wanted to force a replication from DC3 to overwrite info on ... COs beneath the NTDS Settings object, lets say you see a CO that use DC2 ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication issue between domian controller server within same
    ... From DC2 to DC1 ... The replication generated an error: ... Warning: DC2 is the PDC Owner, but is not responding to LDAP Bind. ...
    (microsoft.public.windows.server.active_directory)