Urgent replication not seeming to work

From: troute_kilgore@xxxxxxxxx
Date: 17 Jan 2007 11:37:08 -0800

Group,
In our domain, we have two sites. Site 1 and Site 2 both have Win2k
SP4.
When a user changes a password in Site 1, that change is not replicated
until it is either forced, or during the normal replication period.

Same thing happens if password is changed on Site2 -> It does not
replicate between to site 1 until normal replication scheduled time.

Nothing in the event logs. Same thing happens with other requests
microsoft has defined as urgent, Account lock out, account disable...
etc.

Is there somewhere to force urgent changes to happen? I'm worried one
of the other admins may have changed something to cause urgent changes
not to replicate, but I don't know where they would have done it.

.

Follow-Ups:
- Re: Urgent replication not seeming to work
  - From: Paul Williams [MVP]

Prev by Date: Re: manual Schema extension
Next by Date: Moving DC's from <default-first-site>
Previous by thread: Re: Scripted LDAP Searches
Next by thread: Re: Urgent replication not seeming to work
Index(es):
- Date
- Thread

Relevant Pages

Re: Going Native and the Impact on the Network
... I'd say normal replication amongst domain controllers in the same domain is ... What I meant was Global Catalog replication and not GPO. ... "ptwilliams" wrote:>> Will this kick off a Schema change that inturn kicks off a total GPO ...
(microsoft.public.windows.server.active_directory)
Re: 2003 & R2 Schema Mismatch
... Before normal replication succeeds the schema partition must be in sync ...
(microsoft.public.windows.server.active_directory)