Policies Replication...

G

Guest

Hi, i have 3 servers, 2 in one site and the other. All are in the same
subdomains, but when i create or modify a policy does not replciate each
other. The replication ocurrs between the 60 minutes.
All AD replicate correctly, the users, etc.
Anyone have any idea ?

Thks
Diego
 
G

Guest

Thanks for answeing.
The problem is that never replicate, i have wait one month and it never
replicate.
Once in this domain was a server that was DC and when it dies it will never
run dcpromo to depromote, so i finded some articles to remove it from the dc
and today i found one more object in the AD\system\file replication service
of that server, so i have deleted. But i have to wait for the replicacion to
confirm it.
Anyone know other answer ?
Tks
 
C

Cary Shultz [A.D. MVP]

Okay,

So there was a Domain Controller that was removed 'ungracefully'! Then I
would suggest that you use ntdsutil to do a metadata Cleanup. Search this
news group in the last week or so as I have posted the Microsoft
Knowledgebase article that discusses how to do this.

That might be the first step....

Can you determine which of the remaining DCs ( in each Site ) is the BHS (
or Bridgehead Server ) for each specific Site? That would also be
important.

Hope that this gets you on your way!

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
 
G

Guest

Tks for the reply i will try it, i have this error too:
Tipo de suceso: Advertencia
Origen del suceso: NtFrs
Categoría del suceso: Ninguno
Id. del suceso: 13508
Fecha: 04/05/2005
Hora: 02:37:29 a.m.
Usuario: No disponible
Equipo: SLAN0005
Descripción:
The File Replication Service is having trouble enabling replication from
SLAN0001 to SLAN0005 for c:\winnt\sysvol\domain using the DNS name
slan0001.lanus.bpsam.la. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name slan0001.lanus.bpsam.la from
this computer.
[2] FRS is not running on slan0001.lanus.bpsam.la.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Datos:
0000: d5 04 00 00 Õ...
 
C

Cary Shultz [A.D. MVP]

Diego,

Yo entiendo. Trata de leer el siguente:

http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=NtFrs&phase=1

Tienes el Id. del suceso 13509 tambien?

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com



Diego said:
Tks for the reply i will try it, i have this error too:
Tipo de suceso: Advertencia
Origen del suceso: NtFrs
Categoría del suceso: Ninguno
Id. del suceso: 13508
Fecha: 04/05/2005
Hora: 02:37:29 a.m.
Usuario: No disponible
Equipo: SLAN0005
Descripción:
The File Replication Service is having trouble enabling replication from
SLAN0001 to SLAN0005 for c:\winnt\sysvol\domain using the DNS name
slan0001.lanus.bpsam.la. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name slan0001.lanus.bpsam.la
from
this computer.
[2] FRS is not running on slan0001.lanus.bpsam.la.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Datos:
0000: d5 04 00 00 Õ...


Cary Shultz said:
Okay,

So there was a Domain Controller that was removed 'ungracefully'! Then I
would suggest that you use ntdsutil to do a metadata Cleanup. Search
this
news group in the last week or so as I have posted the Microsoft
Knowledgebase article that discusses how to do this.

That might be the first step....

Can you determine which of the remaining DCs ( in each Site ) is the BHS
(
or Bridgehead Server ) for each specific Site? That would also be
important.

Hope that this gets you on your way!

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
 
G

Guest

Tambien tengo el EventID: 13568
http://support.microsoft.com/kb/308406/en-us
I found that i have to Enable Journal Wrap Automatic Restore.
But i dont understand if a have to make the registry to value = 1 and then
to 0 or always to 1 or 0.
Tks cary

"Cary Shultz [A.D. MVP]" escribió:
Diego,

Yo entiendo. Trata de leer el siguente:

http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=NtFrs&phase=1

Tienes el Id. del suceso 13509 tambien?

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com



Diego said:
Tks for the reply i will try it, i have this error too:
Tipo de suceso: Advertencia
Origen del suceso: NtFrs
Categoría del suceso: Ninguno
Id. del suceso: 13508
Fecha: 04/05/2005
Hora: 02:37:29 a.m.
Usuario: No disponible
Equipo: SLAN0005
Descripción:
The File Replication Service is having trouble enabling replication from
SLAN0001 to SLAN0005 for c:\winnt\sysvol\domain using the DNS name
slan0001.lanus.bpsam.la. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name slan0001.lanus.bpsam.la
from
this computer.
[2] FRS is not running on slan0001.lanus.bpsam.la.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
Datos:
0000: d5 04 00 00 Õ...


Cary Shultz said:
Okay,

So there was a Domain Controller that was removed 'ungracefully'! Then I
would suggest that you use ntdsutil to do a metadata Cleanup. Search
this
news group in the last week or so as I have posted the Microsoft
Knowledgebase article that discusses how to do this.

That might be the first step....

Can you determine which of the remaining DCs ( in each Site ) is the BHS
(
or Bridgehead Server ) for each specific Site? That would also be
important.

Hope that this gets you on your way!

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com



Thanks for answeing.
The problem is that never replicate, i have wait one month and it never
replicate.
Once in this domain was a server that was DC and when it dies it will
never
run dcpromo to depromote, so i finded some articles to remove it from
the
dc
and today i found one more object in the AD\system\file replication
service
of that server, so i have deleted. But i have to wait for the
replicacion
to
confirm it.
Anyone know other answer ?
Tks

:

Diego,

This sounds normal! Well, assuming that someone changed the Intersite
Replication to happen every hour! There are two types of replication:
intrasite replication and intersite replication. By default, the
former
happens every 15 minutes and the later every 180 minutes.

--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com



Hi, i have 3 servers, 2 in one site and the other. All are in the
same
subdomains, but when i create or modify a policy does not replciate
each
other. The replication ocurrs between the 60 minutes.
All AD replicate correctly, the users, etc.
Anyone have any idea ?

Thks
Diego
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top