Script changes not replicating to a particiular DC

  • Thread starter Thread starter Spin
  • Start date Start date
S

Spin

We have 6 AD native-mode DCs. We have a loginscript in our environment
which runs for all users. When I update the script on one DC, it should
replicate the changes to all DCs, right? Well it does for 5 out of 6 of
them. I can't understand why it isn't replicating to the one. There are no
pasword synch problems in our domain, nothing in the eent log of the problem
one to indicate what the problem is. We make the changes to our scripts
inside the SYSVOL\<domain>\scripts folder, btw.

--
 
Spin said:
We have 6 AD native-mode DCs. We have a loginscript in our environment
Click to expand...

Domains are Native mode (not really the DCs) - you couldn't
be native mode unless ALL DCs were Win2000+ (i.e., you
have no NT BDCs.)
which runs for all users. When I update the script on one DC, it should
replicate the changes to all DCs, right? Well it does for 5 out of 6 of
them.
Click to expand...

It's almost always a DNS problem but any other IP issues can stop
the replication too of course.

Run DCDiag /fix on all the DCs.
Run DCDiag a second time and capture the output into a text file --
search the file for FAIL, WARN, IGNORE and fix remaining problems.

Probably the "sixth" DC is not set as a client of the Dynamic DNS
in it's own NIC\IP properties.
I can't understand why it isn't replicating to the one. There are no
pasword synch problems in our domain, nothing in the eent log of the problem
one to indicate what the problem is. We make the changes to our scripts
inside the SYSVOL\<domain>\scripts folder, btw.
Click to expand...

SysVol replication parallels AD replication.

Also make sure the "Sites and Services" Subnet are correct and the DC
is in the right site for it's IP address.
 
Back
Top