Re: Forcing Intersite Group Policy Replication AD 2003
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Mon, 13 Nov 2006 21:56:28 +0100
glad to help!
--
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:unnazpyBHHA.4844@xxxxxxxxxxxxxxxxxxxxxxx
Thanks very much Jorge!
This puts things in persepctive.
"Jorge de Almeida Pinto [MVP - DS]"
<SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx> wrote in message
news:%23C5BZCQBHHA.2140@xxxxxxxxxxxxxxxxxxxxxxx
the same applies... look who replicates from DC3. It can be either DC1 or
DC2
so lets say the replication looks like
DC1<------>DC2 (intra-site)
DC3<-------DC2 (inter-site)
DC3-------->DC1 (inter-site)
intra site replication is unscheduled and quick
inter site replication is scheduled and to replicate outside the
schedules you need to force it using NTFRSUTL
in the case above the command line would look like:
DC3<-------DC2 (inter-site) (DC3 is receiving/destination and DC2 is
sending/source)
a best practice is that SYSVOL updates should only be done on the DC with
the PDC FSMO
--
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:erCjl3OBHHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- Forcing Intersite Group Policy Replication AD 2003
- From: Liam C
- Re: Forcing Intersite Group Policy Replication AD 2003
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: Forcing Intersite Group Policy Replication AD 2003
- From: Liam C
- Re: Forcing Intersite Group Policy Replication AD 2003
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: Forcing Intersite Group Policy Replication AD 2003
- From: Liam C
- Forcing Intersite Group Policy Replication AD 2003
- Prev by Date: Re: Permissions problem
- Next by Date: Re: ADAM replica problems
- Previous by thread: Re: Forcing Intersite Group Policy Replication AD 2003
- Next by thread: Re: PeopleSoft - Integration
- Index(es):
Relevant Pages
|
